Hide Forgot
Description of problem: Having cycles to spare and much preferring the 26" screen not to be a dead looking thing, I tend to remove gnome-screensaver and install xscreensaver (it's just nice when guest who use other OSes get envious ;-) But, gnome3 seems to have the usage of gnome-screensaver hardcoded. It's easy to add a custom keyboard shortcut in gnome3's System Settings, Keyboard, Shortcuts, Custom Shortcuts. Bind it to '/usr/bin/xscreensaver-command -lock' and when assigning ctrl-alt-L one can easily override the call to gnome-screensaver. BUT in the upper right menu, the entry 'Lock Screen' generates this in .xsession-errors JS LOG: Ignored exception from dbus method: Error: DBus error: org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.ScreenSaver" does not exist http://cpaul.is-programmer.com/tag/XScreensaver%20lock works well here. It listens to dbus and triggers xscreensaver -lock. xscreensaver should probably not hijack sth that's not it's own and there seems to be movement upstream to make the dbus notification more screensaver-agnostic. Still, if (before it's more agnostic)an xscreensaver upadte needs to be done, could you include a /usr/share/doc/xscreensaver-base-5.15/README.Fedora showing the script and crediting the site? Looking at the FAQs for both xscreensaver[1] and gnome-screensaver[2] I get the impression that there is a mess I want no part in and I presume neither upstream will appreciate meddling. While this is from my work bugzilla account (my only BZ account, so making this bug private to avoid any potential flame wars), I do not own or maintain either package, still it would be nice if the shipped xscreensaver had the above README.Fedora [1] http://www.jwz.org/xscreensaver/faq.html [2] http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions
No description? By the way, why is this bug marked as "for Private Group"?
sorry, my bad, fixing. I was trying to avoid triggering any flames between gnome-screensaver and xscreensaver. I'll open up the bug
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.