GNOME Bugzilla – Bug 350356
The program 'gok' received an X Window System error
Last modified: 2007-01-10 14:50:04 UTC
i am using a wireless mouse keyboard combo i am running ubuntu 6.06 gnome desktop everthing is working great but gok. when i enter "gok in the terminal. i get this message in the terminal. user@user-desktop:~$ gok /dev/js0: No such file or directory The program 'gok' received an X Window System error. This probably reflects a bug in the program. The error was 'BadDevice, invalid or uninitialized input device'. (Details: serial 148 error_code 168 request_code 145 minor_code 3) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
Thanks for the report Brian. After a preliminary investigation I've discovered it might be useful to know what linux distro you are using... can you report that here?
David, Thanks for the reply. The linux distro that i am trying to use gok in is Ubuntu Linux 6.06. The error occurs when i'm use the Gnome desktop, Xfce desktop and KDE desktop.
Brian, I think this might be an issue with Ubuntu and X... Could you take a look here: http://gnomesupport.org/forums/viewtopic.php?t=11016&start=0&postdays=0&postorder=asc&highlight=&sid=0b3f4ec08689dcc597da7f9057c51c0c The solution was to comment out sections of your X configuration file. It would be great if you could investigate if this works for you and report back. If you have no luck we'll continue to investigate.
There's something weird about one of the input devices in the xserver configuration which causes it to crash when touched. Gok tries to check out all these input devices (in case it wants to receive info from them) and it seems one of them is not OK. It is likely that ANY program which pinged all the xinput devices would hit this problem, but I may be mistaken. Anyhow it does look as though it could be an xserver issue. That said, gok might be able to work around this by installing its own x error trap, so at least it doesn't crash. Will look into that. Bill
I checked out the xorg.conf on my ubuntu laptop. It seems the xorg.conf in ubuntu is always including the wacom xinput device driver, which seems to be a mistake on ubuntu's or XOrg's part. The root cause of the problem does not appear to be GOK, which is just calling to XOpenDevice on a device which the xserver has listed as an input device.
*** Bug 351993 has been marked as a duplicate of this bug. ***
I have installed an error trap to prevent the x error from crashing gok. The root cause is in the xserver/driver/config, but at least we can survive it now. Robustness is good. Fixed in cvs.
That fixed it! :) I commented out the sections of the X configuration file as specificed in: http://gnomesupport.org/forums/viewtopic.php?t=11016&start=0&postdays=0&postorder=asc&highlight=&sid=0b3f4ec08689dcc597da7f9057c51c0c Now it works great. This was my first bug report and I was worried about getting flamed, You guys rock! :)
Brian, I think some cred goes to the gnome support forum but it is always a pleasure for Bill and I to hear such kind words. It would be a terrible thing if folks were afraid to report bugs! We rely on it. Thanks again. (Now... one of us should make sure there is an Ubuntu bug filed...)
Related Ubuntu bugs: https://launchpad.net/distros/ubuntu/+source/wacom-tools/+bug/40473 https://launchpad.net/distros/ubuntu/+source/wacom-tools/+bug/40806 Brian if you want a possibly better solution read the first bug report... it provide an alternate solution which allows you to use the wacom drivers... although it sounds a bit more complicated.
*** Bug 394900 has been marked as a duplicate of this bug. ***