You need to adjust the X server's pointer acceleration options for the device. The Wacom driver stopped providing its own (redundant/crude) acceleration options all the way back in late 2009.
There are three pointer acceleration options of interest that can be adjusted at runtime with the xinput
utility:
$ xinput set-int-prop <device> "Device Accel Profile" 8 <int>
$ xinput set-float-prop <device> "Device Accel Constant Deceleration" <float>
$ xinput set-float-prop <device> "Device Accel Adaptive Deceleration" <float>
You can see the current values of these and other device properties by running xinput list-props <device>
. You'll may notice a "Device Accel Velocity Scaling" property in the output as well -- this knob doesn't do what you might think and should generally be left alone. (For the curious: it should be set to 1000.0/ExpectedRate where ExpectedRate is the rate in Hz at which the input device sends events; the Intuos tablets send touch events at ~100Hz).
To speed up your pointer, first try decreasing the "Constant Deceleration" value. If necessary, you can make it less than 1. At some point this should cause the cursor to move fast enough. If you loose the ability to position the cursor precisely with slow movements afterwards, try increasing the "Adaptive Deceleration". If no amount of tweaking seems to let you both move the pointer quickly across the whole screen and move it slowly in a small area, you should try reseting both properties to 1.0 and then changing the acceleration profile.
These options are more fully documented in the man pages (run man xorg.conf
and search for the "POINTER ACCELERATION" section, or try reading this online copy). You'll definitely need to experiment to find a good setting, since it's more than just a single "faster/slower" knob.
Once you find the settings you like you can either save the commands to a script that you can run whenever you want, or create an "xorg.conf snippet" which will automatically apply the settings whenever the tablet is connected. Such a snippet might look like the following and be saved as "/etc/X11/xorg.conf.d/90-wacom-overrides.conf":
Section "InputClass"
Identifier "Wacom Tablet Overrides"
MatchDriver "wacom"
Option "AccelerationProfile" "<int>"
Option "ConstantDeceleration" "<int>"
Option "AdaptiveDeceleration" "<int>"
EndSection
Note that it is possible that the desktop environment may override settings specified in xorg.conf.d. If this happens, you may have to use the script instead.
I had the exact same problem. I think it worked for a bit of time, then launched into android mode (I don't know why). If I had know how to reset it then (hold buttons 1 and 4), I bet everything would've been fine, but instead I tried to reinstall and debug. My eventual solution is below, followed by some notes. Hopefully some of this will be helpful to someone...
What worked for me: at some point during the process of trying to get my tablet to work, I tried to re-install wacom-input (version 0.45.0). Eventually, simply running sudo make uninstall
from the wacom-input installation directory fixed all of my problems, reverting to the system default driver I think.
My system information: ubuntu 18.04.4 LTS, GNOME 3.28.4.
Tablet information: Intuos PEN (model number CLT-6100WL) (bluetooth capable).
Some notes about how I think I broke things:
At some point, I also tried to purge libwacom-bin
, libwacom-common
and/or libwacom2
, and ended up rendering my desktop environment unable to launch. Even when I reinstalled ubuntu-desktop
(entering the shell directly with F3 during the endless boot screen I was getting) my keyboard didn't work and I had to also sudo apt install xserver-xorg-input-all
using the onscreen accessibility keyboard. How this is possible is truly astounding to me... and makes me sad about the state of (even extremely mainstream) linux.
I ran into the ``duplicate keys'' problem described here, and I think I deleted some of the files in /usr/share/libwacom
to remove duplicates. I'm not sure if it was caused by me, or some sequence of installations/uninstallations, but at some point the file I thought was corresponding to my device (intuos-m-p3-wl.tablet
) was missing. Creating that file, and populating it with sensible data, didn't help (even after restart). (I am not sure the exact relationship between files in this directory and the behavior of the drivers/libraries. Would love an explanation from someone knowledgeable.)
Some notes about how things are working now:
Now that things are working though, it seems my device actually corresponds to /usr/share/libwacom/intuos-m-p3.tablet
. Reason: libwacom-list-local-devices
(and lsusb
) give the address 056a:0378
, which appears in the file intuos-m-p3.tablet
. I am now able to toggle android mode at will (not that I want to) and the address changes to 2d1f:0378
, which appears in intuos-m-p3-wl-android.tablet
. So maybe linking the device to "non-WL" version of the configuration sidesteps the issue where linux is misidentified as android??
My tablet even works in bluetooth. However, it seems to no longer be recognized by libwacom, as it doesn't appear in settings or with libwacom-list-local-devices
.
Bizarrely, when I connect the tablet, it appears twice, with identical entries, under libwacom-list-local-devices
.
Other people are having this issue. Presumably you've found these resources: help, issue filed. Unfortunately these pages didn't solve my problem directly.
Best Answer
Having two cursors when using a tablet in Wayland is by design, but the problem you describe could be due to the fact that you're using X applications on Wayland (using XWayland). Tablet support for X applications under Wayland will be included in the upcoming Xorg 1.20, which will be released in 2018. Until then, you're better of using Xorg. Now, I don't know or use MyPaint myself, so if MyPaint is actually a native Wayland application, my answer does not apply.