Bug 424979 - Notify the user why screen locker was blocked in Xorg (e.g. due to a popup menu or full-screen effect open)
Summary: Notify the user why screen locker was blocked in Xorg (e.g. due to a popup me...
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.2.4
Platform: unspecified Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2020-08-03 22:38 UTC by Alexander Shchadilov
Modified: 2024-12-18 19:03 UTC (History)
2 users (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 Alexander Shchadilov 2020-08-03 22:38:05 UTC
There is a known problem on Xorg with situations when some application prevents locking screen; it was described as unfixable in Bug 383327.
Some related work was done here:
https://phabricator.kde.org/D20804
The number of screen locker attempts was increased to 3, also an "AboutToLock" signal was introduced offering a possibility for 3rd-party apps to change their behaviour right before screen lock attempt.
Plasma could launch a notification when screen locker fails due to Xorg problems.  At least it will serve as an explanation for a user who will get a basic understanding of why a DE's security feature is malfunctioning. Text variant: "Some application prevented screen locking".
A better text label might include an application's name, but I don't know if this is technically possible. Currently log doesn't get further than "Could not establish screen lock". Knowing an app's name will make some workarounds possible, also in this case users might show it to developers and, who knows, maybe somebody will implement "AboutToLock" monitoring in their code.