As a crude workaround, running this in a terminal window will detect
unlocks and run xrandr to detect the screen again:
dbus-monitor --session "type='signal',interface='org.gnome.ScreenSaver'"
| ( while true; do read X; if echo $X | grep "boolean false" &>
/dev/null; then xrandr; fi done )
--
Yo
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
*** This bug is a duplicate of bug 837300 ***
https://bugs.launchpad.net/bugs/837300
Public bug reported:
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 gn
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/25990795/Dependencies.txt
--
gpsd depends on nonexistent /lib/udev/hotplug.functions
https://bugs.launchpad.net/bugs/367197
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: gpsd
When plugging in a USB GPS receiver (GlobalSat ND-100 in my case), udev
tries to add the device to the running gpsd (assuming gpsd is correctly
configured, see below).
The script executed by udev is /lib/udev/gpsd.hotplug.wrapper. This script
depen
