Results 1 to 3 of 3

Thread: Forcing screensaver to unlock using blueproximity

  1. #1
    Join Date
    Jun 2008
    Location
    Kaneohe, HI
    Posts
    129

    Default Forcing screensaver to unlock using blueproximity

    Back when I used openSUSE 10.3 with KDE 3.5.x I used the KDE-specific version of blueproximity found here: K-Blueproximity KDE-Apps.org. The thing that made it great was that it integrated kscreensaver.

    It hasn't been updated in a couple years and isn't compatible with 4.3.x so I'm using the non-KDE-ified standard blueproximity package. For the most part it works. Based on comments I found somewhere I'm running the following command to lock the screen:
    Code:
    qdbus org.kde.screensaver /ScreenSaver Lock ; xset dpms force off
    and to unlock:
    Code:
    xset dpms force on ; killall -9 krunner_lock kblankscrn.kss
    .

    The problem is that the unlock command doesn't work. My monitors will reactivate and the screensaver will display but in order to actually unlock I have to hit a key/move the mouse and enter my password.

    My question is if anyone knows what the command should be to actually unlock the screen since the above doesn't work.

    In addition, there is the Proximity command field. Anyone know what this for?

  2. #2
    Join Date
    Jan 2009
    Location
    Castricum
    Posts
    11

    Default Re: Forcing screensaver to unlock using blueproximity

    Ok, I think I got it to work. This is under openSUSE 11.4 m6 using KDE 4.6:

    to lock the screen:
    Code:
    qdbus org.kde.screensaver /ScreenSaver Lock ; xset dpms force off
    and to unlock:
    Code:
    xset dpms force on ;  killall -9 kscreenlocker
    Further I have the following proximity details (the distances work for me)
    locking 7, 3 sec.
    unlocking 3, 2 sec.

    Hope this is of use to someone.

    Have fun!

    Philip.

  3. #3
    Join Date
    Jun 2008
    Location
    Kaneohe, HI
    Posts
    129

    Default Re: Forcing screensaver to unlock using blueproximity

    Excellent! That one change to kscreenlocker did it. Thanks much! I use 11.2 so it isn't just an 11.4 thing either.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •