Date & Time keeps going back to incorrect time on reboot

In the clock’s “Adjust Date & Time” I have checked “set date and time automatically” and have it set to use “Public Time Server (pool.ntp.org)”. If I untick this and then retick and hit “OK”, it gets the correct time. However, on reboot, the time is again incorrect! It’s always 5 hours too slow despite it having the correct timezone.

How do i get this to stick properly?

Using:
openSUSE 12.2
KDE 4.8.5
(Nothing but opensuse on this computer. No windows)

I may have figured it out. There are multiple places to seemingly change the same thing!

If you right click on the clock (or go into date/time via “Configure Desktop”) you’ll get to a dialog that lets you pretend to set the time automatically. This does not survive reboot despite asking for root password.

If instead you go through YAST2->Date Time, you’ll see it’s set to use the hardware clock. You can then change this to set time automatically (defaults to bigben in dc). I’m hopeful that:

  1. This survives a reboot
  2. Somehow, the openSUSE team (or KDE?) puts this ll into one interface.

I’m skeptical that this will help, but we’ll see. Most of the time when
I’ve seen clocks change after reboot it’s been a battery problem in the
motherboard, but usually that also results in time resetting to something
non-current as well.

You can test whether or not the entire OS is taking your time changes
using the ‘date’ or ‘hwclock’ commands. The latter must be run as root
(sudo /usr/sbin/hwclock) but the former works as any old user.

Good luck.

hwclock command shows the correct time.

On 2013-02-13 21:26, 6tr6tr wrote:
> hwclock command shows the correct time.

If “hwclock --debug” and “date”, run as root in a terminal, show the
correct time, then the clock is correct. Forget what KDE says the time is.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Sorry, I meant after I made the change in YAST2, now hwclock has the right time.

On 2013-02-14 03:16, 6tr6tr wrote:
> Sorry, I meant after I made the change in YAST2, now hwclock has the
> right time.

Ah, ok.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Something else to consider here:

What is UTC or GMT Time & a possible issue with openSUSE 12.2 and its solution: https://forums.opensuse.org/blogs/jdmcdaniel3/what-utc-gmt-time-possible-issue-opensuse-12-2-its-solution-116/

Thank You,

This is a bug in ntp package which is fixed in current ntp update for 12.2: openSUSE-RU-2013:0235-1: moderate: ntp: remove --utc --noadjfile from hw

The most common solution to this is…

  1. Unless you’re multi-booting with Windows, you need to set your Linux time to “UTC” – <not> hardware or something else. Even if you think you’ve solved your problem otherwise, when something like “Daylight Savings Time” comes around, you’ll be seeing problems again.

  2. I haven’t seen it described anywhere, but after setting your time to be UTC based and the correct time zone, the little clock applet in the KDE panel (Taskbar to you Windows people) may display the UTC time instead of the local time zone, you should then rt-click on the panel clock, click “Digital Clock Settings” then <remove> UTC from the Time Zone setings (you’re only removing the display, not altering basic functionality).

HTH,
TSU

On 2013-02-14 20:26, tsu2 wrote:
> 1. Unless you’re multi-booting with Windows, you need to set your Linux
> time to “UTC” – <not> hardware or something else.

With Windows 7 you can also use UTC. Plus Vista and I assume 8.

See SDB:Configuring the clock, section “Other OS”. I’m using that
trick in my laptop and works perfect.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)