Bug 282676

Summary:	Wacom tablet KCModule breaks tablet input
Product:	[Plasma] wacomtablet	Reporter:	Janek Bevendorff <kde>
Component:	general	Assignee:	Jörg Ehrichs <Joerg.Ehrichs>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	1.3
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:

Description Janek Bevendorff 2011-09-24 12:19:12 UTC

Version:           v1.3 (using KDE 4.7.1) 
OS:                Linux

Having the Wacom tablet KCModule installed renders the tablet completely unusable. Pen taps aren't recognized as clicks by all UI elements, unwanted drag operations happen quite frequently, finger taps have absolutely no effect, double tapping the pen shows all windows next to each other, Greasepencil in Blender 2.5 adds straight lines at the end of each stroke etc.

I have filed a (more detailed) bug report about this here: https://sourceforge.net/tracker/index.php?func=detail&aid=3413107&group_id=69596&atid=525124# but then I noticed that most of the issues are not caused directly by the driver but by the KCModule. As soon as I uninstall it, most of them are gone.

I've tried the wacomtablet KCModule from Portage and also compiled the latest sources from kde-apps.org. Both versions have the mentioned issues.

Reproducible: Always

Steps to Reproduce:
1. Install latest wacom kernel module and latest xf86-input-wacom driver
2. Install the Wacom tablet KCModule

Actual Results:  
Tablet input is completely unusable.

Expected Results:  
It should be possible to configure the tablet without breaking everything.

Comment 1 Jörg Ehrichs 2011-09-24 12:48:58 UTC

Hi,
this is in fact a driver bug
caused by using the command
xsetwacom set "tablet" Button 1 1

The latest version of my KCM (1.3.3) does not set this command anymore
But the tabletprofileesrc file has to be deleted when you updated

Comment 2 Janek Bevendorff 2011-09-24 13:29:20 UTC

Well, I installed the latest Git version, restarted KDE and then it suddenly worked. Then I ran make uninstall and reinstalled the version from Portage and also that worked now. Seems there was some left-over, which a Portage uninstall didn't remove. I hate bugs, which solve themselves. :-)

To make sure no errors are left, I deleted the tabletprofilesrc and am now using the latest Git version of the X driver and the KCModule.

Comment 3 Jörg Ehrichs 2011-09-24 16:40:45 UTC

Yes the problem was the tabletprofilesrc

there where still the Button1=1 assignment from previous versions
the 1.3.3 does not create this entry and thus doesn't show the buggy behaviour