Hello! I have two issues with sleep on KDE plasma.
My system specs:
I run CachyOS on Linux 6.19.2-2-cachyos kernel, KDE Plasma 6.5.5
gigabyte B550m aorus elite, Ryzen 9 5950x, RAM amd 32gb 3200 with expo(R9S432G3206U2K), palit geforce rtx 3070 ti.
The major issue is that instead of going to sleep, my screens just black out and computer continues to work. After that state the only thing I could do is power off PSU and power it on, which can’t be healthy. Before upgrading from b450 and ryzen 7 2700 a couple of days ago system went to sleep fine and reliably. I didn’t click anything in bios except boot order and EXPO.
The minor issue I had even before upgrading is that ever since I started using Fcitx5 I can’t switch or see which keyboard layout I use on KDE’s own login screen. This issue resolved with clicking to switch user and typing password in SSDM, where it’s ENG by standard. I often use RU and JP layouts in messaging and searching, so sometimes I end up with then on login screen.
First things first. How are you triggering sleep, and are you sleeping, suspending, or hibernating? After attempting to sleep what does your system log say?
journalctl -b -1 | grep sleep
Also the output of the following would be handy too.
cat /sys/power/mem_sleep - shows available sleep states your system supports
cat /proc/cmdline - shows your kernel boot options
Hello!
About journalctl output, for when I tried to put it asleep:
фев 24 07:29:17 Robo-c0mp systemd-sleep[3766]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
фев 24 07:29:17 Robo-c0mp systemd-sleep[3766]: This is not recommended, and might result in unexpected behavior, particularly
фев 24 07:29:17 Robo-c0mp systemd-sleep[3766]: in suspend-then-hibernate operations or setups with encrypted home directories.
фев 24 07:29:17 Robo-c0mp systemd-sleep[3766]: Performing sleep operation ‘suspend’…
фев 24 07:29:58 Robo-c0mp systemd-sleep[3766]: Failed to put system to sleep. System resumed again: Device or resource busy
фев 24 07:29:59 Robo-c0mp NetworkManager[995]: [1771907399.3181] manager: sleep: wake requested (sleeping: yes enabled: yes)
фев 24 07:29:59 Robo-c0mp org_kde_powerdevil[2517]: [ 2607] (i2c_detect_x37) Extra x37 sleep: Sleeping for 2000 milliseconds
фев 24 07:30:01 Robo-c0mp org_kde_powerdevil[2517]: [ 2607] (i2c_detect_x37) Extra x37 sleep: Sleeping for 2000 milliseconds
фев 24 07:30:03 Robo-c0mp org_kde_powerdevil[2517]: [ 2607] (i2c_detect_x37) Extra x37 sleep: Sleeping for 2000 milliseconds
фев 24 07:30:06 Robo-c0mp org_kde_powerdevil[2517]: [ 2517] (i2c_detect_x37) Extra x37 sleep: Sleeping for 2000 milliseconds
фев 24 07:30:08 Robo-c0mp org_kde_powerdevil[2517]: [ 2517] (i2c_detect_x37) Extra x37 sleep: Sleeping for 2000 milliseconds
фев 24 07:30:10 Robo-c0mp org_kde_powerdevil[2517]: [ 2517] (i2c_detect_x37) Extra x37 sleep: Sleeping for 2000 milliseconds
фев 24 07:30:14 Robo-c0mp org_kde_powerdevil[2517]: [ 2517] (i2c_detect_x37) Extra x37 sleep: Sleeping for 2000 milliseconds
фев 24 07:30:16 Robo-c0mp org_kde_powerdevil[2517]: [ 2517] (i2c_detect_x37) Extra x37 sleep: Sleeping for 2000 milliseconds
фев 24 07:30:18 Robo-c0mp org_kde_powerdevil[2517]: [ 2517] (i2c_detect_x37) Extra x37 sleep: Sleeping for 2000 milliseconds
C:\home\robo-z3ro>
—
As for Cat’s outputs:
C:\home\robo-z3ro> cat /sys/power/mem_sleep
s2idle [deep]
C:\home\robo-z3ro> cat /proc/cmdline
initrd=\initramfs-linux-cachyos.img root=UUID=efbab278-5e9d-41e3-bf66-5fb80bf69e90 rw zswap.enabled=0 nowatchdog quiet splash
as for C:\ things, It’s just bashrc setup.
This indicates either a process or a device isn’t allowing sleep to occur. You can inspect the journal log further to work out which it is. Presuming you’re running this today try journactl -b -1 and just having a look through until you find some errors around the same time as the error above. If it’s a process you’ll also have an error along the lines of “Freezing user space processes failed after XX seconds (X tasks refusing to freeze)”, but it’s the actual process you need to look for.