K.S. Bhaskar on 9 Aug 2011 15:27:58 -0700

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[PLUG] blueproximity fails to unlock under KDE

I have my laptop paired with my BlackBerry Storm2 via Bluetooth, and
use blueproximity to detect when I walk away and automatically blank
the screen with "qdbus org.kde.screensaver /ScreenSaver
org.freedesktop.ScreenSaver.Lock" as the locking command and "killall
kscreenlocker" as the unlocking command.  These are the right commands
("qdbus org.kde.screensaver /ScreenSaver
org.freedesktop.ScreenSaver.Lock ; sleep 2 ; killall kscreenlocker"
blanks the screen for a couple of seconds and then restores).

The problem is that when I walk away, the screen blanks, but when I
return it doesn't unblank.  Worse yet, even when the phone has the
laptop flagged as trusted, and the laptop has the phone as trusted,
when I return, I get prompted for a verification that each of them is
displaying the same number, and they become untrusted.

I have tried flagging the BB as trusted with bluedevil.  I have also
tried flagging it as trusted with bluez-test-device ("sudo
/usr/bin/bluez-test-device trusted 12:34:56:78:9A:BC yes" followed by
restarting the Bluetooth service).  Neither sticks if I walk away and

I have not been able to find a solution to the problem - this works
well under Gnome, but I am trying KDE because I intensely dislike both
the Gnome 3 shell and Unity (yes, I know I can use Ubuntu Classic for
now, but its days seem to be limited).

Thanks in advance.

-- Bhaskar

Windows does to computers what smoking does to humans
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug