Hi,

I'm trying to set AbsWheelUp and AbsWheelDown to scroll up and down.
In the past on Gnome version 3.22 I could do that via:

• disabling the wacom plugin (otherwise you can not map mouse actions to the pad) via:
  gsettings set org.gnome.settings-daemon.plugins.gsdwacom active false

• then hardcoding the two buttons via:

xsetwacom set "Wacom Intuos4 8x13 pad" AbsWheelDown 5
xsetwacom set "Wacom Intuos4 8x13 pad" AbsWheelUp 4

Now in the new gnome version 3.25.4 the setting to disable the wacom plugin is not there. The only settings I have in the plugins folder are:

$ gsettings list-children org.gnome.settings-daemon.plugins
housekeeping   org.gnome.settings-daemon.plugins.housekeeping
power          org.gnome.settings-daemon.plugins.power
color          org.gnome.settings-daemon.plugins.color
media-keys     org.gnome.settings-daemon.plugins.media-keys
xsettings      org.gnome.settings-daemon.plugins.xsettings

I also tried searching the dconf for Wacom settings, but with no results.

As I understand, there has been a major change to the wacom settings in gnome 3.24..

How can I still set the buttons to scrolling and bypass the gnome wacom plugin?

Thank you, any help would be greatly appreciated!

lee

I have a Wacom Intuos CTL-4100 working great under Linux. I am able to configure almost everything I need using xsetwacom except for the CursorProximity parameter. Changing the "Wacom Intuos S Pen cursor's" parameter updates the value, but I notice little to no change in pen hover length. I use the pen in relative mode and would like to reduce the pen detection range.

I am using Ubuntu 18.04 with the HWE kernel (4.18.0-13-generic). I have installed from the repository the package xserver-xorg-input-wacom 0.36.1-0ubuntu1. I tried upgrading with libwacom from 0.29-1 to 0.32 but did not notice a difference when updating CursorProximity.

Thanks

The release.sh for input-wacom includes code that creates a release here on Github in addition to SourceForge. The code which does this should be ported over here so that xf86-input-wacom releases can be done the same way.

Hello,

I have an ancient serial Wacom tablet ArtPad II. I remember it used to work maybe 10 years ago. Now I happend to find it again in box of old stuff and decided to try it again. But it seems it is no more supported. X-org driver just ignores it, and kernel driver says unsupported/ I have tried the following:

# inputattach --wacom_iv /dev/ttyS0
module wacom_serial4 was loaded and the message in subject was logged in syslog
However I do not remember that this was needed before.

I have this xorg.conf.d snippet (copied from old xorg.conf from old backups):

Section "Module"
        Load    "wacom"
EndSection

Section "InputDevice"
        Identifier   "Tablet Stylus"
        Driver       "wacom"
        Option       "Type" "stylus"
        Option       "Device" "/dev/ttyS0"
Endsection

Section "InputDevice"
        Identifier   "Tablet Eraser"
        Driver       "wacom"
        Option       "Type" "eraser"
        Option       "Device" "/dev/ttyS0"
Endsection

But in xorg.0.log is only loading the driver:

[  4430.767] (II) LoadModule: "wacom"
[  4430.768] (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so
[  4430.768] (II) Module wacom: vendor="X.Org Foundation"
[  4430.768]    compiled for 1.19.1, module version = 0.34.0
[  4430.768]    Module class: X.Org XInput Driver
[  4430.768]    ABI class: X.Org XInput driver, version 24.1
[  4430.768] (II) wacom: Driver for Wacom graphics tablets: PenPartner, Graphire,
        Graphire2 4x5, Graphire2 5x7, Graphire3 4x5, Graphire3 6x8,
       ... etc, list of many models, not including ArtPad or KT-0405

I understand this piece of hardware is really old. I would like to know if it is still supported or not. If not, which version is the last that supports it? If yes, what has changed in the way to set it up?

Thanks
Vladki

I'm trying to set up a Cintiq 27QHDT under Debian. Is there any way to set the displays brightness or r/g/b colour channels without having to use the Windows wacom drivers?

This model of Cintiq lacks hardware controls for its display, so would it be possible to add software controls to the driver? Or do I have to set it up under windows? The windows drivers have a tool to adjust them.

Note, I'm not talking about the graphics card settings, rather the cintiqs internal settings)

I need these for setting the colour calibration.

While trying to install via:
$ sudo apt-get install xserver-xorg-input-wacom

I receive the following:
The following packages have unmet dependencies: xserver-xorg-input-wacom : Depends: xserver-xorg-core (>= 2:1.18.99.901)

What I have installed is:
xserver-xorg-core-hwe-18.04 version 2:1.20.1-3ubuntu2.1~18.04.1

which replaced:
xserver-xorg-core version 2:1.19.6-1ubuntu4.2

I understand that this is a different package, although the version does meet the requirements. Will there be compatibility for this, some sort of transitional package or workaround of sort?

Hello!

Original report: https://sourceforge.net/p/linuxwacom/bugs/346/

As I find today, it's still reproducible, under Gnome Shell Wayland too.

All the other button on the stylus, on the pad are working fine.
But I can't get the right configuration apparently for my eraser on the pen (the tip eraser).

I'm on Arch Linux with an Intuos3.

I've tried
xsetwacom set "Wacom Intuos3 6x8 Pen eraser" Button 1 1
-----> The eraser works as a pencil (like a mouse left button in fact)
xsetwacom set "Wacom Intuos3 6x8 Pen eraser" Button 1 2
-----> The eraser works as a mouse middle button
xsetwacom set "Wacom Intuos3 6x8 Pen eraser" Button 1 3
-----> The eraser works as a mouse right button

It's the same result for GIMP or Krita.

Hello, so after realizing I have atrocious allergies I've decided to opt for a drawing tablet instead of a 2-in-1. At the moment I've seen a lot of positive reports on the XP-Pen Artist 22E Pro, but at the same time (having no way to test them in person) I am unsure if I should get the Huion, or save up the extra 500-700 pounds to purchase a Wacom Cintiq 22HD. At the moment I am more of a hobbyist than a professional illustrator, but do highly prefer paying a little extra for more reliability/longevity. Also less headache when finishing up a scanned sketch IE expecting the line to be in one place, but having it appear in another. I was considering the Artist 22E Pro as well, however, I am more likely to upgrade my PC within the next 3 - 5 years, which would support USB-C/4K resolution.

1. What is your budget?

around £1000 .

2. Any preference on screen resolution?

At least 1920x1080p

3. Do you require a pen? With or without pressure sensitivity? Do you prefer Wacom EMR, AES or N-trig?
   See the above linked FAQ for guidance

Yes.

4. What size Tablet PC would you prefer?

Between 21.5 or larger.

5. What will be the primary usage scenario of this tablet? (Email/Web Surfing/Drawing/Word Processing/Entertainment/Notetaking etc)

Illustration

6. What software and tasks do you intend to run? (Microsoft Office or other Word Processing Suite/Photoshop/3D Studio Max/Autocad etc)

Manga Studio, Photoshop, Adobe Illustrate.

XP-Pen is currently running a sale on their Artist 22E Pro for about £500 on Amazon UK : ( https://www.amazon.co.uk/Artist22E-Graphic-Interactive-Shortcut-Adjustable/dp/B01M28DHOA ). it seems to have the best screen.Also, between the XP-Pen Artist 22E Pro and Wacom Cintiq 22HD, which would you recommend? The XP-Pen Artist 22E Pro is £1000 cheaper than the Wacom Cintiq 22HD here, I want to know if the XP-Pen is as good or hopefully better than the Cintiq , especially the color accuracy of the display and accuracy of the pen.

Greetings,

I'm having a strange error on my Arch Linux distribution.
Every time I'm controlling my tablet my pc resets itself.
Always when the pen gets recognized by the tablet my screen goes instantly black and I end up in the login screen.

bernardo@archdesk ~> xsetwacom list devices
Wacom Intuos PT S Pen stylus    	id: 23	type: STYLUS    
Wacom Intuos PT S Finger touch  	id: 24	type: TOUCH     
Wacom Intuos PT S Pad pad       	id: 25	type: PAD       
Wacom Intuos PT S Pen eraser    	id: 31	type: ERASER 

I'm using the Gnome desktop environment on Arch Linux with the 4.18.8 kernel.
The xf86-input-wacom driver version is 0.36.1-1. Also... When removing this packet, everything works fine, but then I can't set the tablet area.

If you need more information or any log, please tell me. I can't find any crash or error report reporting this strange behavior.

I'd appreciate any help because I can't use my tablet at this time.

Regards,
Bernardo de Oliveira

Hi,
I'm having issues with my Lenovo Yoga 730-ikb not registering any input from the included Lenovo Active Pen 2 that came with it. Otherwise the touchsreen functions when using fingers.
I'm not too good at troubleshooting input problems as this is the first 2-in-1 device I've had that I've tried running linux on. I'm currently running Linux Mint with cinnamon but also tested a live ubuntu stick and had fedora installed earlier and they both displayed the same issues.
xinput and xsetwacom finds the devices

x@x-Lenovo-YOGA-730-15IKB:~$ xsetwacom --list devices
Wacom HID 516B Pen stylus       	id: 12	type: STYLUS    
Wacom HID 516B Finger touch     	id: 13	type: TOUCH     
Wacom HID 516B Pen eraser       	id: 16	type: ERASER    
x@x-Lenovo-YOGA-730-15IKB:~$ xinput
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ MSFT0001:02 06CB:7F8F Touchpad          	id=11	[slave  pointer  (2)]
⎜   ↳ Wacom HID 516B Pen stylus               	id=12	[slave  pointer  (2)]
⎜   ↳ Wacom HID 516B Finger touch             	id=13	[slave  pointer  (2)]
⎜   ↳ Wacom HID 516B Pen eraser               	id=16	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Video Bus                               	id=8	[slave  keyboard (3)]
    ↳ Power Button                            	id=9	[slave  keyboard (3)]
    ↳ Integrated Camera: Integrated C         	id=10	[slave  keyboard (3)]
    ↳ Ideapad extra buttons                   	id=14	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=15	[slave  keyboard (3)]

But touching the screen with the stylus and pressing the buttons on it does nothing.
I figure I might try to live boot a windows 10 install to check if it works in windows if I get the time, which is something I should have done before but right now this computer is in daily use and I want to avoid reinstalling OS on it and for some reason this thing runs windows usb sticks extremely slowly.
Any help is appreciated.

I'm not sure whether this covers xsetwacom as well, but as I haven't found other place...
Following Arch wiki I've been trying to set up keys for my tablet (damn, such a shame there's no gui tool that would store configs, but I digress). I had my hopes up when I've seen "displaytoggle" argument that coud have been assigned to the key - would be awesome for my multimonitor setup. But when I try it I get:

The "displaytoggle" keyword is not supported anymore and will be ignored.

Is there any kind of equivalent for it? At the very least what is the way to assign mapping of specific monitor to specific key. Atm I have to use :

xsetwacom set "Wacom Intuos S Pen stylus" maptooutput 2560x1440+0+0

in the terminal each time I connect my tablet.

I'm trying to make old Intuos 3 tablet (PTZ430) work on Linux. It kinda works but is not really usable.
I've mapped it one of the monitors (out of 2 - one is 2k, other 1k) using the command:

xsetwacom set "Wacom Intuos3 4x5 Pen stylus" maptooutput 2560x1440+0+0

But the aspect ratio in wrong. This old tablet has 4:3 aspect ratio, while my monitors are 16:9. So when I'm trying to draw a circle I get ellipse instead.
Tried digging through manual :
https://github.com/linuxwacom/xf86-input-wacom/wiki/Calibration

... but I still have no clue what to enter to get correct aspect ratio.
Isn't there some sort of toggle/switch like on Windows?

edit: btw - tried xinput_calibrator, but I have no clue how to constraint it to single monitor (it displays test "crosshair" on all) and I don't think this would result in solution to the problem (as it would not "cut" part of tablet space to get desired proportions).

edit: ok, figured it out. In my case :

xsetwacom set "Wacom Intuos3 4x5 Pen stylus" Area 0 0 25400 14287

does the trick.
Quite surprised there's no app that does this automatically. Need to think how I could automate it and howto handle this in different tablet / monitors setups.
Something like Piper / SC Controller for Wacom (and ideally non-Wacom as well) tablets would be awesome.

I installed Ubuntu 18.04 on this tablet. It has following devices:

>xinput
   ↳ Wacom HID 485E Pen stylus               	id=10	[slave  pointer  (2)]
   ↳ Wacom HID 485E Finger touch             	id=11	[slave  pointer  (2)]
   ↳ Wacom HID 485E Pen eraser               	id=17	[slave  pointer  (2)]

I tested the pen in Windows 10. The tip works as button 1. Button 3 switches pen to eraser mode while pressed. Button 2 works as right mouse button, but not by itself. I need to hold the button then touch the screen, it is registered as a click. In Ubuntu holding button 3 makes the system get events from Wacom HID 485E Pen eraser device.

Before further testing I issued these commands to terminal, with them I can see a reaction to pressing button 2 in different programs:

# button 2 is the second button from the the tip
xsetwacom set "Wacom HID 485E Pen stylus" "Button" "2" "button +3 "
# button 3 activates eraser and doesn't work by itself,
# it is the first button from the tip
xsetwacom set "Wacom HID 485E Pen stylus" "Button" "3" "button +0 "
# button 8 doesn't work or doesn't exist
xsetwacom set "Wacom HID 485E Pen stylus" "Button" "8" "button +0 "

Next I used the following command to monitor events:
>xinput test "Wacom HID 485E Pen stylus"

The first issue is when I only hover the pen near the monitor but do not touch it, the system registers button 1 presses and releases. It may happen for a minute or two, then these button events stops, then it happen again after some time. In Windows I detected no such behavior.

The second issue is when I hold the button 2 and touch the screen I got both button 1 and button 3 events. But I expect only button 3 events:

button press   3 a[0]=17993 a[1]=8808 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=18043 a[1]=9301 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
button press   1 a[0]=18043 a[1]=9301 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
button release 3 a[0]=18043 a[1]=9301 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=18042 a[1]=9327 a[2]=15335 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=18040 a[1]=9370 a[2]=25462 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=18038 a[1]=9426 a[2]=30706 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=18039 a[1]=9549 a[2]=31610 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=18042 a[1]=9647 a[2]=31610 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=18046 a[1]=9722 a[2]=33346 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=18051 a[1]=9786 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
button release 1 a[0]=18051 a[1]=9786 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=18038 a[1]=9704 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 

The third issue is after pressing button 2 and touching the screen the system from time to time begins to register both button 3 and button 1 events when touching the screen. Here is an example, I only touched the screen without pressing any buttons:

button press   3 a[0]=14053 a[1]=8493 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=14049 a[1]=8527 a[2]=27122 a[3]=0 a[4]=0 a[5]=-900 
button press   1 a[0]=14049 a[1]=8527 a[2]=27122 a[3]=0 a[4]=0 a[5]=-900 
button release 3 a[0]=14049 a[1]=8527 a[2]=27122 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=14049 a[1]=8527 a[2]=22958 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=14049 a[1]=8527 a[2]=22170 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=14036 a[1]=8540 a[2]=21795 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=14024 a[1]=8551 a[2]=20107 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=14009 a[1]=8559 a[2]=17331 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=13994 a[1]=8564 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
button release 1 a[0]=13994 a[1]=8564 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 

I expect only button 1 events in this case. The pen returns to the expected behavior after some time.

Sometimes after holding button 2 and touching the screen another issue appears. Hovering the pen near the screen produces both button 1 and button 3 events, while no button is pressed:

motion a[0]=17906 a[1]=10561 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
button press   3 a[0]=17906 a[1]=10561 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=17906 a[1]=10561 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
button press   1 a[0]=17906 a[1]=10561 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
button release 3 a[0]=17906 a[1]=10561 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
motion a[0]=17906 a[1]=10561 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 
button release 1 a[0]=17906 a[1]=10561 a[2]=0 a[3]=0 a[4]=0 a[5]=-900 

When the Bamboo PAD is used, it can start a stroke, and when quickly stroked you can see a short diagonal line with some pressure information, but you can not draw an actual stroke. Hovering is correctly recognized, but as soon as the pen touches the surface the cursor doesn't move anymore.

I haven't found a way to specify polling rate within the files of this project or anywhere else for wacom drivers,
Arch Linux is my current OS.

I installed xf86-input-wacom and noticed upon rebooting MX-17 (based on Debian 9, x64, XFCE) that single point touch works everywhere. On Slimjet (think google chrome "light") and Qupzilla (WebQT) browser, one-finger and two-finger touch, shrinking/expanding works. In Slimjet, two finger touch also works as a "right-click". But in Firefox, only single touch works. On the XFCE desktop and in other applications, such as LibreOffice, qpdfview, okular, thunar, etc., only "single-touch" works, and it works as a normal mouse / left click. I was hoping you might have some insight on this issue.
Laptop: Lenovo X220 Tablet
OS: MX-17 x64
xf86-input-wacom (the latest from github) and thinkpad-scripts (4.11)

Description:

We observed a bug while using a touchable wacom monitor on a X11 based linux
system. Using multifinger touch can lead to states in which a single finger in a
multi touch sceneario will be mostly ignored.

Prerequireries

Setup wacom device with 'xsetwacom --set [device] Touch on' and 'xsetwacom --set
[device] Gesture off'. After pressing multiple times with multiple fingers a
state can be reached where a single finger will be ignored, especially while
using two fingers. The first contact point of the second finger will be
recognized, but every movement afterwards disappears. This effect can be
visualized by compiling the fingerpaint example of qt (see https://doc.qt.io/qt-5/qtwidgets-touch-fingerpaint-example.html [^]). See the given result
vs the expected result:

In the wrong state a single yellow point is drawn where a line is expected.

The state can 'repaired' by touching the monitor again with e.g 10 fingers

Further observations

We took a look into evdev event by monitoring the multitouch events out of the
evtest tools and an additional look into the output of 'xinput --test-xi2'.
There are 3 files representing the output of a two finger touch while in a false
state. The two finger where moved in parallel similar to 'resultExpected.jpg':

• evdev /dev/input[X] > evdev.txt evdev.txt
• xinput --test-xi2 [X] > test_xi2.txt test_xi2.txt
• 'cat evdev.txt | python3 evdev_parser.py > parsed_evdev_output_finger_positions.txt'
  parsed_evdev_output_finger_positions.txt
  evdev_parser.py.zip

The evdev output seems to be plausible, as it updates each of the two fingers
with a reasonable position. The xinput output has a TouchEnd event of the second
finger (see line 122) that appears too early.

The bug occures only for wacom devices so we suspect the bug inside the
xorg-x11-drv-wacom package

System environments

The error occured for in two different environments with two different wacom
touch monitors. We couldn't reproduce the error with a different non-wacom touch
monitor on the same enviroments:

Centos 7:

cmd:
xsetwacom --list devices

output:

  Wacom Express Key Remote Pad pad id: 13 type: PAD
  Wacom Cintiq Pro 32 Touch Finger touch id: 14 type: TOUCH
  Wacom Cintiq Pro 32 Pen stylus id: 15 type: STYLUS
  Wacom Cintiq Pro 32 Pen eraser id: 16 type: ERASER

cmd:
yum list installed | sed '/(wacom|xorg-x11)/!d':

output:

  libwacom.x86_64 0.30-1.el7 @base
  libwacom-data.noarch 0.30-1.el7 @base
  xorg-x11-drivers.x86_64 7.7-6.el7 @anaconda
  xorg-x11-drv-ati.x86_64 18.0.1-1.el7 @base
  xorg-x11-drv-dummy.x86_64 0.3.7-1.el7.1 @base
  xorg-x11-drv-evdev.x86_64 2.10.6-1.el7 @base
  xorg-x11-drv-fbdev.x86_64 0.5.0-1.el7 @base
  xorg-x11-drv-intel.x86_64 2.99.917-28.20180530.el7 @base
  xorg-x11-drv-nouveau.x86_64 1:1.0.15-1.el7 @base
  xorg-x11-drv-qxl.x86_64 0.1.5-4.el7.1 @base
  xorg-x11-drv-synaptics.x86_64 1.9.0-2.el7 @base
  xorg-x11-drv-v4l.x86_64 0.2.0-49.el7 @base
  xorg-x11-drv-vesa.x86_64 2.4.0-1.el7 @base
  xorg-x11-drv-vmmouse.x86_64 13.1.0-1.el7.1 @base
  xorg-x11-drv-vmware.x86_64 13.2.1-1.el7.1 @base
  xorg-x11-drv-void.x86_64 1.4.1-2.el7.1 @base
  xorg-x11-drv-wacom.x86_64 0.36.1-1.el7 @base
  xorg-x11-font-utils.x86_64 1:7.5-21.el7 @base
  xorg-x11-fonts-Type1.noarch 7.5-9.el7 @anaconda
  xorg-x11-proto-devel.noarch 2018.4-1.el7 @base
  xorg-x11-server-Xorg.x86_64 1.20.1-5.1.el7 @updates
  xorg-x11-server-common.x86_64 1.20.1-5.1.el7 @updates
  xorg-x11-server-utils.x86_64 7.7-20.el7 @anaconda
  xorg-x11-utils.x86_64 7.5-23.el7 @base
  xorg-x11-xauth.x86_64 1:1.0.9-1.el7 @anaconda
  xorg-x11-xinit.x86_64 1.3.4-2.el7 @anaconda
  xorg-x11-xkb-utils.x86_64 7.7-14.el7 @base

cmd:
lsusb | grep 056a

output:

  Bus 002 Device 064: ID 056a:038b Wacom Co., Ltd
  Bus 002 Device 063: ID 056a:038c Wacom Co., Ltd
  Bus 002 Device 062: ID 056a:0389 Wacom Co., Ltd
  Bus 001 Device 026: ID 056a:0352 Wacom Co., Ltd DTH-3220 [Cintiq Pro 32] tablet
  Bus 001 Device 024: ID 056a:0356 Wacom Co., Ltd DTH-3220 [Cintiq Pro 32] touchscreen
  Bus 001 Device 023: ID 056a:038a Wacom Co., Ltd DTH-3220 [Cintiq Pro 32] internal hub
  Bus 001 Device 021: ID 056a:038e Wacom Co., Ltd DTH-3220 [Cintiq Pro 32] external hub
  Bus 001 Device 022: ID 056a:0331 Wacom Co., Ltd
  Bus 001 Device 020: ID 056a:038f Wacom Co., Ltd DTH-3220 [Cintiq Pro 32] internal hub
  Bus 001 Device 019: ID 056a:038d Wacom Co., Ltd DTH-3220 [Cintiq Pro 32] internal hub

Fedora 29:

cmd:
xsetwacom --list devices

output:

  Wacom Cintiq 24HD touch Finger touch id: 9 type: TOUCH
  Wacom Cintiq 24HD touch Pen stylus id: 10 type: STYLUS
  Wacom Cintiq 24HD touch Pad pad id: 11 type: PAD
  Wacom Cintiq 24HD touch Pen eraser id: 15 type: ERASER

cmd:
yum list installed | sed '/\(wacom\|xorg-x11\)/!d':

output:

  libwacom.x86_64 0.32-2.fc29 @updates
  libwacom-data.noarch 0.32-2.fc29 @updates
  xorg-x11-apps.x86_64 7.7-22.fc29 @fedora
  xorg-x11-drv-ati.x86_64 18.1.0-1.fc29 @updates
  xorg-x11-drv-evdev.x86_64 2.10.6-3.fc29 @fedora
  xorg-x11-drv-fbdev.x86_64 0.5.0-2.fc29 @fedora
  xorg-x11-drv-intel.x86_64 2.99.917-39.20180618.fc29 @fedora
  xorg-x11-drv-libinput.x86_64 0.28.1-1.fc29 @updates
  xorg-x11-drv-nouveau.x86_64 1:1.0.15-6.fc29 @fedora
  xorg-x11-drv-nvidia.x86_64 3:415.25-1.fc29 @rpmfusion-nonfree-updates
  xorg-x11-drv-nvidia-cuda.x86_64 3:415.25-1.fc29 @rpmfusion-nonfree-updates
  xorg-x11-drv-nvidia-cuda-libs.x86_64 3:415.25-1.fc29 @rpmfusion-nonfree-updates
  xorg-x11-drv-nvidia-kmodsrc.x86_64 3:415.25-1.fc29 @rpmfusion-nonfree-updates
  xorg-x11-drv-nvidia-libs.x86_64 3:415.25-1.fc29 @rpmfusion-nonfree-updates
  xorg-x11-drv-openchrome.x86_64 0.6.0-6.fc29 @fedora
  xorg-x11-drv-qxl.x86_64 0.1.5-10.fc29 @fedora
  xorg-x11-drv-vesa.x86_64 2.4.0-4.fc29 @fedora
  xorg-x11-drv-vmware.x86_64 13.2.1-8.fc29 @fedora
  xorg-x11-drv-wacom.x86_64 0.36.1-5.fc29 @fedora
  xorg-x11-drv-wacom-serial-support.x86_64 0.36.1-5.fc29 @fedora
  xorg-x11-font-utils.x86_64 1:7.5-40.fc29 @fedora
  xorg-x11-fonts-misc.noarch 7.5-20.fc29 @fedora
  xorg-x11-proto-devel.noarch 2018.4-2.fc29 @fedora
  xorg-x11-server-Xorg.x86_64 1.20.3-2.fc29 @updates
  xorg-x11-server-Xwayland.x86_64 1.20.3-2.fc29 @updates
  xorg-x11-server-common.x86_64 1.20.3-2.fc29 @updates
  xorg-x11-server-utils.x86_64 7.7-26.fc29 @fedora
  xorg-x11-utils.x86_64 7.5-29.fc29 @fedora
  xorg-x11-xauth.x86_64 1:1.0.9-13.fc29 @fedora
  xorg-x11-xbitmaps.noarch 1.1.1-15.fc29 @fedora
  xorg-x11-xinit.x86_64 1.4.0-3.fc29 @fedora
  xorg-x11-xkb-utils.x86_64 7.7-27.fc29 @fedora
  xorg-x11-xkb-utils-devel.x86_64 7.7-27.fc29 @fedor

cmd:
lsusb | grep 056a

output:

  Bus 003 Device 008: ID 056a:00f8 Wacom Co., Ltd DTH-2400 [Cintiq 24HD touch] tablet
  Bus 003 Device 007: ID 056a:00f6 Wacom Co., Ltd DTH-2400 [Cintiq 24HD touch] touchscreen
  Bus 003 Device 006: ID 056a:00f5 Wacom Co., Ltd

It seems Gnome is the only DE that supports configuration of Wacom devices almost fully. But it seems there's no way to configure scrollbars / wheels with it (and it does not take into account monitor rotations correctly - but I understand it is Gnome project's thing to fix).
Is there a way to configure those scrolls through command line?

After some back and forth on this linuxwacom/libwacom#75 It was determined the issue lies somewhere in xf86-input-wacom. But the exact fix is unknown and it's not clear what part of code is failing here.

When using the pen in X11 and Gnome, the pen is triggering the eraser (or whatever tool the 'eraser' end was set to). Applications like GIMP, Xournal, and Stylus Labs Write all showed the same issue.

However under Wayland and Gnome these issues went away. The pen tip wrote fine with pressure sensitivity and the eraser end erased lines. All previously tested applications no longer had issue.

So this is where I'm at now, I'd like to see X11 support fixed as there are still some quirks with Wayland.

Hi guys,

First of all thanks for all the good stuff you guys are making for us.

I do have an issue on past 0.29 versions on the Intuos wacoms we use (PTH-660 intuso 5 and 4). The pressure seems its not working properly for the pen. At some point while pressing a bit more on the tip the pressure value gets inverted or something like that and instead of the line to get thicker and thicker it stops outputting anything on the canvas. If I only press a bit the line would get a bit thicker but then as I press more its interrupted. I'm not sure how to give you guys technical details about the issue. If there's a way i can log something please let me know and I'l send whatever you guys need. For now we use 0.29 and seems its working great but not sure what limitations we would have with new kmod drivers.

Any help would be much appreciated and thanks again for all the work you guys did so far.

Rares

Hi guys,
I'm trying to install the driver for my my Wacom Intuos Pro M to Centos 7(kernel: 3.10.0-693.el7.x86_64) machine, there is no error during the driver building, but I still can't get the device work, from the "dmesg" command, it is saying "Unknown device_type for 'Wacom Co.,Ltd. Wacom Intuos Pro M'. Ignoring." But from "xinput list" or "xsetwacom --list" command, it seems finded the right driver and can recognize the tablet well, please kindly check below output

[root@greyelephant ~]# dmesg | grep -i wacom
[   10.902942] usb 3-13: Product: Wacom Intuos Pro M
[   10.902944] usb 3-13: Manufacturer: Wacom Co.,Ltd.
[   11.909045] usbcore: registered new interface driver wacom
[   11.918517] input: Wacom Co.,Ltd. Wacom Intuos Pro M Pen as /devices/pci0000:00/0000:00:14.0/usb3/3-13/3-13:1.0/0003:056A:0357.0004/input/input5
[   11.918667] wacom 0003:056A:0357.0004: hidraw3: USB HID v1.10 Mouse [Wacom Co.,Ltd. Wacom Intuos Pro M] on usb-0000:00:14.0-13/input0
[   11.918913] wacom 0003:056A:0357.0005: Unknown device_type for 'Wacom Co.,Ltd. Wacom Intuos Pro M'. Ignoring.
[root@greyelephant ~]# xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech USB Optical Mouse              	id=9	[slave  pointer  (2)]
⎜   ↳ Wacom Intuos Pro M Pen cursor           	id=14	[slave  pointer  (2)]
⎜   ↳ Wacom Intuos Pro M Finger touch         	id=15	[slave  pointer  (2)]
⎜   ↳ Wacom Intuos Pro M Pen eraser           	id=13	[slave  pointer  (2)]
⎜   ↳ Wacom Intuos Pro M Pen stylus           	id=12	[slave  pointer  (2)]
⎜   ↳ Wacom Intuos Pro M Pad pad              	id=11	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=8	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=10	[slave  keyboard (3)]
[root@greyelephant ~]# grep -H "" /sys/module/*wacom/versions
grep: /sys/module/*wacom/versions: No such file or directory

There are no commid ID in the "wacom" version:

[root@greyelephant ~]# grep -H "" /sys/module/*wacom/version     
/sys/module/hid_wacom/version:v2.00
/sys/module/wacom/version:v1.53-0.39.0

[root@greyelephant ~]# xsetwacom --list
Wacom Intuos Pro M Pen cursor   	id: 14	type: CURSOR    
Wacom Intuos Pro M Finger touch 	id: 15	type: TOUCH     
Wacom Intuos Pro M Pen eraser   	id: 13	type: ERASER    
Wacom Intuos Pro M Pen stylus   	id: 12	type: STYLUS    
Wacom Intuos Pro M Pad pad      	id: 11	type: PAD   

I'm not sure how to debug more about it, any advise will be appreciated.

Thanks.

Imported from Sourceforge Bug #302

Dear Developers,

I have an Intuos Comic, my OS is Ubuntu 12.04.5, my Xorg version is 1.11.3.

I first installed the Kernel Driver "input-wacom-0.30.2", my tablet can be recognized whenever it is plugged in (FYI, I'm using the Wacom wireless adapter) and it has the basic pen and touch functions.

So I then installed "xf86-input-wacom-0.32.0" for the pressure, gesture and express key functions. After I installed it and rebooted my system, as soon as I plug in and turn on my tablet (with no finger or pen anywhere near the tablet), X crashes and error messages show up on black screen (which I can't read because the first half of each line is outside of the screen, the resolution is messed up. I can provide partial error messages if you need it). However, although my display freezes, my computer is functioning, I can SSH into it and use it from command line.

I read previous bugs and I thought this might be a different bug and might be specific to Ubuntu 12.04.
Here are two similar unanswered threads on the internet:
http://askubuntu.com/questions/693113/information-on-input-wacom-0-30-0-for-intuos-art-compilaton
http://askubuntu.com/questions/506385/black-screen-when-plugging-in-intuos-ctl-480-on-ubuntu-12-04/

Thanks a lot for your help,
wolich

Hi,

My wacom tablet:

$ xsetwacom --list devices
Wacom Graphire4 4x5 Pen stylus      id: 10	type: STYLUS    
Wacom Graphire4 4x5 Pad pad         id: 11	type: PAD       
Wacom Graphire4 4x5 Pen eraser      id: 13	type: ERASER    
Wacom Graphire4 4x5 Pen cursor 	    id: 14	type: CURSOR

Configure the tablet buttons doen't work for this wacom device.
Example:

$ xsetwacom set "Wacom Graphire4 4x5 Pad pad" Button +1 "key p"
$ xsetwacom get "Wacom Graphire4 4x5 Pad pad" Button 1
key +p -p 

But nothing append when button1 is pressed, same for Button2, only wheel pad can be set correctly.
Is it a bug or a limitation ?
Thanks

Hello,
when using xournal my palm sometimes interrupts the writing process on the wacom touchscreen resulting in partial letters / ignored lines.

Specs:
Notebook: Lenovo Yoga 720
$ xsetwacom --list

Wacom HID 50EE Pen stylus               id: 10  type: STYLUS      
Wacom HID 50EE Pen eraser               id: 14  type: ERASER      
Wacom HID 50EE Finger touch             id: 11  type: TOUCH    

Quick solution: xinput disable "Wacom HID 50EE Finger touch" . But in tablet-mode this isn't quite useful.
Alternative approach: map above command to a pen-button.
Desired solutoin:

if pen_is_writing:
   xinput disable 11
else:
   xinput enable 11

Is something like that already implemented, or even possible?

Imported from Sourceforge Bug #294

As discussed on the linuxwacom-devel mailinglist, the Wacom Bluetooth Keyboard does not work under X after pairing. This is because our 50-wacom.conf file ends up matching the device (by name through the "Wacom class") and causes it to try and use our driver:

bluetoothd[1585]: Can't get HIDP connection info
kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2
kernel: Bluetooth: HIDP socket layer initialized
kernel: hid-generic 0005:04F2:1263.0005: unknown main item tag 0x0
kernel: input: Wacom Bluetooth Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/bluetooth/hci0/hci0:71/0005:04F2:1263.0005/input/input31
kernel: hid-generic 0005:04F2:1263.0005: input,hidraw4: BLUETOOTH HID v1.00 Keyboard [Wacom Bluetooth Keyboard] on 00:1b:dc:06:6a:57
/usr/lib/gdm/gdm-x-session[2062]: (II) config/udev: Adding input device Wacom Bluetooth Keyboard (/dev/input/event24)
/usr/lib/gdm/gdm-x-session[2062]: (**) Wacom Bluetooth Keyboard: Applying InputClass "evdev keyboard catchall"
/usr/lib/gdm/gdm-x-session[2062]: (**) Wacom Bluetooth Keyboard: Applying InputClass "Wacom class"
/usr/lib/gdm/gdm-x-session[2062]: (**) Wacom Bluetooth Keyboard: Applying InputClass "system-keyboard"
/usr/lib/gdm/gdm-x-session[1829]: (II) config/udev: Adding input device Wacom Bluetooth Keyboard (/dev/input/event24)
/usr/lib/gdm/gdm-x-session[1829]: (**) Wacom Bluetooth Keyboard: Applying InputClass "evdev keyboard catchall"
/usr/lib/gdm/gdm-x-session[1829]: (**) Wacom Bluetooth Keyboard: Applying InputClass "Wacom class"
/usr/lib/gdm/gdm-x-session[1829]: (**) Wacom Bluetooth Keyboard: Applying InputClass "system-keyboard"
/usr/lib/gdm/gdm-x-session[2062]: (II) systemd-logind: got fd for
/dev/input/event24 13:88 fd 61 paused 0
/usr/lib/gdm/gdm-x-session[2062]: (II) Using input driver 'wacom' for 'Wacom Bluetooth Keyboard'
/usr/lib/gdm/gdm-x-session[2062]: (**) Wacom Bluetooth Keyboard: always reports core events
/usr/lib/gdm/gdm-x-session[2062]: (**) Option "Device" "/dev/input/event24"
/usr/lib/gdm/gdm-x-session[2062]: (EE) Wacom Bluetooth Keyboard: Invalid type 'stylus' for this device.
/usr/lib/gdm/gdm-x-session[2062]: (EE) Wacom Bluetooth Keyboard: Invalid type 'eraser' for this device.
/usr/lib/gdm/gdm-x-session[2062]: (EE) Wacom Bluetooth Keyboard: Invalid type 'cursor' for this device.
/usr/lib/gdm/gdm-x-session[2062]: (EE) Wacom Bluetooth Keyboard: Invalid type 'touch' for this device.
/usr/lib/gdm/gdm-x-session[2062]: (II) Wacom Bluetooth Keyboard: type not specified, assuming 'pad'.
/usr/lib/gdm/gdm-x-session[2062]: (II) Wacom Bluetooth Keyboard: other types will be automatically added.
/usr/lib/gdm/gdm-x-session[2062]: (EE) Wacom Bluetooth Keyboard pad: xmax value is 0, expected > 0.
/usr/lib/gdm/gdm-x-session[2062]: (EE) PreInit returned 8 for "Wacom Bluetooth Keyboard pad"
/usr/lib/gdm/gdm-x-session[2062]: (II) UnloadModule: "wacom"
/usr/lib/gdm/gdm-x-session[2062]: (II) systemd-logind: releasing fd for 13:88
/usr/lib/gdm/gdm-x-session[1829]: (II) systemd-logind: got fd for
/dev/input/event24 13:88 fd 27 paused 1
/usr/lib/gdm/gdm-x-session[1829]: (II) systemd-logind: releasing fd for 13:88

We should modify 50-wacom.conf so that it is more strict about the devices that it binds to. The obvious solution would be to add MatchIsTablet "on" (or similar rules exclusing keyboard, pointer, and joystick devices) but it isn't entirely clear if a pad-only device without its current ABS_X and ABS_Y compatibility axes would be correctly recgonized.

For the moment, this issue can be worked around by creating an /etc/X11/xorg.conf.d/90-wacom-HACK.conf file with the following contents:

Section "InputClass"
    Identifier "Wacom bluetooth hack class"
    MatchDriver "wacom"
    MatchIsKeyboard "on"
    Driver "evdev"
EndSection

Hi all,

after a clean Kubuntu (18.10) install I can't get mz Cintiq 27 HD (without touch) to work. I tried several things (install all possible Wacom-things from the official repo, compiling kernel and XServer drivers from source, reinstalling the stuff from the repo), eventually got it working after the reinstall step, but after a reboot the problem is back: cursor is not reacting to the pen movement. So, to 'clean the mess up' I have sudo make uninstall both drivers, apt remove libwacom-bin xserver-xorg-input-wacom and installed the later two again via apt. But, still Linux is not detecting anything from the pen. I am pretty sure it is a Linus issue as everything works fine in Windows.

Following this thread from the Sourceforge ( https://sourceforge.net/p/linuxwacom/support-requests/54/ ), some data about the state of things:

$ lsusb | grep Wacom
Bus 002 Device 005: ID 056a:0339 Wacom Co., Ltd
Bus 002 Device 004: ID 056a:0337 Wacom Co., Ltd
Bus 002 Device 003: ID 056a:032d Wacom Co., Ltd
Bus 001 Device 010: ID 056a:0331 Wacom Co., Ltd
Bus 001 Device 008: ID 056a:032a Wacom Co., Ltd
Bus 001 Device 006: ID 056a:033a Wacom Co., Ltd
Bus 001 Device 004: ID 056a:0338 Wacom Co., Ltd
Bus 001 Device 002: ID 056a:032e Wacom Co., Ltd

$ grep "" /sys/module/wacom*/version 
v2.00

$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ USB Optical Mouse                         id=9    [slave  pointer  (2)]
⎜   ↳ HOLTEK USB-HID Keyboard Mouse             id=12   [slave  pointer  (2)]
⎜   ↳ HOLTEK USB-HID Keyboard Consumer Control  id=14   [slave  pointer  (2)]
⎜   ↳ Wacom Cintiq 27QHD Pen stylus             id=15   [slave  pointer  (2)]
⎜   ↳ Wacom Express Key Remote Pad pad          id=16   [slave  pointer  (2)]
⎜   ↳ Wacom Cintiq 27QHD Pen eraser             id=18   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Power Button                              id=7    [slave  keyboard (3)]
    ↳ Sleep Button                              id=8    [slave  keyboard (3)]
    ↳ HOLTEK USB-HID Keyboard                   id=10   [slave  keyboard (3)]
    ↳ HOLTEK USB-HID Keyboard Keyboard          id=11   [slave  keyboard (3)]
    ↳ HOLTEK USB-HID Keyboard System Control    id=13   [slave  keyboard (3)]
    ↳ HOLTEK USB-HID Keyboard Consumer Control  id=17   [slave  keyboard (3)]

Which means that X is seeing the tablet (right?).

$ ll /usr/share/X11/xorg.conf.d
insgesamt 32
drwxr-xr-x 2 root root 4096 Feb  9 23:35 ./
drwxr-xr-x 5 root root 4096 Okt 18 00:35 ../
-rw-r--r-- 1 root root   92 Sep 18 09:23 10-amdgpu.conf
-rw-r--r-- 1 root root  206 Aug 28 08:49 10-nvidia.conf
-rw-r--r-- 1 root root 1350 Okt 25 16:53 10-quirks.conf
-rw-r--r-- 1 root root   92 Sep 18 10:54 10-radeon.conf
-rw-r--r-- 1 root root  945 Okt 16 06:48 40-libinput.conf
-rw-r--r-- 1 root root 3025 Apr  3  2018 70-wacom.conf

$ xsetwacom --list devices
Wacom Cintiq 27QHD Pen stylus           id: 15  type: STYLUS    
Wacom Express Key Remote Pad pad        id: 16  type: PAD       
Wacom Cintiq 27QHD Pen eraser           id: 18  type: ERASER

and sudo evemu-record shows absolutely no reaction to pen gestures. I also attach the output of the debugging script mentioned in #27

record_1549752892.tar.gz

I don't mean to sound ungrateful and I really appreciate the work you are doing, but its been a week since I last drawn anything and this gets frustrating :(

xf86-input-wacom: 0.36
OS: Arch linux
Tablet: Intuos 5 PTH-650/K

I noticed issues with tilt direction being broken in Krita and did some digging...

Is my tablet broken?

Probably not, I plugged the tablet into my laptop running an older version of xf86-input-wacom (0.35.x) and tilt works fine.

Where is the issue occurring

I took a dig into events being emitted by the kernel driver for my wacom pen with:

evtest | grep TILT

ABS_TILT_X and ABS_TILT_Y events are being emitted separately, with values corresponding to the angle I'm holding the pen.

On the other hand, looking at xorg events with:

xinput test $pen_id

Gave me rows like:

motion ... a[3]=39 a[4]=39 ...

Where a[3] and a[4] are always equal, and respond to changes in x tilt. Looking at the source for this project indicates they represent x and y tilt, respectively.

I took a dig through source changes which have occurred since xf86-input-wacom 0.35 and spotted this line, which looks like it'd explain the issue I'm seeing: https://github.com/linuxwacom/xf86-input-wacom/blob/master/src/wcmFilter.c#L317

ds->tilty = wcmFilterAverage(state->tiltx, common->wcmRawSample);

It appears there's a typo here, tiltx is being averaged, then being assigned to tilty - I think the line should read:

ds->tilty = wcmFilterAverage(state->tilty, common->wcmRawSample);

Let me know if there's anything I can do to help with this, and thank you for your efforts maintaining this great project 👍

edit: added a little more info to line of source code

Line 877 in wcmISDV4.c says:

xf86WaitForInput(pInfo->fd, 1000000)

According to xf86WaitForInput documentation, the "timeout" value is in microseconds, 1000000 us = 1 second.

The wait is iterated up to MAXTRY (== 250) times, which means it delays up to 250 seconds. According to http://linuxwacom.sourceforge.net/wiki/index.php/ISDV4_Protocol the expected delay is 250 ms.

A suggested fix is to change the call to

xf86WaitForInput(pInfo->fd, 1000)

resulting in a wait of 1000 us = 1 ms per iteration, for a total of expected 250 ms.

Without this change, the boot times into graphical X11 raises by 250 s on a system with ISDV4 Wacom display tablet present.

I'm trying to play with PressureCurve for my tablet. Unfortunately, no matter how I set the value, it always resets to linear when I bring my stylus away from proximity, and then back in proximity again. I've tried:

• setting it in xorg.conf (after boot, before I've brought the stylus in proximity, it is set to that value, but gets set to linear as soon as the stylus is detected)
• turning wacom plugin off in gsettings (I tried setting it explicitly via gsettings also, but I get that "Schema “org.gnome.settings-daemon.peripherals.wacom.stylus” is relocatable (path must be specified)" and then cound't figure out the appropriate path)
• setting it via xinput
• setting it via xsetwacom

For both xinput and xsetwacom, if my stylus is in proximity, the values set correctly, but as soon as I leave proximity and come back again, they reset to linear.

Not sure if this is a bug or just a weird configuration issue, but I though opening an issue may help.

Based on Sourceforge Bug #315

When the xf86-input-libinput driver is installed, it will often end up stealing Wacom devices like touchscreens and pads away from the xf86-input-wacom driver. This prevents the devices from showing up in xsetwacom, can prevevent their configuration through the GNOME control center, and prevents the X driver's pen/touch arbitration from working (though kernel arbitration is usually still available).

This is caused by xf86-input-libinput having a "90-libinput.conf" in xorg.conf.d which the X server uses in preference to our own "50-wacom.conf".

I'm having a problem very similar to this bug report: https://sourceforge.net/p/linuxwacom/bugs/280

My tablet is a ctl-480s-n, and I'm running xf86-input-wacom 0.36.1-1, with the X.org X server 1.19.6, on linux 4.15.7-1-ARCH.

The issue is the same thing described in that bug report, possibly also a copy of #14: like demonstrated in the video sent by the person who reported that bug, when I move my pen quickly while it's not touching the tablet (drawing circles is a good way to reproduce this), it sometimes stops, and skips to another location.

Sorry if my explanation sounds weird, but the video posted in the original bug report explains it pretty well. The only difference I'm having is that my jumps happen in the top left, while the jumps seem to happen in the bottom right in the video.

Also, the RawSample setting seems to make the bug more consistent when set higher, while slowing down movement. This may make it easier to reproduce the bug, too.

Edit: here's the capture.sh results in case it helps.

Can you please help me? How do I enable invers or natural vertical scrolling for two finger scrolling?

I found a couple of outdated sites (e.g. https://help.ubuntu.com/community/Wacom#Fixing_the_Inverted_Scrolling_Problem), but none works for me.

I use Linux Mint 19 and a "Wacom Bamboo Fun small (2FG)" tablet.

Thank you so much for your help!!

I have all the drivers for Wacom installed on my Ubuntu system. I can see my Intuos5 under xinput, and I can control my cursor by the tablet, but several things goes wrong after the installation.

• The cursor flashes, and then there is a chance that the system crashes and bring me back to the log-in menu.
• Several shortcuts are disabled (e.g. < Super >+< Space >, < Ctrl >+< Alt >+T).
• The "System Settings" window terminates when I click on "All Settings > Wacom Tablet".

All these issues happens only when I log in the system with the tablet plugged in, or when I plug in the tablet after logged in.

My Ubuntu is 4.4.0-137-generic, with nvidia-390, and gnome-shell version is 3.10.4.

I'm experiencing a lag when I use a double finger touch scroll or zoom.
I am using 0.36.1-1 on Arch Linux. The lag happens on scroll and on zoom. I am using Wacom Intuos PT S Finger touch. It's exactly as described in this previous bug:

https://sourceforge.net/p/linuxwacom/bugs/218/

There is an early delay then it 'kicks in' (scroll or zoom) so you can then continue to scroll or zoom while you still have your 2 fingers on the tablet, but the behavior is reset once you release your fingers.

Imported from Sourceforge Bug #303

While developing a simple GUI for xsetwacom, I discovered this big issue, if it won't be fixed I'll try some heuristic fixes on xsetwacom output
Just see:

% xsetwacom set "10" "Button" "9" "key +Alt_L key +m key -m key -Alt_L "
% xsetwacom -s --get 10 all 2>/dev/null|grep Alt_L
xsetwacom set "10" "Button" "9" "+Alt_L +m -m -Alt_L "
% xsetwacom set "10" "Button" "9" "+Alt_L +m -m -Alt_L
Cannot parse keyword '+Alt_L' at position 1

there is no "key" prefix, meanwhile this command have a proper output:

% xsetwacom -s --get 10 Button 9
xsetwacom set "10" "Button" "9" "key +Alt_L +m -m -Alt_L "

The bug only happens with the "all" option, so I can easily work it around at price of more shell calls... I'll check the priority you give to it.

When I touch the pen to the tablet and then lift the pen a short distance, the cursor stops moving for a brief moment, even though the pen is still in range of the digitizer. Is there a way I can disable this "feature"? I have a CTL-480 tablet if it matters.

with the pen moved there's nothing happened and theres no item show up in wacom settings page
so any solutions?

BTW:xserver-xorg-input-wacom=0.34

My stylus top button are set up to emulate right mouse button click. But this button works like left button click in a context menus or other situation that it need.
This make a trouble in Krita brush popup menu. I can select colour just due to late to release the top button because in colour selection dialogue it works like "left button". Mouse buttons works as expected.

lsusb: Bus 001 Device 005: ID 056a:5044 Wacom Co., Ltd

This is also mentioned in https://wiki.archlinux.org/index.php/Lenovo_Thinkpad_Yoga_260#TouchScreen_and_Stylus

Is this the right place to post the bug?

The Cintiq 24HD sends KEY_PROG1 through to KEY_PROG3 for the special buttons, but the wacom driver discards them. Let's not do that, let's pass them on and let userspace figure out what to do with them. The default mapping is XF86Launch1 through to XF86Launch3 so they could be assigned.

More recent tablets send KEY_CONTROLPANEL, KEY_ONSCREEN_KEYBOARD, and KEY_BUTTONCONFIG but those have keycodes outside the 255 X keycode range.

Hi, Just encounter an odd situation, I deployed this driver in two machines, both of them are Centos 3.10.0-693.11.1.el7.x86_64. tablet model:pth-660,
After combined the driver use the same steps which you provided in the main page, one machine is working, but another machine still can't use the tablet properly. Debugged for a while still can't find any solution to fix it, Could you please help to take a look?
Use "dmesg" command and print the output, it already recognized the device:

[ 2368.035977] usb 1-4: USB disconnect, device number 7
[ 2374.132641] usb 1-4: new full-speed USB device number 8 using xhci_hcd
[ 2374.298847] usb 1-4: New USB device found, idVendor=056a, idProduct=0357
[ 2374.298852] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2374.298856] usb 1-4: Product: Wacom Intuos Pro M
[ 2374.298858] usb 1-4: Manufacturer: Wacom Co.,Ltd.
[ 2374.298860] usb 1-4: SerialNumber: 7JQ00A1012349
[ 2374.303690] input: Wacom Co.,Ltd. Wacom Intuos Pro M Pen as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/0003:056A:0357.000B/input/input23
[ 2374.303940] wacom 0003:056A:0357.000B: hidraw3: USB HID v1.10 Mouse [Wacom Co.,Ltd. Wacom Intuos Pro M] on usb-0000:00:14.0-4/input0
[ 2374.306231] wacom 0003:056A:0357.000C: Unknown device_type for 'Wacom Co.,Ltd. Wacom Intuos Pro M'. Ignoring.
[ 2374.306288] usb-storage 1-4:1.3: USB Mass Storage device detected
[ 2374.306620] scsi host9: usb-storage 1-4:1.3
[ 2375.307850] scsi 9:0:0:0: Direct-Access     Wacom    Intuos Pro M     1.37 PQ: 0 ANSI: 2
[ 2375.308427] sd 9:0:0:0: Attached scsi generic sg1 type 0
[ 2375.308852] sd 9:0:0:0: [sdb] 65536 512-byte logical blocks: (33.5 MB/32.0 MiB)
[ 2375.309093] sd 9:0:0:0: [sdb] Write Protect is on
[ 2375.309097] sd 9:0:0:0: [sdb] Mode Sense: 00 00 80 00
[ 2375.309379] sd 9:0:0:0: [sdb] Asking for cache data failed
[ 2375.309382] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[ 2375.393425] sd 9:0:0:0: [sdb] Attached SCSI removable disk

But in the log, it keep saying this error:

journal: JS LOG: Unable to mount volume Wacom Start: Gio.IOErrorEnum: Error mounting /dev/sdb at /run/media/lcong/Wacom Start: Command-line `mount -t "exfat" -o "uhelper=udisks2,nodev,nosuid,uid=15001,gid=20003,iocharset=utf8,namecase=0,errors=remount-ro,umask=0077" "/dev/sdb" "/run/media/lcong/Wacom Start"' exited with non-zero exit status 32: mount: unknown filesystem type 'exfat

"xsetwacom --list" can't find my tablet. "lsmod" can find the driver is loaded:

$lsmod  | grep wacom
wacom                  62424  0 
hid_wacom              91810  0 
wacom_w8001            12982  0 

Any suggestion will be appreciated

Thanks.

I'm using a Monoprice-rebranded Huion H610 graphics tablet, which should be compatible (and so far has been) with the wacom X driver. However, when I try to set button 2 on the stylus to pan (such as xsetwacom set "10594 Pen stylus" Button 2 "pan"), it clicks button 3 when I begin panning, and cancels the pan. When I have button 3 on pan, it clicks button 1 and doesn't cancel the pan. Finally, when I do xsetwacom get "10594 Pen stylus" Button 2, it returns an empty string instead of pan, even though it is in fact in pan mode.

System info:

Arch Linux
Kernel: 4.19.12-arch1-1-ARCH x86_64
xf86-input-wacom: 0.36.1-1 (installed from official repository)
xorg-server: 1.20.3-1
value of PanScrollThreshold: 12

I have a pen that is reported as two devices, a stylus and an eraser. It is designed to switch to the eraser when the bottom barrel button is held.

Steps to reproduce

1. Bring the pen close to the screen without holding any button and move it around/touch the screen.
2. Press the eraser button and move the pen around/touch the screen.
3. Release the eraser button and move the pen around/touch the screen.

Expected behavior

1. The device with type STYLUS reports movement/touches.
2. The device with type ERASER reports movement/touches.
3. The device with type STYLUS reports movement/touches.

Actual behavior

1. The device with type ERASER reports movement/touches.
2. The device with type ERASER reports movement/touches.
3. The device with type STYLUS reports movement/touches.

I've tested the pen on a Surface Book with Windows 10, and it works correctly there, so I don't believe it's a hardware issue.

Hardware

• Computer: Dell XPS 15 2 in 1 (9575)
• Pen: Dell Premium Active Pen PN579X

Relavent command output:

~ $ xsetwacom list
Wacom HID 486B Pen stylus               id: 12  type: STYLUS    
Wacom HID 486B Finger touch             id: 13  type: TOUCH     
Wacom HID 486B Pen eraser               id: 20  type: ERASER    
~ $ cat .config/tabletdblocalrc 
[486B]
layout=unknown
model=unknown
name=Wacom HID 486B
padbuttons=0
statusleds=0
touchring=false
touchstripl=false
touchstripr=false
wheel=false
~ $ cat .config/tabletprofilesrc 
[056A:486B]
CurrentProfileEntry=-1
ProfileRotationList=

[056A:486B][Default][eraser]
Area=0 0 0 0
Button1=1
Button2=3
Button3=2
Mode=absolute
PressureCurve=0 0 100 100
RawSample=4
Rotate=auto
ScreenSpace=desktop
Suppress=2
Threshold=27

[056A:486B][Default][stylus]
Area=0 0 0 0
Button1=1
Button2=3
Button3=2
Mode=absolute
PressureCurve=0 0 100 100
RawSample=4
Rotate=auto
ScreenSpace=desktop
Suppress=2
TabletPcButton=off
Threshold=30

[056A:486B][Default][touch]
Area=0 0 0 0
Gesture=on
InvertScroll=off
Mode=absolute
Rotate=auto
ScreenSpace=desktop
ScrollDistance=20
TapTime=250
Touch=on
ZoomDistance=50

[:][Default][eraser]
Button1=1
Button2=2
Button3=3
Mode=absolute
PressureCurve=0 0 100 100
RawSample=4
Rotate=auto
Suppress=2
Threshold=27

[:][Default][pad]
AbsWheelDown=5
AbsWheelUp=4

[:][Default][stylus]
Button1=1
Button2=2
Button3=3
Mode=absolute
PressureCurve=0 0 100 100
RawSample=4
Rotate=auto
Suppress=2
Threshold=27

Recently bought a Lenovo Yoga 720, running Ubuntu 18.04. Finger touch/zoom worked great for about a month, then all of a sudden stopped working. A friend's wacom pen does work as a mouse.

The kernel does seem to acknowledge that the driver's installed; this is the relevant output of more /proc/input/devices

and xinput list suggests that something is recognizing the device's finger-touch functionality...

I did try cleaning the screen, and looking for similar issues, but to no avail. Any help would be appreciated!

Using the default drivers from Ubuntu 16.04 xserver-xorg-input-wacom I get the following error on the Xorg.log

[   217.787] (II) Using input driver 'wacom' for 'Wacom Co.,Ltd. Intuos BT S Pen'
[   217.787] (**) Wacom Co.,Ltd. Intuos BT S Pen: always reports core events
[   217.787] (**) Option "Device" "/dev/input/event22"
[   217.840] (EE) Wacom Co.,Ltd. Intuos BT S Pen: Invalid type 'stylus' for this device.
[   217.840] (EE) Wacom Co.,Ltd. Intuos BT S Pen: Invalid type 'eraser' for this device.
[   217.840] (EE) Wacom Co.,Ltd. Intuos BT S Pen: Invalid type 'cursor' for this device.
[   217.840] (EE) Wacom Co.,Ltd. Intuos BT S Pen: Invalid type 'touch' for this device.
[   217.840] (EE) Wacom Co.,Ltd. Intuos BT S Pen: Invalid type 'pad' for this device.
[   217.840] (EE) Wacom Co.,Ltd. Intuos BT S Pen: No type specified
[   217.864] (EE) PreInit returned 8 for "Wacom Co.,Ltd. Intuos BT S Pen"
[   217.864] (II) UnloadModule: "wacom"
[  1460.378] (--) synaptics: DLL07BF:01 06CB:7A13 Touchpad: touchpad found
[  2205.819] (II) config/udev: Adding input device Wacom Co.,Ltd. Intuos BT S Pen (/dev/input/event22)
[  2205.819] (**) Wacom Co.,Ltd. Intuos BT S Pen: Applying InputClass "Wacom USB device class"
[  2205.819] (**) Wacom Co.,Ltd. Intuos BT S Pen: Applying InputClass "Wacom class"
[  2205.819] (II) Using input driver 'wacom' for 'Wacom Co.,Ltd. Intuos BT S Pen'
[  2205.819] (**) Wacom Co.,Ltd. Intuos BT S Pen: always reports core events
[  2205.819] (**) Option "Device" "/dev/input/event22"
[  2205.872] (EE) Wacom Co.,Ltd. Intuos BT S Pen: Invalid type 'stylus' for this device.
[  2205.872] (EE) Wacom Co.,Ltd. Intuos BT S Pen: Invalid type 'eraser' for this device.
[  2205.872] (EE) Wacom Co.,Ltd. Intuos BT S Pen: Invalid type 'cursor' for this device.
[  2205.872] (EE) Wacom Co.,Ltd. Intuos BT S Pen: Invalid type 'touch' for this device.
[  2205.872] (EE) Wacom Co.,Ltd. Intuos BT S Pen: Invalid type 'pad' for this device.
[  2205.872] (EE) Wacom Co.,Ltd. Intuos BT S Pen: No type specified
[  2205.900] (EE) PreInit returned 8 for "Wacom Co.,Ltd. Intuos BT S Pen"
[  2205.900] (II) UnloadModule: "wacom"

But the utility libwacom-list-local-devices is able to give me some output.This is when connected to Bluetooth and not through USB.

** libwacom-list-local-devices --database /usr/share/libwacom**

[16:15:24] $ libwacom-list-local-devices --database /usr/share/libwacom
[Device]
Name=Wacom Serial Tablet WACf004
DeviceMatch=serial:0000:0000;
Class=ISDV4
Width=0
Height=0
IntegratedIn=Display;System;
Styli=0xfffff;0xffffe;

[Features]
Reversible=false
Stylus=true
Ring=false
Ring2=false
Touch=false
TouchSwitch=false
StatusLEDs=
NumStrips=0
Buttons=0
---------------------------------------------------------------

xinput list

[16:16:39] $ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech M325                           	id=11	[slave  pointer  (2)]
⎜   ↳ DLL07BF:01 06CB:7A13 Touchpad           	id=13	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Video Bus                               	id=8	[slave  keyboard (3)]
    ↳ Power Button                            	id=9	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=10	[slave  keyboard (3)]
    ↳ Integrated_Webcam_HD                    	id=12	[slave  keyboard (3)]
    ↳ Intel HID events                        	id=14	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=15	[slave  keyboard (3)]
    ↳ Dell WMI hotkeys                        	id=16	[slave  keyboard (3)]
    ↳ FaceTime HD Camera (Display)            	id=17	[slave  keyboard (3)]
    ↳ Logitech K810                           	id=18	[slave  keyboard (3)]

dmesg | grep -i wacom

[16:17:57] $ dmesg | grep -i wacom
[  217.078838] usb 1-2: Manufacturer: Wacom Co.,Ltd.
[  217.653518] input: Wacom Co.,Ltd. Intuos BT S Pen as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:056A:0376.000E/input/input25
[  217.653864] wacom 0003:056A:0376.000E: hidraw6: USB HID v1.10 Device [Wacom Co.,Ltd. Intuos BT S] on usb-0000:00:14.0-2/input0
[ 2205.167740] usb 1-2: Manufacturer: Wacom Co.,Ltd.
[ 2205.172255] input: Wacom Co.,Ltd. Intuos BT S Pen as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:056A:0376.0010/input/input28
[ 2205.172513] wacom 0003:056A:0376.0010: hidraw6: USB HID v1.10 Device [Wacom Co.,Ltd. Intuos BT S] on usb-0000:00:14.0-2/input0

In README, there is a link to:

https://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Category:HOWTO

But that URL 404's.

Additionally, the "correct" URL for the Sourceforge-hosted MediaWiki is:

http://linuxwacom.sourceforge.net/wiki/index.php/Main_Page

But that page appears nearly blank (MediaWiki title appears with no body) under Chrome Version 65.0.3325.124 on Ubuntu 16.04

Moving over to 100% GitHub would be a good choice at this point.

I have a Wacom DTI-520, the old LCD tablet.
Cannot drive in Ubuntu 16.04.

[ 528.461] (II) config/udev: Adding input device WACOM DTI-520-U Pen (/dev/input/event7)
[ 528.461] ( ) WACOM DTI-520-U Pen: Applying InputClass "Wacom USB device class"
[ 528.461] ( ) WACOM DTI-520-U Pen: Applying InputClass "Wacom class"
[ 528.461] (II) Using input driver 'wacom' for 'WACOM DTI-520-U Pen'
[ 528.461] ( ) WACOM DTI-520-U Pen: always reports core events
[ 528.461] ( ) Option "Device" "/dev/input/event7"
[ 528.528] (EE) WACOM DTI-520-U Pen: Invalid type 'stylus' for this device.
[ 528.528] (EE) WACOM DTI-520-U Pen: Invalid type 'eraser' for this device.
[ 528.528] (EE) WACOM DTI-520-U Pen: Invalid type 'cursor' for this device.
[ 528.528] (EE) WACOM DTI-520-U Pen: Invalid type 'touch' for this device.
[ 528.528] (EE) WACOM DTI-520-U Pen: Invalid type 'pad' for this device.
[ 528.528] (EE) WACOM DTI-520-U Pen: No type specified
[ 528.560] (EE) PreInit returned 8 for "WACOM DTI-520-U Pen"
[ 528.560] (II) UnloadModule: "wacom"

A device, actually has two ID.
$ lsusb
Bus 001 Device 010: ID 056a:003a Wacom Co., Ltd
Bus 001 Device 009: ID 056a:003b Wacom Co., Ltd

Thank you.

Cannot change Wacom Intuos S cursor proximity. Exact model name is Wacom Intuos Basic Pen S CTL-4100K-N.
Default value:

xsetwacom get 'Wacom Intuos S Pen cursor' CursorProximity
10

Physically it is about 1 cm. I would like to move cursor only when pen touches pad, so I do:

xsetwacom set 'Wacom Intuos S Pen cursor' CursorProximity 1

(or 0 instead of 1, there should not be much difference)
Command itself works, I can check result with get command and it shows 1 for CursorProximity.
But actual behavior was not changed, proximity is still about 1 cm.

xsetwacom --version
0.36.1

I was able to reach desired behavior on Windows using GUI settings tool, so it is not problem of device itself.

I cannot use Wacom CTL-471 on Ubuntu 18.04 LTS.