Bug 427258

Summary:	Wacom Tablet touch screen sometimes not recognizing clicks, but only in KDE applications
Product:	[Plasma] plasmashell	Reporter:	Basti <baschi29>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	baschi29, nate, plasma-bugs
Priority:	NOR
Version:	5.18.5
Target Milestone:	1.0
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Basti 2020-10-02 16:34:06 UTC

SUMMARY

So I came across this very weird bug: Sometimes when connecting the Wacom touchscreen (aka. opening the Laptop/logging in), touch-clicking inside kde does not work. The coursor moves to the position clicked, but no click is registered. 

Clicking with the mouse somewhere else inside KDE omits the original click from the touchscreen. Trying clicking in e.g. Firefox or Thunderbird does always work, so I think it's not an issue with the touchscreen or the drivers.

Reconnecting the tablet a few times always solves the problem, but is very annoying.

STEPS TO REPRODUCE
Happens to my experience always for the initial login while only using the Laptop screen and sometimes when connecting (aka. opening) the touchscreen while using a second monitor.

I hope this is the right place for the bug report and this has something to do with KDE Plasma, but I did not find a better place to start asking for help with this problem.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.4.0-48
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
xsetwacom version: 0.39.0

Comment 1 David Edmundson 2020-10-03 23:21:13 UTC

So sometimes it works in all apps and stays working the whole time it's connected

Sometimes it only works in some apps and that persists till the next time it's reconnected?


Does clicking in "xev" tell us anything.

Comment 2 Basti 2020-10-04 07:39:03 UTC

Exactly.
If it is not working I have to reconnect a few times to get it working again. It does not suddenly start working in all apps without reconnecting. If it's working it stays working in all apps as long as I don't reconnect it (then it sometimes stop working again).

In xev I get the following output while its not working inside kde:

ButtonPress event, serial 37, synthetic NO, window 0x7000001,
    root 0x5c5, subw 0x0, time 219651, (123,78), root:(123,114),
    state 0x10, button 1, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x7000001,
    root 0x5c5, subw 0x0, time 219736, (123,78), root:(123,114),
    state 0x110, button 1, same_screen YES

And while its working in all apps (I tried to not get a MotionNotify event in between, but wasn't able to):

ButtonPress event, serial 40, synthetic NO, window 0x7000001,
    root 0x5c5, subw 0x0, time 642039, (109,77), root:(109,113),
    state 0x110, button 1, same_screen YES

MotionNotify event, serial 40, synthetic NO, window 0x7000001,
    root 0x5c5, subw 0x0, time 642099, (109,77), root:(109,113),
    state 0x110, is_hint 0, same_screen YES

ButtonRelease event, serial 40, synthetic NO, window 0x7000001,
    root 0x5c5, subw 0x0, time 642099, (109,77), root:(109,113),
    state 0x110, button 1, same_screen YES

Of course I'm no expert, but the xev output seem normal to me. Where else can I look for errors?

Comment 3 Bug Janitor Service 2020-10-19 04:33:16 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 Basti 2020-10-19 05:59:42 UTC

Forgot that I needed to change the Status after reporting back.

Comment 5 Nate Graham 2021-08-31 18:29:59 UTC

Figured it out and fixed it. It's a bug in a setting in the Wacom driver. See Bug 440556.

*** This bug has been marked as a duplicate of bug 440556 ***