Bug 179530 - clock on kicker not using system timezone
Summary: clock on kicker not using system timezone
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-01 05:27 UTC by Ellen Shull
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-20 18:42:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ellen Shull 2006-02-01 05:27:01 UTC
Description of problem:
Had just installed FC5T2.  Noticed I had forgotten to purge evil gnome in favor
of happy fun KDE, so used used pirut to install KDE.  Logged into KDE (ahhhh...)
Had system timezone set to America/Phoenix.  KDE was displaying time in
America/New York (IIRC, but it definitely wasn't the right zone whatever it was)

Version-Release number of selected component (if applicable):
kdebase-3.5.0-2.i386.rpm

How reproducible:
Not that bored :P

Steps to Reproduce:
1. Install FC5T2 w/o KDE, setting tz to America/Phoenix
2. install KDE Desktop using pirut
3. log into KDE.  Notice clock not displaying in correct timezone.
  
Actual results:
Eastern Time, ew!

Expected results:
Mountain Standard Time 24/7/365, baby!

Additional info:
"timezone America/Phoenix" in my /root/anaconda-ks.cfg, so I'm not on drugs...
Not sure if the after-the-fact install of KDE had anything to do with it, just
faithfully reporting what I did.

Comment 1 Rahul Sundaram 2006-02-20 11:19:58 UTC

These bugs are being closed since a large number of updates have been released
after the FC5 test1 and test2 releases. Kindly update your system by running yum
update as root user or try out the third and final test version of FC5 being
released in a short while and verify if the bugs are still present on the system
.Reopen or file new bug reports as appropriate after confirming the presence of
this issue. Thanks

Comment 2 Than Ngo 2006-02-20 18:42:00 UTC
it seems to be fixed in current rawhide. You should please update your system
to current rawhide, thanks


Note You need to log in before you can comment on or make changes to this bug.