System Freezes on Power Button Actions After Recent Updates

[kenshiwara]

Hello everyone,

After the latest updates to Manjaro, I’ve been experiencing a critical issue: all power button actions (shutdown, restart, etc.) cause my system to freeze completely. However, I can still execute terminal commands like poweroff and reboot without any problems.

Here’s my system information for reference:

• Operating System: Manjaro Linux
• KDE Plasma Version: 6.1.5
• KDE Frameworks Version: 6.6.0
• Qt Version: 6.7.2
• Kernel Version: 6.11.2-4-MANJARO (64-bit)
• Graphics Platform: X11
• Processors: 12 × AMD Ryzen 5 5500
• Memory: 46.9 GiB RAM
• Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
• Manufacturer: Micro-Star International Co., Ltd.
• Product Name: MS-7D95
• System Version: 1.0

I’ve attempted to troubleshoot this issue using suggestions from LLMs like GPT-4 o1 and Claude Sonnet 3.5, but unfortunately, those solutions did not work.

Can anyone suggest a viable solution or troubleshooting steps?

Thank you for your assistance!

[Kobold]

Widespread issue with the latest stable update:

@philm

KDE Plasma hangs on Shutdown, Restart and Logout

With KDE Plasma 6.1, the session saving feature can make Plasma hang.
A workaround is to disable it in System settings > Session > Desktop Session, by choosing “Start with an empty session”.

• KDE Hangs on Shutdown, Restart and Logout. Black screen [SOLVED] / Applications & Desktop Environments / Arch Linux Forums

[cscs]

same?

KDE don't shut down anymore since last update

Do you have saved session? Set start with empty. After successfully shutting down that way … its reported saved sessions work normally again in most cases. ~ Retroactively quoting illustration ~

[Fangdrasil]

I don’t have the problem where my system freezes after the update you mention, but I do have a problem with session management. I’m responding to this thread because I followed the instructions mentioned by @Kobold and @cscs sometime ago because I thought that would fix my problem, which is this:

When I go to Settings - Session and select the second option, “When session was manually saved”, on applying the change, I’m asked to restart, which I select. That is when I get the black screen and am forced to switch to TTY and restart. The first time I did this a week ago, I followed the instructions mentioned, which “fixed” the problem, or so I thought. But the next time I tried to setup the manual session save option, I had the same problem occur when I try to restart.

I’m fine after the restart until I save a session; then, after saving the session, I am unable to select Restart, Shutdown, or Logout from the Application Launcher. Instead, I am forced to restart/shutdown from a shell.

Maybe my issue is different from kenshiwara’s, but it seems related.

[BG405]

If this is actually an issue with the “Save Session” feature, maybe it’s worth looking into the ~/.config/ksmserverrc file. Mine works, so I’ll put it here as an example:

(Mostly) working saved-session from mine:

[$Version]
update_info=ksmserver_update_loginMode_value.upd:ksmserver_update_loginMode_value_default_enum

[General]
confirmLogout=false
loginMode=restoreSavedSession
offerShutdown=false
screenCount=1
shutdownType=0

[LegacySession: saved at previous logout]
count=0

[LegacySession: saved by user]
clientMachine1=localhost
command1=gimp-2.10
count=1

[Session: saved at previous logout]
clientId1=1010410efacb000168037641100000012700048
count=1
program1=/usr/lib/virtualbox/VirtualBox
restartCommand1=/usr/lib/virtualbox/VirtualBox,-session,1010410efacb000168037641100000012700048_1694301730_329206
restartStyleHint1=0
userId1=brian

[Session: saved by user]
clientId1=1010410efacb000172787082400000009200002
clientId2=1010410efacb000171608160200000009360003
count=2
program1=pulseaudio
program2=/bin/smplayer
restartCommand1=
restartCommand2=/bin/smplayer,-session,1010410efacb000171608160200000009360003_1728577777_652072
restartStyleHint1=0
restartStyleHint2=0
userId1=brian
userId2=brian

Something for me to dig through later and see if I can get my head round it!

Something to try, to help prove it, is back that file up, save a session, then temporarily rename that file & restore the backup you just made.

You of course won’t get your newly-saved session back next boot or logout, but you can compare the files between saved and non saved state. (Maybe post these here?).

[kenshiwara]

Thank you all for the replies. It seems that choosing:

System settings > Session > Desktop Session > “Start with an empty session”

is the solution for now. Since I don’t have much use for the session-saving feature, I will keep it turned off.

[BG405]

I guess there are options for at least some of the programs etc. you use, like Kate with its Kate Sessions and Dolphin remembering the tabs from the last closed window when you open it, so workarounds, anyway. Some other programs too, like Firefox, which at least has been reliable in this respect for the past few years.

It would be nice if Konsole would remember the tabs like it used to, though.

[Kobold]

@Fangdrasil

I’m fine after the restart until I save a session; then, after saving the session

This is only a work around, till KDE really fixed this problem.

If you talking about auto-login, then maybe this could help you:

@philm

Session auto login can’t be re-enabled for X11

Once session auto login for X11 gets disabled, it can’t be re-enabled in settings.
A workaround is to edit the /etc/sddm.conf.d/kde_settings.conf file and replace Session=Plasma (X11) by Session=plasma

[Fangdrasil]

Thanks for that info @kobold, but I’m not using auto-login and I’m currently using Wayland. What I hadn’t paid attention to in the Session settings was the “Show” option for the “Logout Screen”, which was enabled. After I disabled that, my problem vanished. I may create a separate topic for some stuff I’ve observed in the journal logs when exploring the session options. The Logout Screen “Show” option causes issues for me, but that probably belongs in a separate support topic thread.