Can this bug still be reproduced with 16.04 and/or 16.10? If so, what
can be done upstream by GNOME and/or Ubuntu? What are urls to upstream
bugs in GNOME?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can note that this still happens in Trusty, and since bug #726471 is
fixed, this user level workaround now works:
mkdir -p ~/.local/share/dbus-1/services
cat EOF ~/.local/share/dbus-1/services/org.gnome.ScreenSaver.service
[D-BUS Service]
Name=org.gnome.ScreenSaver
Exec=
EOF
On a side note, I
Good luck getting the gnome-screensaver guys to acknowledge that some
people want to use a non-gnome screensaver :)
Please explain again why this is a bug in gnome-screensaver? If you call
org.gnome.ScreenSaver, expect gnome-screensaver to act on it. The
solution would be something like Julien
The original question has not been addressed: should either gnome-
screensaver itself, or the dbus org.gnome.ScreenSaver Exec= command,
check for a running xscreensaver and abort?
Thus, this bug should stay in gnome-screensaver. If you really want to
sweep it under the carpet, mark it as WONTFIX.
As per my above comment, the original issue was not addressed
** Package changed: lxde-common (Ubuntu) = gnome-screensaver (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726480
Title:
This needs to be fixed upstream. Could you please file a bug against
gnome-screensaver et bugzilla.gnome.org and link the bug here. Thanks.
** Changed in: gnome-screensaver (Ubuntu)
Status: New = Confirmed
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided = Low
--
You
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726480
Title:
gnome-screensaver forces itself upon xscreensaver users
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
My remark about processes that pull the trigger was based on an
empirical observation: if I start LXDE with a disabled
/etc/xdg/autostart/update-notifier.desktop, xscreensaver runs, and there
is no gnome screensaver. Whenever one of nm-applet or update-notifier
starts, dbus loads
If your desktop environment uses xscreensaver, you should simply not
have the gnome-screensaver package installed. If the gnome-screensaver
package isn't installed, the dbus service file isn't there.
** Package changed: gnome-screensaver (Ubuntu) = lxde-common (Ubuntu)
--
You received this bug
I am reassigning this to lxde in case something in there is pulling
gnome-screensaver in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726480
Title:
gnome-screensaver forces itself upon
Apparently many developers have forgotten than Linux is a multi-user
system.
Some users log into LXDE, some into gnome. Both need to work.
I've spent many hours debugging this problem and even made the effort to
provide a workaround. The developers need to do their part.
LXDE is powerless to
The problem is more complex.
You can't override gnome-screensaver DBus behavior, because applications should
expect that gnome-screensaver is called with the Dbus method. But, some
applications just assume that gnome-screensaver is the only screensaver in the
world, which is wrong on a LXDE
Regardless of whether gnome-screensaver is started directly, or via the
dbus service -- if it finds that xscreensaver is already present, do you
think it should go right ahead, or quit? I think gnome-screensaver
should notice that a screensaver is already active in X and abort.
The picture you
13 matches
Mail list logo
