Ubuntu

Gutsy keeps setting the time +1h with every reboot

Bug #158664 reported by Cruncher
6
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Here in Germany daylight saving time ended on Oct 28. After having some trouble in Feisty ( https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/91418/comments/12 ), I upgraded to Gutsy.

However, now after every reboot, the time is being ajdusted to an additional +1h into the future. Comparing with the BIOS time: When the BIOS says 2 pm, after booting 7.10, Ubuntu time is 3 pm. Rebooting and checking the BIOS now also says 3 pm, and so on.

Initially, ntp was not installed due to the following problem: https://bugs.launchpad.net/ubuntu/+bug/158653

However, it makes no difference whether ntp is running or not, whether time is manually reset using ntpdate, or using ntpdate with "hwclock --systohc" afterwards.

Revision history for this message
Cruncher (ubuntu-wkresse) wrote :

Follow-up:
Even after setting the configuration in System->Administration->TimeAndDate ("time-admin") to "Manual", the time keeps changing. Pushing "Synchronize now" reset the time correctly - until the next reboot...

Revision history for this message
NeilGreenwood (neil-greenwood) wrote :

I found it changed my time after resuming from hibernate overnight.

My timezone was lost since upgrading to Gutsy. I've reset it to Europe/London now. We'll see what happens next week now.

BTW, using "Synchronize now" left my time 1 hr ahead. I've got it on manual now.

Revision history for this message
Adam Niedling (krychek) wrote :

Has this issue been fixed already?

Revision history for this message
Cruncher (ubuntu-wkresse) wrote :

Hm, at least the problem didn't occur for me again after creating a startscript running ntpdate manually on each boot.
At the moment I'm running Hardy, removed the manual script before this year's switch back from daylight saving time, and have ntp installed.
The automatic time switch worked without problems, so I guess this particular problem is either fixed, or it did not occur due to different setup conditions (the problem occured after the Feisty->Gutsy upgrade).

Revision history for this message
Adam Niedling (krychek) wrote :

I guess this can be closed then. Feisty isn't supported anymore anyway.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.