GNOME Bugzilla – Bug 314511
allow GOK to work partially without XInput or XKB
Last modified: 2011-10-14 10:58:10 UTC
Steps to reproduce: 1. On OS X 10.3, install Apple's X11 2. compile and install gok-1.0.5 using gcc3.3 (from XCode-1.5) with: -no-cpp-precomp -O3 -funroll-loops -fstrict-aliasing 3. ./gok Stack trace: ** (gok:22587): WARNING **: Keyboard Geometry cannot be read from your X Server. ** (gok:22587): WARNING **: Keyboard Geometry cannot be read from your X Server. Xlib: extension "XInputExtension" missing on display ":0.0". Bus error (core dumped) Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000010 Thread 0 Crashed: 0 gok 0x00017d58 gok_input_get_device_list + 0x7c 1 gok 0x00018368 gok_input_init + 0x30 2 gok 0x000039dc on_window1_realize + 0xac 3 libgobject-2.0.0.dylib 0x01098828 g_closure_invoke + 0x130 4 libgobject-2.0.0.dylib 0x010abe78 signal_emit_unlocked_R + 0x8e8 5 libgobject-2.0.0.dylib 0x010ab0ec g_signal_emit_valist + 0x760 6 libgobject-2.0.0.dylib 0x010ab38c g_signal_emit + 0x28 7 libgtk-x11-2.0.0.dylib 0x015a8a54 gtk_widget_realize + 0x1a8 8 libgtk-x11-2.0.0.dylib 0x015ba58c gtk_window_show + 0xd0 9 libgobject-2.0.0.dylib 0x01098828 g_closure_invoke + 0x130 10 libgobject-2.0.0.dylib 0x010abad0 signal_emit_unlocked_R + 0x540 11 libgobject-2.0.0.dylib 0x010ab0ec g_signal_emit_valist + 0x760 12 libgobject-2.0.0.dylib 0x010ab38c g_signal_emit + 0x28 13 libgtk-x11-2.0.0.dylib 0x015a800c gtk_widget_show + 0x54 14 gok 0x00027fdc gok_main_open + 0x6f4 15 gok 0x000278bc main + 0x70 16 gok 0x000033e8 _start + 0x188 (crt.c:267) 17 dyld 0x8fe1a278 _dyld_start + 0x64 Other information: There were no errors or warnings during the build. The crash-log implicates glib2 and gtk+2, which are glib-2.8.0 and gtk+-2.6.8 as provided by Fink; I can dig up version information for all the other gnome libs if it would help.
On the fink bugs-tracker item for this, vasi wrote: XKB doesn't work on darwin, other libraries like libxklavier have this problem too. If you can disable use of XKB in gok's configure script that would be best. Otherwise, patch out the part of gok that uses XKB (and if it's an important feature, find an alternate method to accomplish it).
No way GOK can run without XKB and XInput. Can't fix.
Changing to enhancement request.
We could avoid using XInput OK, but we really need XKB. FOr that matter, if we don't have XInput, we pretty much have to have XEvie, so it's sort of a no-win situation. Using the core pointer only, w/o XInput or XEvie, is inherently bugridden 'cause of limitations of X itself. :-(
gok (GNOME on-screen keyboard) development has been stalled and it has been replaced by caribou [1]. Maintainers don't have future development plan so i am closing all the bugs as WONTFIX. [1] https://mail.gnome.org/archives/gnome-bugsquad/2011-October/msg00001.html