Bug 398760

Summary: Wacom touch functionality handled entirely by the touchpad driver
Product: [Unmaintained] wacomtablet Reporter: Jason Tibbitts <j>
Component: generalAssignee: Valerii Malov <jazzvoid>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version First Reported In: 3.1.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Verbose output of xsetwacom and xinput

Description Jason Tibbitts 2018-09-17 14:47:12 UTC 
Created attachment 115041 [details]
Verbose output of xsetwacom and xinput

Not sure how better to summarize this.  Basically, kcm_wacomtablet used to indicate that my tablet (an Intuos CTH-680) had touch functionality and offered to disable it.  Was testing it recently and found that the option is no longer present.

Digging further, I found the fundamental issue: the Xorg wacom driver does not claim the finger input but leaves it to be processed the same as a laptop touchpad.  xsetwacom --list doesn't show it, and in fact shows the following:

... Found device 'Wacom Intuos PT M Finger' (16).
... 'Wacom Intuos PT M Finger' (16) is not a wacom device.

It seems that this causes kcm_wacomtablet to believe that the tablet has no touch support.  Really all I wanted was to be able to disable the touch support so that the tablet only works with the pen.  I could use the touchpad KCM to disable touch when a mouse is plugged in, but then I also have some old apple touchpad glued to the center of my keyboard and the setting would disable both of them.

I'm petty sure I could disable the touch support with an xinput command.  I think that kcm_wacomtablet can do it as well even though it doesn't show the option.  Touch support was previously disabled but came back when I deleted my old configuration files.

I'll attach the full output of xsetwacom --list -v and xinput --list --long.

I had previously filed a ticket at https://bugzilla.redhat.com/show_bug.cgi?id=1626695; in there it was said that the current behavior is completely intentional.  (I think that's pretty bizarre, but that's the way it is.)
Comment 1 Christoph Feck 2018-10-03 21:58:09 UTC 
Does 'xinput' show different ID for the tablet and the touchscreen? On my system, I can disable touch separately using

    xinput set-prop <ID> "Device Enabled" 0

where <ID> is the shown ID of the touchscreen.
Comment 2 Justin Zobel 2022-12-01 04:34:43 UTC 
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-12-16 05:13:40 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-12-31 05:23:50 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!