Hallo Harold,
I've finally installed Cygwin/XFree86 with setup, until this morning I was
still using a version that I installed manually (ahum).
Haven't spotted the duplicate keystrokes (yet?).
After setup, I installed XWin-4.3.0-20-Test01.exe, since I experienced the
no key input. This didn't
Thanks, that's very interesting. I found that the suggested xset r off
worked well for me, by completely disabling the X autorepeat stuff, since
there's already windows autorepeat. But it's good to get to the bottom of
these subtle race-condition type bugs.
Lev
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
[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
Hello - I've just arrived at this list, so hope I don't break protocol
in any way!!
I have a problem which can be summarised as 'it's the same as the
following past postings':
http://www.google.com/search?hl=enlr=ie=UTF-8q=+site:www.cygwin.com+xfree86+duplicate+keystrokes
The discussions
Yes, I still have it, happens a couple of times per day, but there are worse
things in life.
-Original Message-
From: Virgilio, Vincent [mailto:[EMAIL PROTECTED]]
Sent: donderdag 5 december 2002 15:23
To: '[EMAIL PROTECTED]'
Subject: Duplicate keystrokes
Hello,
I have noticed that my
Hello,
I have noticed that my keystrokes are sometimes duplicated, invisibly. It
happens in remote xterms, using ssh, usually when I am in gdb.
1. I run XWin in rootless mode on my desktop, with the ssh-agent in
/usr/X11R6/bin/startxwin.sh enabled.
2. Then I ssh(-add) into a remote Linux node,
Vince,
Yes, there are occasionally duplicated keystrokes. Unfortunately, as my
February email describes (which I thank you for finding on your own and putting
a link in your email), the problem is not trivial to solve. We will only gain
new information and insight into this problem by spending
