Hi all,
I have two similar machines that have AMD CPU and GPU.
On one machine I installed a fresh Manjaro Plasma release from the manjaro-kde-24.1.0-241001-linux610.iso support. I think this is aligned to the 2024-10-01 stable update.
The problem is that if I try to terminate the session in any manner ( restart, power off, close session) the screen becomes black end I see only the mouse cursor.
The machine doesn’t accept any command and I have to physically power off the machine.
As a workaround I issue a shutdown from a terminal instead of using the Plasma functions.
I have done all the upgrades including the 2024-10-10 but nothing changes.
On the other machine I installed Manjaro Plasma two months ago and I upgraded whenever an upgrade becomes available. On this machine Plasma works correctly and I have no problems.
I’m using an X11 session but the problem is the same if I use wayland.
The solution is in the Update Announcement’s “Known issues and solutions” post:
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”.
Well, I can try the empty session workaround; but restoring by hand at every start a session with 9 applications on 6 desktops is more annoying than rebooting from a terminal.
Anyway this don’t explain why there is no problem with the machine that was installed with a previous Manjaro version and then updated.
I think I read something on this forum a few days ago that said the session saver could be reactivated after it has been switched off and the machine successfully rebooted (although I’m not 100% sure about that). Also, that fix may work only on Plasma X11, as there is a known bug with session restore on Wayland that has (supposedly) been fixed in the just-released Plasma 6.2.
Fixed a bug that caused real-fake-session-restore to not work properly on Wayland (David Edmundson, Plasma 6.2.0. Link)
However, that bug has been reopened, as there is some argument about whether the fix is complete, as it is still a “fake session restore”, and some believe it should remain open until it becomes a proper session restore feature: