Ubuntu
blueproximity package

gnome-screensaver-command no longer supports -p/--poke

Bug #938830 reported by PhilDubach
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
blueproximity (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu 11.10
blueproximity 1.2.5-5
gnome-screensaver 3.2.0-0ubuntu1

On Oneiric, the blueproximity preference dialog comes pre-populated with lock/unlock/proximity action commands for gnome-screensaver and xscreensavers. For gnome-screensaver, the suggested action command is currently 'gnome-screensaver-command -p', which is no longer a supported option since gnome-screensaver introduced the new inhibit scheme.
As a result, when choosing this proximity command, the scren will still lock after the timeout expires, even if the paired device is in the specified range (blueproximity state: active)

On Oneiric, the following can be used instead as a proximity command to reset the screensaver timeout:

dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.SimulateUserActivity

See original description
PhilDubach (phildubach)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in blueproximity (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.