kernel-packages team mailing list archive

[Stefan Bader <stefan.bader@xxxxxxxxxxxxx>]

Please open a new bug report for this. The result may be the same but
the device is again a completely new case. In this report (closed a long
while ago) the devices in question could be identified by a certain key
(BTN_DIGI) which this one does not set. Most properties resemble the
definition of an absolute mouse, but again the defined buttons do not
match the current definition. So this requires a new strategy and some
research. Thanks.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/300143

Title:
  tablet devices show up as non-functional joysticks

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Intrepid:
  Won't Fix
Status in linux source package in Jaunty:
  Won't Fix

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/300143/+subscriptions