Created attachment 397360 [details] udev: wacom add: check_driver Following situation: -I own a Wacom Bamboo Fun Pen & Touch (USB) -My kernel config properly specified to build the correct drivers. -xf86-input-wacom is emerged -I have both wacom and synaptics enabled in my INPUT_DEVICES. -The tablet was recognized as a touchpad and only usable as such. The stylus was inactive. The fix: Force the use of the wacom driver (automatically, synaptics had been loaded, which does not speak the protocol of the stylus). The corresponding rule is attached. (used like that in /etc/udev/rules.d You may want to add this to /usr/lib*/udev/rules.d/wacom.rules or change that file to one of the versions suggested at http://linuxwacom.sourceforge.net/wiki/index.php/Fixed_device_files_with_udev
Enhancement… I'm not so sure about the categories, but I want to underline that the tablet does not work as intended without this.
Looks similar to https://bugzilla.gnome.org/show_bug.cgi?id=739728 - in which case this would be a bug in xf86-input-synaptics (bad 50-synaptics.conf file), not in libwacom. Please attach the output of "emerge --info xorg-server libwacom xf86-input-synaptics"
Created attachment 397462 [details] emerge --info
Thanks. In xf86-input-synaptics-1.8.1 we install 50-synaptics.conf without modifications, so it probably should be ok. I am curious why your "check_driver" patch works: the check_driver script is not a part of udev or systemd; as far as I know it's an obsolete, Debian-only tool that Debian provided with their xorg-input-wacom package until ~2010. So I wonder where it came from on your modern Gentoo system :) (And of course the sourceforge wiki page is very, very obsolete.) Our xf86-input-wacom is old (we have 0.24.0, upstream is 0.28.0) - maybe the problem is fixed in a newer release? Upstream commit 6a9c6a22 (match tablets by raw USP/PnP id instead of kernel device name) sounds like something that might help.
(I'm sorry for being too busy these days…) So, I checked. The check_driver utility is not on my system. So something else must have fixed the problem. I have no clue what and I won't find time to investigate it for nearly a month.
I'm going to mark this as WORKSFORME. If you find there's still a problem, feel free to reopen.
