Bug 77436 – redhat-config-date croaks with python backtrace

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 77436 - redhat-config-date croaks with python backtrace

Summary:	redhat-config-date croaks with python backtrace

Status:	CLOSED DUPLICATE of bug 76313

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	redhat-config-date (Show other bugs)
Sub Component:
Version:	8.0
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Brent Fox
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-11-06 18:42 EST by Anthony Green
Modified:	2008-05-01 11:38 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-11-07 10:52:18 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Anthony Green 2002-11-06 18:42:03 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
I upgraded my machine from RH 7.2 to 8 recently.  I needed to reset the timezone
for some reason, so I ran redhat-config-time, which promptly exited with a
python backtrace.

My old /etc/sysconfig/clock contained:

ZONE="Etc/GMT-5"

Changing this to

ZONE="America/Los_Angeles"

...seems to have fixed the problem.  I had no problem running redhat-config-time
then.


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


How reproducible:
Always

Steps to Reproduce:
1.Modify /etc/sysconfig/clock as above.
2.
3.
	

Additional info:

Comment 1 Brent Fox 2002-11-07 10:51:52 EST


*** This bug has been marked as a duplicate of 7631 ***

Comment 2 Brent Fox 2002-11-07 10:53:01 EST

Oops, I hit Enter too soon.  This is a dupe of bug 76313, not 7631.

*** This bug has been marked as a duplicate of 76313 ***

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