![]() Global Moderator ![]()
|
Ive noticed that upon a new bootup (from a safe shutdown, not a sudden one such as a powercut) the KDE digital clock is wrong. Specifically it is exactly 3 hours behind. All the time.
Right clicking on it and selecting Adjust date and time shows that set time and date automatically is activated, and the timezone is Australia/Sydney, which is correct. If i click Digital clock settings and go to time zones, it see clock defaults to "local". I can manually select Australia/Sydney, but there is no effect. The only way to fix it is to do `kdesu systemsettings` (ie. run as root) and go into Date & Time and uncheck the set date and time automatically, hit apply, then recheck it, then hit apply again. The time will then correct itself. However upon correcting itself, an error message pops up with
Any ideas what's going on?
Moult, proud to be a member of KDE forums since 2008-Oct.
thinkMoult - source for tech, art, and animation: hilarity and interest ensured! WIPUP.org - a unique system to share, critique and track your works-in-progress projects. |
![]() Manager ![]()
|
doing some Google'ing the 3 hours could be caused by the HWCLOCK= setting in /etc/sysconfig/clock
I also have the "Unable to authenticate/execute the action: 6" issue |
![]() Manager ![]()
|
|
![]() Global Moderator ![]()
|
Ahh, yes, this is the combination of settings in /etc/conf.d/hwclock that could be causing it:
Consider this solved until the issue pops up again. As for the bug, my behavior seems to be slightly different - the message pops up, but the changes _are_ applied.
Moult, proud to be a member of KDE forums since 2008-Oct.
thinkMoult - source for tech, art, and animation: hilarity and interest ensured! WIPUP.org - a unique system to share, critique and track your works-in-progress projects. |
![]() Administrator ![]()
|
Interesting. If you are recieving the code 6 error then it should not be possible for the settings to be applied. If you restart System Settings does it still show the correct settings?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Global Moderator ![]()
|
Well, I just uncheck something and recheck it, so technically nothing has changed. However it seems to change in terms of it does update its time.
Moult, proud to be a member of KDE forums since 2008-Oct.
thinkMoult - source for tech, art, and animation: hilarity and interest ensured! WIPUP.org - a unique system to share, critique and track your works-in-progress projects. |
![]() Administrator ![]()
|
Okay, interesting. Possibly it uses two different actions - and only one of them is failing.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
I'm seeing a similar error (Kubuntu Oneiric), where the time set in the system settings is, say, 17:00, the panel displays 18:00.
This thread seems to suggest that the problem is solved but unfortunately I failed "mucking about in the shell" 101. ![]() Cheers |
![]() Global Moderator ![]()
|
Well, check those system values. In my case, the problem was because upon shutdown, the system clock was _not_ being synced with the hardware clock, whereas upon startup, the system clock _was_ being synced with the hardware clock.
The hardware clock, being set to the country I bought the laptop in, therefore didn't update itself as I moved overseas, causing this behavior.
Moult, proud to be a member of KDE forums since 2008-Oct.
thinkMoult - source for tech, art, and animation: hilarity and interest ensured! WIPUP.org - a unique system to share, critique and track your works-in-progress projects. |
![]() Registered Member ![]()
|
What did you actually do to fix it, Moult?
I have the same symptoms, showing time from a zone 7hr west of Los Angeles, with a wrinkle: When I fix it and subsequently reboot, I can't connect to my wireless router until I fix the time again (or disable/re-enable wifi, or wait 7hr). On openSUSE (12.1, w/ KDE 4.8.3), I don't have /etc/conf.d/hwclock. Instead I have /etc/sysconfig/clock, and it has a value for SYSTOHC (yes) but doesn't list HCTOSYS. When I add the latter it has no effect, regardless of whether I set it to yes or no. Thanks, GEF |
![]() Global Moderator ![]()
|
I've suffered from a one hour difference for about a year now but took a different (lazy) approach and put
Debian testing
|
![]() Registered Member ![]()
|
I had the same problem, so I decided to check my BIOS. And what do you know the BIOS was incorrect.
![]() ![]() |
![]() Registered Member ![]()
|
I fix the problem this way :
1. In Digital Clock settings ----> Time Zone choose your city, 2. In Adjust Date and Time -----> Time Zones choose UTC Click on apply and OK and the server changes to the right time. I hope it works for you. |
![]() Registered Member ![]()
|
Solution for me was to fix the link at /etc/localtime by removing it and making a new link "sudo ln /usr/share/zoneinfo/GB-Eire /etc/localtime".
The clock was then wrong by the amount I'd manually adjusted it so I used the KDE panel's clock adjustment dialog to reset it. |
![]() Registered Member ![]()
|
It doesn't look like a lot of clear solutions were suggested for this. I was having similar issues (KDE 4.10.2 and Kubuntu 13.04) where my GUI edits were not sticking. I found http://askubuntu.com/questions/268073/k ... -kde-clock - after finding that my etc/localtime was broke (using "file /etc/localtime" displayed the message "localtime: broken symbolic link to `../SystemV/YST9YDT'" - got hung up at at first as I couldn't figure out how to examine a symlink since I couldn't open it as a text file).
Per the askubuntu.com link above, I just entered "sudo dpkg-reconfigure tzdata" and that did it. |
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]