The clock on my KDE Panel is 1 hour fast, I’ve got the Time Zone set at my correct Time Zone of Europe/London and even told the clock to use the Europe/London Time Zone but yet it’s still 1 hour fast ie saying 09:22 when the correct time is 08:22. How do I set it to the correct time?
>
> The clock on my KDE Panel is 1 hour fast, I’ve got the Time Zone set
> at my correct Time Zone of Europe/London and even told the clock to
> use the Europe/London Time Zone but yet it’s still 1 hour fast ie
> saying 09:22 when the correct time is 08:22. How do I set it to the
> correct time?
First get to a terminal (xterm, konsole), type “date”.
Then promote yourself to root (su -) and type “date” again.
Are the time and timezone correct on both attempts?
If they are, then it is a kde config problem. If they aren’t, it is a
system problem. The solution is different.
Do you double boot to windows, perchance?
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))
The thing is, double booting to windows is a common cause of the clock
being 1 hour off after booting. Or more, depends on the timezone, or
daylight savings time clicking on.
It doesn’t happen to everybody, you need a series of causes to have
that problem.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))
Generally Windows assumes the RTC is set to local time and Linux assumes it is set the UTC. In Yast change the time settings to use Local time not UTC.
>
> Generally Windows assumes the RTC is set to local time and Linux
> assumes it is set the UTC. In Yast change the time settings to use
> Local time not UTC.
I know. And I say that this precise scenario, sooner or later, causes
errors in the clock when you boot. I have been seeing them for decades
(ie, I have been using suse for more than a decade).
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))
I dont have any problem with date/time on my machine. Someone else had and created the thread. Carlos mentioned of a doubt over dualboot to which I replied I multiboot and have no issues with date/time conflict after switching operating system.
To Rolandh31
If you’re still watching this thread try this:
Yast>Date & Time
When you click that you’ll see the time zone map in the lower right you’ll see a “Change” button then
a box will come up it’ll have Change Date and Time across the top
2.check the Synchronize with NTP server
3.If one is not already in the NTP server box select one from here: NIST NTP Stratum 1 and Stratum 2 Servers List
click Synchronize Now then click Configure
5.You’ll get a box Advanced NTP Configuration
6.check Now & On Boot
7.click Add in the box that comes up type in the NTP server you chose in my case that’s time-b.nist.gov click OK
click the Accept button in the lower right then
9.back a the map click OK Done!
Now when you come back from W7 the clock might be fast or slow when you get back but it’ll sync to the right time after a bit.
That not true. It might work for you because you live in the UTC zone. I get a 5 hour difference here (EST) unless both OS’s use the same base time for the RTC ie both local or both UTC. I don’t dual boot but I see it in the VM based XP I run
I’ve managed to get the KDE clock to show the correct time by setting the Hardware clock to UTC/GMT instead of being on UK BST. I never had this problem with the BIOS clock being set correctly ond the OS clock being an hour out when I was running Ubuntu. I’m only running OpenSuse on my Netbook so it’s not some wierd dual boot clock problem, it was most likely an error on my part for not un ticking Hardware clock is set to UTC in setup, but all is fine with the clock now.
If you have NTP configured in both in dual boot things tend to work them selves out since the clock gets reset according to each systems rules form the MTP source on a boot. But by default in Suse NTP is not configured. Not sure if it is in Windows but I think not. Telling time is way more complicated then most people realize.