12.1 - System date reset incorrectly on reboot and on exit from Yast System Date

English Install/Boot/Login
#1

I’m using 12.1 with KDE 4.9. When I reboot the computer, the system date is set one day in the future and the time is set to one hour behind the actual time. The same thing happens when I go to Yast’s System Date and Time to make sure the time zone is set correctly and then exit the module. If the date and time was correct when I entered, it is reset incorrectly when I exit. If I then go to Network Services in Yast to test that the connection to an NTP server is correct and then exit Yast’s NTP module, the system date and time is reset correctly. This seems to have started with one of the updates to KDE, though I can’t be certain of that.

Is anyone else having a similar problem? I’ve searched and haven’t seen it reported.

#2

bearymore wrote:

>
> I’m using 12.1 with KDE 4.9. When I reboot the computer, the system date
> is set one day in the future and the time is set to one hour behind the
> actual time. The same thing happens when I go to Yast’s System Date and
> Time to make sure the time zone is set correctly and then exit the
> module. If the date and time was correct when I entered, it is reset
> incorrectly when I exit. If I then go to Network Services in Yast to
> test that the connection to an NTP server is correct and then exit
> Yast’s NTP module, the system date and time is reset correctly. This
> seems to have started with one of the updates to KDE, though I can’t be
> certain of that.
>
> Is anyone else having a similar problem? I’ve searched and haven’t seen
> it reported.
>
>

Did you do this

https://dl.dropbox.com/u/10573557/ntp_settings.jpeg

#3

Thanks for the tip. I didn’t realize there was a second page to the date and time dialog. I did go to it and found that everything was already filled in on the page as it was on yours. All I did was hit synchronize now which resulted in the correct date and time. What was curious to me was that the date and time was correct on rebooting. So the synchronize now button seems to have solved the problem.

Thanks again.

#4

bearymore wrote:

> So the synchronize
> now button seems to have solved the problem.
>
Great