moving the clock 1 h forward starts the screensaver

right, that shouldnt happen

I'm not sure this bug is really in gnome-screensaver. I just switched to xscreensaver and the same thing happens, at least when ntpdate is run (see #36303).

Am running Dapper 6.06 on Toshiba Tecra 8100 and found the same thing. Only the calender window has to be open when you right click to adjust time, (from pressing the clock button). If calender window is not open this bug does not occur for me. When you press OK the screensaver starts

the video players send messages to the screensaver to stop it activating. could the the adjust time panel do the same?

Presumably they'd need to send such a message in the tiny interval between the time changing and the screensaver activating.
Far better (I would think), would be for the screensaver daemon to notice that the time just jumped an unreasonable amount of time and reset its counters; Providing that that doesn't cause problems with other expected behaviours.

I can confirm this too. I'm running the latest daily dapper available at the time of writing: 20060806.1 , so this hasn't been fixed yet.

the changelog of system-tools-backends (1.9.3-0ubuntu1) suggests that this is fixed.
i am away from broadband so i can't test this currently.

can somebody check.

http://bugzilla.gnome.org/show_bug.cgi?id=336114

Fixed upstream, thanks to Matthias Clasen.

In xscreensaver, this bug has existed like forever. I used to see it a lot when my laptop's CMOS battery was failing and I had to tweak the time by hand every time I rebooted. This was like a year ago, then on a Woody installation (thankfully now also running Dapper, still on xscreensaver).

This was fixed in glib2.0:

2006-08-27 Matthias Clasen <email address hidden>

        * configure.in: Fix the pthread compiler flag detection more.

        * configure.in: Check for clock_gettime.
        * glib/gtimer.c: Use Posix monotonic clocks instead of
        gettimeofday when available. (#336114, William Jon McCann)

era: could you test if xscreensaver still has this issue?

On Dapper you mean? I haven't seen any upgrades to libc6 or xscreensaver so why should it have gone away? OK, maybe the recent kernel or X upgrades would have been compiled with the new glibc ...?

Okay, I grabbed a VMware Dapper image which I made when I installed this system, installed all security updates, including reinstalling linux-image-386 and linux-restricted-modules-386, and started up X. I checked that xscreensaver was running, and set the clock an hour and a half into the future. And yes, it blanked the screen.

This is Dapper i386 with universe but no backports.

Oh, that's with a reboot before starting X, just to make sure the kernel and X were indeed the newest version.

yes, it isn't fixed for dapper, at least not yet.

Do we have a clear, small patch which fixes it, that has been tested in
Edgy?

No longer happens in Feisty. Closing bug.