Ubuntu
gnome-system-tools package

NTP installs but does not update

Bug #80933 reported by BHowell
2
Affects Status Importance Assigned to Milestone
gnome-system-tools (Ubuntu)
Invalid
Undecided
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-system-tools

I'm not sure if this is a gnome-system-tools bug or ntp.

To reproduce:

Right-Click on clock panel
Select "adjust date and time"
Select "keep synchronized with internet servers" from configuration drop down
if it's the first time follow prompts to install NTP packages

the "time servers" button is enabled but the "synchronize now" button stays greyed out.
The time does not get updated (my clock was still more than an hour off).

the ntpd process appears to be running. Running /etc/init.d/ntp restart does not help.

My workaround:

sudo /etc/init.d/ntp stop
sudo ntpdate-debian

I can provide logs if needed.

Revision history for this message
BHowell (mute-howell-ersatz) wrote :

Forgot to mention. I'm on Feisty amd64 with latest updates (Jan 22, 2007).

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug, that's not a bug, you can use either ntp which is slowly adjusting the clock or using ntpdate to force a sync, ntpdate is activate only if you are not using ntp. Closing the bug, that's done that way by design, that's not a bug

Changed in gnome-system-tools:
assignee: nobody → desktop-bugs
status: Unconfirmed → Rejected
Revision history for this message
BHowell (mute-howell-ersatz) wrote :

I understand the mechanics now but wouldn't it make more sense to run ntpdate before starting ntpd? My clock was off by almost 18 hours once ntpd started. The standard ntp polling interval is 64 seconds and the maximum clock shift is 128ms. At that rate, it will take weeks to shift to the correct time.

Revision history for this message
Sebastien Bacher (seb128) wrote :

there is some people who use ntpd who don't want any disruptive adjustment. If you really think that should be changed could you open a bug upstream which is the right place to discuss the behaviour for the tool? We have thousand of bugs open a few people working on them at the moment which means it's not likely somebody from the Ubuntu team will work now on that behaviour change

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.