Antw: Re: [EXT] [systemd‑devel] no log information about why machine is sleeping

["Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>]

>>> George Avrunin <avrunin@xxxxxxxxxxxxxx> schrieb am 12.08.2021 um 14:10 in
Nachricht <20210812081008.4ca3ce4c@g.localdomain>:
> On Thu, 12 Aug 2021 09:24:25 +0200, Ulrich Windl wrote:
> 
>> > However, I haven't been able to figure out why the machine puts itself
>> > to sleep when it can't reach the switch.  I asked about this on the
>> > Fedora  
>> 
>> I don't know, but caring about the earch climate my PC goes to STR
>> (suspend to RAM) when there is no activity for a longer time.
>> Maybe your PC uses a similar setting, and being constantly attacked
>> keeps it busy, so when there is no switch connection your PC becomes
>> actually idle ;‑)
> 
> I suppose that's possible, though I haven't been able to find anywhere
> that's configured.  (I'll ask again on the Fedora list to be sure.)  In
> the places where I know I've manually configured it (e.g., in the KDE
> power settings), it's not supposed to sleep at all when it's on AC power. 

Amazingly in my Leap 15 system it's GNOME that triggers it: If I'm not logged
in, no suspend happens, but when I have a GNOME session suspend happens.

> 
>> 
>> > users list (and included the log entries shown below), and Chris Murphy
>> > noted that systemd doesn't normally insert the sleep request in the
>> > log, so it's not possible to determine what caused the sleep request.
>> > He suggested that I start a thread here to ask if at least a single
>> > line of information about how the sleep is being initiated could be
>> > dumped into the log by default.    
>> 
>> Mine logs a lot when suspending or resuming, bu tOI dn't run Fedora
>> (Leap 15.3 instead).
> 
>   George