Hide Forgot
Description of problem: On the time setting screen, right below the check-box for "hardware clock uses UTC", please add a line that reads "with the current settings the hardware clock time is ___" and the time. On dual-boot machines, machines with removable hard drives (such as used in the school's computer lab and classrooms), it can be hard to know what the hardware clock is currently set to use. With such a line, can can check and uncheck the Use UTC box and know. (this especially applies to the use of this tool by Anaconda.) Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Run anaconda or system-config-date directly 2. 3. Actual results: Current hardware clock time, interpreted by the settings chosen, doesn't appear. Expected results: Current hardware clock time, interpreted by the settings chosen, should appear. Additional info: Applies to Red Hat too. (Bug #714390)
This needs a way to simulate what hwclock would write with the chosen time zone settings, as well as avoiding this code path on platforms that don't have a hardware clock which is settable from the OS.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Thanks for taking the time to submit this bug. Unfortunately, I haven't gotten around to fix this issue, sorry for that. Because I don't actively develop system-config-date anymore, I won't likely find the time to work on this ticket, so I'll close this bug now.