As the title says: I updated manjaro today to the last version, then sleep (suspension to RAM) doesn’t work anymore, i.e. it does nothing when I try to suspend, from konsole or from shortcuts. Some idea about how to fix it? I’m using wayland.
I don’t know whether this applies to you, but if you use Activities, then you should check the settings for each Activity, as they all have separate settings for suspend and shutdown.
Thanks, but I’m not talking about automatic suspend/sleep, and any this is activated in the two activities that I have. I’m talking about sleep at will, as I did many times in the past. However I can’t see in plasma anymore the buttons to restart, suspend or shutdown.
This is
UNIT LOAD ACTIVE SUB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Local Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
imports.target loaded active active Image Downloads
integritysetup.target loaded active active Local Integrity Protected Volumes
local-fs-pre.target loaded active active Preparation for Local File Systems
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User System
network.target loaded active active Network
paths.target loaded active active Path Units
remote-fs.target loaded active active Remote File Systems
slices.target loaded active active Slice Units
sockets.target loaded active active Socket Units
sound.target loaded active active Sound Card
swap.target loaded active active Swaps
sysinit.target loaded active active System Initialization
time-set.target loaded active active System Time Set
timers.target loaded active active Timer Units
tpm2.target loaded active active Trusted Platform Module
veritysetup.target loaded active active Local Verity Protected Volumes
Legend: LOAD → Reflects whether the unit definition was properly loaded.
ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
SUB → The low-level unit activation state, values depend on unit type.
21 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Yeah. I forgot it probably won’t be listed in that. My bad. Please provide the output of:
systemctl status suspend.target sleep.target
This is
○ suspend.target - Suspend
Loaded: loaded (/usr/lib/systemd/system/suspend.target; static)
Active: inactive (dead)
Docs: man:systemd.special(7)
○ sleep.target - Sleep
Loaded: loaded (/usr/lib/systemd/system/sleep.target; static)
Active: inactive (dead)
Docs: man:systemd.special(7)
Hmmmmm…
And:
systemctl status systemd-suspend.service
…please?
There is
○ systemd-suspend.service - System Suspend
Loaded: loaded (/usr/lib/systemd/system/systemd-suspend.service; static)
Drop-In: /usr/lib/systemd/system/systemd-suspend.service.d
└─10-nvidia-no-freeze-session.conf
Active: inactive (dead)
Docs: man:systemd-suspend.service(8)
Mostly the same as mine, that’s working. For:
systemctl is-enabled --user systemd-suspend.service
What I must do with this? Just run it in the konsole?
I discovered a thing: I can suspend the system from the button that appears when you close the session.
EDIT: after I run in konsole
systemctl is-enabled --user systemd-suspend.service
it says not-found, however for some reason now the system can suspend from the assigned hotkey, as usual. I’m not sure if this happens because I suspended before from the close session menu or because I ran the previous command in konsole. Strange.
not-found on mine as well, so it’s not that, but:
It is indeed strange, I don’t get it. Maybe you did a reboot after something changed and now it works again. I don’t know, but that kind of is all that makes sense.
Anyway, glad it’s working again.
I restarted the system, and again suspend doesn’t work from the assigned hotkey, so I closed the session again to have access to the screen with buttons to open a new session. In this screen there is a suspend button, I press it and indeed the system suspend. I awake the system enter in a new session and now (as before) the suspension works using the hotkey of plasma.
This is weird, but I have a way to suspend the system.
I haven’t finished today’s stable update yet, so I can’t test. But on previous updates if I installed and ran the new plasma display manager, I had the same symptoms you mention. When I go back to sddm, everything was fine. I was hoping this massive update on stable would fix that by updating all the kde libraries and frameworks.