Bug 498003 - Desktop shows briefly before lock scren as laptops wake up from S3/S0ix
Summary: Desktop shows briefly before lock scren as laptops wake up from S3/S0ix
Status: RESOLVED DUPLICATE of bug 485085
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (show other bugs)
Version: 6.2.4
Platform: Other Linux
: NOR critical
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-29 03:24 UTC by Mingcong Bai
Modified: 2024-12-30 14:00 UTC (History)
1 user (show)

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


Attachments
Lock screen delay (2.47 MB, video/mp4)
2024-12-29 03:34 UTC, Mingcong Bai
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mingcong Bai 2024-12-29 03:24:56 UTC
With Plasma 6 (since at least 6.2, when I upgraded), the lock screen only displays with a second-long delay (potentially longer when battery is low) when I open my laptop's lid (waking up from suspend). During this interval, KDE shows a *live* desktop as though the screen was not locked and only switches back to the lock screen after that delay. This issue is only reproducible on X11.

This seems like a pretty severe security risk? It would only take enough tries for my desktop to become vulnerable. For your reference, this issue had been found in GNOME and MATE before:

- https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/830348
- https://github.com/mate-desktop/mate-screensaver/issues/145

Only on Plasma, the delay can be much longer before the lock screen was shown.

I have filmed this behaviour to better explain what I mean.
Comment 1 Mingcong Bai 2024-12-29 03:34:49 UTC
Created attachment 176936 [details]
Lock screen delay
Comment 2 cwo 2024-12-30 14:00:10 UTC
Thanks for the bug report! There already is an issue filed for this, marking it as a duplicate of that one.

I can confirm that it does not happen with Wayland; the lock appears immediately.

*** This bug has been marked as a duplicate of bug 485085 ***