Well, there are no events from device 11. The first log X220t_onboard_debug.txt was the only one that had them. I can see you using the track point in X220t_onboard_debug2.txt, so this can't be a general problem for all devices.
Maybe try to reboot, the xsetwacom command should only affect the current session. Then without using xsetwacom at all directly run
killall onboard; ./onboard -d event &>X220t_onboard_debug4.txt
tap some of onboard's keys with the touch screen and quit.
When you run
grep "dev_id=" X220t_onboard_debug4.txt
there should be lines with dev_id=11. The number could change after reboot, but it would always be higher than 2.
Well, there are no events from device 11. The first log X220t_onboard_ debug.txt was the only one that had them. I can see you using the track point in X220t_onboard_ debug2. txt, so this can't be a general problem for all devices. onboard_ debug4. txt
Maybe try to reboot, the xsetwacom command should only affect the current session. Then without using xsetwacom at all directly run
killall onboard; ./onboard -d event &>X220t_
tap some of onboard's keys with the touch screen and quit.
When you run debug4. txt
grep "dev_id=" X220t_onboard_
there should be lines with dev_id=11. The number could change after reboot, but it would always be higher than 2.