[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2018-09-16 Thread Jarno Suni
Oh, I see. It does not work anyway in 18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536237 Title: gnome-screensaver-command --lock starts the daemon To manage notifications about this bug

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2018-09-16 Thread Theo Linkspfeifer
Tested in 18.04, and the command did spawn gnome-screensaver --no- daemon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536237 Title: gnome-screensaver-command --lock starts the daemon To manage

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2018-09-16 Thread Jarno Suni
Bug #1777848 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536237 Title: gnome-screensaver-command --lock starts the daemon To manage notifications about this bug go to:

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2018-09-16 Thread Jarno Suni
And in 18.04 it is unable to start the lock even if the daemon is running, and still exits with 0, so it is badly broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536237 Title:

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2018-09-16 Thread Jarno Suni
Oddly in Xenial, where gnome-screensaver is 3.6.1-7ubuntu4 the bug occurs, but in 18.04, where the version is 3.6.1-8ubuntu3, it does not launch the daemon, but exits with 0 without locking. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2016-01-28 Thread Jarno Suni
It could be that this is by design, so that gnome-screensaver locks whenever it is possible. It just makes script xflock4 from xfce4-session more difficult to implement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2016-01-24 Thread adbot
I can confirm that for me the daemon is not automatically launched when it is not already running. --gnome-screensaver 3.6.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536237 Title:

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2016-01-24 Thread Jarno Suni
Well, here (in Xubuntu Linux) it launches automatically: $ killall light-locker light-locker: no process found $ gnome-screensaver --version gnome-screensaver 3.6.1 $ ps aux | grep [g]nome-screensaver $ gnome-screensaver-command --lock $ ps aux | grep [g]nome-screensaver myusername9731 0.0

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2016-01-20 Thread Jarno Suni
They tell this has been fixed in 2010, but apparently not for Ubuntu: https://bugzilla.gnome.org/show_bug.cgi?id=629740 ** Bug watch added: GNOME Bug Tracker #629740 https://bugzilla.gnome.org/show_bug.cgi?id=629740 -- You received this bug notification because you are a member of Ubuntu