Bug 172237 - clock-applet doesn't update clock after changing time
Summary: clock-applet doesn't update clock after changing time
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gnome-applets   
(Show other bugs)
Version: 4.0
Hardware: i386
OS: Linux
Target Milestone: ---
: ---
Assignee: Ray Strode [halfline]
QA Contact: desktop-bugs@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2005-11-01 20:00 UTC by Waldo Bastian
Modified: 2012-06-20 15:59 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 15:59:14 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Waldo Bastian 2005-11-01 20:00:54 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

Description of problem:
After changing the time by RMB clicking on the clock and selecting "Adjust Date & Time", the clock isn't adjusted until the next minute, giving the impression that changing the time didn't work.

Version-Release number of selected component (if applicable):
clock 2.8.1

How reproducible:

Steps to Reproduce:
1. RMB on the clock
2. Select Adjust Date & Time
3. Enter root password
4. Adjust time to be one hour earlier
5. Click OK

Actual Results:  Notice that the clock applet doesn't update the hour till the first new minute

Expected Results:  The time displayed by the clock applet should be adjusted immediately to provide the user with a confrimation that the adjustment of the time succeeded.

Additional info:

Comment 1 Jiri Pallich 2012-06-20 15:59:14 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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