FS#20037 - [xf86-input-synaptics] synaptic driver steals wacom touchpad

Attached to Project: Arch Linux
Opened by Nicolas Bigaouette (big_gie) - Thursday, 01 July 2010, 01:49 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 10 August 2011, 12:36 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
The synaptic driver's X configuration file (/etc/X11/xorg.conf.d/10-synaptics.conf) steals my Wacom Bamboo Pen & Touch's touchpad. See http://aur.pastebin.com/y1xG5qR5 for the Xorg.log when I plug in my tablet.

I was able to bypass the problem by adding a match in /etc/X11/xorg.conf.d/10-synaptics.conf for my laptop's touchpad:
MatchProduct "AlpsPS"

How could this be generalized?

I installed http://aur.archlinux.org/packages.php?ID=31540 which provides an X conf:
Section "InputClass"
Identifier "Wacom class"
# WALTOP needs a patched kernel driver, that isn't in mainline lk yet,
# so for now just let it fall through and be picked up by evdev instead.
# MatchProduct "Wacom|WALTOP|WACOM"
MatchProduct "Wacom|WACOM"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
EndSection

Section "InputClass"
Identifier "Wacom serial class"
MatchProduct "Serial Wacom Tablet"
Driver "wacom"
Option "ForceDevice" "ISDV4"
EndSection

Section "InputClass"
Identifier "Wacom serial class identifiers"
MatchProduct "WACf|FUJ02e5|FUJ02e7"
Driver "wacom"
Option "ForceDevice" "ISDV4"
EndSection


# N-Trig Duosense Electromagnetic Digitizer
Section "InputClass"
Identifier "Wacom N-Trig class"
MatchProduct "HID 1b96:0001|N-Trig Pen"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
Option "Button2" "3"
EndSection


Thank you.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 10 August 2011, 12:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  This was fixed long time ago. Should be no issue anymore in 1.4.1 which is in our repositories.
Comment by Andrzej Giniewicz (Giniu) - Wednesday, 29 December 2010, 19:58 GMT
Checkxorg-devel@lists.x.org/msg13263.html"> http://www.mail-archive.com/xorg-devel@lists.x.org/msg13263.html and previous emails, seems like it will be fixed in next release, but meanwhile we can apply two patches from this email to obtain same, general solution.
Comment by Andrzej Giniewicz (Giniu) - Wednesday, 29 December 2010, 20:01 GMT
the url once again: http://www.mail-archive.com/xorg-devel%40lists.x.org/msg12670.html
Comment by Andrzej Giniewicz (Giniu) - Wednesday, 29 December 2010, 20:07 GMT
Oh, and the patches in git for easy inclusion:

http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?id=f2039cb7fba41032ec87315a3a4511472a5ef0dc
http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?id=f5687a6741a19ef3081e7fd83ac55f6df8bcd5c2
Comment by Andrzej Giniewicz (Giniu) - Saturday, 01 January 2011, 10:00 GMT
actually looks like second patch is enough for 1.3 (first is already in code, but was removed later in git that's why it had to be reapplied I believe), I'm attaching source package for tests as described in http://www.mail-archive.com/xorg-devel%40lists.x.org/msg12903.html
(application/x-gzip)    xf86-input-synaptics-1.3.0-3.... (1.2 KiB)
Comment by Andrzej Giniewicz (Giniu) - Monday, 14 March 2011, 22:51 GMT
I think this might be fixed in xf86-input-synaptics that just hit extra, but I cannot confirm as I never experienced this issue. Just reminding about it :)

Loading...