I have the same problem and came to the same conclusion trying things out with xinput. Then I thought setting the tablet to relative would help it because that would mean a relative movement of 0 but there are two problems with that. The major one being:
xinput set-mode 8 RELATIVE X Error of failed request: XI_BadMode (invalid Mode parameter) Major opcode of failed request: 143 (XInputExtension) Minor opcode of failed request: 5 (X_SetDeviceMode) Mode id in failed request: 0x17 Serial number of failed request: 17 Current serial number in output stream: 17 Works fine for the stylus but the pad does not know relative mode at all. Great... The second problem being that relative is not necessarily what I want. Although less noticeable the same problem exists for the stylus in vice versa - which resets the touchring to 0! and here RELATIVE is NOT an option. Then, the touchring might be preferred to be absolute anyway. That's very bad. Maybe someone has an idea on how to merge the data from the stylus and that from the tablet into one motion-positional tuple so no values overwrite the others!? -- wacom buttons don't work/cause mouse to move to upper left corner and click. https://bugs.launchpad.net/bugs/560180 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
