keymap.get_entries_for_keyval returns None when run inside an freenx nxserver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
FreeNX Server |
New
|
Undecided
|
Unassigned | ||
PyGTK |
Expired
|
Critical
|
|||
gtk+2.0 (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Description: Ubuntu 9.10
Release: 9.10
python-gtk2 2.16.0-0ubuntu1
freenx-server: 0.7.3+teambzr10
michael@frigg:~$ python
Python 2.6.4 (r264:75706, Dec 7 2009, 18:45:15)
[GCC 4.4.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import gtk
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
>>> keymap = gtk.gdk.
>>> print gtk.keysyms.Insert, keymap.
65379 None
>>>
This may be an freenx bug, this may be a gtk or pygtk bug... This is when running an X session with freenx-server and connecting remotely. If I ssh to the machine, export my display to :0 (even though the machine is in a headless vm) and run the same test, it returns a proper value. I'm filing the bug under pygtk since that's the highest level package I can think of. This is causing gajim (as of the latest development versions) to crash on startup, with the traceback pointing to the keymap.
Those Xlib warnings are because the freenx-server does not support the XGE extension.
description: | updated |
affects: | pygtk (Ubuntu) → gtk+2.0 (Ubuntu) |
Changed in gtk+2.0 (Ubuntu): | |
status: | New → Triaged |
Changed in gtk+2.0 (Ubuntu): | |
importance: | Undecided → Low |
Changed in libgtk: | |
status: | Unknown → New |
Changed in pygtk: | |
status: | Unknown → New |
Changed in libgtk: | |
importance: | Unknown → Critical |
Changed in pygtk: | |
importance: | Unknown → Critical |
Changed in libgtk: | |
status: | New → Expired |
Changed in pygtk: | |
status: | New → Expired |
This sounds like the same keymap issues that were experienced with an older version. It may be that the solution that was implemented to solve those issues may not resolve this issue or may be aggravating it. I believe this stems out of the new evdev input system that is in use in newer desktops. Unfortunately, the X server in FreeNX is old and does not translate keymaps properly for evdev so several kludges need to be implemented to overcome this shortfall. The only way to resolve these issues so far has been to add specific fixes for the program to do a manual keymap or the login script to do this.