After latest update, clicking at "Sleep" hangs the system

Hello,

  • 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).

Not sure how to actually fix this, but using a different display manager might be helpful. Try lightdm.

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.

I am going to try this on another system.

Just tested on another system (Intel NUC 8i5BEK2) - sleep works, but there’s no Plasma after waking up :slight_smile:
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.

1 Like

I still think you should try a different display manager. Sddm is not always the best. Try lightdm

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 :slight_smile:
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.

install.., disable.. , enable.. do it after logout from tty or in console mode boot.

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…

It could just be a setting in your bios.

Read the first few replies on this post.

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

2 Likes