wacom configuration kills gok
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | xorg (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
The current wacom tablet configuration in Ubuntu causes the on-screen keyboard gok to segfault.
Removing the wacom specific lines from xorg.conf fixes the problem. The issue likely pops up here because wacom adds a second pointer input device. GOK is designed to work with two pointer inputs as well.
I'll attach my xorg.conf, showing which lines cause the problem.
Clearly when gok segfaults it is a serious gok bug as well (reported as #42308), but it is clear the the wacom configuration brings it out. Perhaps the problem from xorg's point of view is just that a wacom tablet was detected and configured when I clearly don't have one.
Other's have reported the same thing: http://
| Henrik Nilsen Omma (henrik) wrote : | #2 |
Crash still occurs on latest edgy. Here is a .crash file
| sam tygier (samtygier) wrote : | #3 |
the dupelicate Bug #67617 has a backtrace with debugging symbols
| Changed in xorg: | |
| status: | Unconfirmed → Confirmed |
| Henrik Nilsen Omma (henrik) wrote : | #4 |
Fixed if Feisty with recent upstream update.
| Changed in xorg: | |
| status: | Confirmed → Fix Released |
My xorg.conf file
Note the three commented out wacom sections and these at the end:
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
Without the comments gok segfaults.