System details (Debian)
Operating System: Debian GNU/Linux 13
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.12.57+deb13-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i3-1125G4 @ 2.00GHz
Memory: 8 GiB of RAM (7.6 GiB usable)
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: Google
Product Name: Eldrid
System Version: rev3
It stopped working about a month ago so I pivoted to systemd and then that has also recently stopped working. Here is the line that made me think it might be KDE-specific:
$ qdbus6 org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement org.kde.Solid.PowerManagement.isActionSupported 32
false
Open to suggestions.
So, this is a Chromebook with a Tiger Lake board? These can have quirks compared to normal laptop hardware/firmware. Have you tried booting to a previous kernel ?
I run KDE neon on my similar HP Tiger Lake Chromebook, and it has no problems with suspending, even when it was still on the previous 6.11 and original 6.8 kernels in Ubuntu LTS as far as I can recall. I am currently running something that needs the 6.8 kernel, so I have been using this for the past couple of days instead of the current 6.14.
Operating System: KDE neon User Edition
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.8.0-90-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 8 GiB of RAM (7.6 GiB usable)
Graphics Processor: Intel® Iris® Xe Graphics
Manufacturer: Google
Product Name: Elemi
System Version: rev3
My result of your qdbus output is identical.
This is probably just what your system is reporting for some attribute, but for what? What does “32” indicate?
What about:
$ cat /sys/power/mem_sleep
[s2idle] deep
1 Like
So I noticed this when you made your post:
$ cat /sys/power/mem_sleep
s2idle [deep]
I know for a fact that this was set to s2idle in the past. I thought it was a weird quirk and changed it back to s2idle. It worked for ~24h after a reboot, but then set itself to deep?
Something is breaking deeper in the system. It appears to be systemd-related perhaps because there are a ton of systemd services failing:
$ rgj systemd|rg failed
231:1193:Jan 12 08:33:08 optiplex systemd[1]: auditd.service: Failed with result 'exit-code'.
232:1194:Jan 12 08:33:08 optiplex systemd[1]: Failed to start auditd.service - Security Audit Logging Service.
304:1318:Jan 12 08:33:09 optiplex systemd[1]: clamav-daemon.service: Failed with result 'exit-code'.
316:1361:Jan 12 08:33:09 optiplex systemd[1]: auditd.service: Failed with result 'exit-code'.
317:1362:Jan 12 08:33:09 optiplex systemd[1]: Failed to start auditd.service - Security Audit Logging Service.
341:1475:Jan 12 08:33:09 optiplex systemd[1]: auditd.service: Failed with result 'exit-code'.
342:1476:Jan 12 08:33:09 optiplex systemd[1]: Failed to start auditd.service - Security Audit Logging Service.
359:1554:Jan 12 08:33:09 optiplex systemd[1]: auditd.service: Failed with result 'exit-code'.
360:1555:Jan 12 08:33:09 optiplex systemd[1]: Failed to start auditd.service - Security Audit Logging Service.
371:1606:Jan 12 08:33:09 optiplex systemd[1]: auditd.service: Failed with result 'exit-code'.
372:1607:Jan 12 08:33:09 optiplex systemd[1]: Failed to start auditd.service - Security Audit Logging Service.
375:1610:Jan 12 08:33:09 optiplex systemd[1]: audit-rules.service: Failed with result 'start-limit-hit'.
376:1611:Jan 12 08:33:09 optiplex systemd[1]: Failed to start audit-rules.service - Load Audit Rules.
377:1612:Jan 12 08:33:09 optiplex systemd[1]: Dependency failed for auditd.service - Security Audit Logging Service.
378:1613:Jan 12 08:33:09 optiplex systemd[1]: auditd.service: Job auditd.service/start failed with result 'dependency'.
409:1738:Jan 12 08:33:15 optiplex systemd[1]: mnt-ideap4d.mount: Failed with result 'exit-code'.
410:1739:Jan 12 08:33:15 optiplex systemd[1]: Failed to mount mnt-ideap4d.mount - NFS Mount for Ideap4d Server.
411:1740:Jan 12 08:33:15 optiplex systemd[1]: Dependency failed for remote-fs.target - Remote File Systems.
412:1741:Jan 12 08:33:15 optiplex systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.
624:2186:Jan 12 08:33:28 optiplex systemd[1984]: jellyfin-mpv-shim.service: Failed with result 'exit-code'.
669:2335:Jan 12 08:33:30 optiplex systemd[1984]: drkonqi-sentry-postman.path: Failed with result 'trigger-limit-hit'.
674:2354:Jan 12 08:33:31 optiplex systemd[1]: mnt-ideap4d.mount: Failed with result 'exit-code'.
675:2355:Jan 12 08:33:31 optiplex systemd[1]: Failed to mount mnt-ideap4d.mount - NFS Mount for Ideap4d Server.
679:2360:Jan 12 08:33:31 optiplex systemd[1]: mnt-ideap4d.mount: Failed with result 'exit-code'.
680:2361:Jan 12 08:33:31 optiplex systemd[1]: Failed to mount mnt-ideap4d.mount - NFS Mount for Ideap4d Server.
687:2381:Jan 12 08:33:32 optiplex systemd[1]: mnt-ideap4d.mount: Failed with result 'exit-code'.
688:2382:Jan 12 08:33:32 optiplex systemd[1]: Failed to mount mnt-ideap4d.mount - NFS Mount for Ideap4d Server.
696:2393:Jan 12 08:33:32 optiplex systemd[1]: mnt-ideap4d.mount: Failed with result 'exit-code'.
697:2394:Jan 12 08:33:32 optiplex systemd[1]: Failed to mount mnt-ideap4d.mount - NFS Mount for Ideap4d Server.
701:2400:Jan 12 08:33:32 optiplex systemd[1]: mnt-ideap4d.mount: Failed with result 'exit-code'.
702:2401:Jan 12 08:33:32 optiplex systemd[1]: Failed to mount mnt-ideap4d.mount - NFS Mount for Ideap4d Server.
711:2428:Jan 12 08:33:33 optiplex systemd[1]: mnt-ideap4d.mount: Failed with result 'exit-code'.
712:2429:Jan 12 08:33:33 optiplex systemd[1]: Failed to mount mnt-ideap4d.mount - NFS Mount for Ideap4d Server.
713:2430:Jan 12 08:33:33 optiplex systemd[1]: mnt-ideap4d.automount: Failed with result 'mount-start-limit-hit'.
719:2438:Jan 12 08:33:33 optiplex systemd[1984]: jellyfin-mpv-shim.service: Failed with result 'exit-code'.
809:2645:Jan 12 08:33:34 optiplex systemd[1984]: app-pulseaudio@autostart.service: Failed with result 'exit-code'.
815:2672:Jan 12 08:33:34 optiplex dbus-daemon[2027]: [session uid=1000 pid=2027 pidfd=5] Activation via systemd failed for unit 'evolution-source-registry.service': Unit evolution-source-registry.service not found.
817:2675:Jan 12 08:33:34 optiplex dbus-daemon[2027]: [session uid=1000 pid=2027 pidfd=5] Activation via systemd failed for unit 'evolution-source-registry.service': Unit evolution-source-registry.service not found.
879:2894:Jan 12 08:33:38 optiplex systemd[1984]: jellyfin-mpv-shim.service: Failed with result 'exit-code'.
889:2983:Jan 12 08:33:43 optiplex systemd[1984]: jellyfin-mpv-shim.service: Failed with result 'exit-code'.
898:3040:Jan 12 08:33:49 optiplex systemd[1984]: jellyfin-mpv-shim.service: Failed with result 'exit-code'.
902:3063:Jan 12 08:33:54 optiplex systemd[1984]: jellyfin-mpv-shim.service: Failed with result 'exit-code'.
903:3064:Jan 12 08:33:54 optiplex systemd[1984]: Failed to start jellyfin-mpv-shim.service - Jellyfin MPV Shim - MPV Cast Client for Jellyfin.
Is this a Chromebook? If so, have you updated the MrChromebox firmware in the past few months? He has had some updates, and there are now more options available in the firmware (“bios”) settings, including S0ix, which iirc is what you need to make sure is enabled (it should be) to have s2idle instead of the traditional deep sleep.
It could also be your kernel, but that seems less likely.
In any case, those systemd messages, and setting the suspend method are all unrelated to KDE.
How did you switch back to s2idle? You need a grub parameter for it to stick, just switching it in /sys/power/mem_sleep won’t persist.
I am up-to-date w/ the latest chultrabook firmware. The issue is also occurring on my Optiplex device as well and so I do not believe that is the culprit.
I do realize that the lack of hibernation/sleep working via KDE’s Settings is a symptom not a cause, so as you suggested, I don’t think KDE is the culprit any longer either.
Seems to potentially be Debian-specific but apparently/potentially something custom to my config given that there doesn’t seem to be a lot of complaints online