Bug 113746

Summary: Wish: "transparent" screenlock, such that all activity on screen is displayed.
Product: [Unmaintained] kscreensaver Reporter: Nathaniel Taylor <kden>
Component: generalAssignee: kscreensaver bugs tracking <kscreensaver-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: medhefgo, mgraesslin, vemod, zyagon
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Nathaniel Taylor 2005-10-03 00:07:25 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

Locking a screen is clearly often desirable.

But all KDE "screensavers" I know of either lose the desktop image entirely or
somehow play with a frozen version of the moment at which the screen was locked.

I now use "xtrlock" which simply stops keyboard and mouse being used to influence the display until the password is given:  then the clock is still useful, video can be watched, new email seen -- and cats and children can't damage anything.  

It would be nice to have such a screenlock option for when the lock desktop button in KDE is used, instead of having to have a true "screensaver".
I'm surprised it doesn't already exist in KDE (or will you tell me that it does!).
Comment 1 Oswald Buddenhagen 2007-05-12 12:46:16 UTC
this can have serious security implications. ok, maybe not more serious than the screen savers that take a snapshot of the desktop and distort it somehow ...
Comment 2 Oswald Buddenhagen 2010-10-23 21:18:56 UTC
*** Bug 194428 has been marked as a duplicate of this bug. ***
Comment 3 ola 2011-05-27 20:27:02 UTC
#1 it depends on the usage scenario, if for example keyboard/mouse input could be blocked on monitoring/trading screens that are sometimes left unattended and are intended mainly to display information it would clearly improve the security. 

or another scenario would be embedded devices/servers that are not supposed to take kb/mice input during normal operation. i'm not sure how difficult it would be to implement this feature but if any dev is interested and needs hardware/funding/whatever please let me know.
Comment 4 Nathaniel Taylor 2011-05-28 13:33:24 UTC
Bearing in mind that Xtrlock already exists as an example, and that the only requirement is to prevent /input/ to the X-server, I'd hope it's pretty easy to implement.  More so than also displaying different images, like other screensavers.

I don't see there's any "security" issue.  If a user chooses to lock the screen with a lock that keeps showing what's happening, then people can see what's happening ... that's the idea.   If a user unlocks a normal screenlock, then people can not only see but even change things ... yet we don't prevent screensavers from unlocking on security grounds.

I'm surprised there aren't more people who'd find this type of lock to be useful, i.e. where there's only an issue of wanting no 'damage' to their  files/settings, but no problem with the desktop being seen.   For me, xtrlock comes in handy every day, and no other screen lock is useful.  It's just a shame that it isn't in KDE so that more people can see the benefit.  (I found it only by telling an inquisitive friend exactly what I /wanted/ -- a few months later, he'd found xtrlock when looking for other things.  How much better just to find it in the list of KDE screenlock options.)
Comment 5 vemod 2014-03-06 14:03:52 UTC
Common guys, its not complicated to add this feature.
I have several monitoring machines and kde widgets won't help if i want to have fullscreen opera running in background. And leaving unlocked PCs is the security issue rather showing whats going on in the background. 

I tried transparent image, changing background color to "transparent" in main.qml. But I get white background instead. Seems the screen locker gets initialized with white background then an image gets applied on top. 

Can you please tell me at least how to get rid of white background?

Thanks
Comment 6 Martin Flöser 2015-01-23 09:15:14 UTC
The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this feature request won't be implemented as it doesn't apply to our current version any more. Furthermore it is a security design choice that the screen content is blanked behind the screen locker. A transparent look-through is not possible as it would circumvent the security targets of the lock screen.

I want to thank you for your feature suggestion and I'm sorry that we were not able to provide the requested feature before we retired the affected component.