Hallo Harold,

Thanks for the input.  Maybe the solution to this minor itch will be enough
incentive for me to start following the evolution of Xwin again: I'm stuck
on a pre-setup version (nov.2002).

You wouldn't happen to have some guidelines floating around about how to
move from a pre-setup to a setup version of Cygwin/XFree86?  I'm sure I
could handle it myself, I wouldn't like to count the hours I spent
installing X on different OS's, but I don't like to reinvent the warm water.
There are some other things I have to do while at work.  If you don't, I'll
try it at home first.  Just yesterday I rediscovered my first Cygwin
installation on one of my PC's, so this one could serve for a trial.

I tried to read Ivan's explanation, but he lost me halfway.  Monday morning
or I am getting too old for this shit.

Geert

> -----Original Message-----
> From: Harold L Hunt II [mailto:[EMAIL PROTECTED]
> Sent: zondag 21 september 2003 20:59
> To: cygx
> Subject: [Cygwin/XFree86] Duplicate keystrokes in X Server
> 
> 
> [BCCing seven people that have asked about this bug somewhat recently]
> 
> This bug has been around for a long time, but it was thought to be a 
> Cygwin/XFree86-specific bug.  However, I recently learned 
> that this is a 
> general XFree86 bug that is reproducible on, probably, all 
> other platforms.
> 
> Ivan Pascal submitted a patch to XFree86 that fixes the problem.  His 
> description of the problem and his patch can be found in this 
> archive of 
> his email:
> 
> http://www.mail-archive.com/devel%40xfree86.org/msg03245.html
> 
> 
> XFree86's Bugzilla Bug #301 also has information and discussion about 
> this bug:
> 
> http://bugs.xfree86.org/show_bug.cgi?id=301
> 
> 
> Finally, Ivan's patch was applied to XFree86-xserv-4.3.0-13, 
> which can 
> be downloaded and installed via Cygwin's setup.exe.  The "Test100" 
> release notes describe the other changes made in 4.3.0-13:
> 
> http://xfree86.cygwin.com/devel/shadow/changelog.html
> 
> 
> Enjoy,
> 
> Harold
> 


===============================
This email is confidential and intended solely for the use of the individual to whom 
it is addressed. 
If you are not the intended recipient, be advised that you have received this email in 
error and that any use, dissemination, forwarding, printing, or copying of this email 
is strictly prohibited.
You are explicitly requested to notify the sender of this email that the intended 
recipient was not reached.

Reply via email to