Karmic screensaver asks for password

NoOp glgxg at sbcglobal.net
Fri Nov 13 18:07:12 UTC 2009

On 11/13/2009 07:43 AM, Laura Conrad wrote:
> I really think the xscreensaver thing is a red herring.  When I first
> reported the problem, it was an xscreensaver dialog box, and a
> subsidiary problem was that the xscreensaver configuration tool no
> longer had the box for checking whether you wanted to lock the
> screen.  Of course, if the system has hard-wired the answer, it's
> better to not have the box.
> But since I removed xscreensaver, the box is a gnome-screensaver box,
> and the bug is that the lock screen entry in the gnome-screensaver
> configuration box isn't having any effect.  I did a "ps auxww" from a
> terminal while it was on screen this morning and my guess is that the
> program that's asking me for my password is "gnome-screensaver-dialog
> --enable-switch".

You might have a look through:
and this one is interesting:
[gnome-screensaver not functioning]
and consider filing a bug report. But first I'd try testing to see if
it's actually the screensaver or something else:

$ mv /home/<username>/.gconf/apps/gnome-screensaver
$ sudo apt-get purge gnome-screensaver
$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo apt-get install gnome-screensaver

Note: yes I've just done this on a karmic machine to test before
suggesting :-)

.gconf/apps/gnome-screensaver is your screen saver settings and is an
xml file which can be looked at/edited in the standard gedit text
editor. When you reinstall gnome-screensaver it will create a new
.gconf/apps/gnome-screensaver, so you can compare against the old
'x-gnome-screensaver-x' file. I doubt this is the issue, but it can't
hurt to give it a try in the event the xml file is corrupted. Also note,
that you can/should move 'x-gnome-screensaver-x' out of that folder
eventually, as the gconf editor will pick it up as an app. Won't hurt
anything to leave it there, but may be confusing later on if you forget
what it is.

You can also try the 'gnome-screensaver-command' options, see:

Try inhibiting it first, then deactivate & then exit.

Note that I'm guessing at all of this right now... :-)

More information about the ubuntu-users mailing list