Comment 5 for bug 1307163

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?