Suspend/Sleep does not work in KDE plasma

Help
1

Hey all, I just recently decided to give Plasma a try, but there has been one consistently annoying issue I have been having. Triggering suspend from the lock-screen, power menu, command line or closing the lid (I am using a laptop; I don’t know if this is relevant). results in the screen turning off and then my device reboots. This problem has been a KDE/Plasma only problem as suspending using systemctl suspend(or any of the other described options) from GNOME or tty, the system is able to suspend properly.

Here is my system info:

Operating System: Arch Linux
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 12th Gen Intel® Core™ i3-1215U
Memory: 8 GiB of RAM (7.6 GiB usable)
Graphics Processor: Intel® Graphics
System Version: rev3
2

hi, welcome.

what are your settings in plasma?

so you are saying that sudo systemctl suspend is working properly for you on this plasma, but just not from plasma itself?

do you have more than one DE installed?

do you plan to use hibernate?

what are the outputs of the following:

cat /sys/power/state

cat /sys/power/mem_sleep

cat /sys/power/disk
3

All the defaults. This is a fresh install.

Inhibiting any sort of suspend action from within plasma results in suspend failure and a reboot.

Yes, GNOME is also installed.

No I do not.

cat /sys/power/state outputs freeze mem
cat /sys/power/mem_sleep outputs [s2idle]
cat /sys/power/disk outputs [disabled]

4

defaults settings can vary by distro, so if you would share your settings then others would know what they are.

your answer to the question about sudo systemctl suspend is unclear.

if you issue that command in a terminal, what happens? and have you check the journal logs for that time to see if there is anything of interest.

it’s also quite possible there is a conflict in the system between how gnome thinks things are supposed to be and how plasma thinks things are supposed to be.

if you must have access to both DE’s on the same install then having them under different users is at least part way toward keeping them separate.

5

My KDE sleep settings are the following:
On AC power, when inactive, sleep after 15 mins. The screen will turn off after 5 mins. The power button press shows the “logout menu”. The same is for when on battery. Low battery, the device will sleep after 5 mins. The screen will turn off after 2 mins. There are no additional settings or scripts to be run. There is no charge limit. The critical power action is sleep.

Running sudo systemctl suspend results in the exact same situation. Here are the logs:

PWD=/home/ak234 ; USER=root ; COMMAND=/usr/bin/systemctl suspend
Jul 25 16:15:45 omnigul sudo[10719]:    ak234 : TTY=pts/1 ; PWD=/home/ak234 ; USER=root ; COMMAND=/usr/bin/systemctl suspend
Jul 25 16:15:45 omnigul systemd-logind[894]: The system will suspend now!
Jul 25 16:15:45 omnigul NetworkManager[889]: <info>  [1753474545.9451] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jul 25 16:15:45 omnigul NetworkManager[889]: <info>  [1753474545.9453] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jul 25 16:15:45 omnigul NetworkManager[889]: <info>  [1753474545.9457] manager: NetworkManager state is now ASLEEP
Jul 25 16:15:45 omnigul NetworkManager[889]: <info>  [1753474545.9460] device (wlp0s20f3): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jul 25 16:15:45 omnigul kwin_wayland[9987]: kwin_core: Failed to delay sleep: Sender is not authorized to send message
Jul 25 16:15:46 omnigul NetworkManager[889]: <info>  [1753474546.0666] device (wlp0s20f3): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jul 25 16:15:46 omnigul NetworkManager[889]: <info>  [1753474546.1116] device (wlp0s20f3): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jul 25 16:15:46 omnigul systemd[1]: Reached target Sleep.
Jul 25 16:15:46 omnigul systemd[1]: Starting System Suspend...
Jul 25 16:15:46 omnigul systemd-sleep[10781]: Successfully froze unit 'user.slice'.
Jul 25 16:15:46 omnigul systemd-sleep[10781]: Performing sleep operation 'suspend'...
Jul 25 16:15:46 omnigul kernel: PM: suspend entry (s2idle)
Jul 25 16:16:13 archlinux kernel: Low-power S0 idle used by default for system suspend
Jul 25 16:16:43 archlinux kernel: Low-power S0 idle used by default for system suspend
[ak234@omnigul ~]$

GNOME and KDE are using separate users. KDE’s being ak234 and GNOME’s being ak.

6

those last two lines if the journal lead me to suspect it has something to do with the arch kernel

but you say it suspends normally when using the gnome DE so perhaps compare logs between the two and see if those lines are present with gnome as well.

another thing you could try is to disable the freeze option, as i’ve found issues with that on certain motherboards.

edit your /etc/systemd/sleep.conf or whatever arch uses in its place

uncomment the line

# SuspendState=mem standby freeze

and delete the word freeze

7

This is sudo systemctl suspend from GNOME:

ak : TTY=pts/0 ; PWD=/home/ak ; USER=root ; COMMAND=/usr/bin/systemctl suspend
Jul 26 08:15:37 omnigul systemd-logind[898]: The system will suspend now!
Jul 26 08:15:37 omnigul kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jul 26 08:15:37 omnigul NetworkManager[893]: <info>  [1753532137.5379] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jul 26 08:15:37 omnigul NetworkManager[893]: <info>  [1753532137.5381] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jul 26 08:15:37 omnigul NetworkManager[893]: <info>  [1753532137.5385] manager: NetworkManager state is now ASLEEP
Jul 26 08:15:37 omnigul NetworkManager[893]: <info>  [1753532137.5386] device (wlp0s20f3): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jul 26 08:15:37 omnigul systemd[1]: Starting Network Manager Script Dispatcher Service...
Jul 26 08:15:37 omnigul systemd[1]: Started Network Manager Script Dispatcher Service.
Jul 26 08:15:37 omnigul NetworkManager[893]: <info>  [1753532137.6583] device (wlp0s20f3): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jul 26 08:15:37 omnigul NetworkManager[893]: <info>  [1753532137.7046] device (wlp0s20f3): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jul 26 08:15:42 omnigul systemd-logind[898]: Delay lock is active (UID 1000/ak, PID 1619/gnome-shell) but inhibitor timeout is reached.
Jul 26 08:15:42 omnigul systemd[1]: Reached target Sleep.
Jul 26 08:15:42 omnigul systemd[1]: Starting System Suspend...
Jul 26 08:15:42 omnigul systemd[1]: user@1000.service: Unit now frozen-by-parent.
Jul 26 08:15:42 omnigul systemd[1]: session-3.scope: Unit now frozen-by-parent.
Jul 26 08:15:42 omnigul systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Jul 26 08:15:42 omnigul systemd[1]: user.slice: Unit now frozen.
Jul 26 08:15:42 omnigul systemd-sleep[3018]: Successfully froze unit 'user.slice'.
Jul 26 08:15:42 omnigul systemd-sleep[3018]: Performing sleep operation 'suspend'...
Jul 26 08:15:42 omnigul kernel: PM: suspend entry (s2idle)
Jul 26 08:15:48 omnigul kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jul 26 08:15:48 omnigul systemd-sleep[3018]: System returned from sleep operation 'suspend'.
Jul 26 08:15:48 omnigul kernel: PM: suspend exit
Jul 26 08:15:48 omnigul systemd[1]: user@1000.service: Unit now thawed.
Jul 26 08:15:48 omnigul systemd[1]: session-3.scope: Unit now thawed.
Jul 26 08:15:48 omnigul systemd[1]: user.slice: Unit now thawed.
Jul 26 08:15:48 omnigul systemd[1]: user-1000.slice: Unit now thawed.
Jul 26 08:15:48 omnigul systemd-sleep[3018]: Successfully thawed unit 'user.slice'.
Jul 26 08:15:48 omnigul systemd[1]: systemd-suspend.service: Deactivated successfully.
Jul 26 08:15:48 omnigul systemd[1]: Finished System Suspend.
Jul 26 08:15:48 omnigul systemd[1]: Stopped target Sleep.
Jul 26 08:15:48 omnigul systemd[1]: Reached target Suspend.
Jul 26 08:15:48 omnigul systemd-logind[898]: Operation 'suspend' finished.
Jul 26 08:15:48 omnigul systemd[1]: Stopped target Suspend.
Jul 26 08:15:48 omnigul NetworkManager[893]: <info>  [1753532148.2229] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jul 26 08:15:52 omnigul systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 26 08:15:52 omnigul systemd[1]: Starting Network Manager Script Dispatcher Service...
Jul 26 08:15:52 omnigul systemd[1]: Started Network Manager Script Dispatcher Service.
Jul 26 08:16:02 omnigul systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
[ak@omnigul ~]$

Uncommenting the SuspendState= line and removing freeze from the list of options doesn’t seem to fix the problem. As the user mentioned in the Arch Linux issue you posted here, before the device reboots, waking it (after the screen turns off and before it reboots) and running systemctl suspend several times, it does seem to suspend after the 4th or 5th try.

8

With kernel 6.15.7-arch1-1 (64-bit):

Have you begun using a more recent kernel and if so, are all symptoms the same?

9

Yes, I am using the most recent kernel (6.17). Yes, all the symptoms are still the same. For the time being, I am using GNOME.

10

I had suspend/sleep problems with KDE Plasma Debian on a Lenovo T460 and T450s. I worked with Google Gemini, adjusting BIOS settings and grub options. Both machines now sleep and wake as expected. It was quite a long process and the grub option strings were complex and slightly different for each machine. But they are solid now and good to have them working with the latest system software.