Bug 214289 - bluelock seems not to save the device id and does not lock screen on absence
Summary: bluelock seems not to save the device id and does not lock screen on absence
Status: RESOLVED DUPLICATE of bug 266829
Alias: None
Product: kde-bluetooth
Classification: Unmaintained
Component: kbluelock (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Mattia Merzi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-12 18:37 UTC by Ferdinand Gassauer
Modified: 2011-04-11 19:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ferdinand Gassauer 2009-11-12 18:37:37 UTC 
Version:            (using 4.3.3 (KDE 4.3.3) "release 1", KDE:43 / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.37-0.1-default

0.4RC2
the device is detected, but IMHO not saved nothing happens if I turn off bluetooth on the device (or is there a longer delay  and / or keyboard activity detection ?)

the symbol for locking (pressed/unpressed) is difficult to recognize. (not userfriendly)
IMHO should get a different symbol lock open/closed or red crossed.
Comment 1 Lamarque V. Souza 2011-04-11 19:54:06 UTC 
Since kbluetooth is unmaintained (http://bugs.kde.org/270702) I am marking this bug as duplicate of the Bluedevil bluelock request feature.

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