Bug 85112

Summary: Default entry not set prevent redhat-config-date from starting
Product: [Retired] Red Hat Linux Reporter: Guillaume Sauzon <drinegui>
Component: redhat-config-dateAssignee: Brent Fox <bfox>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:51:58 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 Guillaume Sauzon 2003-02-25 20:49:18 UTC
Description of problem:


Version-Release number of selected component (if applicable):
timezone_map_gui.py no version indicated

How reproducible:
When ntpd is seleted and fail at startup, no time server is found. In that case, 
redhat-config-date doesn't start.

Steps to Reproduce:
1. Launch redhat-config-date
2. Put activate network time protocol synchronisation, with whatever server
3. Restart the computer without networking (unplug ethernet link)
4. Try to start redhat-config-date
    
Actual results:
redhat-config-date doesn't start

Expected results:
redhat-config-date works

Additional info:
The bug is on the line 176 of timezone_map_gui.py. There, it stands:
self.currentEntry = self.fallbackEntry
It should be replaced by:
entry=self.currentEntry = self.fallbackEntry and then everything works OK

Comment 1 Brent Fox 2003-02-25 21:57:35 UTC

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

Comment 2 Red Hat Bugzilla 2006-02-21 18:51:58 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.