Committed to Jaunty (target 2.6.28-13.44)
** Changed in: linux (Ubuntu Jaunty)
Status: In Progress => Fix Committed
** Description changed:
- *NOTE* this is not a bug in the upstream kernel: as far as I can tell,
- it exists only in patched Ubuntu kernels.
+ SRU justification:
+
+ Impact: The joydev driver blacklists some input devices based on a
+ keymask. This does not work for the wacom driver as this does not set
+ the checked key.
+
+ Fix: Add another key to the blacklist to catch digitizers and tablets.
+ Patch prepared to be submitted upstream.
+
+ Testcase: Running X in Intrepid and onwards will result in a broken
+ joystick device visible for the tabled. Which is not there after.
+
+ [submitted upstream]
---
joydev blacklists devices that claim BTN_TOUCH (which excludes
touchscreens and so forth), but not BTN_DIGI (which would exclude
tablets). Without this blacklisting, a non-functional joystick device
appears which interferes with the function of joystick-supporting
applications.
This went unnoticed in the past since until recently the wacom driver
unconditionally claimed BTN_TOUCH whether or the device was a TabletPC
touchscreen.
Original report:
---
In Intrepid, the Wacom driver seems to create a /dev/input/js node--
When X is running, these devices are nonfunctional--they return -32768
on all axes, according to jstest.
Unfortunately, this plays havoc with games that use joysticks-- if the
tablet happens to be joystick zero, the game tries to use it, and ends
up with a joystick that's stuck at full up-left. Udev hackery might be
able to solve this, but for the time being i've been relegated to
manually deleting the tablet's joystick node before starting up any
games.
--
tablet devices show up as non-functional joysticks
https://bugs.launchpad.net/bugs/300143
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
