Red Hat Bugzilla – Bug 146970
KDE displays the wrong timezone
Last modified: 2007-11-30 17:10:59 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
The clock in the task bar shows UTC. This seems to occur after a
reboot, but I have not fully vetted that.
Adjust Date & Time, shows current timezone as UTC, America/Chicago.
Change to America/Chihuahua, click Apply,
shows current timezone as MST, America/Chihuahua
Change back to America/Chicago, click Apply,
shows current timezone as CST, America/Chicago. (And its little clock
shows the right time, though the clock in the task bar hasn't changed.)
click OK to exit.
The clock in the task bar is still showing UTC.
The above process can be repeated over and over again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to set the timezone for the KDE clock
Actual Results: The timezone does not change.
Expected Results: The timezone should change.
There may be a clue as to what is going on here:
# cat /etc/timezone; echo; date
Sat Feb 5 01:09:43 UTC 2005
# hwclock --show
Sat 05 Feb 2005 06:10:41 PM UTC -0.804128 seconds
My watch says 7:11pm Feb 4, 2005.
[root@pegasus etc]# hwclock --show --localtime
Sat 05 Feb 2005 06:12:21 PM UTC -0.167392 seconds
[root@pegasus etc]# hwclock --show --utc
Sat 05 Feb 2005 06:12:28 PM UTC -0.381786 seconds
# ls -l /etc/localtime
ls: /etc/localtime: No such file or directory
# ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime
Fri Feb 4 19:15:10 CST 2005
# rpm -qf /etc/localtime
So why did /etc/localtime disappear? And why didn't the system fix that?
After making the /etc/localtime link, I logged out and back in. The
timezone is now correct. But why didn't the KDE clock utility fix the
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
I haven't had this problem in a long time; and I have upgraded to FC6. Closing.