Bug 500811

Summary: timezoneBackend.py guesses hwclock "UTC" default setting wrong
Product: [Fedora] Fedora Reporter: MarcH <Marc.Herbert+rhzilla>
Component: system-config-dateAssignee: Nils Philippsen <nphilipp>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 13CC: nphilipp
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 14:12:03 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:
Attachments:
Description Flags
change default none

Description MarcH 2009-05-14 10:36:03 UTC
Description of problem:
system-config-date/timezoneBackend.py features a "system clock uses UTC" checkbox. This checkbox is initialized according to the current hwclock setting... not!

Version-Release number of selected component (if applicable):
1.9.36-1.fc10

How reproducible:
always

Steps to Reproduce:
1. remove (or misspell) the third line in the /etc/adjtime configuration file
2. run system-config-date. See "system clock uses UTC" checkbox is ticked ON
3. see inconsistency with "hwclock" assuming --localtime (i.e., UTC OFF)
 
Actual results:
"system clock uses UTC" checkbox ticked on

Expected results:
"system clock uses UTC" checkbox ticked off

Comment 1 MarcH 2009-05-14 10:37:39 UTC
Created attachment 343939 [details]
change default

Comment 2 MarcH 2009-07-29 15:19:04 UTC
In a similar fashion, timezoneBackend.py refrains to add a UTC/LOCAL line to the /etc/adjtime file when there is none in the first place. Any reason why?

Comment 3 Bug Zapper 2009-11-18 12:52:35 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-12-18 09:26:16 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 5 Nils Philippsen 2009-12-18 09:32:39 UTC
Reopened.

Comment 6 Bug Zapper 2010-03-15 12:36:37 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 MarcH 2010-07-30 10:35:06 UTC
This minor Fedora 10 bug can be reproduced unchanged in Fedora 13.

This bug is really just about two different tools reading the same config file and disaggreeing about a default value when it is missing. That's all.

The fix attached more than one year ago is a no-brainer, one-line change of a default value. Anything wrong with it?

Comment 8 Bug Zapper 2011-06-02 18:05:35 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Bug Zapper 2011-06-27 14:12:03 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.