Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 77247

Summary: Problems with XFree86 after changing system clock
Product: [Retired] Red Hat Linux Reporter: Need Real Name <zlb>
Component: XFree86Assignee: Mike A. Harris <mharris>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-12-14 15:58:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
X server log file
X config file
This patch seems to solve my problem. none

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.