Bug 104046
Summary: | adjusting timezone is not reflected in applet | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | teuben |
Component: | gnome-panel | Assignee: | Mark McLoughlin <markmc> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | jakub, rth |
Target Milestone: | --- | Keywords: | MoveUpstream, Triaged |
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-10-01 12:45:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
teuben
2003-09-09 13:30:33 UTC
I'm guessing libc caches the timezone information. I'm not sure whether there's a way to force it to refresh. Calling tzset () causes TZ env variable to be reevaluated and timezone file reread. I'd like to add that while playing with a mandrake 9.1 box i noticed the changing the time will adjust the time in the Clock tool on the panel. THeir version is also 2.2.0.1, but of course they look different to the users, since mandrake and redhat do something else below the hood. Obviously mandrake can do it right (one little caveat, that machine runs the hardware clock in civil time, not in GMT, like mine). I will experiment with that to make sure that is not the difference. But thus far i'd say the redhat version does have a problem. I confirmed that the version in Fedora RC1 also exhibits the same problem as RH9. I don't recall the version of that Clock. *** This bug has been marked as a duplicate of 98140 *** Wrong dup, sorry :-) *** Bug 123614 has been marked as a duplicate of this bug. *** This is fixed in latest rawhide with glibc-2.3.3-60 or later |