OpenMandriva Lx version:
Rome 24.12 updated to latest
Desktop environment (KDE, LXQT…):
KDE Plasma 6
Description of the issue (screenshots if relevant):
Clicking “Power / Session → Sleep” immediatelly hangs the system.
This worked just fine before the update, with plain Rome 24.12. I used the System Update tool to bring my installation to the latest, and since that, the problem appeared. Please note it hangs immediatelly after clicking “Sleep” in the Plasma menu, it does not even go to the next screen.
Relevant informations (hardware involved, software version, logs or output…):
i9400F, 32GB RAM, installed on NVMe, GTX750 (nvidia drivers not yet installed). The OMV installation is fresh, just a few hours old (it’s not my first attempt to identify the problem).
Thanks. I tried Lxqt and the problem is pretty much the same (to my surprise). Plain Rome 24.12 works fine, but as soon as I update the distro to 25.03, the computer hangs when attempting sleep. This time, it’s not in the menu, but after clicking “OK” when OS complains about missing compatible screensaver, however the behavior is similar - the menu darkens a little, like it’s about to close, and then system stops responding, within fraction of a second after clicking OK.
I also tried to update my original Plasma installation to Cooker, but the problem still persists.
I tried updating BIOS on the mainboard, but no change.
Just tested on another system (Intel NUC 8i5BEK2) - sleep works, but there’s no Plasma after waking up
Does anyone have any problems with Sleep in latest rolling (25.03)?
EDIT: actually, on subsequent reboots, Plasma appears correctly after sleep, it seems this was just a glitch.
Hmmm… I think I might need help with that. To clarify the situation, last time I actually used Linux for more than just HW testing was end of 90’s (hi Slackware 3) and we only had X11, nothing else. Programs were started from the command line
How do I switch to another display manager? I thought installing Lxqt version of OM does the trick, but I apparently don’t quite understand the difference between all the managers (display, window…)
As somewhat of a Linux noob myself (only been using it for the past 3 years), my understanding of a display manager is essentially just the login screen. The default with OMLx is sddm (simple desktop display manager), but you can change your display manager. You should be able to run dnf install [display manager] then disable the old display manager with systemctl disable [old display manager]. Then you can enable to newly installed display manager with systemctl enable [new display manager], then you just reboot your system.
Thanks, Mike!
I actually tried something else. After some reinstalls, I managed to get sleep working even after updating system. However, the problem returned after istalling nvidia drivers…
Also, I am beginning to believe this has nothing to do with any X stuff. I figured out I can initiate sleep by “systemctl suspend” - and when I do that, the system freezes.
BTW: I also tried Devuan (but it’s extremely unfriendly and I could not force myself to using it), MX Linux (I know, I know - but almost worked) and Bunsenlabs Boron (doesn’t even install properly). I’m beginning to believe this machine is incompatible with Linux…
I’m pretty sure this is what you should try:
ctrl+alt+F2 (this will be a terminal only)
Login with your user and password sudo dnf in lightdm sudo systemctl disable sddm sudo systemctl enable lightdm sudo reboot
Or as wilson said, it might be some setting in your bios
I can confirm this - it just happened to me today. It can’t be a BIOS issue because I have Nobara 41 on another SSD on this same system and suspend (and wake) works perfectly.
This is also a relatively clean OM Rome install (just Steam and a few other Flatpaks installed), fully updated as at time of posting.
System Specs -
Operating System: OpenMandriva ROME 25.03
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.14.0-desktop-0.rc6.2omv2590 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31,3 GiB of RAM
Graphics Processor: AMD Radeon RX 6750 XT
Manufacturer: ASUS
I kind of gave up for the moment. I tried installing lightdm but there was a collision with existing package so I did not get very far. Some tweaking actually led to system not booting, hanging after loading the initial ramdisk. As the problem happens on my main workhorse, I was without a computer. My wife is complaining about her computer being too slow so I’ll move my mobo to her system and I’ll get myself a new one in near future.
Anyway - from what Kevin wrote, it points to something in the update. Is there a way of updating step by step, package by package?
Select ‘N’ for No to not perform the dsync transaction. Use the list to upgrade packages one at the time with:
sudo dnf up >package_name<
You could probably do this with dnfdrake also.
Reboot and open terminal (Konsole) and run:
journalctl -b -1 | grep suspend
or:
journalctl -b -1 | grep systemd
and see if you can see any relevant errors. If you file a bug report include all the output of ‘journalctl -b -1’. These journalctl commands need to be run after freezing the system with systemctl suspend and rebooting.
Edit: This smells like something hardware related or systemd related, but I am not a developer so just speculation at this point. Opinion: It is also possibly sddm as that is not exactly prize winning software. But the important point is to find a cause for the problem otherwise developers have nothing to work on. journalctl -b -1 produces the journal log of the previous boot.
OpenMandriva Lx 25.03 (ROME) Rolling znver1 Plasma6
ASUSLaptop M1605YA
AMD Ryzen 5 7530U with Radeon Graphics
System was just dsynced (upgraded)
What I found is that systemctl suspend freezes this laptop if I am using X11, in other words, does not work properly. If I use Wayland systemctl suspend works perfectly here. Using this command basically works the same as using “Sleep” from Power/Session menu.
This is from the journal log using X11 with systemctl suspend:
Mar 29 10:06:21 3243 systemd-logind[973]: The system will suspend now!
Mar 29 10:06:21 3243 wpa_supplicant[1023]: p2p-dev-wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 29 10:06:21 3243 wpa_supplicant[1023]: p2p-dev-wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 29 10:06:21 3243 wpa_supplicant[1023]: nl80211: deinit ifname=p2p-dev-wlp1s0 disabled_11b_rates=0
Mar 29 10:06:21 3243 systemd[1]: Reached target sleep.target - Sleep.
Mar 29 10:06:21 3243 systemd[1]: Starting systemd-suspend.service - System Suspend...
Mar 29 10:06:21 3243 wpa_supplicant[1023]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 29 10:06:21 3243 systemd[1]: user@1001.service: Unit now frozen-by-parent.
Mar 29 10:06:21 3243 systemd[1]: session-c3.scope: Unit now frozen-by-parent.
Mar 29 10:06:21 3243 systemd[1]: user.slice: Unit now frozen.
Mar 29 10:06:21 3243 systemd[1]: user-1001.slice: Unit now frozen-by-parent.
Mar 29 10:06:21 3243 systemd-sleep[5856]: Successfully froze unit 'user.slice'.
Mar 29 10:06:21 3243 systemd-sleep[5856]: Performing sleep operation 'suspend'...
Mar 29 10:06:21 3243 kernel: PM: suspend entry (s2idle)
Mar 29 10:06:21 3243 kernel: Filesystems sync: 0.003 seconds
Mar 29 10:06:21 3243 wpa_supplicant[1023]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 29 10:06:21 3243 wpa_supplicant[1023]: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
Mar 29 10:06:25 3243 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 29 10:06:26 3243 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
So for me I can just use Wayland and not worry. As of today everything I am aware of is working under Wayland in ROME Plasma6 including KDE clipboard. If anyone is really bothered by this filing a bug report is usually the best thing to do.
Just for information: I am thinking suspend or sleep will not work with nvidia drivers. But you don’t seem to be using those. I do not have nVidia hardware so can not confirm or test this. If you were using X11 then I am seeing same behavior as you reported initially. Perhaps try Wayland? Or file a bug report.
