GNOME Bugzilla – Bug 330347
documentation for starting gnome-screensaver
Last modified: 2006-03-19 02:08:29 UTC
Please describe the problem: With the 2.14 release we will have new gnome-screensaver, fast-user-switch-applet, lock screen applet stack that works and integrates with gdm. This is basically a call to add some info to already very nice and helpfull documentation at http://www.gnome.org/projects/garnome/docs.html about ways of starting gnome-screensaver (i.e adding it to the "Startup Programs" via Desktop --> Preferences --> Sessions ) or to garnome-session script. We also lack that info atm. for the gnome-volume-manager (auto mounting) too. Also I have one problem atm with it when using garnome 2.13.90: If I start it with "gnome-screensaver --no-daemon" in terminal and click on "Lock Screen" applet on panel or Lock Screen item at Desktop menu, a screensaver starts but doesn't offer password dialog as I expect at all. It gives warning/error message in terminal: (process:3141): gnome-screensaver-WARNING **: Couldn't get password of "slobo" (process:3141): gnome-screensaver-WARNING **: Couldn't get password of "root" (gnome-screensaver-dialog:3141): gnome-screensaver-WARNING **: Screen locking di sabled: error getting password I also expect lock screen password dialog when using fast-user-switch-applet and come back to old session but it doesn't appear. Am I missing something or this is bug in gnome-screensaver? Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
gnome-screensaver doesn't need any docs. It should just work. It works fine for me. Did you start dbus/hal as specified on the docs page/README? gnome-volume-manager also uses hal so it should just work as well.
Please read the README section on starting DBus/HAL. Once DBus/HAL are running things should "just work".
Update your startup script that launches your display manager. I had the same problem. I was using the Gnome 2.12.2 (SUSE) version of the display manager along with the 2.14 version of the gnome-screensaver. This caused my similar issue. Modify the script to use the garnome version of gdm. Then launch the gnome-screensaver with dbus-launch. That should fix the problem...did for me. Regards, Wendell Mackenzie