not work gnome-screensaver-command -d

[Pavlo Bohmat]

After the upgrade not work gnome-screensaver-command --deactivate
jwm + gnome-screensaver impossible to see video because not working gnome-screensaver-command -d

not works:
gnome-screensaver-command -a
gnome-screensaver-command -d
gnome-screensaver-command -l

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-screensaver 3.6.1-0ubuntu13
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Apr 13 18:47:32 2014
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GsettingsGnomeSession:
 org.gnome.desktop.session session-name 'ubuntu'
 org.gnome.desktop.session idle-delay uint32 0
InstallationDate: Installed on 2014-04-11 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140410)
SourcePackage: gnome-screensaver
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for your bug report. That's not really a gnome-screensaver bug, that component stopped being used in trusty. The videoplayer should inhibit locking without you having to use those commands though. What video player do you use?

[Pavlo Bohmat (bohm)]

After new upgrade -a -l work, but -d not. Firefox+flashplayer on the jwm.
Video players (totem, mplayer) themselves stop the screensaver, but I need to force stop 'gnome-screensaver-command -d' which does not work.

[Pavlo Bohmat (bohm)]

Already release 14.04, but does not help gnome-system-monitor 'Stop (End/Kill)Process' and 'killall gnome-screensaver' it strongly enrages. Please fix it!

[Jeremy Collins (jeremy+ubuntu)]

I have the same issue with my blueproximity unlock script as it issues the same gnome-screensaver-commands. After upgrading to 14.04 the unlock script broke, while the lock script still works.

I think the point here is that "gnome-screensaver-command -d" isn't functioning while "gnome-screensaver-command -l" and "gnome-screensaver-command -a" are. The component is still installed in trusty and now is half working. If its not used it should be removed or if its left it should work. From an end user prospective this doesn't seem to make sense to have a partially functioning ap; it looks as though its gnome-screensaver-command half working to those not aware of the lock screen change in Trusty.

I'm not sure whats broken or where to file it if not here? Should this bug be filed as a bug against the new lockscreen instead of gnome-screen-saver for not unlocking when gnome-screensaver-command requests? Or is the issue with gnome-screensaver for not issuing the correct unlock request for the new lockscreen?

[Launchpad Janitor (janitor)]

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

[Vojtěch Látal (vojtik)]

Hi, I am also using blueproximity as Jeremy, so I am affected by this bug.

I have tried strace-ing both commands, attaching their outputs:
gnome-screensaver-command -a
gnome-screensaver-command -d

Hope that will help someone.

 Is there something I can provide to solve this bug?

[Andy Buchanan (andy-buchanans)]

I too am affected by this problem as I used blueproximity under 12.04 to lock and unlock my desktop, and it is now unable to unlock it again with gnome-screensaver-command -d.

What is the solution to this? I need to be able to programmatically unlock the desktop.

[Bruno Molino (molino-bruno)]

Same bug here. I've installed and configured Blueproximity (I've used it for months with 10.04 but never with 12.04) but gnome-screensaver-command -d seems not work. Same issue with xscreensaver (xscreensaver-command -d).

[Boris Boruchovich (bboruchovich)]

I too am affect by this. gnome-screensaver-command -d was working with Ubuntu version 12.04. It is not working with Ubuntu 14.04. Is there a recommended way to unlock the screensaver programmatically?

[Ben (benshayden)]

I think I've found a work-around.
Open dconf-editor.
Search (ctrl+f) for "screen-keyboard-enabled".
Turn it on.
(I have both org.gnome.desktop.a11y.applications and org.cinnamon.desktop.a11y.applications. I'm not sure which you need.)

http://bazaar.launchpad.net/~unity-team/unity/trunk/view/head:/lockscreen/LockScreenController.cpp
http://bazaar.launchpad.net/~unity-team/unity/trunk/view/head:/lockscreen/LockScreenSettings.cpp
The Unity LockScreenController falls back to a org.gnome.ScreenSaver dbus proxy when settings->use_legacy, which is set to true when either the screen reader or the on-screen keyboard is enabled.

[Ben (benshayden)]

On the command line:

gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled true

The on-screen keyboard appears when you first sign-in but you can close it.

[Andrew Bolster (bolster)]

Confirmed Again with BlueProximity and 14.10.

Suggest that while this is a low priority for gnome-screensaver, it's a pretty high priority for BlueProximity, as locking and unlocking is a large portion of its use case.