Bug 234925 - powerdevil screen locking information leakage
Summary: powerdevil screen locking information leakage
Status: RESOLVED DUPLICATE of bug 224517
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: powermanagement-daemon (show other bugs)
Version: unspecified
Platform: Debian testing Unspecified
: NOR normal
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-20 22:42 UTC by Florian Kriener
Modified: 2010-11-10 01:08 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Kriener 2010-04-20 22:42:23 UTC 
Version:            (using KDE 4.4.2)
Installed from:    Debian testing/unstable Packages

I configured powerdevil to lock the screen on resume, but when I suspend and resume the screen is not immediately locked and the screen contents are shown. I do not like that, because it allows an attacker to read my screen.
Comment 1 Scott Jacobsen 2010-05-18 22:20:08 UTC 
I also sometimes can see my screen contents when I lock the screen through the 'leave' menu, and sometimes on suspend to RAM/restore. It is intermittent. Sometimes I can see the contents, sometimes I cannot. I have a laptop with an attached monitor using NVIDIA TwinView to manage the monitors. I'm using KDE 4.4.2 on Ubuntu.
Comment 2 Jon Nelson 2010-05-29 20:29:43 UTC 
I see this too from time to time.
It's not a powerdevil issue specifically, I think, but rather a screensaver issue.
Comment 3 Otso Helenius 2010-10-05 19:38:35 UTC 
I had this same issue whenever I locked the screen and wanted to unlock it. Just before the unlock dialog appeared, the desktop flashed on the screen revealing whatever I had open when I locked it. This no longer happens in KDE 4.5.1 (Fedora 14 beta, intel display driver), so I suggest testing if it has been fixed for suspend as well.
Comment 4 Dario Freddi 2010-11-10 01:08:48 UTC 

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