keycodes all off by one with GTK and $DISPLAY pointing to an R5 server

[Russell Shaw]

Kean Johnston wrote:
>> Gtk should use XLookupString to convert the keycode to
>> keysym, because the mappings can vary between servers.
>> Looks like gtk needs fixing. I don't use gtk any more.
> 
> I'm sure Owen can shed some light on this.
> 
> Whats *really* odd is that Shift-q yields 'Q', as it
> should. Ctrl-q yields Ctrl-Shift-Tab, but Ctrl-Shift-q
> yields Ctrl-Q (in gvim that is).
> 
> So it seems like the Shift state makes the problem
> go away, and without the shift key down, 'q' and 'Tab'
> have their keycodes borked. Why its only those two
> keys is a complete and utter mystery to me.

Maybe your XF86Config file has the wrong keyboard in it.
It has various options:

Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
Option "XkbVariant" ""
Option "XKbOptions" ""
Option "XkbKeycodes" "xfree86"
Option "XkbTypes"    "basic+pc"
Option "XkbSymbols"  "us(pc102)"
Option "XkbGeometry" "pc(pc102)"
Option "XkbCompat"   "basic"