Hello, I am experiencing what appears to be the same problem as described below. I am attaching my own copy of XWin.0.log and the output of xev which I hope will be helpful.
It appears that for every keypress that fails we have the xev output:
XLookupString gives 1 bytes: (00) "
instead of something like
XLookupString gives 1 bytes: (23) "#"
Also, sometimes after attempting such a failed AltGr key combination,
subsequent keypresses on normal keys act as if the the ctrl key is
depressed. Hitting ctrl again returns the keyboard to its normal
state.
I am running xorg-server 1.5.3 on XP Pro (Version 2002 SP2), and I'm
using a French keyboard [layout "French (Standard)" (40c), type "4"
is detected].
This problem began for me with the move to X.Org X11R7.4 (when all the
/usr/X11R6 paths moved to /usr, etc.). I have found several mentions
of this type of problem in past postings (dating back to 2005 for
example) but they appeared to have been resolved for previous cygwin X
implementations.
Regards. . .
> I can't do |@\{}[] in X (they all need the AltGr key), but I can do #
> perfectly, with the AltGr key. (It's the 3 key with AltGr)
>
> I have a Toshiba laptop running Vista. I used to have a Toshiba with
> XP and Cygwin X and never had this problem.
>
> The non-X bash terminal window works fine.
>
> Here's a sequence from xev where I press down the AltGr key, then
> press and release the 1 key, then press and release the 2 key, then
> press and release the 3 key and then release the AltGr key:
>
XWin.0.log
Description: Binary data
xev.log
Description: Binary data
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
