Activity log for bug #300143

Date Who What changed Old value New value Message
2008-11-20 00:26:02 Dave Ahlswede bug added bug
2008-12-05 04:08:43 Bryce Harrington wacom-tools: status New Incomplete
2008-12-29 02:19:29 Dave Ahlswede bug added attachment 'lspci.out' (Output of lspci -vvnn)
2008-12-29 02:19:46 Dave Ahlswede bug added attachment 'xorg.conf' (xorg.conf)
2008-12-29 02:20:35 Dave Ahlswede bug added attachment 'Xorg.0.log' (Xorg.0.log)
2009-01-08 22:59:53 Tim Cole title Wacom Joystick device interferes with joystick-using games in X wacom tablet shows up as (non-functiaonal) joystick
2009-01-08 23:00:11 Tim Cole title wacom tablet shows up as (non-functiaonal) joystick wacom tablet shows up as (non-functional) joystick
2009-01-08 23:05:41 Tim Cole wacom-tools: bugtargetdisplayname wacom-tools (Ubuntu) linux (Ubuntu)
2009-01-08 23:05:41 Tim Cole wacom-tools: bugtargetname wacom-tools (Ubuntu) linux (Ubuntu)
2009-01-08 23:05:41 Tim Cole wacom-tools: statusexplanation
2009-01-08 23:05:41 Tim Cole wacom-tools: title Bug #300143 in wacom-tools (Ubuntu): "wacom tablet shows up as (non-functional) joystick" Bug #300143 in linux (Ubuntu): "wacom tablet shows up as (non-functional) joystick"
2009-01-08 23:57:42 Tim Cole linux: status Incomplete Confirmed
2009-01-09 00:39:17 Tim Cole description Binary package hint: wacom-tools 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. 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.
2009-01-09 00:39:17 Tim Cole title wacom tablet shows up as (non-functional) joystick tablet devices show up as non-functional joysticks
2009-01-09 00:40:39 Tim Cole description 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. 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.
2009-01-09 00:42:06 Tim Cole description 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. 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.
2009-01-09 01:07:01 Tim Cole bug added attachment 'joydev-blacklist-tablets.diff' (patch to properly blacklist tablets and digitisers from being joystick devices)
2009-01-09 01:17:48 Connor Imes linux: status Confirmed Triaged
2009-01-09 01:17:48 Connor Imes linux: importance Undecided Medium
2009-01-09 01:17:48 Connor Imes linux: statusexplanation Thanks Tim, I'll mark this bug as Triaged so a kernel team member can deal with it. Cheers.
2009-03-01 20:34:10 Tim Cole description 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. *NOTE* this is not a bug in the upstream kernel: as far as I can tell, it exists only in patched Ubuntu kernels. --- 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.
2009-03-01 20:37:49 Rolf Leggewie linux: statusexplanation Thanks Tim, I'll mark this bug as Triaged so a kernel team member can deal with it. Cheers. setting for next Jaunty milestone. Seems like this is really well triaged and thus easy to either include or reject. I can't help in further debugging this for lack of hardware (and knowledge of kernel internals)
2009-03-01 20:37:49 Rolf Leggewie linux: milestone jaunty-alpha-5
2009-04-28 14:51:45 Stefan Bader linux (Ubuntu): status Triaged In Progress
2009-04-28 14:51:45 Stefan Bader linux (Ubuntu): assignee stefan-bader-canonical
2009-04-28 14:54:25 Stefan Bader attachment added Updated patch for upstream submission http://launchpadlibrarian.net/26075898/0001-UBUNTU-SAUCE-input-Blacklist-digitizers-from-joyd.patch
2009-05-01 16:49:09 Tim Gardner bug task added linux (Ubuntu Jaunty)
2009-05-01 16:49:34 Tim Gardner linux (Ubuntu Jaunty): status New In Progress
2009-05-01 16:49:34 Tim Gardner linux (Ubuntu Jaunty): assignee Stefan Bader (stefan-bader-canonical)
2009-05-01 16:50:09 Tim Gardner linux (Ubuntu): importance Medium Undecided
2009-05-01 16:50:09 Tim Gardner linux (Ubuntu): status In Progress Fix Committed
2009-05-01 16:50:09 Tim Gardner linux (Ubuntu): milestone jaunty-alpha-5
2009-05-01 16:50:09 Tim Gardner linux (Ubuntu): assignee Stefan Bader (stefan-bader-canonical)
2009-05-01 16:50:25 Tim Gardner bug task added linux (Ubuntu Intrepid)
2009-05-01 16:50:52 Tim Gardner linux (Ubuntu Intrepid): status New In Progress
2009-05-01 16:50:52 Tim Gardner linux (Ubuntu Intrepid): assignee Stefan Bader (stefan-bader-canonical)
2009-05-06 15:50:06 Launchpad Janitor linux (Ubuntu): status Fix Committed Fix Released
2009-05-07 07:34:20 Stefan Bader linux (Ubuntu Intrepid): status In Progress Fix Committed
2009-05-07 07:35:24 Stefan Bader linux (Ubuntu Jaunty): status In Progress Fix Committed
2009-05-07 07:37:22 Stefan Bader description *NOTE* this is not a bug in the upstream kernel: as far as I can tell, it exists only in patched Ubuntu kernels. --- 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. 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.
2009-05-07 07:38:45 Stefan Bader bug added subscriber Ubuntu Stable Release Updates Team
2009-06-05 10:06:19 Martin Pitt tags verification-needed
2009-06-16 17:11:49 Steve Beattie tags verification-needed hw-specific verification-needed
2009-07-03 09:20:20 Launchpad Janitor branch linked lp:ubuntu/karmic/linux-ports
2009-08-17 23:56:29 Launchpad Janitor linux (Ubuntu Jaunty): status Fix Committed Fix Released
2009-08-26 05:36:51 Martin Pitt tags hw-specific verification-needed hw-specific regression-updates verification-needed
2009-08-26 05:37:20 Martin Pitt linux (Ubuntu Jaunty): importance Undecided Critical
2009-08-26 05:37:20 Martin Pitt linux (Ubuntu Jaunty): status Fix Released Triaged
2009-08-26 09:41:06 Stefan Bader bug watch added http://bugzilla.kernel.org/show_bug.cgi?id=14049
2009-08-26 09:41:06 Stefan Bader bug task added linux
2009-08-26 09:49:46 Stefan Bader linux (Ubuntu Intrepid): status Fix Committed Won't Fix
2009-08-26 09:49:46 Stefan Bader linux (Ubuntu Intrepid): assignee Stefan Bader (stefan-bader-canonical)
2009-08-26 10:20:44 Bug Watch Updater linux: status Unknown Confirmed
2009-08-27 07:44:25 Stefan Bader linux (Ubuntu Jaunty): importance Critical High
2009-08-31 13:21:17 Martin Pitt linux (Ubuntu Jaunty): status Triaged Won't Fix
2009-09-14 13:52:08 Launchpad Janitor linux (Ubuntu Intrepid): status Won't Fix Fix Released
2009-09-29 08:48:26 Launchpad Janitor linux (Ubuntu Jaunty): status Won't Fix Fix Released
2009-11-20 21:28:09 Eduard Hasenleithner nominated for series linux/2.6.31
2010-01-05 16:21:28 Bug Watch Updater linux: status Confirmed Fix Released
2010-01-28 14:15:51 Stefan Bader linux (Ubuntu Intrepid): status Fix Released Won't Fix
2010-01-28 14:16:16 Stefan Bader linux (Ubuntu Jaunty): status Fix Released Won't Fix
2011-02-04 12:44:31 Bug Watch Updater linux: importance Unknown Medium
2011-02-04 13:43:07 bwRavencl removed subscriber bwRavencl