Bug 1281881 - [regression] Thinkpad X201t wacom penabled touchscreen tablet screen not recognized properly on Fedora 23
Summary: [regression] Thinkpad X201t wacom penabled touchscreen tablet screen not reco...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-wacom
Version: 23
Hardware: ia64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1349686
TreeView+ depends on / blocked
 
Reported: 2015-11-13 17:09 UTC by Jean-François Fortin Tam
Modified: 2016-06-24 01:38 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
: 1349686 (view as bug list)
Environment:
Last Closed: 2016-04-07 01:50:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Xorg.log (29.04 KB, text/plain)
2015-11-16 03:44 UTC, Jean-François Fortin Tam
no flags Details

Description Jean-François Fortin Tam 2015-11-13 17:09:21 UTC
Someone else already noticed the problem here: https://ask.fedoraproject.org/en/question/77611/f23-refuses-to-recognize-tablets-existence/

I also have the Thinkpad X201t which has a wacom tablet built into the screen, and get the exact same symptoms and results as what was reported in that question over there. 


$ lsusb|grep -i wacom

$ dmesg | grep -i wacom
[   12.940811] input: Wacom Serial Penabled 2FG Touchscreen as /devices/pnp0/00:05/tty/ttyS4/serio3/input/input16


In gnome-control-center, the Wacom Tablet panel does not recognize the presence of the wacom hardware.

Comment 1 Peter Hutterer 2015-11-15 20:55:14 UTC
Please attach your Xorg.log and the output of libwacom-list-local-devices. Thanks

Comment 2 Jean-François Fortin Tam 2015-11-16 03:44:54 UTC
Created attachment 1094719 [details]
Xorg.log

Comment 3 Jean-François Fortin Tam 2015-11-16 03:45:52 UTC
$ libwacom-list-local-devices

[Device]
Name=Wacom Serial Tablet WACf004
DeviceMatch=serial:0000:0000;
Class=ISDV4
Width=0
Height=0
IntegratedIn=Display;System;
Styli=0xfffff;0xffffe;

[Features]
Reversible=false
Stylus=true
Ring=false
Ring2=false
Touch=false
TouchSwitch=false
StatusLEDs=
NumStrips=0
Buttons=0
---------------------------------------------------------------
[Device]
Name=Wacom Serial Tablet WACf004
DeviceMatch=serial:0000:0000;
Class=ISDV4
Width=0
Height=0
IntegratedIn=Display;System;
Styli=0xfffff;0xffffe;

[Features]
Reversible=false
Stylus=true
Ring=false
Ring2=false
Touch=false
TouchSwitch=false
StatusLEDs=
NumStrips=0
Buttons=0
---------------------------------------------------------------

Comment 4 Peter Hutterer 2015-11-18 05:06:24 UTC
What's the output of "systemctl status wacom-inputattach" on your machine?

Also, please run evemu-record against the "Wacom Serial Penabled 2FG Touchscreen" device (/dev/input/event14 in the previous log) and touch the screen once. Then attach the output here.

Comment 5 Peter Hutterer 2015-11-18 06:49:11 UTC
managed to reproduce this here. The problem is that the device is both a touchscreen and a tablet device at the same time. libinput does not yet support tablet devices and xorg-x11-drv-libinput usually skips tablets for that reason. In this case libinput does get assigned because it has both the ID_INPUT_TOUCHSCREEN and the ID_INPUT_TABLET udev property.

That's why the touchscreen portion of it works but the stylus part of it doesn't.

I don't have a good solution to this yet, we're lacking the ability to negate xorg.conf matches, so it's extremely hard to say "Don't match on this". Until I can fix this, you'll have to use a local workaround:

$ cat /etc/X11/xorg.conf.d/99-wacom-serial-override.conf
Section "InputClass"
  Identifier "override serial wacom driver"
  MatchProduct "Wacom Serial Penabled 2FG Touchscreen"
  Driver "wacom
EndSection

Comment 6 Jean-François Fortin Tam 2015-11-18 16:34:20 UTC
Yeah, the wacom-inputattach was loaded and active without errors.

FWIW, I've seen this on Wayland too, but I suppose that's precisely because libinput doesn't support it... or would there be Wayland-specific differences here?

Meanwhile, great to hear you managed to reproduce it. So AFAIU you don't need further info from my end?

Comment 7 Peter Hutterer 2015-11-18 20:58:01 UTC
no, I've got all I need thanks. Wayland has the same issue because we use the same input stack, i.e. libinput. There are no specific differences that apply here.

Comment 8 4of92000 2015-11-23 16:13:52 UTC
I was the poster with the problem on the Fedora help page, mentioned in the Description.

For one session, the tablet started working again, but now it again refuses to work. I don't know if that's significant, but I thought I'd throw it in. I don't know how to reproduce it working again, since if I did, I would do that every time I started the computer. Also, I'm pretty new to Linux.

Comment 9 4of92000 2015-11-23 16:16:31 UTC
I just checked the local workaround mentioned in Comment 5, and it works.

Comment 10 Peter Hutterer 2015-11-26 10:34:37 UTC
For the archives: long-term this actually needs a kernel fix. Having the two different devices off the same event node is not ideal and not how other similar devices work. So expect this to get fixed in the kernel, libinput will then just work.

Comment 11 Peter Hutterer 2015-12-07 05:27:27 UTC
The fix is in Dmitry's input tree now.

http://git.kernel.org/cgit/linux/kernel/git/dtor/input.git/commit/?id=e0361b70175f0cd6199dd9ed6679632de73973d4

Comment 12 Peter Hutterer 2016-04-07 01:50:47 UTC
Closing as NEXTRELEASE. If kernel 4.5 ends up in f23 then it'll work there too.

Workaround is outlined in Comment 5.


Note You need to log in before you can comment on or make changes to this bug.