Bug 329089

Summary:	Feature to not lock the screen while in a known secure location
Product:	[Plasma] plasmashell	Reporter:	Hrtmt Brng <hbrnng.sw_dev>
Component:	Screen locking	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	bshah, caco3, mgraesslin, nate, olaf.the.lost.viking
Priority:	NOR
Version First Reported In:	6.2.4
Target Milestone:	1.0
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Hrtmt Brng 2013-12-21 18:54:38 UTC

I have a cool feature request. Read first and think later about my suggestion below. :-)
Often I want that the screen will be locked when I go to suspend. But I need this behaviour if I am not at home. At home I do not need screen locking at all. The scenarios are the following:

I am at home and go to suspend. When I wake up the laptop and I am still at home I don't want that the screen is locked. When I wake up and I am not at home, the screen should be locked.

My suggestion is:
The screen will be always locked when going to stand by. There is no change. But connecting to my home's wireless LAN unlocks the screen.

Reproducible: Always



Expected Results:  
In the energy configuration or screensaver configuration I can tell the system that locking and screensaver will be disabled in a specific wireless lan networt.

Comment 1 Martin Flöser 2015-01-23 09:54:39 UTC

I like the idea in general and had thought about similar ideas myself. E.g. use bluetooth proximity to smart phone, interact with kde connect, etc.

What I'm mostly concerned at the moment and why I haven't started implementing it is the added complexity both in the lock screen architecture as well as in the configuration dialog.

Comment 2 CaCO3 2015-01-27 22:10:40 UTC

I also would welcome this feature.
I unlock my phone when my smart watch is paired. Using my home network would also be great.

Comment 3 Martin Flöser 2015-12-15 16:56:37 UTC

as a note: one can use kdeconnect to inhibit the screenlocker.

Comment 4 Martin Flöser 2016-05-09 06:13:20 UTC

*** Bug 362763 has been marked as a duplicate of this bug. ***

Comment 5 OlafLostViking 2016-05-09 06:49:38 UTC

Martin marked "my" bug as duplicate; thank you - I don't understand how I could miss this one when searching. Sorry!

But just as an additional comment (and to make sure Martin is even more frightened by the complexity ;-p ): this bug report here talks about unlocking after a suspend/resume cycle, which I like as an idea, too. In my bug report I talked about inhibiting locking the screen (after X minutes) when in a specific WiFi network (but still keep it locked when it was locked beforehand or manually). Just semantics, I guess.

Comment 6 Hrtmt Brng 2016-05-09 08:30:34 UTC

I think we are talking about nuances of the same idea. But Olaf, you are right. It is a slightly a different feature. But I suppose the one who hopefully implements this some day will be aware of the consequences and finds a nice solution. For instance leaving my home with a computer that is not locked, could be a security risk. So, perhaps inhibiting the locking is more dangerous than unlocking by SSID. But having a computer outside my home that has no auto locking after x minutes is also a security risk.