Bug 76313 - if timezone isn't in timezone list, redhat-config-date tracebacks
if timezone isn't in timezone list, redhat-config-date tracebacks
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-date (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
:
: 74206 76164 76707 77254 77436 78786 79400 79699 80058 80431 80432 82721 82829 83353 83469 84071 85112 98092 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-19 15:25 EDT by Jeremy Katz
Modified: 2008-05-01 11:38 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-19 15:25:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeremy Katz 2002-10-19 15:25:47 EDT
If the current timezone isn't in the zone.tab list (ie, it's something like
'UTC'), then redhat-config-date will traceback in timezone_map_gui.py
setCurrent() with currentEntry being None.  Something like the following looks
like the right patch

Index: timezone_map_gui.py
===================================================================
RCS file: /usr/local/CVS/redhat-config-date/src/timezone_map_gui.py,v
retrieving revision 1.11
diff -u -u -r1.11 timezone_map_gui.py
--- timezone_map_gui.py 21 Aug 2002 23:08:35 -0000      1.11
+++ timezone_map_gui.py 19 Oct 2002 19:20:19 -0000
@@ -174,9 +174,10 @@
         if not entry:
             # If the value in /etc/sysconfig/clock is invalid, default to New York
             self.currentEntry = self.fallbackEntry
+        else:
+            self.currentEntry = entry

         self.markers[self.currentEntry.tz].show()
-        self.currentEntry = entry
         self.markers[self.currentEntry.tz].hide()
         x, y = self.map2canvas(self.currentEntry.lat, self.currentEntry.long)
         self.current.set(x=x, y=y)
Comment 1 Brent Fox 2002-10-22 11:22:04 EDT
Patch applied in cvs.  The fix should appear in redhat-config-date-1.5.3-1. 
Thanks for the patch.
Comment 2 Brent Fox 2002-10-22 11:59:54 EDT
*** Bug 76164 has been marked as a duplicate of this bug. ***
Comment 3 Brent Fox 2002-10-22 12:05:24 EDT
*** Bug 74206 has been marked as a duplicate of this bug. ***
Comment 4 Brent Fox 2002-10-25 09:34:28 EDT
*** Bug 76707 has been marked as a duplicate of this bug. ***
Comment 5 Brent Fox 2002-11-04 11:08:33 EST
*** Bug 77254 has been marked as a duplicate of this bug. ***
Comment 6 Brent Fox 2002-11-07 10:52:52 EST
*** Bug 77436 has been marked as a duplicate of this bug. ***
Comment 7 Brent Fox 2002-12-11 09:51:05 EST
*** Bug 79400 has been marked as a duplicate of this bug. ***
Comment 8 Brent Fox 2002-12-11 11:52:07 EST
*** Bug 78786 has been marked as a duplicate of this bug. ***
Comment 9 Brent Fox 2002-12-17 12:11:52 EST
*** Bug 79699 has been marked as a duplicate of this bug. ***
Comment 10 Brent Fox 2002-12-19 09:58:20 EST
*** Bug 80058 has been marked as a duplicate of this bug. ***
Comment 11 Brent Fox 2002-12-26 11:25:29 EST
*** Bug 80432 has been marked as a duplicate of this bug. ***
Comment 12 Brent Fox 2002-12-26 11:26:29 EST
*** Bug 80431 has been marked as a duplicate of this bug. ***
Comment 13 Brent Fox 2003-01-27 14:38:08 EST
*** Bug 82829 has been marked as a duplicate of this bug. ***
Comment 14 Brent Fox 2003-02-04 15:24:37 EST
*** Bug 83469 has been marked as a duplicate of this bug. ***
Comment 15 James Beale 2003-02-05 16:08:26 EST
After reading this (76313) I hope this further information will be of use to 
someone, but try by checking the "clock" file in “etc/sysconfig” first.

Mine looked like:

ZONE="Etc/GMT"
UTC=true
ARC=false

But the ZONE statement should have been:

ZONE="Europe/London"
Comment 16 Brent Fox 2003-02-05 16:55:31 EST
*** Bug 83353 has been marked as a duplicate of this bug. ***
Comment 17 Brent Fox 2003-02-05 21:24:16 EST
*** Bug 83353 has been marked as a duplicate of this bug. ***
Comment 18 Brent Fox 2003-02-06 14:25:49 EST
*** Bug 83353 has been marked as a duplicate of this bug. ***
Comment 19 Brent Fox 2003-02-11 16:47:16 EST
*** Bug 84071 has been marked as a duplicate of this bug. ***
Comment 20 Brent Fox 2003-02-25 16:57:38 EST
*** Bug 85112 has been marked as a duplicate of this bug. ***
Comment 21 Brent Fox 2003-04-01 12:40:32 EST
*** Bug 82721 has been marked as a duplicate of this bug. ***
Comment 22 Brent Fox 2003-06-26 11:22:09 EDT
*** Bug 98092 has been marked as a duplicate of this bug. ***

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