Bug 85112 - Default entry not set prevent redhat-config-date from starting
Default entry not set prevent redhat-config-date from starting
Status: CLOSED DUPLICATE of bug 76313
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-date (Show other bugs)
8.0
All Linux
medium Severity low
: ---
: ---
Assigned To: Brent Fox
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-25 15:49 EST by Guillaume Sauzon
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:51:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Guillaume Sauzon 2003-02-25 15:49:18 EST
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 16:57:35 EST

*** This bug has been marked as a duplicate of 76313 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:51:58 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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