gnome-screensaver started delayed in session

I was able to duplicate this bug in dapper

ctrl alt backspace to kill the x server

login

lock screen does nothing

I had killed gnome-screensaver in my running session while reproducing a different bug. I logged out and back in, but it wasn't started again. Running gnome-screensaver-preferences started it, but after logout/login at that point, it was gone again. No errors from gnome-screensaver in ~/.xsession-errors.

Some time after submitting that comment, I saw the screensaver activate on my laptop(!).

ps showed that gnome-screensaver had started approximately one minute after I had checked for it last.

Can either of you check whether gnome-screensaver does eventually start for you? It looks like it is simply delayed for some reason.

Laurent, cerebrix:

Have you had any luck following up on Matt's previous comment?

I can't reproduce now because when I hit ctr-alt-backspace X doesn't restart anymore, I stay in text-mode console and has to run "sudo /etc/init.d/gdm restart". Then gnome-screensaver is started.

Some times ago (when X restarted after killing him) I was able to reproduce the bug, but i not waited 1 minute to see if it starts...

oops, wrong browser tab, sorry

That still occurs. if I kill the session, gnome-screensaver is started about 30 seconds after the login

The screensaver is started 25 seconds after login:

http://cvs.gnome.org/viewcvs/gnome-control-center/gnome-settings-daemon/gnome-settings-screensaver.c?view=markup

For me, screensaver never restarts. I simply cannot lock my screen at all. I'll try to reboot and see what happens then.

This bug is being assigned to Oliver Grawert, one of the gnome-screensaver packages. It has also been nominated for release in Gutsy and Hardy.

Mark, this bug has not had a single comment in a year and a half, so it's worth asking if people still have this bug in 7.10 or hardy..

Timo, you are right.

I ran into the same symptom today on Gutsy when using the "Lock Screen" button. However, I'm uncertain if the trigger was the same as described here. I have either experienced this bug in Gutsy, or something closely related to it.

Are others still still having problems with this on Gutsy or Hardy?

I am having similar screensaver issues, but I believe mine issues are tied to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195982

I have this problem also. However, it all started when I installed the xscreensaver package from the package manager. I did this so that I would be able to configure my screensavers. Since then, I have removed xscreensaver, and reinstalled gnome-screensaver, but it still does not work. Screensavers do not launch when I am idle, nor does locking the computer work.

same problem here on gnome 2.22.1 under opensuse 11.0.

Anyone seen this in Ubuntu 8.10 or in Jaunty?

updated to packages in the ../gnome/[community, stable, gnome1] opensuse repositories and problem is gone.

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

both 32b and 64b are present in the same
problem, the most interesting is that I have another machine
32b is not having the error ....