Package: systemd
Version: 238-2
Followup-For: Bug #807041
Actuall, having said that, I have found
https://github.com/systemd/systemd/issues/786 and my new laptop does
have Nvidia with closed source driver so this would explain it.
Will dig up my old laptop and test again with that...
George
Am 08.12.2015 um 00:30 schrieb George B.:
> On 04/12/15 14:39, Michael Biebl wrote:
>>
>> Can you attach the output of (as root)
>> journalctl -u systemd-logind
>>
>> and mark the time when the auto-suspend happens.
>
> ```
> -- Logs begin at Mon 2015-12-07 14:25:13 GMT, end at Mon 2015-12-07
>
On 08/12/15 14:52, Michael Biebl wrote:
Have you set IdleAction= and IdleActionSec= in /etc/systemd/logind.conf?
If not, this looks like the suspend request is triggered externally and
logind simply executes the action.
No, my logind.conf is the Debian default with all the options commented
On 04/12/15 14:39, Michael Biebl wrote:
Can you attach the output of (as root)
journalctl -u systemd-logind
and mark the time when the auto-suspend happens.
```
-- Logs begin at Mon 2015-12-07 14:25:13 GMT, end at Mon 2015-12-07 23:26:59
GMT. --
Dec 07 14:25:15 deli systemd[1]: Starting
On Friday, 4 December 2015, Michael Biebl wrote:
>
>
> Do you use a graphical desktop environment, if so which one?
I use the Awesome WM, started from console - I don't think that counts as a
DE?
> Can you attach the output of (as root)
> journalctl -u systemd-logind
>
> and
Am 04.12.2015 um 13:44 schrieb George B.:
> Package: systemd
> Version: 228-2
> Severity: important
>
> Hello,
>
> As of a few weeks ago (after an update) my laptop started auto-suspending
> after a period
> of inactivity. I assume this is logind related because I couldn't find
> anything else