Bug 250049 - clock-applet shows invalid time
Summary: clock-applet shows invalid time
Keywords:
Status: CLOSED DUPLICATE of bug 249857
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 7
Hardware: All
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-30 06:01 UTC by The Source
Modified: 2007-11-30 22:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-07-30 13:49:20 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description The Source 2007-07-30 06:01:20 UTC 
Description of problem:
Clock on panel show always one time (not moving) and it is the time of system
start + shift from UTC (even if system clock uses UTC option is not set). I
checked system clock with date function and it shows proper value.

Version-Release number of selected component (if applicable):
2.18.3-1.fc7

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jiri Cerny 2007-07-30 09:23:56 UTC 
I had the same problem today. It is maybe related to the update of the kernel
package from kernel-2.6.22.1-27.fc7 to kernel-2.6.22.1-33.fc7. The problem first
time appeared when I booted with -33 after an update. It also disappears when I
reboot with -27.

The same date as shown at gnome panel is also in all lines of syslog, but date
command on the command line gives the right time.

Probably should be reasigned as kernel bug.
Comment 2 Mario Torre 2007-07-30 11:23:27 UTC 
I can confirm that this bug appeared after the kernel update (-33).
Comment 3 The Source 2007-07-30 11:30:58 UTC 
I may be wrong but it looks like clock-applet returned to life after I used
clock command.
Comment 4 Ray Strode [halfline] 2007-07-30 13:49:20 UTC 

*** This bug has been marked as a duplicate of 249857 ***
Note You need to log in before you can comment on or make changes to this bug.