*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY In KDE Neon 6.1, when I'm trying to make use of X11 instead of Wayland, I cannot logout, shutdown, or restart normally. Wayland is NOT impacted. STEPS TO REPRODUCE 1. Upon reaching the login screen, specify the Plasma (X11) desktop environment. 2. Complete the login process, activating aforementioned desktop environment. 3. Attempt to logout, shutdown, or restart. OBSERVED RESULT Black screen with cursor still present. The kwin/ksmserver process does not appear to terminate at all, leaving the default tty2 unusable. EXPECTED RESULT kwin/ksmserver should terminate gracefully and swiftly instead of hanging and not doing anything else, completing the logout/shutdown/restart action. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION WORKAROUNDS USED To complete the process, I either need to send a SIGHUP, SIGTERM, or SIGKILL to /usr/bin/ksmserver to achieve a logout, or pass the `reboot` or `shutdown` commands to another tty session.
can confirm this x11 arch linux kde plasma 6.1 kwin, logout prompt failing see here: https://0x0.st/XTdh.txt full session journal: https://0x0.st/XTdO.txt
I can also confirm this, same log as @nyl
Same problem on amdgpu, but no such problem on nvidia.
(In reply to VK from comment #3) > Same problem on amdgpu, but no such problem on nvidia. I can confirm problem DOES exist on nvidia
On plasma-workspace 6.1.1-1 and 6.1.0-1 the problem still exists.
I am running Plasma 6.1.1 with nvidia 555 driver. Logout fails on x11 but works properly with wayland.
I experience similar problems. Session doesn't end when logging out, leaves a blank screen with the mouse cursor. I'm using X11, happens with and without the external screen attached. Using KDE neon with Plasma 6.1.2, problems started after an upgrade to 6.1.0.
On plasma-workspace 6.1.3-1 the problem still exists.
In System settings > Session > Desktop Session, select 'Start with an empty session' and reboot. The problem disappears: plasma 'Restart' and 'Shut down' work as expected.
So this bug exists across all graphical environments (Intel, nVidia, AMD) and still exists on the latest version of Plasma, breaking session saving. Can we get this escalated somehow?
On openSUSE Slowroll i have the same problem. When I activate “manually saved session”, the shutdown fails. However, if I set it to “at last logout” everything works fine. The latest Slowroll, did not solved the problem!
Reverting https://invent.kde.org/plasma/plasma-workspace/-/commit/0857d18dfc3fc870a7f768731fdf46dc3abc5f8f was shown to "fix" this problem, but of course it is no solution.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4684
Any affected user can test https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4684 ?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4731
Git commit 9bd2dcc8a785d977cdf67a7cbb467423803e3327 by Fushan Wen, on behalf of David Edmundson. Committed on 20/09/2024 at 13:01. Pushed by fusionfuture into branch 'master'. startkde: Disable session management in our session management We have two types of session restore, ksmserver for ICE clients and a small fallback app that runs after ksmserver for any stragglers. This fallback app is a gui application, as such it will try and connect to ksmserver. This isn't useful and can cause a block. M +1 -0 startkde/session-restore/restore.cpp M +1 -0 startkde/session-restore/save.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/9bd2dcc8a785d977cdf67a7cbb467423803e3327
I just tried https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4684 and it did /not/ work. I did this after building with the patch: 1. Create a new user so there is no old user cruft to confuse things. 2. Log on. 3. Log off. This worked 4. Logged on again. 5. Changed the Session Restore setting to When session was manually saved. 6. Added a konsole to the desktop. 7. Saved the session. 8. Log off. This hung. I waited 30 minutes, it still hadn't logged off so I killed ksmserver and the logoff then completed. I will now try the new patch https://invent.kde.org/plasma/plasma-workspace/-/commit/9bd2dcc8a785d977cdf67a7cbb467423803e3327
Git commit 792586f26e532dc049fc2f613d9a77db976f9054 by Fushan Wen. Committed on 20/09/2024 at 13:02. Pushed by fusionfuture into branch 'Plasma/6.2'. startkde: Disable session management in our session management We have two types of session restore, ksmserver for ICE clients and a small fallback app that runs after ksmserver for any stragglers. This fallback app is a gui application, as such it will try and connect to ksmserver. This isn't useful and can cause a block. (cherry picked from commit 9bd2dcc8a785d977cdf67a7cbb467423803e3327) Co-authored-by: David Edmundson <kde@davidedmundson.co.uk> M +1 -0 startkde/session-restore/restore.cpp M +1 -0 startkde/session-restore/save.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/792586f26e532dc049fc2f613d9a77db976f9054
The patch https://invent.kde.org/plasma/plasma-workspace/-/commit/9bd2dcc8a785d977cdf67a7cbb467423803e3327 worked for me. Thanks.
*** Bug 487616 has been marked as a duplicate of this bug. ***
*** Bug 493952 has been marked as a duplicate of this bug. ***