** Summary changed: - wacom tablet shows up as (non-functional) joystick + tablet devices show up as non-functional joysticks
** Description changed: - Binary package hint: wacom-tools + 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. + + 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. ** Description changed: 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 for a long time the wacom driver + unconditionally claimed BTN_TOUCH whether or the device was a TabletPC + touchscreen. This has been fixed in the latest wacom driver sources + which we merged, exposing the joydev bug. 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. ** Description changed: 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 for a long time the wacom driver + This went unnoticed in the past since until recently the wacom driver unconditionally claimed BTN_TOUCH whether or the device was a TabletPC - touchscreen. This has been fixed in the latest wacom driver sources - which we merged, exposing the joydev bug. + 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
