Bug 266829

Summary: Add "lock screen when paired device is out of range" feature to bluedevil.
Product: [Plasma] plasmashell Reporter: Bruno <bruno.canning>
Component: Bluetooth in generalAssignee: David Rosca <nowrep>
Status: CONFIRMED ---    
Severity: wishlist CC: antonis+kdebugs, gassauer, heri+kde, jonathand131, KaiUweBroulik2, kde, Loci79, matofesi, MurzNN, niss24079, suppandi, toddrme2178
Priority: HI    
Version First Reported In: 6.2.4   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Bruno 2011-02-21 18:36:12 UTC 
Version:           unspecified (using KDE 4.4.4) 
OS:                Linux

I would like to see the functionality provided by KBlueLock in kbluetooth implemented in bluedevil please.

For the benefit of those unfamiliar with this, KBlueLock locks the screen when a device paired with the PC in kbluetooth is moved out of range and unlocks the screen when the device reappears. This is useful for those working in a shared environment who frequently need to leave their PC unattended for short periods of time and wish to avoid the hassle of manually locking the screen on each occasion.

Reproducible: Always

Steps to Reproduce:
N/A

Actual Results:  
N/A

Expected Results:  
N/A

Reading some of the bugs/wishes for kbluetooth, a user requested that if the PC had a removable bluetooth adaptor and the adaptor was removed whilst the screen was locked, the screen should stay locked until the user's password is entered. I would also imagine that users should be able to unlock the screen with their password in case the paired device is unavailable.

If it is decided to implement this feature, I think that bluedevil would then be a complete replacement for kbluetooth. Great work getting this far, folks.
Comment 1 Todd 2011-03-10 20:23:03 UTC 
I also agree this would be a very useful feature.
Comment 2 Kai Uwe Broulik 2011-03-10 20:34:36 UTC 
I recently read a nice article about how to implement this on Mac OS in c‘t magazine and now I defenitly want this for KDE :P
Comment 3 Lamarque V. Souza 2011-04-09 08:20:50 UTC 
*** Bug 179342 has been marked as a duplicate of this bug. ***
Comment 4 Lamarque V. Souza 2011-04-11 19:52:31 UTC 
*** Bug 238159 has been marked as a duplicate of this bug. ***
Comment 5 Lamarque V. Souza 2011-04-11 19:53:02 UTC 
*** Bug 233472 has been marked as a duplicate of this bug. ***
Comment 6 Lamarque V. Souza 2011-04-11 19:53:40 UTC 
*** Bug 216970 has been marked as a duplicate of this bug. ***
Comment 7 Lamarque V. Souza 2011-04-11 19:54:06 UTC 
*** Bug 214289 has been marked as a duplicate of this bug. ***
Comment 8 Lamarque V. Souza 2011-04-11 19:54:24 UTC 
*** Bug 179347 has been marked as a duplicate of this bug. ***
Comment 9 Lamarque V. Souza 2011-04-11 19:54:48 UTC 
*** Bug 163558 has been marked as a duplicate of this bug. ***
Comment 10 Lamarque V. Souza 2011-04-11 19:55:09 UTC 
*** Bug 163557 has been marked as a duplicate of this bug. ***
Comment 11 Michael F. 2012-01-23 16:12:29 UTC 
*** This bug has been confirmed by popular vote. ***
Comment 12 Murz 2013-09-12 06:01:51 UTC 
Is there any progress in bluetooth desktop locking for KDE 4.x?
At now I use Gnome Blueproximity app that works normally, but it can unlock screen only with ugly hack command "qdbus | grep kscreenlocker_greet | xargs -I {} qdbus {} /MainApplication quit".
Will be good that KDE SC have integrated app for bluetooth locking/unlocking, can you provide any plans or roadmap for this feature?
Comment 13 Murz 2013-09-12 06:04:22 UTC 
And maybe better to move this issue from Product solid to kbluetooth https://bugs.kde.org/describecomponents.cgi?product=kbluetooth ?
Comment 14 Kai Uwe Broulik 2013-09-12 06:06:37 UTC 
KBluetooth is unmaintaied, BlueDevil is a part of Solid, so the assignee is correct.
Comment 15 Nicolas Fella 2020-12-01 00:25:23 UTC 
*** Bug 411164 has been marked as a duplicate of this bug. ***