Bug 77247 - Problems with XFree86 after changing system clock
Summary: Problems with XFree86 after changing system clock
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2002-11-04 07:19 UTC by Need Real Name
Modified: 2007-04-18 16:48 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2002-12-14 15:58:09 UTC

Attachments (Terms of Use)
X server log file (671.88 KB, text/plain)
2002-11-05 00:09 UTC, Need Real Name
no flags Details
X config file (3.46 KB, text/plain)
2002-11-05 00:12 UTC, Need Real Name
no flags Details
This patch seems to solve my problem. (803 bytes, patch)
2002-11-07 23:53 UTC, Need Real Name
no flags Details | Diff

Description Need Real Name 2002-11-04 07:19:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
XFree86-4.2.0: the keys do not repeat after changing system time backwards.

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

How reproducible:

Steps to Reproduce:
1. Change the system clock a coupel of minutes backwards using `date'.

2. The keys do not repeat any more under X before system time gets
   to the point when the time was changed. On my laptop (ATI Rage     
   Mob.), the windows are also frozen (i.e., they can't be dragged).

   I ran into this problem after suspending/resuming my laptop and
   finally I figured out that the problem was caused by the
   'hwclock' command in /etc/sysconfig/apm-scripts/apmscript

   I believe that this bug is related to some timing functions
   in XFree86 4.2.0

Additional info:

Comment 1 Mike A. Harris 2002-11-04 08:45:08 UTC
I probably don't need it, but just in case.... could you attach your
X server config file and log?  It might come in handy perhaps while

Comment 2 Thais Smith 2002-11-04 11:03:10 UTC
Might this be because X events are timestamped? "Old" events would therefore 
get ignored. I get the same problem when correcting the clock under a number 
of different window managers (kwin, metacity, afterstep). Quick workaround is 
to switch to another VT and back again. Just a thought.

Comment 3 Need Real Name 2002-11-05 00:09:09 UTC
Created attachment 83604 [details]
X server log file

Comment 4 Need Real Name 2002-11-05 00:11:27 UTC
Switching to a VT then back does not solve the problem.

I have attached my X config/log files.

Comment 5 Need Real Name 2002-11-05 00:12:03 UTC
Created attachment 83605 [details]
X config file

Comment 6 Need Real Name 2002-11-07 23:53:58 UTC
Created attachment 84104 [details]
This patch seems to solve my problem.

Comment 7 pedro_rodriguez 2002-11-13 18:18:21 UTC
There is a also a fix by Egbert Eich in xfree cvs :


290. Fixed GetTimeInMillis() to use deltas instead of absolute time
     returend by gettimeofday(). This ensures time is monotonic in X
     (Egbert Eich).

Comment 8 Mike A. Harris 2002-12-14 15:58:09 UTC
Indeed Egbert's fix is in CVS.  I have backported the fix to 4.2.1 and 4.1.0,
and it will appear in all future erratum releases.

Thanks guys.

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