[SOLVED] Systemd-logind triggers idle action when laptop is active

prosoitos · 2018-12-21 01:27:54

Since yesterday's updates, my laptop goes to sleep seemingly randomly, while it is being used (sometimes even while I am typing).

I have this in my .xinitrc file and I have not changed anything related to sleep options lately:

xset dpms 0 0 300

/etc/systemd/logind.conf does not have weird settings. I have laptop-mode-tools, but there again, no weird settings.

In the output of `dmesg`, I have a bunch of ACPI warnings which might be related (?):

[    0.092101] ACPI: NMI not connected to LINT 1!
[    2.530882] ACPI: AC Adapter [AC] (off-line)
[    2.536581] ACPI Warning: \_SB.IETM._ART: Return Package type mismatch at index 0 - found Integer, expected Reference (20180810/nspredef-263)
[    2.536592] ACPI: Invalid package element [0]: got number, expecting [R]
[ 1835.673625] acpi PNP0401:00: Already enumerated
[ 1835.693012] acpi PNP0501:00: Still not present
[ 1834.379310] ACPI: button: The lid device is not compliant to SW_LID.

I have other warnings, though they don't seem to me to be relevant (but I am a noob). I would be happy to post the full log if that may be useful.

By running `sudo journalctl -b`, I also got:

ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored

I am on a DELL Latitude E7450, in case that might be at all relevant.

Thank you for advice/suggestions. Also let me know what other information could be useful here.

Last edited by prosoitos (2019-02-06 02:09:25)

prosoitos · 2018-12-22 23:25:40

I am not having any luck in my search for solution.

These random and quite frequent sleep events are very disruptive (external drives get improperly unmounted and any work with them is impossible, I get interrupted in the middle of work, etc.).

If anyone has any thought, I would sincerely appreciate. Also happy to provide more information if needed.

Thank you very much!

jasonwryan · 2018-12-22 23:30:12

Remove LMT from the equation and see if it continues to recur.

prosoitos · 2018-12-24 04:35:11

OK. I will try and report here. Thank you for the suggestion. Reading the Arch wiki on power management, I noticed the sentence "Only run one of these tools to avoid possible conflicts" and I was worried about the fact that I am running more than one... (acpid and LMT). So I was debating to do exactly that actually.

Of note, I ran LMT and acpid together for a year without issue. And restoring all packages to just before this issue started solved the problem. But of course, that is not a long term solution.

prosoitos · 2018-12-24 05:16:21

Removing LMT does not solve the problem...

So I am restoring all packages again to just before the issue started. One of the updates triggered this, but I have no idea which.

I guess one way to trouble-shoot may be to update packages one at a time??? I have only ever updated Arch with "pacman -Syu", but maybe to pinpoint the problem it is ok to update things one by one?

Last edited by prosoitos (2018-12-24 05:21:40)

jasonwryan · 2018-12-24 05:21:47

What is in the journal immediately before it sleeps?

prosoitos · 2018-12-24 05:49:34

Are you talking of the systemd journal reached by "journalctl"? (sorry, noob here...).

If so, I don't see anything just before an event: last sleep was at 21:45 and the last entry given by journalctl is at 21:18...

jasonwryan · 2018-12-24 05:56:41

Yes. You need to try and narrow down what is triggering the sleep.

prosoitos · 2018-12-24 06:00:26

I restored all packages to their current version and I will look at the journal after each sleep event. But so far, whatever is happening doesn't seem to create any entry in it.

Would you have any other suggestion on how I could narrow the problem down?

Thank you for your time.

jasonwryan · 2018-12-24 06:14:44

Create a new user and determine if it is related to anything specific to your environment or is system-wide.

prosoitos · 2019-01-25 19:11:47

I am still battling with this issue.

- I disabled acpid (didn't seem to have any negative effect on my ACPI events actually, at least that I could tell): didn't help
- I updated my BIOS: didn't help
- I had to change laptop for unrelated reasons and setup Arch Linux in a very similar way on a similar machine and the problem is exactly the same on the new machine

Here is my dmesg:

[    7.263205] 8021q: 802.1Q VLAN Support v1.8
[    8.139906] kauditd_printk_skb: 21 callbacks suppressed
[    8.139911] audit: type=1131 audit(1548399181.916:32): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    9.076126] audit: type=1006 audit(1548399182.850:33): pid=445 uid=0 old-auid=4294967295 auid=1000 tty=tty1 old-ses=4294967295 ses=1 res=1
[    9.092966] audit: type=1130 audit(1548399182.866:34): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    9.098180] audit: type=1006 audit(1548399182.873:35): pid=576 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=2 res=1
[    9.156252] audit: type=1130 audit(1548399182.930:36): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   13.185121] audit: type=1130 audit(1548399186.960:37): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rtkit-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   13.474773] Bluetooth: RFCOMM TTY layer initialized
[   13.474778] Bluetooth: RFCOMM socket layer initialized
[   13.474781] Bluetooth: RFCOMM ver 1.11
[   33.672488] audit: type=1131 audit(1548399207.447:38): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   95.746673] logitech-hidpp-device 0003:046D:1025.0004: HID++ 1.0 device connected.
[  297.423149] audit: type=1130 audit(1548399471.609:39): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=upower comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  541.121519] PM: suspend entry (deep)
[  541.121521] PM: Syncing filesystems ... done.
[  541.131953] Freezing user space processes ... (elapsed 0.001 seconds) done.
[  541.133042] OOM killer disabled.
[  541.133043] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[  541.134166] printk: Suspending console(s) (use no_console_suspend to debug)
[  541.134403] wlp2s0: deauthenticating from 10:9f:a9:5d:60:88 by local choice (Reason: 3=DEAUTH_LEAVING)
[  541.152840] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[  541.152885] e1000e: EEE TX LPI TIMER: 00000011
[  541.160476] sd 1:0:0:0: [sda] Stopping disk
[  541.459575] ACPI: EC: interrupt blocked
[  541.526751] ACPI: Preparing to enter system sleep state S3
[  541.530808] ACPI: EC: event blocked
[  541.530809] ACPI: EC: EC stopped
[  541.530810] PM: Saving platform NVS memory
[  541.530848] Disabling non-boot CPUs ...
[  541.557758] smpboot: CPU 1 is now offline
[  541.585661] smpboot: CPU 2 is now offline
[  541.637813] smpboot: CPU 3 is now offline
[  541.641548] ACPI: Low-level resume complete
[  541.641599] ACPI: EC: EC started
[  541.641599] PM: Restoring platform NVS memory
[  541.641911] Enabling non-boot CPUs ...
[  541.641963] x86: Booting SMP configuration:
[  541.641964] smpboot: Booting Node 0 Processor 1 APIC 0x2
[  541.642575]  cache: parent cpu1 should not be sleeping
[  541.642733] CPU1 is up
[  541.642752] smpboot: Booting Node 0 Processor 2 APIC 0x1
[  541.643218]  cache: parent cpu2 should not be sleeping
[  541.643454] CPU2 is up
[  541.643473] smpboot: Booting Node 0 Processor 3 APIC 0x3
[  541.643990]  cache: parent cpu3 should not be sleeping
[  541.644349] CPU3 is up
[  541.655843] ACPI: Waking up from system sleep state S3
[  541.711060] ACPI: EC: interrupt unblocked
[  541.919234] ACPI: EC: event unblocked
[  541.932548] sd 1:0:0:0: [sda] Starting disk
[  542.162441] usb 2-2: reset full-speed USB device number 2 using xhci_hcd
[  542.168707] usb 1-1.6: reset high-speed USB device number 4 using ehci-pci
[  542.246447] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  542.246479] ata1: SATA link down (SStatus 0 SControl 300)
[  542.248019] ata2.00: configured for UDMA/133
[  542.342114] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
[  542.678547] OOM killer enabled.
[  542.678548] Restarting tasks ... done.
[  542.694866] Bluetooth: hci0: read Intel version: 370810011003110e00
[  542.694871] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[  542.703993] audit: type=1130 audit(1548399736.060:40): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  542.712268] pci_bus 0000:01: Allocating resources
[  542.714051] pcieport 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 01] add_size 1000
[  542.714054] pcieport 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 01] add_size 200000 add_align 100000
[  542.714061] pci_bus 0000:02: Allocating resources
[  542.714216] pcieport 0000:00:1c.3: bridge window [io  0x1000-0x0fff] to [bus 02] add_size 1000
[  542.714219] pcieport 0000:00:1c.3: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000 add_align 100000
[  542.714226] pci_bus 0000:03: Allocating resources
[  542.714233] pcieport 0000:00:1c.4: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
[  542.714234] pcieport 0000:00:1c.4: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
[  542.714236] pcieport 0000:00:1c.4: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
[  542.714249] pcieport 0000:00:1c.0: BAR 15: assigned [mem 0xdf800000-0xdf9fffff 64bit pref]
[  542.714255] pcieport 0000:00:1c.3: BAR 15: assigned [mem 0xdfa00000-0xdfbfffff 64bit pref]
[  542.714257] pcieport 0000:00:1c.4: BAR 14: assigned [mem 0xdfc00000-0xdfdfffff]
[  542.714263] pcieport 0000:00:1c.4: BAR 15: assigned [mem 0xdfe00000-0xdfffffff 64bit pref]
[  542.714266] pcieport 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
[  542.714267] pcieport 0000:00:1c.3: BAR 13: assigned [io  0x3000-0x3fff]
[  542.714269] pcieport 0000:00:1c.4: BAR 13: assigned [io  0x4000-0x4fff]
[  542.714476] pci_bus 0000:01: Allocating resources
[  542.718398] pci_bus 0000:02: Allocating resources
[  542.718566] pci_bus 0000:03: Allocating resources
[  542.759062] pci_bus 0000:01: Allocating resources
[  542.760925] pci_bus 0000:02: Allocating resources
[  542.761143] pci_bus 0000:03: Allocating resources
[  542.803634] acpi PNP0401:00: Already enumerated
[  542.807168] acpi PNP0501:00: Still not present
[  542.807963] PM: suspend exit
[  542.810602] audit: type=1130 audit(1548399736.166:41): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  542.810616] audit: type=1131 audit(1548399736.166:42): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  543.022003] Bluetooth: hci0: Intel firmware patch completed and activated
[  546.077210] wlp2s0: authenticate with 10:9f:a9:5d:60:88
[  546.082049] wlp2s0: send auth to 10:9f:a9:5d:60:88 (try 1/3)
[  546.085872] wlp2s0: authenticated
[  546.088638] wlp2s0: associate with 10:9f:a9:5d:60:88 (try 1/3)
[  546.092779] wlp2s0: RX AssocResp from 10:9f:a9:5d:60:88 (capab=0x411 status=0 aid=3)
[  546.096185] wlp2s0: associated
[  547.711211] audit: type=1131 audit(1548399741.066:43): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  916.844900] audit: type=1130 audit(1548400110.207:44): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  916.844904] audit: type=1131 audit(1548400110.207:45): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1816.830290] PM: suspend entry (deep)
[ 1816.830292] PM: Syncing filesystems ... done.
[ 1816.841409] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 1816.842860] OOM killer disabled.
[ 1816.842861] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 1816.843958] printk: Suspending console(s) (use no_console_suspend to debug)
[ 1816.844244] wlp2s0: deauthenticating from 10:9f:a9:5d:60:88 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1816.866949] e1000e: EEE TX LPI TIMER: 00000011
[ 1816.867525] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 1816.875396] sd 1:0:0:0: [sda] Stopping disk
[ 1816.967803] ACPI: EC: interrupt blocked
[ 1817.020853] ACPI: Preparing to enter system sleep state S3
[ 1817.024441] ACPI: EC: event blocked
[ 1817.024442] ACPI: EC: EC stopped
[ 1817.024443] PM: Saving platform NVS memory
[ 1817.024478] Disabling non-boot CPUs ...
[ 1817.048619] smpboot: CPU 1 is now offline
[ 1817.089863] smpboot: CPU 2 is now offline
[ 1817.142007] smpboot: CPU 3 is now offline
[ 1817.144970] ACPI: Low-level resume complete
[ 1817.145020] ACPI: EC: EC started
[ 1817.145021] PM: Restoring platform NVS memory
[ 1817.145338] Enabling non-boot CPUs ...
[ 1817.145370] x86: Booting SMP configuration:
[ 1817.145371] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 1817.145979]  cache: parent cpu1 should not be sleeping
[ 1817.146137] CPU1 is up
[ 1817.146180] smpboot: Booting Node 0 Processor 2 APIC 0x1
[ 1817.146646]  cache: parent cpu2 should not be sleeping
[ 1817.146879] CPU2 is up
[ 1817.146898] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 1817.147312]  cache: parent cpu3 should not be sleeping
[ 1817.147450] CPU3 is up
[ 1817.150843] ACPI: Waking up from system sleep state S3
[ 1817.206952] ACPI: EC: interrupt unblocked
[ 1817.370742] ACPI: EC: event unblocked
[ 1817.381174] sd 1:0:0:0: [sda] Starting disk
[ 1817.384223] ACPI: button: The lid device is not compliant to SW_LID.
[ 1817.616422] usb 2-2: reset full-speed USB device number 2 using xhci_hcd
[ 1817.622907] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
[ 1817.693553] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1817.693585] ata1: SATA link down (SStatus 0 SControl 300)
[ 1817.695280] ata2.00: configured for UDMA/133
[ 1817.792974] usb 1-1.6: reset high-speed USB device number 4 using ehci-pci
[ 1817.951081] OOM killer enabled.
[ 1817.951082] Restarting tasks ... 
[ 1817.953658] pci_bus 0000:01: Allocating resources
[ 1817.958267] pci_bus 0000:02: Allocating resources
[ 1817.958312] done.
[ 1817.958429] pci_bus 0000:03: Allocating resources
[ 1817.975905] audit: type=1130 audit(1548401088.826:46): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1817.981162] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 1817.981208] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 1817.999824] pci_bus 0000:01: Allocating resources
[ 1818.001628] pci_bus 0000:02: Allocating resources
[ 1818.001839] pci_bus 0000:03: Allocating resources
[ 1818.024797] pci_bus 0000:01: Allocating resources
[ 1818.026600] pci_bus 0000:02: Allocating resources
[ 1818.026778] pci_bus 0000:03: Allocating resources
[ 1818.087993] acpi PNP0401:00: Already enumerated
[ 1818.112524] acpi PNP0501:00: Still not present
[ 1818.181575] PM: suspend exit
[ 1818.184130] audit: type=1130 audit(1548401089.036:47): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1818.185249] audit: type=1131 audit(1548401089.036:48): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1818.308259] Bluetooth: hci0: Intel firmware patch completed and activated
[ 1821.484137] wlp2s0: authenticate with 10:9f:a9:5d:60:88
[ 1821.488491] wlp2s0: send auth to 10:9f:a9:5d:60:88 (try 1/3)
[ 1821.492544] wlp2s0: authenticated
[ 1821.496196] wlp2s0: associate with 10:9f:a9:5d:60:88 (try 1/3)
[ 1821.514489] wlp2s0: RX AssocResp from 10:9f:a9:5d:60:88 (capab=0x411 status=0 aid=1)
[ 1821.518613] wlp2s0: associated
[ 1822.975590] audit: type=1131 audit(1548401093.826:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 3646.804147] PM: suspend entry (deep)
[ 3646.804148] PM: Syncing filesystems ... done.
[ 3646.818869] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 3646.820278] OOM killer disabled.
[ 3646.820279] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 3646.821482] printk: Suspending console(s) (use no_console_suspend to debug)
[ 3646.821871] wlp2s0: deauthenticating from 10:9f:a9:5d:60:88 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 3646.837613] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 3646.845235] sd 1:0:0:0: [sda] Stopping disk
[ 3646.845277] e1000e: EEE TX LPI TIMER: 00000011
[ 3647.895522] ACPI: EC: interrupt blocked
[ 3647.947856] ACPI: Preparing to enter system sleep state S3
[ 3647.952243] ACPI: EC: event blocked
[ 3647.952244] ACPI: EC: EC stopped
[ 3647.952245] PM: Saving platform NVS memory
[ 3647.952285] Disabling non-boot CPUs ...
[ 3647.983083] smpboot: CPU 1 is now offline
[ 3648.036862] smpboot: CPU 2 is now offline
[ 3648.062229] smpboot: CPU 3 is now offline
[ 3648.065463] ACPI: Low-level resume complete
[ 3648.065514] ACPI: EC: EC started
[ 3648.065515] PM: Restoring platform NVS memory
[ 3648.065833] Enabling non-boot CPUs ...
[ 3648.065866] x86: Booting SMP configuration:
[ 3648.065868] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 3648.066482]  cache: parent cpu1 should not be sleeping
[ 3648.066640] CPU1 is up
[ 3648.066661] smpboot: Booting Node 0 Processor 2 APIC 0x1
[ 3648.067134]  cache: parent cpu2 should not be sleeping
[ 3648.067367] CPU2 is up
[ 3648.067385] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 3648.067902]  cache: parent cpu3 should not be sleeping
[ 3648.068249] CPU3 is up
[ 3648.079600] ACPI: Waking up from system sleep state S3
[ 3648.135565] ACPI: EC: interrupt unblocked
[ 3648.314027] ACPI: EC: event unblocked
[ 3648.314053] usb usb2: root hub lost power or was reset
[ 3648.314055] usb usb3: root hub lost power or was reset
[ 3648.324423] sd 1:0:0:0: [sda] Starting disk
[ 3648.573130] usb 1-1: reset high-speed USB device number 2 using ehci-pci
[ 3648.637149] ata1: SATA link down (SStatus 0 SControl 300)
[ 3648.637193] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 3648.638886] ata2.00: configured for UDMA/133
[ 3648.676608] usb 2-2: reset full-speed USB device number 2 using xhci_hcd
[ 3649.006503] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
[ 3649.176528] usb 1-1.6: reset high-speed USB device number 4 using ehci-pci
[ 3649.346489] usb 1-1.7: reset full-speed USB device number 5 using ehci-pci
[ 3649.456754] OOM killer enabled.
[ 3649.456756] Restarting tasks ... done.
[ 3649.486862] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 3649.486867] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 3649.492315] pci_bus 0000:01: Allocating resources
[ 3649.494200] pci_bus 0000:02: Allocating resources
[ 3649.494523] pci_bus 0000:03: Allocating resources
[ 3649.494921] pci_bus 0000:01: Allocating resources
[ 3649.496749] pci_bus 0000:02: Allocating resources
[ 3649.497239] pci_bus 0000:03: Allocating resources
[ 3649.503703] pci_bus 0000:01: Allocating resources
[ 3649.505493] pci_bus 0000:02: Allocating resources
[ 3649.505719] pci_bus 0000:03: Allocating resources
[ 3649.506738] audit: type=1130 audit(1548402922.440:50): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 3649.521350] acpi PNP0401:00: Already enumerated
[ 3649.523574] acpi PNP0501:00: Still not present
[ 3649.524102] PM: suspend exit
[ 3649.526104] audit: type=1130 audit(1548402922.456:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 3649.526117] audit: type=1131 audit(1548402922.456:52): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 3649.814073] Bluetooth: hci0: Intel firmware patch completed and activated
[ 3652.986433] wlp2s0: authenticate with 10:9f:a9:5d:60:88
[ 3652.991030] wlp2s0: send auth to 10:9f:a9:5d:60:88 (try 1/3)
[ 3652.995273] wlp2s0: authenticated
[ 3652.996340] wlp2s0: associate with 10:9f:a9:5d:60:88 (try 1/3)
[ 3653.000357] wlp2s0: RX AssocResp from 10:9f:a9:5d:60:88 (capab=0x411 status=0 aid=1)
[ 3653.004364] wlp2s0: associated
[ 3654.501892] audit: type=1131 audit(1548402927.433:53): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

I can see the cycles of sleep state S3 but I don't understand what triggers them.

Here is a dmesg from the old machine showing a lot of those unwanted sleep events:

[ 1826.515578] ACPI: Waking up from system sleep state S3
[ 1826.565621] ACPI: EC: interrupt unblocked
[ 1826.771602] ACPI: EC: event unblocked
[ 1826.772068] sd 1:0:0:0: [sda] Starting disk
[ 1826.787026] ACPI: button: The lid device is not compliant to SW_LID.
[ 1827.011030] usb 2-2: reset full-speed USB device number 2 using xhci_hcd
[ 1827.030645] usb 1-1.6: reset high-speed USB device number 4 using ehci-pci
[ 1827.084636] ata1: SATA link down (SStatus 0 SControl 300)
[ 1827.084670] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1827.087330] ata2.00: configured for UDMA/133
[ 1827.200784] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
[ 1827.349120] OOM killer enabled.
[ 1827.349121] Restarting tasks ... 
[ 1827.364072] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 1827.365416] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 1827.368596] done.
[ 1827.380830] pci_bus 0000:01: Allocating resources
[ 1827.382616] pcieport 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 01] add_size 1000
[ 1827.382620] pcieport 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 01] add_size 200000 add_align 100000
[ 1827.382628] pci_bus 0000:02: Allocating resources
[ 1827.382779] pcieport 0000:00:1c.3: bridge window [io  0x1000-0x0fff] to [bus 02] add_size 1000
[ 1827.382783] pcieport 0000:00:1c.3: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000 add_align 100000
[ 1827.382790] pci_bus 0000:03: Allocating resources
[ 1827.382799] pcieport 0000:00:1c.4: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
[ 1827.382802] pcieport 0000:00:1c.4: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
[ 1827.382805] pcieport 0000:00:1c.4: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
[ 1827.382821] pcieport 0000:00:1c.0: BAR 15: assigned [mem 0xdf800000-0xdf9fffff 64bit pref]
[ 1827.382826] pcieport 0000:00:1c.3: BAR 15: assigned [mem 0xdfa00000-0xdfbfffff 64bit pref]
[ 1827.382829] pcieport 0000:00:1c.4: BAR 14: assigned [mem 0xdfc00000-0xdfdfffff]
[ 1827.382833] pcieport 0000:00:1c.4: BAR 15: assigned [mem 0xdfe00000-0xdfffffff 64bit pref]
[ 1827.382837] pcieport 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
[ 1827.382840] pcieport 0000:00:1c.3: BAR 13: assigned [io  0x3000-0x3fff]
[ 1827.382842] pcieport 0000:00:1c.4: BAR 13: assigned [io  0x4000-0x4fff]
[ 1827.383210] pci_bus 0000:01: Allocating resources
[ 1827.390015] pci_bus 0000:02: Allocating resources
[ 1827.390231] pci_bus 0000:03: Allocating resources
[ 1827.399989] audit: type=1130 audit(1546578086.896:48): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1827.420673] pci_bus 0000:01: Allocating resources
[ 1827.422620] pci_bus 0000:02: Allocating resources
[ 1827.422788] pci_bus 0000:03: Allocating resources
[ 1827.502717] acpi PNP0401:00: Already enumerated
[ 1827.516990] acpi PNP0501:00: Still not present
[ 1827.569975] PM: suspend exit
[ 1827.574092] audit: type=1130 audit(1546578087.073:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1827.574098] audit: type=1131 audit(1546578087.073:50): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1827.691254] Bluetooth: hci0: Intel firmware patch completed and activated
[ 1830.944997] wlp2s0: authenticate with 10:9f:a9:5d:60:88
[ 1830.949718] wlp2s0: send auth to 10:9f:a9:5d:60:88 (try 1/3)
[ 1830.952875] wlp2s0: authenticated
[ 1830.954107] wlp2s0: associate with 10:9f:a9:5d:60:88 (try 1/3)
[ 1830.959459] wlp2s0: RX AssocResp from 10:9f:a9:5d:60:88 (capab=0x411 status=0 aid=1)
[ 1830.962127] wlp2s0: associated
[ 1832.398353] audit: type=1131 audit(1546578091.896:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 3606.491353] audit: type=1006 audit(1546579866.905:52): pid=2439 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=4 res=1
[ 3635.597553] PM: suspend entry (deep)
[ 3635.597555] PM: Syncing filesystems ... done.
[ 3635.646490] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 3635.648528] OOM killer disabled.
[ 3635.648529] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 3635.649866] printk: Suspending console(s) (use no_console_suspend to debug)
[ 3635.650289] wlp2s0: deauthenticating from 10:9f:a9:5d:60:88 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 3635.665270] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 3635.670364] sd 1:0:0:0: [sda] Stopping disk
[ 3635.670566] e1000e: EEE TX LPI TIMER: 00000011
[ 3636.310221] ACPI: EC: interrupt blocked
[ 3636.382258] ACPI: Preparing to enter system sleep state S3
[ 3636.387764] ACPI: EC: event blocked
[ 3636.387765] ACPI: EC: EC stopped
[ 3636.387766] PM: Saving platform NVS memory
[ 3636.387847] Disabling non-boot CPUs ...
[ 3636.403258] smpboot: CPU 1 is now offline
[ 3636.457628] smpboot: CPU 2 is now offline
[ 3636.510040] smpboot: CPU 3 is now offline
[ 3636.513016] ACPI: Low-level resume complete
[ 3636.513069] ACPI: EC: EC started
[ 3636.513070] PM: Restoring platform NVS memory
[ 3636.515498] Enabling non-boot CPUs ...
[ 3636.515537] x86: Booting SMP configuration:
[ 3636.515538] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 3636.517328]  cache: parent cpu1 should not be sleeping
[ 3636.517512] CPU1 is up
[ 3636.517535] smpboot: Booting Node 0 Processor 2 APIC 0x1
[ 3636.518067]  cache: parent cpu2 should not be sleeping
[ 3636.518333] CPU2 is up
[ 3636.518354] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 3636.518853]  cache: parent cpu3 should not be sleeping
[ 3636.519007] CPU3 is up
[ 3636.522314] ACPI: Waking up from system sleep state S3
[ 3636.570832] ACPI: EC: interrupt unblocked
[ 3636.768323] ACPI: EC: event unblocked
[ 3636.778619] sd 1:0:0:0: [sda] Starting disk
[ 3637.011043] usb 2-2: reset full-speed USB device number 2 using xhci_hcd
[ 3637.020689] usb 1-1.6: reset high-speed USB device number 4 using ehci-pci
[ 3637.091454] ata1: SATA link down (SStatus 0 SControl 300)
[ 3637.091489] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 3637.094678] ata2.00: configured for UDMA/133
[ 3637.194053] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
[ 3637.311836] OOM killer enabled.
[ 3637.311838] Restarting tasks ... done.
[ 3637.328542] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 3637.328548] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 3637.344441] pci_bus 0000:01: Allocating resources
[ 3637.346232] pci_bus 0000:02: Allocating resources
[ 3637.346449] pci_bus 0000:03: Allocating resources
[ 3637.346878] pci_bus 0000:01: Allocating resources
[ 3637.348681] pci_bus 0000:02: Allocating resources
[ 3637.348841] pci_bus 0000:03: Allocating resources
[ 3637.361756] audit: type=1130 audit(1546579900.846:53): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 3637.365314] pci_bus 0000:01: Allocating resources
[ 3637.369135] pci_bus 0000:02: Allocating resources
[ 3637.369458] pci_bus 0000:03: Allocating resources
[ 3637.457317] acpi PNP0401:00: Already enumerated
[ 3637.473841] acpi PNP0501:00: Still not present
[ 3637.531602] PM: suspend exit
[ 3637.534039] audit: type=1130 audit(1546579901.019:54): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 3637.534064] audit: type=1131 audit(1546579901.019:55): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 3637.657739] Bluetooth: hci0: Intel firmware patch completed and activated
[ 3640.951048] wlp2s0: authenticate with 10:9f:a9:5d:60:88
[ 3640.955947] wlp2s0: send auth to 10:9f:a9:5d:60:88 (try 1/3)
[ 3640.959032] wlp2s0: authenticated
[ 3640.960818] wlp2s0: associate with 10:9f:a9:5d:60:88 (try 1/3)
[ 3640.964522] wlp2s0: RX AssocResp from 10:9f:a9:5d:60:88 (capab=0x411 status=0 aid=1)
[ 3640.966240] wlp2s0: associated
[ 3642.366238] audit: type=1131 audit(1546579905.849:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 5401.317450] audit: type=1006 audit(1546581665.048:57): pid=2932 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=5 res=1
[ 5465.586845] PM: suspend entry (deep)
[ 5465.586846] PM: Syncing filesystems ... done.
[ 5465.613164] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 5465.614819] OOM killer disabled.
[ 5465.614820] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 5465.616085] printk: Suspending console(s) (use no_console_suspend to debug)
[ 5465.616389] wlp2s0: deauthenticating from 10:9f:a9:5d:60:88 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 5465.629583] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 5465.632696] sd 1:0:0:0: [sda] Stopping disk
[ 5465.635495] e1000e: EEE TX LPI TIMER: 00000011
[ 5466.174418] ACPI: EC: interrupt blocked
[ 5466.219961] ACPI: Preparing to enter system sleep state S3
[ 5466.224529] ACPI: EC: event blocked
[ 5466.224531] ACPI: EC: EC stopped
[ 5466.224532] PM: Saving platform NVS memory
[ 5466.224616] Disabling non-boot CPUs ...
[ 5466.255100] smpboot: CPU 1 is now offline
[ 5466.295449] smpboot: CPU 2 is now offline
[ 5466.334369] smpboot: CPU 3 is now offline
[ 5466.337389] ACPI: Low-level resume complete
[ 5466.337443] ACPI: EC: EC started
[ 5466.337443] PM: Restoring platform NVS memory
[ 5466.339859] Enabling non-boot CPUs ...
[ 5466.339899] x86: Booting SMP configuration:
[ 5466.339900] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 5466.341695]  cache: parent cpu1 should not be sleeping
[ 5466.341877] CPU1 is up
[ 5466.341901] smpboot: Booting Node 0 Processor 2 APIC 0x1
[ 5466.342431]  cache: parent cpu2 should not be sleeping
[ 5466.342698] CPU2 is up
[ 5466.342718] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 5466.343217]  cache: parent cpu3 should not be sleeping
[ 5466.343596] CPU3 is up
[ 5466.353133] ACPI: Waking up from system sleep state S3
[ 5466.396239] ACPI: EC: interrupt unblocked
[ 5466.547675] ACPI: EC: event unblocked
[ 5466.557881] sd 1:0:0:0: [sda] Starting disk
[ 5466.791877] usb 2-2: reset full-speed USB device number 2 using xhci_hcd
[ 5466.795014] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
[ 5466.872076] ata1: SATA link down (SStatus 0 SControl 300)
[ 5466.875783] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 5466.878484] ata2.00: configured for UDMA/133
[ 5466.965080] usb 1-1.6: reset high-speed USB device number 4 using ehci-pci
[ 5467.193169] OOM killer enabled.
[ 5467.193171] Restarting tasks ... done.
[ 5467.211324] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 5467.211388] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 5467.228749] pci_bus 0000:01: Allocating resources
[ 5467.230542] pci_bus 0000:02: Allocating resources
[ 5467.230700] pci_bus 0000:03: Allocating resources
[ 5467.231092] pci_bus 0000:01: Allocating resources
[ 5467.235826] pci_bus 0000:02: Allocating resources
[ 5467.236055] pci_bus 0000:03: Allocating resources
[ 5467.242592] audit: type=1130 audit(1546581731.903:58): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 5467.269768] pci_bus 0000:01: Allocating resources
[ 5467.271562] pci_bus 0000:02: Allocating resources
[ 5467.271876] pci_bus 0000:03: Allocating resources
[ 5467.340548] acpi PNP0401:00: Already enumerated
[ 5467.346137] acpi PNP0501:00: Still not present
[ 5467.365672] PM: suspend exit
[ 5467.367350] audit: type=1130 audit(1546581732.026:59): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 5467.367363] audit: type=1131 audit(1546581732.026:60): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 5467.541546] Bluetooth: hci0: Intel firmware patch completed and activated
[ 5470.771421] wlp2s0: authenticate with 10:9f:a9:5d:60:88
[ 5470.776001] wlp2s0: send auth to 10:9f:a9:5d:60:88 (try 1/3)
[ 5470.779439] wlp2s0: authenticated
[ 5470.781652] wlp2s0: associate with 10:9f:a9:5d:60:88 (try 1/3)
[ 5470.785505] wlp2s0: RX AssocResp from 10:9f:a9:5d:60:88 (capab=0x411 status=0 aid=1)
[ 5470.787806] wlp2s0: associated
[ 5472.249297] audit: type=1131 audit(1546581736.910:61): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 7295.565438] PM: suspend entry (deep)
[ 7295.565440] PM: Syncing filesystems ... done.
[ 7295.594973] Freezing user space processes ... (elapsed 0.015 seconds) done.
[ 7295.610201] OOM killer disabled.
[ 7295.610203] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 7295.611555] printk: Suspending console(s) (use no_console_suspend to debug)
[ 7295.612404] wlp2s0: deauthenticating from 10:9f:a9:5d:60:88 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 7295.630642] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 7295.631039] sd 1:0:0:0: [sda] Stopping disk
[ 7295.632336] e1000e: EEE TX LPI TIMER: 00000011
[ 7296.201330] ACPI: EC: interrupt blocked
[ 7296.263569] ACPI: Preparing to enter system sleep state S3
[ 7296.267469] ACPI: EC: event blocked
[ 7296.267470] ACPI: EC: EC stopped
[ 7296.267471] PM: Saving platform NVS memory
[ 7296.267541] Disabling non-boot CPUs ...
[ 7296.288610] smpboot: CPU 1 is now offline
[ 7296.329157] smpboot: CPU 2 is now offline
[ 7296.368070] smpboot: CPU 3 is now offline
[ 7296.371070] ACPI: Low-level resume complete
[ 7296.371123] ACPI: EC: EC started
[ 7296.371124] PM: Restoring platform NVS memory
[ 7296.373545] Enabling non-boot CPUs ...
[ 7296.373584] x86: Booting SMP configuration:
[ 7296.373585] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 7296.375267]  cache: parent cpu1 should not be sleeping
[ 7296.375458] CPU1 is up
[ 7296.375482] smpboot: Booting Node 0 Processor 2 APIC 0x1
[ 7296.376019]  cache: parent cpu2 should not be sleeping
[ 7296.376288] CPU2 is up
[ 7296.376309] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 7296.376805]  cache: parent cpu3 should not be sleeping
[ 7296.377170] CPU3 is up
[ 7296.386705] ACPI: Waking up from system sleep state S3
[ 7296.428102] ACPI: EC: interrupt unblocked
[ 7296.646134] ACPI: EC: event unblocked
[ 7296.646698] sd 1:0:0:0: [sda] Starting disk
[ 7296.895612] usb 2-2: reset full-speed USB device number 2 using xhci_hcd
[ 7296.898740] usb 1-1.6: reset high-speed USB device number 4 using ehci-pci
[ 7296.959149] ata1: SATA link down (SStatus 0 SControl 300)
[ 7296.959184] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 7296.961478] ata2.00: configured for UDMA/133
[ 7297.068799] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
[ 7297.188186] OOM killer enabled.
[ 7297.188187] Restarting tasks ... done.
[ 7297.206639] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 7297.206645] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 7297.221028] audit: type=1130 audit(1546583567.846:62): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 7297.222916] pci_bus 0000:01: Allocating resources
[ 7297.224714] pci_bus 0000:02: Allocating resources
[ 7297.225037] pci_bus 0000:03: Allocating resources
[ 7297.225334] pci_bus 0000:01: Allocating resources
[ 7297.227129] pci_bus 0000:02: Allocating resources
[ 7297.227452] pci_bus 0000:03: Allocating resources
[ 7297.270494] pci_bus 0000:01: Allocating resources
[ 7297.272309] pci_bus 0000:02: Allocating resources
[ 7297.272534] pci_bus 0000:03: Allocating resources
[ 7297.370193] acpi PNP0401:00: Already enumerated
[ 7297.387726] acpi PNP0501:00: Still not present
[ 7297.453812] PM: suspend exit
[ 7297.456477] audit: type=1130 audit(1546583568.083:63): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 7297.456498] audit: type=1131 audit(1546583568.083:64): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 7297.535879] Bluetooth: hci0: Intel firmware patch completed and activated
[ 7300.695760] wlp2s0: authenticate with 10:9f:a9:5d:60:88
[ 7300.700425] wlp2s0: send auth to 10:9f:a9:5d:60:88 (try 1/3)
[ 7300.703576] wlp2s0: authenticated
[ 7300.705308] wlp2s0: associate with 10:9f:a9:5d:60:88 (try 1/3)
[ 7300.709127] wlp2s0: RX AssocResp from 10:9f:a9:5d:60:88 (capab=0x411 status=0 aid=1)
[ 7300.711284] wlp2s0: associated
[ 7302.222786] audit: type=1131 audit(1546583572.850:65): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 8995.999838] audit: type=1006 audit(1546585266.716:66): pid=4153 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=6 res=1
[ 9125.470019] PM: suspend entry (deep)
[ 9125.470021] PM: Syncing filesystems ... done.
[ 9125.483193] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 9125.484571] OOM killer disabled.
[ 9125.484572] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 9125.485754] printk: Suspending console(s) (use no_console_suspend to debug)
[ 9125.486074] wlp2s0: deauthenticating from 10:9f:a9:5d:60:88 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 9125.500197] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 9125.504056] sd 1:0:0:0: [sda] Stopping disk
[ 9125.504113] e1000e: EEE TX LPI TIMER: 00000011
[ 9126.082077] ACPI: EC: interrupt blocked
[ 9126.128216] ACPI: Preparing to enter system sleep state S3
[ 9126.134259] ACPI: EC: event blocked
[ 9126.134261] ACPI: EC: EC stopped
[ 9126.134262] PM: Saving platform NVS memory
[ 9126.134350] Disabling non-boot CPUs ...
[ 9126.169341] smpboot: CPU 1 is now offline
[ 9126.197119] smpboot: CPU 2 is now offline
[ 9126.249331] smpboot: CPU 3 is now offline
[ 9126.252317] ACPI: Low-level resume complete
[ 9126.252371] ACPI: EC: EC started
[ 9126.252371] PM: Restoring platform NVS memory
[ 9126.254807] Enabling non-boot CPUs ...
[ 9126.254846] x86: Booting SMP configuration:
[ 9126.254847] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 9126.256641]  cache: parent cpu1 should not be sleeping
[ 9126.256824] CPU1 is up
[ 9126.256848] smpboot: Booting Node 0 Processor 2 APIC 0x1
[ 9126.257377]  cache: parent cpu2 should not be sleeping
[ 9126.257647] CPU2 is up
[ 9126.257668] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 9126.258165]  cache: parent cpu3 should not be sleeping
[ 9126.258325] CPU3 is up
[ 9126.261632] ACPI: Waking up from system sleep state S3
[ 9126.311258] ACPI: EC: interrupt unblocked
[ 9126.500934] ACPI: EC: event unblocked
[ 9126.511207] sd 1:0:0:0: [sda] Starting disk
[ 9126.746899] usb 2-2: reset full-speed USB device number 2 using xhci_hcd
[ 9126.759992] usb 1-1.6: reset high-speed USB device number 4 using ehci-pci
[ 9126.823717] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 9126.824050] ata1: SATA link down (SStatus 0 SControl 300)
[ 9126.826133] ata2.00: configured for UDMA/133
[ 9126.930026] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
[ 9127.250614] OOM killer enabled.
[ 9127.250615] Restarting tasks ... done.
[ 9127.266898] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 9127.267064] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 9127.283771] pci_bus 0000:01: Allocating resources
[ 9127.285561] pci_bus 0000:02: Allocating resources
[ 9127.285779] pci_bus 0000:03: Allocating resources
[ 9127.286784] pci_bus 0000:01: Allocating resources
[ 9127.288628] pci_bus 0000:02: Allocating resources
[ 9127.288790] pci_bus 0000:03: Allocating resources
[ 9127.296624] audit: type=1130 audit(1546585401.043:67): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 9127.313112] pci_bus 0000:01: Allocating resources
[ 9127.315030] pci_bus 0000:02: Allocating resources
[ 9127.315191] pci_bus 0000:03: Allocating resources
[ 9127.330776] acpi PNP0401:00: Already enumerated
[ 9127.334102] acpi PNP0501:00: Still not present
[ 9127.343099] PM: suspend exit
[ 9127.345090] audit: type=1130 audit(1546585401.090:68): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 9127.345094] audit: type=1131 audit(1546585401.090:69): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 9127.592161] Bluetooth: hci0: Intel firmware patch completed and activated

I would really appreciate any help as this is really disrupting work and I am at a loss to move forward.

I created a new user, but unless I fully set it up, there isn't much I can do under that user, so it is hard to spend enough time to see whether a sleep event would occur. So I will do it if necessary, but it would be a very time consuming test.

Thank you very much for your time.

Last edited by prosoitos (2019-01-25 19:14:44)

seth · 2019-01-25 21:25:27

prosoitos wrote:

If so, I don't see anything just before an event: last sleep was at 21:45 and the last entry given by journalctl is at 21:18...

That's not possible, you'll in any case have kernel messages - try "sudo journalctl -b" (journalctl will probably just print the session journal)

Also try whether this also happens from a rescue.target, https://wiki.archlinux.org/index.php/Sy … ent_target

prosoitos · 2019-01-26 04:18:27

This is what I get from "sudo journalctl -b"

Jan 25 19:55:00 prosoitos dbus-daemon[459]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.161' (uid=1000 pid=4079 comm="/usr/bin/pkttyagent --notify-fd 5 --fallback ")
Jan 25 19:55:00 prosoitos systemd[1]: Starting Authorization Manager...
Jan 25 19:55:00 prosoitos systemd-logind[462]: System idle. Taking action.
Jan 25 19:55:00 prosoitos systemd-logind[462]: Operation 'hybrid-sleep' requested but not supported, using regular suspend instead.
Jan 25 19:55:00 prosoitos systemd-logind[462]: Suspending...
Jan 25 19:55:00 prosoitos systemd[1]: Reached target Sleep.
Jan 25 19:55:00 prosoitos systemd[1]: Starting Suspend...
Jan 25 19:55:00 prosoitos polkitd[4082]: Started polkitd version 0.116
Jan 25 19:55:00 prosoitos systemd-sleep[4083]: Suspending system...
Jan 25 19:55:00 prosoitos kernel: PM: suspend entry (deep)
Jan 25 19:55:03 prosoitos kernel: PM: Syncing filesystems ... done.
Jan 25 19:55:03 prosoitos kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Jan 25 19:55:03 prosoitos kernel: OOM killer disabled.
Jan 25 19:55:03 prosoitos kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jan 25 19:55:03 prosoitos kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 25 19:55:03 prosoitos kernel: wlp2s0: deauthenticating from 10:9f:a9:5d:60:88 by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 25 19:55:03 prosoitos kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache
Jan 25 19:55:03 prosoitos kernel: e1000e: EEE TX LPI TIMER: 00000011
Jan 25 19:55:03 prosoitos kernel: sd 1:0:0:0: [sda] Stopping disk
Jan 25 19:55:03 prosoitos kernel: ACPI: EC: interrupt blocked
Jan 25 19:55:03 prosoitos kernel: ACPI: Preparing to enter system sleep state S3
Jan 25 19:55:03 prosoitos kernel: ACPI: EC: event blocked
Jan 25 19:55:03 prosoitos kernel: ACPI: EC: EC stopped
Jan 25 19:55:03 prosoitos kernel: PM: Saving platform NVS memory
Jan 25 19:55:03 prosoitos kernel: Disabling non-boot CPUs ...
Jan 25 19:55:03 prosoitos kernel: smpboot: CPU 1 is now offline
Jan 25 19:55:03 prosoitos kernel: smpboot: CPU 2 is now offline
Jan 25 19:55:03 prosoitos kernel: smpboot: CPU 3 is now offline
Jan 25 19:55:03 prosoitos kernel: ACPI: Low-level resume complete
Jan 25 19:55:03 prosoitos kernel: ACPI: EC: EC started
Jan 25 19:55:03 prosoitos kernel: PM: Restoring platform NVS memory
Jan 25 19:55:03 prosoitos kernel: Enabling non-boot CPUs ...
Jan 25 19:55:03 prosoitos kernel: x86: Booting SMP configuration:
Jan 25 19:55:03 prosoitos kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jan 25 19:55:03 prosoitos kernel:  cache: parent cpu1 should not be sleeping
Jan 25 19:55:03 prosoitos kernel: CPU1 is up
Jan 25 19:55:03 prosoitos kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
Jan 25 19:55:03 prosoitos kernel:  cache: parent cpu2 should not be sleeping
Jan 25 19:55:03 prosoitos kernel: CPU2 is up
Jan 25 19:55:03 prosoitos kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Jan 25 19:55:03 prosoitos kernel:  cache: parent cpu3 should not be sleeping
Jan 25 19:55:03 prosoitos kernel: CPU3 is up
Jan 25 19:55:03 prosoitos kernel: ACPI: Waking up from system sleep state S3
Jan 25 19:55:03 prosoitos kernel: ACPI: EC: interrupt unblocked
Jan 25 19:55:03 prosoitos kernel: ACPI: EC: event unblocked
Jan 25 19:55:03 prosoitos kernel: sd 1:0:0:0: [sda] Starting disk
Jan 25 19:55:03 prosoitos kernel: usb 2-2: reset full-speed USB device number 2 using xhci_hcd
Jan 25 19:55:03 prosoitos kernel: usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
Jan 25 19:55:03 prosoitos kernel: ata1: SATA link down (SStatus 0 SControl 300)
Jan 25 19:55:03 prosoitos kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 25 19:55:03 prosoitos kernel: ata2.00: configured for UDMA/133
Jan 25 19:55:03 prosoitos kernel: usb 1-1.6: reset high-speed USB device number 4 using ehci-pci
Jan 25 19:55:03 prosoitos kernel: OOM killer enabled.
Jan 25 19:55:03 prosoitos kernel: Restarting tasks ... done.

and etc. with all the other restart processes.

So, finally some clue (thank you both for advice):

2nd line, I get the message

Jan 25 19:55:00 prosoitos systemd-logind[462]: System idle. Taking action.

while I was actually busy on the machine at 19:55. This is the exact same message that shows in journalctl when I indeed leave the laptop idle (and the behaviour is also the same: suspend since I still have to create a swap file to allow for hybrid-sleep). So why does systemd-logind think that the laptop is idle when it isn't?

I don't understand that first line (noob here-will do some googling), just before systemd-logind gets it wrong and I feel it may be key:

Jan 25 19:55:00 prosoitos dbus-daemon[459]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.161' (uid=1000 pid=4079 comm="/usr/bin/pkttyagent --notify-fd 5 --fallback ")

Of note, I don't think it is when I do something particular that this happens as I have had those sleep events happen while I was browsing the web, typing, using various GUI, the cli, etc. It seems to happen totally randomly.

For your 2nd question @Seth, there is not much I can do when in rescue.target as I can't do much without Xorg with my current settings. So I may not have left it enough time. But it *seemed* that it was not happening. I don't feel very confident in my test though.

Last edited by prosoitos (2019-01-26 04:21:14)

prosoitos · 2019-01-26 04:29:01

Just had another sleep event and this time, there is absolutely nothing before the "System idle":

Jan 25 20:25:31 prosoitos systemd-logind[462]: System idle. Taking action.
Jan 25 20:25:31 prosoitos systemd-logind[462]: Operation 'hybrid-sleep' requested but not supported, using regular suspend instead.
Jan 25 20:25:31 prosoitos systemd-logind[462]: Suspending...
Jan 25 20:25:31 prosoitos systemd[1]: Reached target Sleep.
Jan 25 20:25:31 prosoitos systemd[1]: Starting Suspend...
Jan 25 20:25:31 prosoitos systemd-sleep[8550]: Suspending system...
Jan 25 20:25:31 prosoitos kernel: PM: suspend entry (deep)
Jan 25 20:25:34 prosoitos kernel: PM: Syncing filesystems ... done.
Jan 25 20:25:34 prosoitos kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Jan 25 20:25:34 prosoitos kernel: OOM killer disabled.
Jan 25 20:25:34 prosoitos kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jan 25 20:25:34 prosoitos kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 25 20:25:34 prosoitos kernel: wlp2s0: deauthenticating from 10:9f:a9:5d:60:88 by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 25 20:25:34 prosoitos kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache
Jan 25 20:25:34 prosoitos kernel: sd 1:0:0:0: [sda] Stopping disk
Jan 25 20:25:34 prosoitos kernel: e1000e: EEE TX LPI TIMER: 00000011
Jan 25 20:25:34 prosoitos kernel: ACPI: EC: interrupt blocked
Jan 25 20:25:34 prosoitos kernel: ACPI: Preparing to enter system sleep state S3

So is there something wrong with systemd-logind?

prosoitos · 2019-01-26 04:31:47

Here is the content of my /etc/systemd/logind.conf

HandlePowerKey=poweroff
HandleSuspendKey=suspend
HandleHibernateKey=hibernate
HandleLidSwitch=suspend
IdleAction=hybrid-sleep
IdleActionSec=30min

which I think is the default. So nothing bizarre in it.

seth · 2019-01-26 07:42:18

As the manpage will tell you, the default IdleAction is "ignore" and these entries are also all commented by default.
Furthermore the systemd IdleAction completely relies on signals and locks from the active session.
Please post the output of "loginctl session-status" and a complete journal and explain how you installed archlinux resp. what led you to the assumption about these default?

prosoitos · 2019-01-26 21:29:11

Oh, totally my bad about the default. I really appreciate your time and apologize for not having double-checked this myself. My assumption was that I (erroneously obviously) thought that I had never changed the systemd-longind config. But I guess I must have done so when I first set up Arch on a first machine a year and a bit ago and totally forgot about it. (To set up the 2nd machine, I transferred a lot of the config files over which is why I have the same issue on the new machine as on the old one).

With this realization, I just commented out the whole /etc/systemd/logind.conf and re-enabled acpid.service which I will now use to customize ACPI actions. I will see if this changes anything to my unwanted suspend events.

Here is the output "loginctl session-status":

1 - marie (1000)
           Since: Sat 2019-01-26 13:14:39 PST; 6min ago
          Leader: 1776 (login)
            Seat: seat0; vc1
             TTY: tty1
         Service: login; type tty; class user
           State: active
            Unit: session-1.scope
                  ├─ 1776 login -- marie
                  ├─ 8223 -zsh
                  ├─ 8236 /bin/sh /usr/bin/startx
                  ├─ 8280 xinit /home/marie/.xinitrc -- /home/marie/.xserverrc :0 vt1 -keeptty -auth /tmp/serverauth.qIIXf8uwcG
                  ├─ 8282 /usr/lib/Xorg -nolisten tcp :0 vt1 -keeptty -auth /tmp/serverauth.qIIXf8uwcG vt1
                  ├─ 8318 xf86-video-intel-backlight-helper intel_backlight
                  ├─ 8459 emacs
                  ├─ 8562 sxhkd
                  ├─ 8620 /usr/bin/python /usr/bin/autokey-gtk
                  ├─ 8621 goldendict
                  ├─ 8622 redshift
                  ├─ 8623 /usr/bin/python3 /usr/bin/qutebrowser
                  ├─ 8643 ssh-agent
                  ├─12198 /usr/lib/qt/libexec/QtWebEngineProcess --type=zygote --webengine-schemes=qrc:sLV --lang=en-CA
                  ├─13699 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --redu>
                  ├─13724 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --redu>
                  ├─16580 /usr/bin/aspell -a -m -B --encoding=utf-8
                  ├─29188 sh /home/marie/parvus/doc/bin/launch_startup-apps1.sh
                  ├─29201 volumeicon
                  ├─29202 /usr/bin/python2 -OO /usr/bin/pypanel
                  ├─30937 urxvt
                  ├─30938 zsh
                  ├─30989 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --redu>
                  ├─31001 /usr/lib/qt/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --redu>
                  ├─31189 loginctl session-status
                  └─31190 less

Jan 26 13:14:39 prosoitos systemd[1]: Started Session 1 of user marie.
Jan 26 13:14:39 prosoitos login[1776]: LOGIN ON tty1 BY marie
Jan 26 13:19:06 prosoitos sudo[31095]:    marie : TTY=tty1 ; PWD=/home/marie ; USER=root ; COMMAND=/usr/bin/emacs -q -l /home/marie/.emacs_root /etc/systemd/l>
Jan 26 13:19:06 prosoitos sudo[31095]: pam_unix(sudo:session): session opened for user root by marie(uid=0)
Jan 26 13:19:23 prosoitos sudo[31095]: pam_unix(sudo:session): session closed for user root
Jan 26 13:19:34 prosoitos sudo[31149]:    marie : TTY=tty1 ; PWD=/home/marie ; USER=root ; COMMAND=/usr/bin/emacs -q -l /home/marie/.emacs_root /etc/systemd/l>
Jan 26 13:19:34 prosoitos sudo[31149]: pam_unix(sudo:session): session opened for user root by marie(uid=0)
Jan 26 13:19:53 prosoitos sudo[31149]: pam_unix(sudo:session): session closed for user root

(I guess I could have left out the last lines which are only my history on this session...)

Last edited by prosoitos (2019-01-26 21:35:21)

seth · 2019-01-26 22:07:41

No problem - and I'm easily willing to believe that that session doesn't come out of a braindead arch-derivate for dummies

I don't know whether logind (now) defaults to "dead until proven alive" but don't expect usable support w/ anything but gnome (and maybe KDE and probably console sessions)
Looking at the list of processes, I'd say autokey-gtk or volumeicon could trigger somthing (you can "dbus-monitor --system" to check whether and what sends something along "" to "org.freedesktop.login1")
Also see eg. https://github.com/swaywm/sway/issues/886

prosoitos · 2019-01-27 00:05:37

I'm easily willing to believe that that session doesn't come out of a braindead arch-derivate for dummies.

No no I follow the Arch Wiki!

I think that you solved my problem. I will wait a few more hours before marking it as solved to confirm that those suspend events don't occur anymore, but I think that the problem was those "IdleAction" lines in the logind.conf... What is weird is that I must have set those many months ago and they never created any problem until a system update on Dec 19.

Anyhow, I *think* (hope!) that those suspend events have stopped.

I decided in the end to stop using laptop-mode-tools and acpid (I don't really want to lower performance to increase battery time and I am happy with as simple a system as possible).

The systemd defaults seem to work fine for me. The only thing that I will set is hybrid-sleep by creating a sleep.conf file following https://wiki.archlinux.org/index.php/Po … on_request (I just created a swap file).

Thank you very much for your help! This has been really annoying for over a month and I am really glad if it is indeed finally sorted

Note: thank you for pointing this issue out. Reading it made me wonder if my suspend events were happening every 30 min, following "IdleActionSec=30min" in my logind.conf. I never paid attention to the timing, but it is possible.

Last edited by prosoitos (2019-01-27 00:10:22)

prosoitos · 2019-01-27 01:32:07

Well, still no suspend event Marking this as solved. Thank you!!!

prosoitos · 2019-01-27 19:49:28

Silly follow-up question: now that I have commented out the "IdleAction" line in my /etc/systemd/logind.conf (which reverts it to default behaviour "IdleAction=ignore"), of course my laptop never goes to hybrid-sleep, no matter how long it idles.

Telling systemd to do nothing on idle was a fix of the symptom, but did not address the cause (why is the laptop considered idle when it is in use?).

So I still would like to:

- understand what is going on to address it and be able to set IdleAction
- alternatively, even if less satisfactory, I need to find another way to start hybrid-sleep cycles when my laptop idles for x amount of time (does acpid do that? I read the Wiki but the info was only on "active" ACPI events such as pressing buttons, closing lid, etc.)

Note: I will remove the [solved] tag, now that I have realized that my problem is not really fixed.

Last edited by prosoitos (2019-01-27 19:52:07)

seth · 2019-01-27 20:07:28

Actually you're more facing a different issue. However: https://www.archlinux.org/packages/comm … xautolock/ ?
Don't be confused by the name, you can make it run anything after an idle delay.

prosoitos · 2019-01-27 20:10:26

According to this bug report https://bugs.freedesktop.org/show_bug.cgi?id=77671:

"Your DE needs to inform logind about when it is idle or not, logind cannot figure that out on its own. GNOME and KDE do this correclty. Please file a bug against your DE of choice."

I filled in an issue to EXWM (https://github.com/ch11ng/exwm). But the problem only started on Dec 19. I had no problem before then while already using EXWM...

prosoitos · 2019-01-27 20:17:04

Great. Thank you @seth. I will look at xautolock. I would prefer to rely on systemd-logind, but since I am stuck, I will happily take something that works.

Last edited by prosoitos (2019-01-27 20:17:21)

seth · 2019-01-27 20:35:45

About the idle condition:

sudo qdbus --system org.freedesktop.login1 /org/freedesktop/login1/seat/seat0 org.freedesktop.login1.Seat.IdleHint

should say "false".
You can actually set it there (and that should prevent involuntary sleeps unless the session sends an idle hint, but oc. that's nearly pointless - you can just skip that system and sleep on idleness)

Arch Linux

#1 2018-12-21 01:27:54

[SOLVED] Systemd-logind triggers idle action when laptop is active

#2 2018-12-22 23:25:40

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#3 2018-12-22 23:30:12

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#4 2018-12-24 04:35:11

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#5 2018-12-24 05:16:21

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#6 2018-12-24 05:21:47

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#7 2018-12-24 05:49:34

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#8 2018-12-24 05:56:41

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#9 2018-12-24 06:00:26

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#10 2018-12-24 06:14:44

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#11 2019-01-25 19:11:47

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#12 2019-01-25 21:25:27

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#13 2019-01-26 04:18:27

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#14 2019-01-26 04:29:01

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#15 2019-01-26 04:31:47

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#16 2019-01-26 07:42:18

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#17 2019-01-26 21:29:11

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#18 2019-01-26 22:07:41

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#19 2019-01-27 00:05:37

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#20 2019-01-27 01:32:07

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#21 2019-01-27 19:49:28

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#22 2019-01-27 20:07:28

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#23 2019-01-27 20:10:26

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#24 2019-01-27 20:17:04

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

#25 2019-01-27 20:35:45

Re: [SOLVED] Systemd-logind triggers idle action when laptop is active

Board footer