On-screen keyboard (gok v1.0.7-0ubuntu3) fails

Thanks for your bug report. I'll upload gok 1.0.9 in some minutes - can you check with that version and or 1.0.8 to see if they work better for you?

1.0.8 works fine for me on my dapper desktop, but I get nearly the same error as him on the Live CD version.

ubuntu@ubuntu:~$ gok
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 150 error_code 166 request_code 144 minor_code 3)

This still happens on the 20060518 Live CD which has gok 1.0.10-1ubuntu1.

Im also affected by this bug. Using DAPPER with all latest updates. Hopefully this will be resolved soon, since our handicapped students are unable to use DAPPER now and are forced to use fallback WinXP machines which were to be converted to DAPPER but aslong as accessibilty features dont work we are forced to stick with WinXP.

ps. This is what I also tried:
q@zavod:/dev/input$ sudo mkdir mknod /dev/js0 c 13 0

and now I receive the following error when lunching GOK:
GTK Accessibility Module initialized
Bonobo accessibility support initialized
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 150 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

please fix this bug as soon as possible.

Also tried 0.8 and 0.9 but I receive the same error.

ps. This is what I've noticed when removing GOK
I/O warning : failed to load external entity "/var/lib/scrollkeeper/(null)/scrollkeeper_cl.xml"

wtf??? is this??

Okay. Here is my experience with this bug:

josh@dell:~$ gok --sync
GTK Accessibility Module 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 238 error_code 169 request_code 147 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

What you might need to know is that I also use the IOGear MiniView Micro 2-port KVM switch with built in cables. I have a feeling that might be the problem. Please let me know if you need any more information! Thanks! Best of luck!

Hi,

I believe that error is described (and solved) here: http://www.ubuntuforums.org/showthread.php?t=186890&highlight=gok

Please also try SOK, which will be the default in Ubuntu 6.10:
https://wiki.ubuntu.com/Accessibility/Projects/SOK

- Henrik

Thanks bunches!

I suggest finding out which X bug this is a duplicate of - I'm sure it is.

I believe Bill Haneman is finishing up a patch to have GOK fail more gracefully when it encounters this problem. BTW here are some other links related to this issue (i.e. phantom wacom input devices in ubuntu's x config):

http://www.chenqi.org/blog/archives/2006/06/howto_fix_gok_s.html
or
http://gnomesupport.org/forums/viewtopic.php?t=11016

I'm hoping we'll be able to close this soon!

FYI this bug exists in GNOME bugzilla, in case you wish to review that thread:

http://bugzilla.gnome.org/show_bug.cgi?id=350356

The error still occurs in edgy and gok 1.2.0.

The followed the explanation in this thread already mentioned above and it fixed the problem.
http://www.ubuntuforums.org/showthread.php?t=186890&highlight=gok

Crashed for me too on Ubuntu Edgy (gok 1.2.0), here's report:

I've got this too. I'll spare the report as it's exactly the same.

Here's a crash report.

Isn't this a dup of bug 58600?