I checked out beta1 and experienced strange problems with the german
keyboard layout (-k de).
It is impossible to use AltGr to get for example "@".
What I see is, that the keysym returned by XLookupString ist the keysym
corresponding to "q".
So maybe my problem has to deal with XFree - but in XFree "@" shows up
just in the right way.
This would be no problem at all, because the events for pressing and
releasing AltGr are sent to the Server, so the server could handle this.
But since in beta1 the function ensure_remote_modifiers is called from
xwin_process_events, ensure_remote_modifiers sees that, according to the
keysym, it looks like AltGr was released. Consequently
ensure_remote_modifiers sends a release event to the server - bingo, I
see a "q" on the screen (which is not what I want).
I solved this by commenting out ensure_remote_modifiers in
So far this imposes no problems, but I think there should be another
Thanks in advance.
> What I see is, that the keysym returned by XLookupString ist the keysym
> corresponding to "q".
> So maybe my problem has to deal with XFree -
Yes, I think your X11 modmap is wrong.
>but in XFree "@" shows up
> just in the right way.
Give me some details. Does it work in all X11 applications, like xterm,
emacs, Mozilla etc? Can you run "xev" and press AltGr+q, and send me the
output? Which XFree86 version are you using?
> I solved this by commenting out ensure_remote_modifiers in
> So far this imposes no problems, but I think there should be another
You will probably run into some other problems later, if you comment out
Get latest updates about Open Source Projects, Conferences and News.