Bug 72149 - Time zone's value ignores the current setting
Time zone's value ignores the current setting
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-date (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Mike McLean
: 78935 79772 84028 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2002-08-21 10:48 EDT by Akira TAGOH
Modified: 2007-04-18 12:45 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-10-22 14:56:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Akira TAGOH 2002-08-21 10:48:17 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020809

Description of problem:
a value of the list view on the Time zone tab ignores the current setting. looks
like it's always pointed America/New_York.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.runs redhat-config-date
2.select the Time zone tab.
3.look at the list view.

Actual Results:  I've selected 'Asia/Tokyo' for Time zone at the install time,
but redhat-config-date always point 'America/New_York.

Expected Results:  the current setting's value should be selected by default.

Additional info:
Comment 1 Brent Fox 2002-08-21 16:26:37 EDT
Should be fixed in 1.5.2-3.

QA, please verify.
Comment 2 Mike McLean 2002-09-12 02:45:14 EDT
Hmm, there seems to be qa contact for this bug, adding myself.

This bug is fixed in the literal sense: redhat-config-date does indeed read the
currect timezone/utc settings from /etc/sysconfig/clock.  However, any changes
mad e are not written back to this file.  I am testing with 

See also bug#73498.
Comment 3 Brent Fox 2002-10-10 15:21:05 EDT
The fix is in CVS now, but I can't push new packages to Rawhide now due to some
problem with the build system.  Should be fixed in 1.5.2-11.  

QA, please verify.  The RPM can be found in dist-8.0.1.
Comment 4 Mike McLean 2002-10-10 15:53:56 EDT

[mike@test114 mike]$ /usr/bin/redhat-config-date
Traceback (most recent call last):
  File "/usr/share/redhat-config-date/redhat-config-date.py", line 35, in ?
  File "/usr/share/redhat-config-date/mainWindow.py", line 180, in __init__
    self.timezonePage = timezone_gui.timezonePage()
  File "/usr/share/redhat-config-date/timezone_gui.py", line 53, in __init__
    if int(self.asUTC) == 1:
ValueError: invalid literal for int(): true
[mike@test114 mike]$ rpm -q redhat-config-date
[root@test114 root]# cat /etc/sysconfig/clock

it seems to be thrown off by boolean keywords like true/false on/off.  It seems
to want to only see 0/1 and it seems to always write 0/1.  Note that rc.sysinit
*doesn't understand* 0 or 1 for UTC or ARC, though to be fair this is probably a
bug in initscripts (since it does initialize them to be 0).
Comment 5 Bill Nottingham 2002-10-10 16:05:32 EDT
UTC/ARC is a true/false field, not a 0/1 field. At least, that's how it's
documented and implemented. ;)
Comment 6 Brent Fox 2002-10-22 14:56:38 EDT
Should be fixed properly now (hopefully).  Please test with
redhat-config-date-1.5.3-1 in dist-8.0.1
Comment 7 Mike McLean 2002-10-23 08:21:52 EDT
Confirmed fix.
Comment 8 Brent Fox 2002-12-03 14:40:40 EST
*** Bug 78935 has been marked as a duplicate of this bug. ***
Comment 9 Brent Fox 2002-12-17 12:37:57 EST
*** Bug 79772 has been marked as a duplicate of this bug. ***
Comment 10 Brent Fox 2003-02-11 12:06:02 EST
*** Bug 84028 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.