Title:
tablet devices show up as non-functional joysticks
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/300143/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
joysticks
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/300143/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/300143/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: linux
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/300143
Title:
tablet devices show up as non-functional joysticks
--
ubuntu-bugs mailing list
This is still causing issues with the X52 pro with 10.10 maverick and
the latest kernel. Could someone please fix this in Ubuntu's
repositories so that we don't have to recompile the kernel every update?
--
tablet devices show up as non-functional joysticks
https://bugs.launchpad.net/bugs/300143
Hi, I am using an X-52 with X-Plane 9 under Karmic - this used to work
fine, (Last used it in November or so) but the X-52 is no longer
detected. (Kernel 2.6.31-17-generic) Is there any experiment I can do
that will help debug/resolve this?
hi. no, basically not, since there is a fix already
** Changed in: linux (Ubuntu Intrepid)
Status: Fix Released = Won't Fix
** Changed in: linux (Ubuntu Jaunty)
Status: Fix Released = Won't Fix
--
tablet devices show up as non-functional joysticks
https://bugs.launchpad.net/bugs/300143
You received this bug notification because you
I hope to be able to clarify the situation here. The problem initially reported
with this bug is the fact that tablet devices did show up as non-functional
joysticks and this has been fixed by blacklisting devices that report to have a
BTN_DIGI. Basically the first button a device gets assigned
Hi, I am using an X-52 with X-Plane 9 under Karmic - this used to work
fine, (Last used it in November or so) but the X-52 is no longer
detected. (Kernel 2.6.31-17-generic) Is there any experiment I can do
that will help debug/resolve this?
--
tablet devices show up as non-functional joysticks
** Changed in: linux
Status: Confirmed = Fix Released
--
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
Hi
I hope i can permit to give my two cents about this :
I'm a owner of a X52, and i wonder if all this stuff around BTM_DIGI is
related to the fact that this stick gets a mouse control (with its click
button). For the 39 buttons it has (of course) quite less but it has a mode
switch that
acts
There has been some more discussion on that (see
http://markmail.org/message/5jraw2mk6k6nvlos). In essence the maintainer seemed
to be rather thinking that the joystick should not use the BTM_DIGI.
Unfortunately I don't know what the solution should be and the discussion went
silent after
I don't know if this is the right place to report following bug:
On karmic my X52 pro is not detected again. It appears that the
regression is still active in karmic.
linux-source-2.6.31/drivers/input/joydev.c:854
static const struct input_device_id joydev_blacklist[] = {
/* ... snip */
Sorry for raising false hopes. The fix message is just a false positive. The
current state is that it is reverted to before the fix. So tablets not working
but the joystick does. Have not looked at the state upstream lately...
--
tablet devices show up as non-functional joysticks
This bug was fixed in the package linux - 2.6.28-15.52
---
linux (2.6.28-15.52) jaunty-proposed; urgency=low
[ Stefan Bader ]
* Revert SAUCE: ACPI: Populate DIDL before registering ACPI video device
on Intel
- LP: #423296
* SAUCE: Allow less restrictive acpi video
thanks for fixing. how are chances that the fix will make it into 2.6.32
mainline? :-)
--
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.
--
can someone make it clear that the X52 actually has 39 buttons. it seems
that they're working again on the base of assumptions :-)
As far as I can remember that fact had been replied already and they got some
real debug data to work with. :)
--
tablet devices show up as non-functional
Tim, I saw a bit of discussion going on on linux-input (linux kernel
HID problem with Saitek X52 Pro Flight System) between Jiri Kosina and
Dmitry Torokhov about this and Jiri sounded like being on the same
issue. Maybe you want to jump into that thread.
--
tablet devices show up as
i'm not subscribed to that list, but browsing the archive i found
following statement in the mentioned thread:
I find it doubtful that the device actually has 39 buttons...
can someone make it clear that the X52 actually has 39 buttons. it seems
that they're working again on the base of
It seems to me that the correct fix in this case would have been to fix
the x25/x52pro drivers to not advertise BTN_DIGI, since they are not
that sort of device, rather than re-regressing the way tablets are
handled. :(
--
tablet devices show up as non-functional joysticks
If I prepared another patch which also fixed x25/x52pro, would that be
accepted?
--
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.
--
Tim Cole [2009-09-17 13:38 -]:
If I prepared another patch which also fixed x25/x52pro, would that be
accepted?
Sure. We just backed it out since it's the fastest and most robust way
of fixing a regression.
Thanks!
--
tablet devices show up as non-functional joysticks
I'll get on that then, thanks.
--
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
This bug was fixed in the package linux - 2.6.27-14.41
---
linux (2.6.27-14.41) intrepid-proposed; urgency=low
[ Stefan Bader ]
* Revert SAUCE: input: Blacklist digitizers from joydev.c
- LP: #300143
linux (2.6.27-14.40) intrepid-proposed; urgency=low
[ Amit Kucheria ]
Nobody really wants to keep a blacklist in sync manually with devices popping
up and going at a rate they do. The detection based on the BTN codes might or
might not be ideal. But on the other hand any device can only claim to be
something, so your theoretical device with all in one likely
linux (2.6.27-14.41) intrepid-proposed; urgency=low
.
[ Stefan Bader ]
.
* Revert SAUCE: input: Blacklist digitizers from joydev.c
- LP: #300143
--
tablet devices show up as non-functional joysticks
https://bugs.launchpad.net/bugs/300143
You received this bug notification because
wontfixing in jaunty, too.
** Changed in: linux (Ubuntu Jaunty)
Status: Triaged = Won't Fix
--
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
I have to second the posting of sothis. I have an Saitek X52pro joystick
and cannot use it on jaunty with kernel 2.6.28-15-generic because no
/dev/input/js0 device is created! The same joystick works with
2.6.28-14-generic.
--
tablet devices show up as non-functional joysticks
i don't know much about the input subsystem of the kernel, but wouldn't
it be better to just blacklist devices according to their vendor and
product id if applicable, and not according to features they may or may
not have? someday there might be a grafic tablet with integrated mini
joystick, using
I set this back to high as I commit (and soon upload) the revert of the
patch. We are then at the stage we were before with the tablets creating
an unusable joystick and have to wait how upstream handles this. I would
hope there is a way that joysticks do not use BTN_DIGI but lets see.
** Changed
** Bug watch added: Linux Kernel Bug Tracker #14049
http://bugzilla.kernel.org/show_bug.cgi?id=14049
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=14049
Importance: Unknown
Status: Unknown
--
tablet devices show up as non-functional joysticks
The patch would cause regressions. The fix needs to be done upstream and
won't be backported to Intrepid.
** Changed in: linux (Ubuntu Intrepid)
Status: Fix Committed = Won't Fix
** Changed in: linux (Ubuntu Intrepid)
Assignee: Stefan Bader (stefan-bader-canonical) = (unassigned)
--
** Changed in: linux
Status: Unknown = Confirmed
--
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
Reopening, because this caused a regression for existing working
hardware. Can you please revert or tighten that change?
** Tags added: regression-updates
** Changed in: linux (Ubuntu Jaunty)
Importance: Undecided = Critical
** Changed in: linux (Ubuntu Jaunty)
Status: Fix Released =
the fix causes a regression in 2.6.28-15. the saitek x52 and x52pro
joysticks get blacklisted now too, i.e. the joystick device
/dev/input/js* won't be created.
--
tablet devices show up as non-functional joysticks
https://bugs.launchpad.net/bugs/300143
You received this bug notification because
Can someone with an affected tablet check the current proposed kernel to
see whether the issue got fixed there. I only have a Bamboo to test and
that seems to get the BTN_TOUCH key set, so it does not trigger the bug.
--
tablet devices show up as non-functional joysticks
This bug was fixed in the package linux - 2.6.28-15.48
---
linux (2.6.28-15.48) jaunty-proposed; urgency=low
[ Andy Whitcroft ]
* SAUCE: pnp: add PNP resource range checking function
- LP: #349314
* SAUCE: i915: enable MCHBAR if needed
- LP: #349314
[ Brad Figg ]
Accepted linux into jaunty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
--
tablet devices show up as
** Branch linked: lp:ubuntu/karmic/linux-ports
--
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
** Tags added: hw-specific
--
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
Accepted linux into intrepid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
Commited to Intrepid (target 2.6.27-14.34)
** Changed in: linux (Ubuntu Intrepid)
Status: In Progress = Fix Committed
--
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,
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:
+
+
This bug was fixed in the package linux - 2.6.30-3.4
---
linux (2.6.30-3.4) karmic; urgency=low
[ Kees Cook ]
* SAUCE: [x86] implement cs-limit nx-emulation for ia32
- LP: #369978
[ Stefan Bader ]
* SAUCE: input: Blacklist digitizers from joydev.c
- LP: #300143
It has been lost in the mass of bugs. This also looks like something
that should get upstream.
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Stefan Bader (stefan-bader-canonical)
--
tablet devices show up as
I just added a bit of description and the signed-off-by trail and will
try to get that submitted upstream.
** Attachment added: Updated patch for upstream submission
http://launchpadlibrarian.net/26075898/0001-UBUNTU-SAUCE-input-Blacklist-digitizers-from-joyd.patch
--
tablet devices show up
Here (http://people.ubuntu.com/~smb/bug300143/) would be some test
kernels containing the patch. Can someone confirm this works as
expected? Thanks
--
tablet devices show up as non-functional joysticks
https://bugs.launchpad.net/bugs/300143
You received this bug notification because you are a
Does anyone actually care about this bug?
** 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.
+
+ ---
+
joydev blacklists devices that claim BTN_TOUCH (which excludes
touchscreens and so forth), but
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)
** Changed in: linux (Ubuntu)
Target: None = jaunty-alpha-5
--
tablet
Examining the latest Jaunty .diff.gz, it looks like the issue is still
present in Jaunty kernels.
--
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
UEVENT[1231455478.455224] add
/devices/pci:00/:00:1d.0/usb4/4-1/4-1:1.0/input/input18/mouse1 (input)
UEVENT[1231455478.470234] add
/devices/pci:00/:00:1d.0/usb4/4-1/4-1:1.0/input/input18/event7 (input)
UEVENT[1231455478.484739] add
my kernel (I am affected by the problem also) is 2.6.27-9-generic on an
amd64 system, btw
** Changed in: linux (Ubuntu)
Sourcepackagename: wacom-tools = linux
--
wacom tablet shows up as (non-functional) joystick
https://bugs.launchpad.net/bugs/300143
You received this bug notification because
It's definitely a kernel issue; /proc/bus/input/devices reports:
I: Bus=0003 Vendor=056a Product=0042 Version=0126
N: Name=Wacom Intuos2 6x8
P: Phys=
S: Sysfs=/devices/pci:00/:00:1d.0/usb4/4-1/4-1:1.0/input/input19
U: Uniq=
H: Handlers=mouse1 event7 js0
B: EV=1f
B: KEY=18df 1f 0 0 0
Looking at our own patched kernel sources, it looks like we report
BTN_TOUCH only for TabletPC. Which may actually be correct.
In that case, though, we also need to augment the blacklist in joydev,
which is currently still just:
static const struct input_device_id joydev_blacklist[] = {
Evidently this is a consequence of merging the updated wacom driver
(which we had to do for X compatibility).
--
wacom tablet shows up as (non-functional) joystick
https://bugs.launchpad.net/bugs/300143
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(Specifically, the bitmask reported by /proc/bus/inputs/devices
corresponds to BTN_STYLUS2 | BTN_STYLUS | BTN_TOOL_FINGER |
BTN_TOOL_AIRBRUSH | BTN_TOOL_BRUSH | BTN_TOOL_RUBBER | BTN_DIGI |
BTN_EXTRA | BTN_SIDE | BTN_MIDDLE | BTN_RIGHT | BTN_LEFT)
[BTN_TOOL_PEN also being an alias for BTN_DIGI,
Looking at the source, it looks like blacklisting BTN_DIGI in addition
to BTN_TOUCH for joysticks is the correct thing to do. So that would
be:
static const struct input_device_id joydev_blacklist[] = {
{
.flags = INPUT_DEVICE_ID_MATCH_EVBIT |
** 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
** Attachment added: patch to properly blacklist tablets and digitisers from
being joystick devices
http://launchpadlibrarian.net/21040355/joydev-blacklist-tablets.diff
--
tablet devices show up as non-functional joysticks
https://bugs.launchpad.net/bugs/300143
You received this bug
Thanks Tim, I'll mark this bug as Triaged so a kernel team member can
deal with it. Cheers.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Status: Confirmed = Triaged
--
tablet devices show up as non-functional joysticks
https://bugs.launchpad.net/bugs/300143
You
wacom-tools is the wrong package for this bug; I have this problem even
on machines without wacom-tools installed.
--
Wacom Joystick device interferes with joystick-using games in X
https://bugs.launchpad.net/bugs/300143
You received this bug notification because you are a member of Ubuntu
Bugs,
In this case, i do have a joystick already hooked up, so the tablet is
js1 instead of js0, but here are the requested files.
I've changed my xorg config file slightly since originally filing the
bug report, to override the HAL hotplug detection of my Tablet, but that
had no effect on the problem.
** Attachment added: xorg.conf
http://launchpadlibrarian.net/20786387/xorg.conf
--
Wacom Joystick device interferes with joystick-using games in X
https://bugs.launchpad.net/bugs/300143
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/20786389/Xorg.0.log
--
Wacom Joystick device interferes with joystick-using games in X
https://bugs.launchpad.net/bugs/300143
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
[This is an automated message]
Hi mightyquinn,
Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log
file from after reproducing this issue. If you've made any customizations to
your /etc/X11/xorg.conf please attach that as well.
** Changed in: wacom-tools (Ubuntu)
Public bug reported:
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
66 matches
Mail list logo
