gok not starting with vnc, but starting with nx

Bug #70269 reported by Francesco Fumanti
This bug report is a duplicate of:  Bug #58600: wacom configuration kills gok. Edit Remove
2
Affects Status Importance Assigned to Milestone
gok (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gok

System:
- headless celeronbox with an uptodate edgy desktop i386 upgraded from dapper
- remote connection through openssh, nx and vnc shipped with ubuntu

gok does not start when forwarding the session through vnc; here is what I get when I try to start it from the terminal:

frafu@UbuntuDesktop:~$ gok
GTK Accessibility Module initialized
Bonobo accessibility support initialized
/dev/js0: No such file or directory

** (gok:14590): WARNING **: Cannot open input device!

Segmentation fault (core dumped)
frafu@UbuntuDesktop:~$ gok &
[1] 14602
frafu@UbuntuDesktop:~$ GTK Accessibility Module initialized
Bonobo accessibility support initialized
/dev/js0: No such file or directory

** (gok:14602): WARNING **: Cannot open input device!

[1]+ Segmentation fault (core dumped) gok

However, when I login into the ubuntubox with nx, gok starts up. Here is what I get when I start it up from the terminal:

frafu@UbuntuDesktop:~$ gok &
[1] 8678
frafu@UbuntuDesktop:~$ GTK Accessibility Module initialized
Bonobo accessibility support initialized

** (gok:8678): WARNING **: Keyboard Geometry cannot be read from your X Server.
/dev/js0: No such file or directory
0 event types available
login mode = false
Word prediction dictionary contains a total of 2979 words
GTK Accessibility Module initialized
Bonobo accessibility support initialized
Usage:program_name [address][:port]

Have a nice day.

frafu

Revision history for this message
Francesco Fumanti (frafu) wrote :

Here is the dump from /var/crash corresponding to the vnc crash.

Revision history for this message
Francesco Fumanti (frafu) wrote :

I was told, that it was a duplicate of bug 42308 that can be found here:
https://launchpad.net/distros/ubuntu/+source/gok/+bug/42308

By the way, you can find in the comments of bug 42308 a link with an explanation about how to fix the problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.