Created attachment 107313 [details] Xorg log for xf86-input-synaptics installed / xf86-input-wacom installed X.Org X Server 1.16.1 loads Synaptics driver for Wacom Bamboo graphics tablet (CTL-460K) and crashes. I use xf86-input-wacom 0.26.0 driver from http://linuxwacom.sourceforge.net/ for my Wacom tablet and xf86-input-synaptics 1.8.1 for the touchpad in my notebook. When I plug in the Wacom tablet before X.Org Server starts it crashes immediately after start and when I plug in the Wacom tablet after X.Org Server starts it crashes, too. I tested the following cases: xf86-input-synaptics installed / xf86-input-wacom installed: Crash xf86-input-synaptics installed / xf86-input-wacom not installed: Crash xf86-input-synaptics not installed / xf86-input-wacom installed: No crash xf86-input-synaptics not installed / xf86-input-wacom not installed: No crash I attached the Xorg log from the first case.
I fixed the crash with a new "InputClass" section in my X.Org X Server configuration: Section "InputClass" Identifier "Wacom device" MatchVendor "Wacom|WACOM" Driver "wacom" EndSection
Still a bug in synaptics, it certainly shouldn't crash. Reopening.
please run evemu-describe against the Wacom Bamboo Pen Finger device and attach the output here. Thanks. more info: http://www.freedesktop.org/wiki/Evemu
Created attachment 108671 [details] evemu-describe for Wacom Bamboo Pen Finger device
Huh, what's going on here. ABS_MT_SLOT, but no ABS_MT_POSITION_X? That's not a homebrew kernel or something, is it? Really looks like a wacom kernel issue, maybe jason knows more
(In reply to Peter Hutterer from comment #5) > Huh, what's going on here. ABS_MT_SLOT, but no ABS_MT_POSITION_X? That's not > a homebrew kernel or something, is it? It is a Vanilla kernel 3.17.0 with a few patches applied from Arch Linux [core] repository.
if it's 3.17 that could be the recent wacom cleanup patches. Benjamin?
Well, it look like the new wacom driver does not like your device :( Can you attach a hid-recorder[1] trace of all of the wacom devices it finds on your setup? (when Xorg does not crash). [1] http://bentiss.github.io/hid-replay-docs/
There is no "hidraw" module on my kernel. The kernel config you can see here: https://projects.archlinux.org/svntogit/packages.git/tree/trunk/config.x86_64?h=packages/linux I have no device node like /dev/hidrawN. hid-recorder only shows a USAGE message, but no trace.
I've figured out that X.org Server only crash when I use this config section: Section "InputClass" Identifier "touchpad" Driver "synaptics" MatchIsTouchpad "on" Option "TapButton1" "1" Option "TapButton2" "3" Option "TapButton3" "2" Option "VertEdgeScroll" "true" Option "HorizEdgeScroll" "true" Option "CornerCoasting" "true" Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0" Option "SecondarySoftButtonAreas" "58% 0 0 8% 42% 58% 0 8%" EndSection It looks like 'MatchIsTouchpad "on"' matches the Wacom Bamboo Pen Finger device, too. PS: I removed the additional Section mentioned in comment #2.
don't worry about the xorg.conf, this is a kernel issue. Do you know the last kernel version that worked for you? You don't have a /dev/hidraw0 or something? Note that the N must be replaced with the number of your device, try them all to find the right one.
I rarely use the Wacom Bamboo at my notebook. The last time I used it was fall 2013, around Kernel version 3.11 or 3.10. There is no device node that begins with hidraw in /dev/ (or in its subfolders). Note: It's a Wacom Bamboo without touchpad support.
Not having a hidraw node while your device is plugged is rather worrying (your kernel is compiled with HIDRAW=Y). Can we also have a look at the dmesg when the device is plugged?
Created attachment 109978 [details] dmesg entries after connecting the device
Sorry for the lag. The bug has actually been fixed in the kernel v3.19 for Bamboo Pen CTL460 (product ID 0x00d4). Please try a v3.19 or v4.0-rc series and close the bug if your device now works properly.
(In reply to Benjamin Tissoires from comment #15) > Please try a v3.19 or v4.0-rc series and close the bug if your device now > works properly. Actually, if it works, the bug should be closed as a duplicate of bug #88903
*** This bug has been marked as a duplicate of bug 88903 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.