Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 8994

Summary:	panel clocks loosing time
Product:	[Retired] Red Hat Linux	Reporter:	Hans de Goede <hdegoede>
Component:	gnome-core	Assignee:	Jonathan Blandford <jrb>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	ddumas
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-03-11 14:42: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:

Description Hans de Goede 2000-01-30 21:45:09 UTC

I have this problem bith with the regular clock-applet and with the
afterstep clock, so it's probably somewhere in soem code they share.

The easiest way to reproduce it is:
set clock forward with date -s
wait for clock to catch up.
set clock back to real time.
clock doesn't catch up untill the time passes the time it was set forward
too.

This is might seem a small bug but for some reason the clocks also
decide to jump an hour forward after each suspend / resume cycle.
(probably has something todo with my time zone which is gmt-1)

I think that if the simple problem is fixed the complex problem will be
hidden, but I don't care as long as my clock shows the correct time.

And then it takes an hour before it show a usable time again, if my laptop
/ system doesn't suspend before that.

Comment 1 Jonathan Blandford 2000-02-04 19:51:59 UTC

This has finally been fixed, and was just put in Rawhide.

Comment 2 Hans de Goede 2000-02-13 14:51:59 UTC

I just tried gnome-core-1.0.55-7 (dated 02/09/00)
And this bug still seems present both in the normal and Afterstep clock, I used
the method described above to make the clock freeze.

Comment 3 Jonathan Blandford 2000-02-14 00:12:59 UTC

Sorry, I should have been more clear.  The bug was in gtk+, so try upgrading
that see if it fixes it.  If this doesn't fix it, reopen the bug, and we'll try
to figure it out, but it seems to work here. (TM)

Comment 4 Hans de Goede 2000-02-14 06:54:59 UTC

I still have the problem with gtk+-1.2.6-5, the latest I can get my hands on, in
which version should it be fixed?

Comment 5 Hans de Goede 2000-03-02 10:33:59 UTC

Running with the latest gnome-core gnome-libs and gtk from the snapshots dir on
ftp.beta.redhat.com I still have this problem. Even worse if I now set the time
backwards not only the clock freezes, but also sawmill.

I do get a few heuh time seems to be traveling backwards messages in my Xlog

Comment 6 Hans de Goede 2000-03-11 14:39:59 UTC

Okay, this bug is fixed for me in the 4 march snapshot, so I'm closing it,
the sawmill problem still is there, but the clock problem is gone.

So I'll open a new bug report for sawmill.

In the meanwhile I'm closing this one.