Red Hat Bugzilla – Bug 133643
The kernel mistakes wacom tablets for mouse
Last modified: 2015-01-04 17:10:01 EST
Description of problem:
The Fedora kernel treats wacom tablets as mice, so the events from
them flow out of /dev/input/event* directory and /dev/input/mice
directory. This can cause a problem if you use a mouse and a wacom
same time, because a pen pressured event from /dev/input/event* is
disturbed by a button pressed event from /dev/input/mice and you can't
draw anything when you use the tablet in gimp.
Steps to Reproduce:
1.connect a mouse and a wacom tablet.
2.run "cat /dev/input/mice &" from the terminal.
3.move the mouse and the tablet.
You get the text output when you move the mouse or the tablet.
You get the text output only when you move the mouse.
Some people say you can use /dev/input/mouse* instead of
/dev/input/mice for mice device, but you can't use hotplug for mice by
that. And my computer sometimes loses sight of the mouse (I don't know
why), although I don't pull off the mouse, so I must use
/dev/input/mice not /dev/input/mouse*.
Created attachment 104319 [details]
This patch makes the kernel stop treating wacom tablets as mice.
I made a patch for the kernel#2.6.8-1.584 (from
http://people.redhat.com/arjanv/), refering to linuxwacom#0.6.4 (from
Could you try using /dev/input/mouse0 instead of /dev/input/mice for
your core pointer? The /dev/input/mice is per design meant to combine
all input events from mouse-like devices. If you want to prevent the
wacom tablet from contributing events to your core X pointer, the
solution is to explictly specify which mouse device to use for the
Also, make sure the wacom tablet is set up as described here
Finally, we're now packaging the linuxwacom.sourceforge.net drivers in
Fedora Core - please consider installing the linuxwacom RPM from
rawhide and test it (which will require upgrading xorg-x11 as well).
Thank you for the replying.
> Could you try using /dev/input/mouse0 instead of /dev/input/mice for
your core pointer?
Yes, I've done. That is one solution. But I use an usb mouse, which I
can hotplug it using /dev/input/mice. You can't use hotplug if you use
And, what makes the matter worse, as I've written, My system sometimes
lose sight of my mouse. It suddenly makes a sound as if I plugged
something (I think kudzu or hotplug makes such a sound), then the
first mouse dev dies, and another mouse dev is activated. For example,
if I use /dev/input/mouse0 as the first mouse dev, after the noise,
cat /dev/input/mouse0 makes no output, no error. After few second,
/dev/input/mouse1 becames activated, cat /dev/input/mouse1 makes
output when I move the mouse. I checked the log but no error was
found. I think it is another bug.
That is why I persist in using /dev/input/mice. If I use
/dev/input/mice, the events from newly activated mouse dev is sended
to /dev/input/mice after my system lose sight of the mouse.
> please consider installing the linuxwacom RPM from
rawhide and test it
I'll try it, thank you.
I'm sorry if my english is too poor to understand.
I've tested the rawhide linuxwacom RPM (and xorg, udev). But in vain.
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.