I switched to the Testing Branch. This branch has shutdown Now and restart Now. Neither when activated leads to an immediate shutdown or restart. Is this a bug. I just use the command line “shutdown now.”
??
Please try to be a bit more explanatory.
What do you mean? What desktop are you using?
2 Likes
I am assuming that you are using Plasma as per your user profile. There are several options:
This first command will exit a Plasma session the correct way. However, if you have an app open that requires confirmation to close (such as Firefox with multiple tabs open), then this may not be the best choice for a machine that will be unattended when shutting down:
qdbus org.kde.Shutdown /Shutdown logoutAndShutdown
To log out of Plasma & reboot:
qdbus org.kde.Shutdown /Shutdown logoutAndReboot
To exit a Plasma session, displaying the shutdown options page with the countdown timer first, any of these:
qdbus org.kde.LogoutPrompt /LogoutPrompt promptLogout
qdbus org.kde.LogoutPrompt /LogoutPrompt promptReboot
qdbus org.kde.LogoutPrompt /LogoutPrompt promptShutDown
To shutdown the same way as shutdown now:
systemctl poweroff
(you can also replace poweroff in the above with suspend or reboot or hibernate)
1 Like
Do you mean the 30-second timer with the options appears instead?
If so, and if you are using KDE, System settings → Session → Desktop Session and remove the checkmark ✓ from the box below Logout Screen.
I was about to open a support thread as well, as I might experience the same thing like @jcgghb.
I’m on the KDE unstable branch with Kernel 6.11 and as soon as I click on “Restart” or “Shutdown” in the GUI, my computer doesn’t shutdown or restart. All windows are closed before that and all that happens is, that I’m left with a black screen and the mouse cursor.
I’ve waited 10+ minutes, but the computer just doesn’t shutdown (or restart).
1 Like
Is this any different with e.g. 6.6 LTS?
I think it is. It didn’t happen on 6.10 either and started happening with 6.11
I guessed so; hopefully the upcoming linux612 will have a fix included. This seems to suggest it’s not a Plasma issue as such.
If linux66 (or linux61, also LTS) work, I’d suggest sticking with those for now.
1 Like
Yeah I figured. Think this is kernel related, too. Thank you 
1 Like
After today’s stable update this is happening to me on 6.10. I can’t really try 6.11 because the xone dkms driver doesn’t work.
Update: So I tried this on my laptop with kernel 6.6. It also didn’t shutdown. When I rebooted, I logged into plasma wayland instead. It shuts down no problem. I am thinking this is a problem with plasma x11 not the kernel.
My current kernel version is: 6.9.12-3-MANJARO (linux69), and I have the same problem!
Then your system is not in a valid state.
Kernel 6.9 is EOL.
It does not exist in the repos any longer.
(and if you are on a branch other than Stable this happened a while ago …)
PS.
For all others … if plasma refuses to shut down … just use a command.
Whenever I have experienced this just running something like the following worked.
systemctl reboot
systemctl poweroff
But the same problem happened when I switched to linux66 this TLS
I’m just saying that if you have an EOL kernel its 1 obvious thing that is broken.
There are probably other issues. We cant know without more information.
System info:
inxi -Farz
Pacnews?
pacdiff -o
Unsupported packages?
pacman -Qmq
Orphans?
pacman -Qdtq
Are you really up to date?
sudo pacman-mirrors -f && sudo pacman -Syu
Did you ever refresh desktop cache and configs (especially between major plasma versions)?
KDE - ArchWiki
Do you use 'saved session’s?
Today's upgrade KDE Plasma Logs Out to a Black Screen
What happens if you enter a shutdown command?
At the same time I’m experiencing a strange problem, the performance of KDE’s animations is significantly degraded, the packages on my system are up to date, and I enabled the archlinuxcn source during the rolling updates
You mean you added an unsupported and incompatible repository?
Thats also not going to help.
If you were ever going to do such a thing on manjaro it would have to be on Unstable branch. Otherwise it would almost certainly break things.
It might break things there too … but on branches other than Unstable the packages would not line up at all… you would be in a partial upgrade state.
Anyhoo … besides all that … maybe it is the same as the other saved sessions, as I already noted above.
And on other topics:
3 Likes