Bug 73498 - "System clock uses UTC" doesn't work
"System clock uses UTC" doesn't work
Status: CLOSED RAWHIDE
Product: Red Hat Public Beta
Classification: Retired
Component: redhat-config-date (Show other bugs)
null
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Mike McLean
:
: 75676 80681 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-09-05 11:10 EDT by Braden McDaniel
Modified: 2007-04-18 12:46 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-10 23:39:27 EDT
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 Braden McDaniel 2002-09-05 11:10:54 EDT
Description of Problem:
Checking the box for "System clock uses UTC" has no effect, and the box is
unchecked when I launch redhat-config-date subsequently.

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

How Reproducible:
Consistently on my machine.
Comment 1 Need Real Name 2002-09-07 12:06:53 EDT
Same problem on mine. 
 
Additionally, the applet under gnome has an option to set date and 
time, it doesnt. 
 
The applet runs kcmshell "clock" 
it prompts for root password, then ends. 
Comment 2 Brent Fox 2002-10-10 15:20:53 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 3 Brent Fox 2002-10-10 15:21:44 EDT
Oops, I meant to set the state to 'modified' instead of 'resolved'.
Comment 4 Brent Fox 2002-10-10 23:39:21 EDT
*** Bug 75676 has been marked as a duplicate of this bug. ***
Comment 5 Mike McLean 2002-11-06 17:51:29 EST
Fix confirmed
CLOSING->RAWHIDE
Comment 6 Brent Fox 2003-01-02 09:02:43 EST
*** Bug 80681 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.