After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 394900 - gok crashes on startup
gok crashes on startup
Status: RESOLVED DUPLICATE of bug 350356
Product: gok
Classification: Deprecated
Component: general
unspecified
Other All
: Normal critical
: ---
Assigned To: David Bolter
David Bolter
Depends on:
Blocks:
 
 
Reported: 2007-01-10 02:08 UTC by Diann
Modified: 2007-01-10 14:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Diann 2007-01-10 02:08:39 UTC
Steps to reproduce:
When I start gok, it does not load.  Whether it matters or not, I am using a Dell laptop with an external, wireless keyboard.  The console output is below.

Stack trace:
biteme@biteme-laptop:~$ gok --sync
GTK Accessibility Module initialized
Bonobo accessibility support initialized
/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 250 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.)
application finalize called


Other information:
Comment 1 David Bolter 2007-01-10 14:50:04 UTC
Thanks for the report Diann, I am closing this bug as a duplicate of another one. If that report (http://bugzilla.gnome.org/show_bug.cgi?id=350356) workaround doesn't help you please reopen this one for further discussion. 

We are working towards a more complete solution to this problem. Again, thanks for reporting a gok bug.

*** This bug has been marked as a duplicate of 350356 ***