Bug 404063

Summary: Show password prompt immediately if lock screen is displayed after a wake-from-sleep
Product: [Plasma] plasmashell Reporter: Nate Graham <nate>
Component: Theme - BreezeAssignee: visual-design
Status: CONFIRMED ---    
Severity: wishlist CC: aspotashev, bugseforuns, plasma-bugs
Priority: NOR    
Version First Reported In: 5.14.90   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=469810
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Nate Graham 2019-02-07 17:08:16 UTC 
The two-stage lock screen design serves its purpose to allow people to display a pretty image/slideshow/animated-thing-that-we-don't-call-screensaver after the screen is locked, but it's slightly annoying when you wake from sleep, because the interactive UI isn't visible until you interact some way. Yes, it's true that you can just immediately start typing, but this is not super obvious and we get complaints about it.

Suggestion: when the lock screen is displayed immediately after waking from sleep, show the interactive UI rather than the wallpaper-and-clock view. The standard timeout can apply so that it goes back to the wallpaper-and-clock view after 10 seconds.
Comment 1 Nate Graham 2022-05-15 03:30:32 UTC 
This appears to have been done for Plasma 5.25.
Comment 2 Patrick Silva 2022-05-20 10:50:15 UTC 
Weird. I can reproduce on neon unstable after suspending to RAM via kickoff.
Comment 3 Patrick Silva 2022-06-28 20:33:42 UTC 
Is this bug really fixed for you Nate? I can also reproduce on Arch running Plasma 5.25.2.
Comment 4 Nate Graham 2022-06-28 20:37:09 UTC 
Thanks for the reminder. No, it's actually only half-fixed for me.

I use fingerprint unlocking, and I notice that the prompt is shown immediately if PAM responds quickly enough to show the "place your finger on the fingerprint reader" message by the time the screen wakes up. If it's slower than that because the message appears later, then the prompt is not automatically shown.

For the non-fingerprint case, it is probably never shown, but I didn't notice that since I'm using fingerprint auth.

So really, the root cause is still an issue, because we make showing the password prompt conditional based on some PAM thing, rather than just always doing it.