Comment 8 for bug 1297692

Thanks for chiming in, Tom. It could be the same problem, but I can't really tell yet. Are you using Onboard 1.0.1 from the community repo? The warnings are most likely unrelated, but I'll keep them in mind. I've seen them before but no more since some time into Ubuntu 13.10.

Your device reports as XIDependentTouch like my touch pad, meaning the Touch Input setting would be ignored. Onboard ought to just use the regular (emulated) pointer events then, like it does here. I have no good idea yet where this fails. Bear with me, I guess we need to keep digging.

Please paste this into your terminal again, all lines at once. If you can, make sure you used the touch screen last, not the mouse, before you run this.

(killall onboard; \
xsetwacom --list; xsetwacom --list | cut -f 2 | cut -d " " -f2 | xargs xinput list-props; \
xinput; \
xinput list --long; \
xinput test-xi2 2) &>X220t_xinput.txt

Again, tap the little window a few times somewhere in the middle, close it and attach X220t_xinput.txt here. The list of devices was missing before and there was some confusion about which id is what device.

Then please collect debug output from Onboard. Turn the Input event source setting back to "XInput" before, because the Gtk path doesn't log pointer events.

(killall onboard; onboard -ddebug) &>X220t_onboard_debug.txt

Once the keyboard shows, tap a few of its keys (any keys really), quit Onboard and attach X220t_onboard_debug.txt here. I'm looking for lines containing "TouchInput: listening to" and "TouchInput: device event".