When I press one of the buttons of my Cintiq Companion Hybrid, the pen input freezes until I take the pen out of reach or move the cursor using a mouse and no key event (in my case I tried "key +ctrl z -ctrl") gets fired.
This happens on 0.28.0 (latest version compiled from git including kernel drivers, X drivers and libwacom) and 0.26.0 on Ubuntu 14.10.
I also tried my notebook with Ubuntu 14.04 and 0.23.0 and it works like a charm.
Are there any config/log files that I can provide to help?
Best regards,
Jakob
Update: The keys are partially working (They don't seem to work in Krita but if I bind them to 'key m' or such I can type m in a terminal but it still freezes pen input...).
And the Versions I testet is not 0.26.0 but 0.25.0 (the latest in the utopic repo)
The 0.26.0 release did have a bug that could cause similar symptoms, but it should have been fixed in 0.27.0. Could you verify that the 0.28.0 was properly installed for me? One of the following commands should display some output (I'm not sure which on Ubuntu 14.10), that contains e.g. "module version = 0.28.0":
If you are indeed running 0.28.0, then something else is amiss. Since you're familiar with installing the driver, would you mind running a "git bisect" to narrow things down a little more? Instructions are below:
Within the git source tree, run the following command:
git bisect start master xf86-input-wacom-0.23.0You should see a message which says something like "Bisecting: 65 revisions left to test after this (roughly 6 steps)".
Compile and install the driver (
./autogen.sh --prefix=/usr && make && sudo make install)Reboot to apply the changes
Does the problem still exist? YES: Run
git bisect bad. NO: Rungit bisect good.If you see another "Bisecting" message appear, then repeat from step 3. If instead you see "<sha> is the first bad commit", then please run
git bisect logand provide its output here.</sha>Clear the bisect log by running
git bisect reset.I think I found the issue: I still had the old drivers active. So I uninstalled the repo package and did a clean compile&install of all three packages described here: http://linuxwacom.sourceforge.net/wiki/index.php/Downloads and after a reboot xsetwacom shows version 0.28.0 but X doesn't load the wacom module...
The kernel module is loading (dmesg says input: Wacom ISDv5 307 Pen...... and the same with Finger) but the tablet doesn't work (& isn't showing up in xsetwacom).
Is there something missing in the readmes and the howtos or am I doing something wrong?
Thanks
Jakob
EDIT: Nevermind... got the newest driver running. I had the wrong lib-path for xf86-input-wacom...
But the bug also affects the latest version.
The command above now gives this output:
[ 1024.294] compiled for 1.16.0, module version = 0.28.0
Now Im trying your instructions.
Last edit: XDjackieXD 2015-01-16
After a trail of endless reboots I have a working driver and this is the git bisect log:
bad: [335f885bcc15d7ba85bcd2b6000434c39f1beb13] wacom 0.28.0
good: [5395d18c4bbaa0d9ea96617ad41bd94848fb05e9] wacom 0.23.0
git bisect start 'master' 'xf86-input-wacom-0.23.0'
bad: [ac6ad1d7e0a7c428ce609c3bda33099758cf7fde] Remove unnecesary device variables: current[XY]
git bisect bad ac6ad1d7e0a7c428ce609c3bda33099758cf7fde
good: [24c660a8ed16c04ed938355c9c2009af476d7638] conf: ship a udev rule and a systemd service file for inputattach
git bisect good 24c660a8ed16c04ed938355c9c2009af476d7638
good: [533220d3f2369b80afc404df1e5bb6a024309616] Zero is not a valid device ID, don't derive a type from it
git bisect good 533220d3f2369b80afc404df1e5bb6a024309616
bad: [89547bf9e01c9feb33947532c3ca3c4ba9a88a02] Remove dead code: [xy]_padding
git bisect bad 89547bf9e01c9feb33947532c3ca3c4ba9a88a02
bad: [3eacea1058ef255e01ba83d0297bf0e5c533879b] Attempt to derive the tool type from a known button/key event
git bisect bad 3eacea1058ef255e01ba83d0297bf0e5c533879b
bad: [8f44f3568c46ab9cca543b830fb2e84dd56a2af9] Store the last used channel rather than blindly taking channel 0
git bisect bad 8f44f3568c46ab9cca543b830fb2e84dd56a2af9
good: [e08c45f3caf371a8e4123119aeb0b0d7fc227cca] Fix initial device type detection
git bisect good e08c45f3caf371a8e4123119aeb0b0d7fc227cca
first bad commit: [8f44f3568c46ab9cca543b830fb2e84dd56a2af9] Store the last used channel rather than blindly taking channel 0
And while Im at it: I found another bug: I cannot bind the "y" key. It always gets changed to a "z".
Im using a german keyboard if it matters...
Thanks for your help!
-Jakob
Related
Commit: [24c660]
Commit: [335f88]
Commit: [3eacea]
Commit: [533220]
Commit: [5395d1]
Commit: [89547b]
Commit: [8f44f3]
Commit: [ac6ad1]
Commit: [e08c45]
Thanks for that output. Based on what the bad commit does, it sounds almost like the kernel driver isn't sending appropriate tool type information. A closer look there seems to confirm that some of the necessary events aren't being sent when a button is pressed.
Please try building our input-wacom driver with the attached patch. You may need to install the kernel development headers package for your system first.
Let me know if you have any luck.
With the patch everything is working with the newest xf86-input-wacom and the z-y bug is also fixed (probably in one of the many releases between 0.23.0 and 0.28.0).
Thank you! :D
-Jakob
Good to hear! I'll queue that up input-wacom and submit a version to kernel.org for upstreaming as well.