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.
--
You received this bug notification because you are a member of Desktop
** Changed in: blueproximity (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1307163
Title:
not work gnome-screensaver-command -d
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?
--
You received this bug notification because you are a member of Desktop
Packages, which is
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.)
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.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
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).
--
You received this bug notification because you are a member of
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.
--
You received this bug
** Attachment added: strace gnome-screensaver-command -d
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1307163/+attachment/4114231/+files/deactivate.strace.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
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?
** Attachment
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: blueproximity (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
** Changed in: gnome-screensaver (Ubuntu)
Status: Incomplete = Confirmed
** Also affects: blueproximity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in
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
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!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
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?
** Changed in: gnome-screensaver (Ubuntu)
Importance:
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.
--
You received this bug notification because you are a member of Desktop
15 matches
Mail list logo
