Bug 507321 - [Privacy risk] Screen locker: Application content is visible for ~400 ms after returning from Sleep
Summary: [Privacy risk] Screen locker: Application content is visible for ~400 ms afte...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.3.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-21 17:41 UTC by Alexander Potashev
Modified: 2025-07-22 13:42 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Potashev 2025-07-21 17:41:36 UTC
SUMMARY
Screen locker: Application content is visible for ~400 ms after returning from Sleep.

STEPS TO REPRODUCE
1. Power Management settings: "When laptop lid closed: Sleep"
2. Screen Locking settings: "Lock after waking from sleep" in enabled.
3. Open some apps on a laptop.
4. Close laptop lid. Wait a few seconds for laptop to go to Sleep.
5. Open laptop lid.


OBSERVED RESULT
Application(s) and all their window content is visible for ~400 ms. After that, the screen locker UI appears on screen.

This is a privacy and security risk: an unauthorized person may get access to sentitive data, including credentials/passwords if they were on screen before closing laptop lid.

EXPECTED RESULT
Screen locker UI (or at least a black screen) should appear immediately after returning from Sleep.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux rodete 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.12.27-1rodete1-amd64 (64-bit)
Graphics Platform: X11
Processors: 14 × Intel® Core™ Ultra 7 165U
Memory: 62.3 GiB of RAM
Graphics Processor: Intel® Graphics

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2025-07-22 13:42:04 UTC
>Graphics Platform: X11

This is known and not fixable. There are issues below us in the stack. It's one of the we're moving to wayland.

There's a dupe somewhere with more details, I've seen your name on bugzilla enough to know you'll be able to find it.