Bug 447225 - Time set fails
Summary: Time set fails
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-applets
Version: 9
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-05-18 22:44 UTC by Jason Taylor
Modified: 2009-07-14 16:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-07-14 16:19:18 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
GNOME Bugzilla 559538 None None None Never

Description Jason Taylor 2008-05-18 22:44:54 UTC
Description of problem: When right clicking on the clock in Gnome and selecting
adjust date & time, adjustment and authentication fails with no
error/informational message

Version-Release number of selected component (if applicable): clock version is, /usr/libexec/clock-applet is version 0 (according to
/usr/libexec/clock-applet --version = GNOME ClockApplet 0)

How reproducible: If clock time is inaccurate, right click on the clock in Gnome
and select Adjust Data & Time, when the time has been modified clicking on Set
System Time will produce a prompt for the root password, entry of the password
(correctly) will fail to commit the changes to the time.

Steps to Reproduce:
1. Right click on the date/time portion of the Gnome Panel
2. Select Adjust Date/Time
3. Modify the time and then click on Set System Time
Actual results: Repeated prompt for root password, which, when entered just
brings the dialog to enter the password again up. This happens 3 times and then
returned to the Time Settings Window

Expected results: Modification of system time

Additional info: This occurs whether or not NTP is selected. The workaround is
to disable NTP, Go to System -> Administration -> Date & Time and adjust the
time through this menu. Once successful, re-enable NTP and everything appears to
work as expected. Throughout the whole scenario no messages/errors are displayed
and nothing is logged to /var/log/messages. This behaviour was also experienced
by f_newton and workaround was successful for him as well.

Comment 1 Fabrício Godoy 2009-01-08 23:42:09 UTC
This happens with Fedora 10 too.

Comment 2 Fabrício Godoy 2009-01-08 23:55:37 UTC
Sorry, my mistake.

Comment 3 Bug Zapper 2009-06-10 00:59:00 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 '9'.

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 9'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 9 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: 

Comment 4 Bug Zapper 2009-07-14 16:19:18 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.

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