It appears that these problems are indeed not caused by a bug in gnome-power-manager. In my case, the lock only persists when using the Indicator-Applet-Session or Gnome-Do to initiate the suspend. Suspending with the Shut Down-applet or the dedicated sleep key on my notebook follows the gconf settings. The Indicator-Applet-Session completely bypasses the gnome-power-manager according to bug 501252 so it's logical the gconf setting has no effect. I suspect the same applies for Gnome-Do.
- addressing to devicekit-power directly with the command:
dbus-send --print-reply --system --dest=org.freedesktop.DeviceKit.Power /org/freedesktop/DeviceKit/Power org.freedesktop.DeviceKit.Power.Suspend
I've put this last line in a bash script that I can execute quickly with Gnome-Do, so I'm satisfied for the moment.
It appears that these problems are indeed not caused by a bug in gnome-power- manager. In my case, the lock only persists when using the Indicator- Applet- Session or Gnome-Do to initiate the suspend. Suspending with the Shut Down-applet or the dedicated sleep key on my notebook follows the gconf settings. The Indicator- Applet- Session completely bypasses the gnome-power-manager according to bug 501252 so it's logical the gconf setting has no effect. I suspect the same applies for Gnome-Do.
Workarounds that have worked for me are:
- disable screen lock altogether in gconf-editor > desktop > gnome > lockdown
- addressing to devicekit-power directly with the command: org.freedesktop .DeviceKit. Power /org/freedeskto p/DeviceKit/ Power org.freedesktop .DeviceKit. Power.Suspend
dbus-send --print-reply --system --dest=
I've put this last line in a bash script that I can execute quickly with Gnome-Do, so I'm satisfied for the moment.