https://bugs.kde.org/show_bug.cgi?id=455360
Bug ID: 455360
Summary: Screen saver activates but auto lock screen doesn't
(security issue?)
Product: plasmashell
Version: 5.24.5
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: catcool...@gmail.com
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
After recent plasma's screensaver behavior changes, plasma now doesn't take
into account screensaver inhibitors that come from non focused apps. This is a
correct behavior, however, while screen dimming works in that case, automatic
screen locking doesn't work. Some apps do dim screen inhibiting randomly (for
example, steam) and this can lead to unexpected results, as the user may think
that if the screen turns off and nothing interferes with it, then the system
should be locked as specified in the settings, but because it doesn't trigger
screen locking, unwanted persons can access the OS.
STEPS TO REPRODUCE
1. Set both screen dimming and auto locking timeout to 1 minute
2. Open some video in a chromium (so it will inhibit screen dimming)
3. Minimize this window
OBSERVED RESULT
Screensaver works but after 1 minute OS is still unlocked
EXPECTED RESULT
Both screensaver and automatic screen locking works
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
ADDITIONAL INFORMATION
Wayland/Xorg
--
You are receiving this mail because:
You are watching all bug changes.
