I've been using this as a proximity command instead:
dbus-send --type=method_call --dest=org.gnome.ScreenSaver
/org/gnome/ScreenSaver org.gnome.ScreenSaver.SimulateUserActivity
I'm not sure whether numerigraphe's suggestion to simply use the '-d'
option has the same effect.
--
You received th
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: blueproximity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/837300
Title:
I suggest using gnome-screensaver-command -d instead, just to make sure the
screen is unlocked.
Lionel Sausin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/837300
Title:
gnome-screensaver proximity
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/837300
Title:
gnome-screensaver proximity command doesn't exist
To manage notifications about this bug go to:
https://bugs.launc
--poke/-p did exist until gnome-screensaver version 2.91.91, when it was
removed: http://mail.gnome.org/archives/ftp-release-
list/2011-March/msg00074.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
