Bug 509079 - Forcible termination of lock screen kills the entire graphical session in KDE Wayland
Summary: Forcible termination of lock screen kills the entire graphical session in KDE...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.3.6
Platform: Other Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-03 16:40 UTC by alerikaisattera
Modified: 2025-09-04 10:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description alerikaisattera 2025-09-03 16:40:56 UTC
SUMMARY
Forcible termination of lock screen causes plasmashell to crash, which kills the entire graphical session in KDE Wayland

STEPS TO REPRODUCE
1. Run a KDE Wayland session
2. Forcibly terminate the lock screen

OBSERVED RESULT
The entire GUI session is terminated

EXPECTED RESULT
The lock screen is terminated

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION

Coupled with https://bugs.kde.org/show_bug.cgi?id=505173, this leads to a chance that an unlock attempt during the passwordless unlock interval leads to a guaranteed failure of entire GUI session
Comment 1 Bug Janitor Service 2025-09-03 17:33:41 UTC
Thank you for the bug report!

However Plasma 6.3.6 no longer receives updates or maintenance from KDE; active versions are 6.4 or newer. Please upgrade to an active version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one.

If you need help with Plasma 6.3.6, please contact your distribution, who bears the responsibility of providing help for older releases that are no longer receiving updates from KDE.

If you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Comment 2 Kai Uwe Broulik 2025-09-04 10:08:24 UTC
Not entirely sure what you expect but the goal is that the session can never be unlocked by crashing or killing the greeter.

You probably want to gracefully unlock the system by using loginctl unlock-session