Ok, I figured out what was wrong. When a touch class device is created
it must have at least two axes, X and Y. In the previous iteration of
the server it also required a tracking ID axis. I was also thinking of
mandating a proximity axis. This resulted in a check that required at
least four axes for the device to initialize.

The devices I have been testing have four axes, but this is due to them
having extra data like touch width in two directions and an orientation.
I have fixed up the source on my local branch and I'll push the changes
and new packages to test soon.

Thanks!

-- 
xinput2 test breaks touch screen and synaptics touchpad
https://bugs.launchpad.net/bugs/675691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to