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 do believe this is a bug in gnome screensaver. It should have a notion of whether or not it is supposed to be managing screensaving in the user session, and if not then it should respond to DBus clients with an appropriate error if they try to activate it. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/726480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
