I want to use my Wacom pen's opposite (eraser side) as a middle button mouse!

I'm using a Wacom GD-0912-U graphics tablet. I'm running Debian 12.5 and Gimp 2.10.34. In Gimp, when I touch the pointed end of the pen to the tablet, it registers as a press. But when I lift the pen, the release isn't registered until the pen is about 2.5cm off the tablet. The eraser end of the pen works fine, however. The release occurs as soon as I lift the pen. What can I do to make the pointed end work the same way?

I turned off the touchscreen as described here and here on my Lenovo ThinkPad with Debian and Wayland/libinput .

echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="5144", ATTR{authorized}="0"' > /etc/udev/rules.d/80-touchscreen.rules

Now I need to use the ThinkPad Pen Pro, which is a stylus for the screen/monitor's inbuilt tablet function. The pen is affected by the udev rule. Cancelling the rule makes the pen work but also reactivates touch. The devices have idVendor and idProduct in common . But are touchscreen and stylus not operating independently, and so shouldn't it be possible to disable the one without the other? (Note, xinput disable does not work for some reason, and I don't know what model number goes into xsetwacom --set 'model' Touch off because xsetwacom --list devices returns nothing, so I cannot test it that way.) At least someone reported touch not working while pen and tablet did function . *Can someone help specify a working udev rule *, there are a few ? I tried the following but both became deactivated.

SUBSYSTEM=="usb", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="5144", ATTR{name}=="Wacom Pen and multitouch sensor Pen", ATTR{authorized}="1"
SUBSYSTEM=="usb", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="5144", ATTR{name}=="Wacom Pen and multitouch sensor Finger", ATTR{authorized}="0"

$ cat /proc/bus/input/devices
I: Bus=0003 Vendor=056a Product=5144 Version=0111
N: Name="Wacom Pen and multitouch sensor Finger"
P: Phys=usb-0000:00:14.0-10/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:056A:5144.0005/input/input32
U: Uniq=
H: Handlers=mouse2 event21 
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 0
B: ABS=260800000000003

I: Bus=0003 Vendor=056a Product=5144 Version=0111
N: Name="Wacom Pen and multitouch sensor Pen"
P: Phys=usb-0000:00:14.0-10/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:056A:5144.0006/input/input34
U: Uniq=
H: Handlers=mouse3 event25 
B: PROP=2
B: EV=1b
B: KEY=1e03 0 0 0 0 0
B: ABS=1000d000003
B: MSC=1

$ lsusb
Bus 001 Device 007: ID 056a:5144 Wacom Co., Ltd Pen and multitouch sensor

$ inputx --list devices
⎡ Virtual core pointer                        	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ xwayland-pointer:18                     	id=6	[slave  pointer  (2)]
⎜   ↳ xwayland-relative-pointer:18            	id=7	[slave  pointer  (2)]
⎜   ↳ xwayland-stylus:18                      	id=10	[slave  pointer  (2)]
⎜   ↳ xwayland-eraser:18                      	id=11	[slave  pointer  (2)]
⎜   ↳ xwayland-cursor:18                      	id=12	[slave  pointer  (2)]
⎜   ↳ xwayland-touch:18                       	id=9	[slave  pointer  (2)]

$ xsetwacom --list devices


$ libwacom-list-local-devices 
# Device node: /dev/input/event25
[Device]
Name=ISDv4 5144
ModelName=
DeviceMatch=usb:056a:5144;
Class=ISDV4
Width=12
Height=7
IntegratedIn=Display;System;
Styli=0x1;0x11;0x19;0x21;0x31;0x39;0x49;0x71;0x221;0x231;0x271;0x421;0x431;0x621;0x631;0x8051;0x805b;0x806b;0x807b;0x826b;0x846b;

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

---------------------------------------------------------------

# Device node: /dev/input/event21
[Device]
Name=ISDv4 5144
ModelName=
DeviceMatch=usb:056a:5144;
Class=ISDV4
Width=12
Height=7
IntegratedIn=Display;System;
Styli=0x1;0x11;0x19;0x21;0x31;0x39;0x49;0x71;0x221;0x231;0x271;0x421;0x431;0x621;0x631;0x8051;0x805b;0x806b;0x807b;0x826b;0x846b;

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

$ udevadm info /sys/class/input/input32/
P: /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:056A:5144.0005/input/input32
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:056A:5144.0005/input/input32
E: PRODUCT=3/56a/5144/111
E: NAME="Wacom Pen and multitouch sensor Finger"
E: PHYS="usb-0000:00:14.0-10/input0"
E: UNIQ=""
E: PROP=2
E: EV=b
E: KEY=400 0 0 0 0 0
E: ABS=260800000000003
E: MODALIAS=input:b0003v056Ap5144e0111-e0,1,3,k14A,ra0,1,2F,35,36,39,mlsfw
E: SUBSYSTEM=input
E: USEC_INITIALIZED=6838074
E: ID_INPUT=1
E: ID_INPUT_TOUCHSCREEN=1
E: ID_BUS=usb
E: ID_MODEL=Pen_and_multitouch_sensor
E: ID_MODEL_ENC=Pen\x20and\x20multitouch\x20sensor
E: ID_MODEL_ID=5144
E: ID_SERIAL=Wacom_Co._Ltd._Pen_and_multitouch_sensor
E: ID_VENDOR=Wacom_Co._Ltd.
E: ID_VENDOR_ENC=Wacom\x20Co.\x2cLtd.
E: ID_VENDOR_ID=056a
E: ID_REVISION=0003
E: ID_TYPE=hid
E: ID_USB_MODEL=Pen_and_multitouch_sensor
E: ID_USB_MODEL_ENC=Pen\x20and\x20multitouch\x20sensor
E: ID_USB_MODEL_ID=5144
E: ID_USB_SERIAL=Wacom_Co._Ltd._Pen_and_multitouch_sensor
E: ID_USB_VENDOR=Wacom_Co._Ltd.
E: ID_USB_VENDOR_ENC=Wacom\x20Co.\x2cLtd.
E: ID_USB_VENDOR_ID=056a
E: ID_USB_REVISION=0003
E: ID_USB_TYPE=hid
E: ID_USB_INTERFACES=:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usbhid
E: ID_PATH=pci-0000:00:14.0-usb-0:10:1.0
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_10_1_0
E: ID_FOR_SEAT=input-pci-0000_00_14_0-usb-0_10_1_0
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:

$ udevadm info /sys/class/input/input34
P: /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:056A:5144.0006/input/input34
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:056A:5144.0006/input/input34
E: PRODUCT=3/56a/5144/111
E: NAME="Wacom Pen and multitouch sensor Pen"
E: PHYS="usb-0000:00:14.0-10/input1"
E: UNIQ=""
E: PROP=2
E: EV=1b
E: KEY=1e03 0 0 0 0 0
E: ABS=1000d000003
E: MSC=1
E: MODALIAS=input:b0003v056Ap5144e0111-e0,1,3,4,k140,141,149,14A,14B,14C,ra0,1,18,1A,1B,28,m0,lsfw
E: SUBSYSTEM=input
E: USEC_INITIALIZED=6961475
E: ID_INPUT=1
E: ID_INPUT_TABLET=1
E: ID_BUS=usb
E: ID_MODEL=Pen_and_multitouch_sensor
E: ID_MODEL_ENC=Pen\x20and\x20multitouch\x20sensor
E: ID_MODEL_ID=5144
E: ID_SERIAL=Wacom_Co._Ltd._Pen_and_multitouch_sensor
E: ID_VENDOR=Wacom_Co._Ltd.
E: ID_VENDOR_ENC=Wacom\x20Co.\x2cLtd.
E: ID_VENDOR_ID=056a
E: ID_REVISION=0003
E: ID_TYPE=hid
E: ID_USB_MODEL=Pen_and_multitouch_sensor
E: ID_USB_MODEL_ENC=Pen\x20and\x20multitouch\x20sensor
E: ID_USB_MODEL_ID=5144
E: ID_USB_SERIAL=Wacom_Co._Ltd._Pen_and_multitouch_sensor
E: ID_USB_VENDOR=Wacom_Co._Ltd.
E: ID_USB_VENDOR_ENC=Wacom\x20Co.\x2cLtd.
E: ID_USB_VENDOR_ID=056a
E: ID_USB_REVISION=0003
E: ID_USB_TYPE=hid
E: ID_USB_INTERFACES=:030000:
E: ID_USB_INTERFACE_NUM=01
E: ID_USB_DRIVER=usbhid
E: ID_PATH=pci-0000:00:14.0-usb-0:10:1.1
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_10_1_1
E: ID_FOR_SEAT=input-pci-0000_00_14_0-usb-0_10_1_1
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:

$ sudo udevadm info -a -p /sys/class/input/input32


$ sudo udevadm info -a -p /sys/class/input/input34

I have a small wacom pad and a large monitor. And i wanted to reduce the area of the screen where the tablet surface is mapped. Sadly graphical utility does not allow this. Currently the configuration is the following: Coordinate Transformation Matrix (216): 0.571429, 0.000000, 0.428571, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 This maps to the HDMI connected 2nd monitor in landscape mode. I want to rotate mapping 90 degrees and use half of the screen in portrait mode. Infotunnely just multiplying given figures to rotation matrix gives total mess. As i unerstand due to not square shape of the area. But no idea how to do it right. So basically i need do the following.

I am testing Debian Bullseye on a Thinkpad X1 Yoga Gen 6, using a live cd with KDE and non-free drivers ([debian-live-11.5.0-amd64-kde+nonfree.iso](https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.5.0-live+nonfree/amd64/iso-hybrid/)) . I'd like to be sure that everything I need works before wiping the hard drive. Everything seems to work indeed, except that when I use a finger to touch objects or buttons, these are not clicked as expected, only selected at best. This seems to happen with anything related to plasma/Qt: - touching any icon on the plasma panel (including the application launcher) just places the cursor there; - touching buttons in KDE apps/settings dialogs selects them but does not click them; - touching menus in KDE apps unfolds them, but touching menu items just selects them (eg File -> New Tab in Konqueror). Situations where the **finger works as expected**: - everything on web pages (HTML buttons, HTML5 controls on eg youtube) - everything in non-KDE applications (eg Firefox) - window titlebar buttons (minimize/maximize/close) for **all** apps. The included Wacom digitizer pen always works as expected (touching an object clicks on it). Here are some infos that may be relevant: KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2

user@debian:~$ uname -a
Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) x86_64 GNU/Linux
user@debian:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

user@debian:~$ sudo Xorg -version

X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System: linux Debian
Current Operating System: Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) x86_64
Kernel command line: BOOT_IMAGE=(hd0,gpt4)/live/vmlinuz-5.10.0-18-amd64 boot=live quiet splash fsck.mode=skip persistence --
Build Date: 05 August 2022  08:00:36AM
xorg-server 2:1.20.11-1+deb11u2 (https://www.debian.org/support)  
Current version of pixman: 0.40.0
        Before reporting problems, check http://wiki.x.org 
        to make sure that you have the latest version.

user@debian:~$ lsmod|grep wacom
wacom                 131072  0
usbhid                 65536  1 wacom
hid                   147456  7 i2c_hid,wacom,usbhid,hid_multitouch,hid_sensor_hub,intel_ishtp_hid,hid_generic

Relevant dmesg lines:

user@debian:~$ sudo dmesg|grep -i wacom
[    2.483787] input: Wacom HID 5278 Pen as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-WACF2200:00/0018:056A:5278.0002/input/input15
[    2.483979] input: Wacom HID 5278 Finger as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-WACF2200:00/0018:056A:5278.0002/input/input16
[    2.484211] wacom 0018:056A:5278.0002: hidraw1: I2C HID v1.00 Mouse [WACF2200:00 056A:5278] on i2c-WACF2200:00
user@debian:~$ sudo dmesg|grep -i screen
[    2.245919] input: WACF2200:00 056A:5278 Touchscreen as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-WACF2200:00/0018:056A:5278.0002/input/input9

xinput and evdev:

user@debian:~$ cat /proc/bus/input/devices 

[...]

I: Bus=0018 Vendor=056a Product=5278 Version=0100
N: Name="Wacom HID 5278 Pen"
P: Phys=i2c-WACF2200:00
S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-WACF2200:00/0018:056A:5278.0002/input/input15
U: Uniq=
H: Handlers=mouse2 event7 
B: PROP=2
B: EV=1b
B: KEY=1e03 0 0 0 0 0
B: ABS=1000d000003
B: MSC=1

I: Bus=0018 Vendor=056a Product=5278 Version=0100
N: Name="Wacom HID 5278 Finger"
P: Phys=i2c-WACF2200:00
S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-WACF2200:00/0018:056A:5278.0002/input/input16
U: Uniq=
H: Handlers=mouse3 event8 
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 0
B: ABS=260800000000003

[...]

user@debian:~$ xinput|grep Wacom
⎜   ↳ Wacom HID 5278 Pen stylus                 id=13   [slave  pointer  (2)]
⎜   ↳ Wacom HID 5278 Finger touch               id=14   [slave  pointer  (2)]
⎜   ↳ Wacom HID 5278 Pen eraser                 id=20   [slave  pointer  (2)]
user@debian:~$ xinput list-props 14
Device 'Wacom HID 5278 Finger touch':
        Device Enabled (188):   1
        Coordinate Transformation Matrix (190): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
        Device Accel Profile (319):     0
        Device Accel Constant Deceleration (320):       1.000000
        Device Accel Adaptive Deceleration (321):       1.000000
        Device Accel Velocity Scaling (322):    10.000000
        Device Node (311):      "/dev/input/event8"
        Wacom Tablet Area (363):        0, 0, 12064, 7540
        Wacom Rotation (364):   0
        Wacom Pressurecurve (365):      0, 0, 100, 100
        Wacom Serial IDs (366): 21112, 1, 3, 0, 0
        Wacom Serial ID binding (367):  0
        Wacom Pressure Threshold (368): 0
        Wacom Sample and Suppress (369):        2, 4
        Wacom Enable Touch (370):       1
        Wacom Enable Touch Gesture (372):       1
        Wacom Touch Gesture Parameters (373):   530, 235, 250
        Wacom Tool Type (374):  "TOUCH" (381)
        Wacom Button Actions (375):     "Wacom button action 0" (376), "Wacom button action 1" (377), "Wacom button action 2" (378)
        Wacom button action 0 (376):    1572865
        Wacom button action 1 (377):    1572866
        Wacom button action 2 (378):    1572867
        Device Product ID (312):        1386, 21112
        Wacom Debug Levels (380):       0, 0

It seems that touching the screen does produce the right event: when I touch the screen I see button press 1 and button release 1 both with xinput and with evtest

user@debian:~$ xinput test 14 
motion a=8704 a=4839 a=0 a=0 a=0 a=0 
button press   1 a=8704 a=4839 a=0 a=0 a=0 a=0 
motion a=8701 a=4836 a=0 a=0 a=0 a=0 
button release 1 

user@debian:~$ sudo evtest /dev/input/event8
Input driver version is 1.0.1
Input device ID: bus 0x18 vendor 0x56a product 0x5278 version 0x100
Input device name: "Wacom HID 5278 Finger"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value   8833
      Min        0
      Max    12064
      Resolution      40
    Event code 1 (ABS_Y)
      Value   1925
      Min        0
      Max     7540
      Resolution      40
    Event code 47 (ABS_MT_SLOT)
      Value      0
      Min        0
      Max        9
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max    12064
      Resolution      40
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max     7540
      Resolution      40
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max    65535
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Event: time 1668884040.469294, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 770
Event: time 1668884040.469294, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 9293
Event: time 1668884040.469294, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 3886
Event: time 1668884040.469294, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1668884040.469294, type 3 (EV_ABS), code 0 (ABS_X), value 9293
Event: time 1668884040.469294, type 3 (EV_ABS), code 1 (ABS_Y), value 3886
Event: time 1668884040.469294, -------------- SYN_REPORT ------------
Event: time 1668884040.471569, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 9282
Event: time 1668884040.471569, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 3888
Event: time 1668884040.471569, type 3 (EV_ABS), code 0 (ABS_X), value 9282
Event: time 1668884040.471569, type 3 (EV_ABS), code 1 (ABS_Y), value 3888
Event: time 1668884040.471569, -------------- SYN_REPORT ------------
Event: time 1668884040.477811, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 9279
Event: time 1668884040.477811, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 3896
Event: time 1668884040.477811, type 3 (EV_ABS), code 0 (ABS_X), value 9279
Event: time 1668884040.477811, type 3 (EV_ABS), code 1 (ABS_Y), value 3896
Event: time 1668884040.477811, -------------- SYN_REPORT ------------
Event: time 1668884040.488292, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1668884040.488292, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1668884040.488292, -------------- SYN_REPORT ------------

So I assume the issue lies somewhere in the interaction with plasma/KDE/Qt (as GTK and HTML work as expected). So my question is, **how do I make sure that plasma/Qt/KDE process a screen touch as a mouse button left click** ? Can you help me debug this? PS: basic multi-touch that works: two fingers for right click and scrolling; inch-to-zoom works (emulating key press/release 37) but is tricky, you have to try multiple times. PPS: I have read that Wayland seems to have a better support of gestures, but I really don't need anything fancy, and I'd rather stick with Xorg because I'm too old to learn new things, and Wayland in Plasma seems [too young](https://community.kde.org/Plasma/Wayland_Showstoppers) .

user@debian:~$ echo $XDG_SESSION_TYPE
x11

**Edit**: Reading a bit more on wayland, I am now willing to give it a try, so far I had mixed experiences: touch and basic gestures work, including pinch-to-zoom, but at the cost of loosing some pen functionality; moreover it gets less responsive and buggy after some time. I plan to experiment more with it. Maybe the version in Debian unstable will be better.

I have an issue with my wacom display on my thinkpad x390. The linux does not react to any movement of stylus or buttons on pen. I have wacom drivers installed. this is output of libwacom-list-local-devices:

devices:
- name: 'Wacom ISDv4 51af'
  bus: 'usb'
  vid: '0x056a'
  pid: '0x51af'
  nodes:
  - /dev/input/event9
  - /dev/input/event7

This is output of xinput:

xinput
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Wacom Pen and multitouch sensor Finger  	id=9	[slave  pointer  (2)]
⎜   ↳ Wacom Pen and multitouch sensor Pen stylus	id=10	[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              	id=14	[slave  pointer  (2)]
⎜   ↳ TPPS/2 Elan TrackPoint                  	id=15	[slave  pointer  (2)]
⎜   ↳ Wacom Pen and multitouch sensor Pen eraser	id=17	[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)]
    ↳ Sleep Button                            	id=8	[slave  keyboard (3)]
    ↳ Integrated Camera: Integrated C         	id=11	[slave  keyboard (3)]
    ↳ Integrated Camera: Integrated I         	id=12	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=13	[slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                  	id=16	[slave  keyboard (3)]

Output of xinput list-props 9:

Device 'Wacom Pen and multitouch sensor Finger':
	Device Enabled (186):	1
	Coordinate Transformation Matrix (188):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Calibration Matrix (315):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Calibration Matrix Default (316):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Send Events Modes Available (298):	1, 0
	libinput Send Events Mode Enabled (299):	0, 0
	libinput Send Events Mode Enabled Default (300):	0, 0
	Device Node (301):	"/dev/input/event7"
	Device Product ID (302):	1386, 20911

output of xinput list-props 17

Device 'Wacom Pen and multitouch sensor Pen eraser':
	Device Enabled (186):	1
	Coordinate Transformation Matrix (188):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	Device Accel Profile (309):	0
	Device Accel Constant Deceleration (310):	1.000000
	Device Accel Adaptive Deceleration (311):	1.000000
	Device Accel Velocity Scaling (312):	10.000000
	Device Node (301):	"/dev/input/event9"
	Wacom Tablet Area (324):	0, 0, 29376, 16524
	Wacom Rotation (325):	0
	Wacom Pressurecurve (326):	0, 0, 100, 100
	Wacom Serial IDs (327):	20911, 0, 10, 0, 0
	Wacom Serial ID binding (328):	0
	Wacom Proximity Threshold (329):	10
	Wacom Pressure Threshold (330):	26
	Wacom Sample and Suppress (331):	2, 4
	Wacom Enable Touch (332):	0
	Wacom Enable Touch Gesture (334):	0
	Wacom Touch Gesture Parameters (335):	0, 0, 250
	Wacom Tool Type (336):	"ERASER" (403)
	Wacom button action 0 (337):	1572865
	Wacom button action 1 (338):	1572866
	Wacom button action 2 (339):	1572867
	Wacom button action 3 (340):	1572872
	Wacom Button Actions (341):	"Wacom button action 0" (337), "Wacom button action 1" (338), "Wacom button action 2" (339), "None" (0), "None" (0), "None" (0), "None" (0), "Wacom button action 3" (340)
	Wacom Pressure Recalibration (342):	1
	Wacom Panscroll Threshold (343):	1300
	Device Product ID (302):	1386, 20911
	Wacom Debug Levels (344):	0, 0

Xournal++ is a very sofisticated program for digital pen/table, but have a bug with colour of Latex equations. It is like in the imagem below. It doesn't matter you make, the color is the same. Look, the red colour even was not selected.

I have recently switched to wayland, and running sway on Ubuntu 20.04. I'm trying to map my touch screen and wacom tablet to specific monitors. I have 3 monitors connected and working properly. I have been reading the libinput documentation without being able to find a solution. The PC recognizes the devices, and they work, however, they are mapped to all the available area. I tried using xinput map-to-output however it displays a warning message and then gives an error:

WARNING: running xinput against an Xwayland server. See the xinput man page for details.
Unable to find output 'eDP-1'. Output may not be connected.

Any help is appreciated.

I've been trying to run a command, when I press the top key on my Bamboo Ink Pen. I realized that it connects via Bluetooth, when I press the button and ceases the connection, when I release it. I stumbled over Run a script when bluetooth device is connected and when I run udevadm monitor --environment --udev --kernel --property and press the button once, I get the following output:

KERNEL[5118.647193] add      /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:3585 (bluetooth)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:3585
SUBSYSTEM=bluetooth
DEVTYPE=link
SEQNUM=4094

UDEV  [5118.657098] add      /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:3585 (bluetooth)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:3585
SUBSYSTEM=bluetooth
DEVTYPE=link
SEQNUM=4094
USEC_INITIALIZED=5118654305
SYSTEMD_ALIAS=/sys/subsystem/bluetooth/devices/hci0:3585
SYSTEMD_WANTS=bluetooth.target
SYSTEMD_USER_WANTS=bluetooth.target
TAGS=:systemd:

KERNEL[5119.311809] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:3585 (bluetooth)
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:3585
SUBSYSTEM=bluetooth
DEVTYPE=link
SEQNUM=4095

UDEV  [5119.317304] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:3585 (bluetooth)
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:3585
SUBSYSTEM=bluetooth
DEVTYPE=link
SEQNUM=4095
USEC_INITIALIZED=5118654305
SYSTEMD_ALIAS=/sys/subsystem/bluetooth/devices/hci0:3585
SYSTEMD_WANTS=bluetooth.target
SYSTEMD_USER_WANTS=bluetooth.target
TAGS=:systemd:

Unfortunately there is no idVendor or idProduct. When I run sudo tail -f /var/log/syslog though, it complains that the file does not exist. My udev rules looks like this so far.

# Run a program when my Bamboo Ink is connected
ACTION=="add" , SUBSYSTEM=="bluetooth", ATTR{idVendor}=="xxx", ATTR{idProduct}=="yyy", ATTRS{model}=="Bamboo Ink", RUN+="xournalpp"

Guessing the model is "Bamboo Ink", since I found this line in journalctl -b

26 14:57:35 X380-Yoga kernel: wacom 0005:056A:035F.000C: Unknown device_type for 'Bamboo Ink'. Ignoring.

So I need to find the idVendor, idProduct and model. Is there another way to do that?

I am a teacher and I have some students in the room and others via web, using  3 screens my laptop + a Wacom one tablet + a video projector screen.  I need to  (using an HP zbook 15u G3 wich can use 3 screens) 1) sync the video projector screen  with  [ a part of ] my 'Wacom one' screen. 2) Map the stylus only to the Wacom one's screen ( so I can see what I am writing by just looking at my tablet) So far I was able to do - (1) but not (2) with plasma - and (2) but not (1) with gnome.  With plasma even with only 2 screens I was not able to get a correct mapping using kde-config-tablet app (the result was always that  moving the stylus across tablet will mean moving the pointer from the left of one screen to the right of the other). I suspected it is bugged but maybe I am just stupid enough not to make it work... With Gnome the mapping was correct (limited to the tablet) but I could not have anything else than an extended desktop, where the video projector's screen and the wacom's  screen are next to each other and not sync (nor overlapping) . Pretty Please If someone know any solutions. I am very willing to try (even with command line tool [xrandr?]) I desperately need this to work!

I have a Wacom Cintiq 22HD connected to my Dell Precision 7510. The screen is working fine but the pen does not trigger any mouse cursor movement. From what I understand, Debian does suppport it out of the box. The screen and pen are working fine with the same setup under Windows 10, so it is not a hardware problem. The pen is hooked up to /dev/input/mouse2 but does not trigger any input when moving around. The screen recognized the pen and the small LED related to pen movement is blinking when the pen touches the screen. The following packages are installed: libwacom-bin, libwacom-common, libwacom-dev, libwacom2:amd64 and xserver-xorg-input-wacom`. The output of xsetwacom --list is:

Wacom Cintiq 22HD Pen stylus    	id: 12	type: STYLUS    
Wacom Cintiq 22HD Pad pad       	id: 13	type: PAD       
Wacom Cintiq 22HD Pen eraser    	id: 23	type: ERASER

There are also entries in dmesg related to the tablet (output of dmesg | grep -i wacom):

[    3.003718] usb 1-2: Manufacturer: WACOM
[    3.504373] input: Wacom Cintiq 22HD Pen as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.1/1-2.1:1.0/0003:056A:00FA.0001/input/input12
[    3.504409] input: Wacom Cintiq 22HD Pad as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.1/1-2.1:1.0/0003:056A:00FA.0001/input/input14
[    3.564182] wacom 0003:056A:00FA.0001: hidraw0: USB HID v1.10 Mouse [Tablet Cintiq 22HD Tablet] on usb-0000:00:14.0-2.1/input0

The pen is hooked up to /dev/input/mouse2 and /dev/input/event9 according to cat /proc/bus/input/devices | grep -i -A8 wacom:

N: Name="Wacom Cintiq 22HD Pen"
P: Phys=usb-0000:00:14.0-2.1/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.1/1-2.1:1.0/0003:056A:00FA.0001/input/input12
U: Uniq=
H: Handlers=mouse2 event9 
B: PROP=2
B: EV=1b
B: KEY=1c1f 0 0 0 0 0
B: ABS=1000f000107
--
N: Name="Wacom Cintiq 22HD Pad"
P: Phys=usb-0000:00:14.0-2.1/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.1/1-2.1:1.0/0003:056A:00FA.0001/input/input14
U: Uniq=
H: Handlers=kbd event10 js0 
B: PROP=0
B: EV=b
B: KEY=800 3f00c0000003ff 400 300000 0 0
B: ABS=1000000001b

I have tested the input with sudo xxd /dev/input/mouse2 but there is nothing coming. The Wacom Pen and Pad are recognized by the X session. The output of journalctl | grep -i wacom does not give any interesting output except maybe for the Invalid type 'xxx' for this device sections. But I have no idea what the output here should actually look like:

Apr 15 06:34:17 DAX kernel: usb 1-2: Manufacturer: WACOM
Apr 15 06:34:17 DAX kernel: input: Wacom Cintiq 22HD Pen as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.1/1-2.1:1.0/0003:056A:00FA.0001/input/input12
Apr 15 06:34:17 DAX kernel: input: Wacom Cintiq 22HD Pad as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.1/1-2.1:1.0/0003:056A:00FA.0001/input/input14
Apr 15 06:34:17 DAX kernel: wacom 0003:056A:00FA.0001: hidraw0: USB HID v1.10 Mouse [Tablet Cintiq 22HD Tablet] on usb-0000:00:14.0-2.1/input0
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) config/udev: Adding input device Wacom Cintiq 22HD Pen (/dev/input/event9)
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen: Applying InputClass "libinput tablet catchall"
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen: Applying InputClass "Wacom USB tablet class"
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen: Applying InputClass "Wacom tablet class"
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) LoadModule: "wacom"
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Module wacom: vendor="X.Org Foundation"
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) wacom: Driver for Wacom graphics tablets: PenPartner, Graphire,
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Using input driver 'wacom' for 'Wacom Cintiq 22HD Pen'
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen: always reports core events
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pen: type not specified, assuming 'stylus'.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pen: other types will be automatically added.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (--) Wacom Cintiq 22HD Pen stylus: using pressure threshold of 851 for button 1
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (--) Wacom Cintiq 22HD Pen stylus: maxX=95440 maxY=53860 maxZ=2047 resX=200000 resY=200000  tilt=enabled
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pen stylus: hotplugging dependent devices.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pen stylus: Invalid type 'cursor' for this device.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pen stylus: Invalid type 'touch' for this device.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pen stylus: Invalid type 'pad' for this device.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pen stylus: hotplugging completed.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) XINPUT: Adding extended input device "Wacom Cintiq 22HD Pen stylus" (type: STYLUS, id 12)
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen stylus: (accel) keeping acceleration scheme 1
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen stylus: (accel) acceleration profile 0
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen stylus: (accel) acceleration factor: 2.000
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen stylus: (accel) acceleration threshold: 4
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) config/udev: Adding input device Wacom Cintiq 22HD Pen (/dev/input/mouse2)
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) config/udev: Adding input device Wacom Cintiq 22HD Pad (/dev/input/event10)
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad: Applying InputClass "libinput keyboard catchall"
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad: Applying InputClass "libinput tablet catchall"
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad: Applying InputClass "Wacom USB tablet class"
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad: Applying InputClass "Wacom tablet class"
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Using input driver 'wacom' for 'Wacom Cintiq 22HD Pad'
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad: always reports core events
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad: Invalid type 'stylus' for this device.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad: Invalid type 'eraser' for this device.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad: Invalid type 'cursor' for this device.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad: Invalid type 'touch' for this device.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pad: type not specified, assuming 'pad'.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pad: other types will be automatically added.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pad pad: hotplugging dependent devices.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad pad: Invalid type 'stylus' for this device.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad pad: Invalid type 'eraser' for this device.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad pad: Invalid type 'cursor' for this device.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad pad: Invalid type 'touch' for this device.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pad pad: hotplugging completed.
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) XINPUT: Adding extended input device "Wacom Cintiq 22HD Pad pad" (type: PAD, id 13)
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad pad: (accel) keeping acceleration scheme 1
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad pad: (accel) acceleration profile 0
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad pad: (accel) acceleration factor: 2.000
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad pad: (accel) acceleration threshold: 4
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) config/udev: Adding input device Wacom Cintiq 22HD Pad (/dev/input/js0)
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: Applying InputClass "libinput tablet catchall"
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: Applying InputClass "Wacom USB tablet class"
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: Applying InputClass "Wacom tablet class"
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) Using input driver 'wacom' for 'Wacom Cintiq 22HD Pen eraser'
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: always reports core events
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (--) Wacom Cintiq 22HD Pen eraser: maxX=95440 maxY=53860 maxZ=2047 resX=200000 resY=200000  tilt=enabled
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (II) XINPUT: Adding extended input device "Wacom Cintiq 22HD Pen eraser" (type: ERASER, id 23)
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: (accel) keeping acceleration scheme 1
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: (accel) acceleration profile 0
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: (accel) acceleration factor: 2.000
Apr 15 06:34:21 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: (accel) acceleration threshold: 4
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) config/udev: Adding input device Wacom Cintiq 22HD Pen (/dev/input/event9)
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen: Applying InputClass "libinput tablet catchall"
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen: Applying InputClass "Wacom USB tablet class"
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen: Applying InputClass "Wacom tablet class"
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) LoadModule: "wacom"
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Module wacom: vendor="X.Org Foundation"
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) wacom: Driver for Wacom graphics tablets: PenPartner, Graphire,
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Using input driver 'wacom' for 'Wacom Cintiq 22HD Pen'
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen: always reports core events
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pen: type not specified, assuming 'stylus'.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pen: other types will be automatically added.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (--) Wacom Cintiq 22HD Pen stylus: using pressure threshold of 851 for button 1
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (--) Wacom Cintiq 22HD Pen stylus: maxX=95440 maxY=53860 maxZ=2047 resX=200000 resY=200000  tilt=enabled
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pen stylus: hotplugging dependent devices.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pen stylus: Invalid type 'cursor' for this device.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pen stylus: Invalid type 'touch' for this device.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pen stylus: Invalid type 'pad' for this device.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pen stylus: hotplugging completed.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) XINPUT: Adding extended input device "Wacom Cintiq 22HD Pen stylus" (type: STYLUS, id 12)
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen stylus: (accel) keeping acceleration scheme 1
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen stylus: (accel) acceleration profile 0
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen stylus: (accel) acceleration factor: 2.000
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen stylus: (accel) acceleration threshold: 4
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) config/udev: Adding input device Wacom Cintiq 22HD Pen (/dev/input/mouse2)
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) config/udev: Adding input device Wacom Cintiq 22HD Pad (/dev/input/event10)
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad: Applying InputClass "libinput keyboard catchall"
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad: Applying InputClass "libinput tablet catchall"
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad: Applying InputClass "Wacom USB tablet class"
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad: Applying InputClass "Wacom tablet class"
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Using input driver 'wacom' for 'Wacom Cintiq 22HD Pad'
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad: always reports core events
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad: Invalid type 'stylus' for this device.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad: Invalid type 'eraser' for this device.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad: Invalid type 'cursor' for this device.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad: Invalid type 'touch' for this device.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pad: type not specified, assuming 'pad'.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pad: other types will be automatically added.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pad pad: hotplugging dependent devices.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad pad: Invalid type 'stylus' for this device.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad pad: Invalid type 'eraser' for this device.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad pad: Invalid type 'cursor' for this device.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (EE) Wacom Cintiq 22HD Pad pad: Invalid type 'touch' for this device.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Wacom Cintiq 22HD Pad pad: hotplugging completed.
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) XINPUT: Adding extended input device "Wacom Cintiq 22HD Pad pad" (type: PAD, id 13)
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad pad: (accel) keeping acceleration scheme 1
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad pad: (accel) acceleration profile 0
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad pad: (accel) acceleration factor: 2.000
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pad pad: (accel) acceleration threshold: 4
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) config/udev: Adding input device Wacom Cintiq 22HD Pad (/dev/input/js0)
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: Applying InputClass "libinput tablet catchall"
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: Applying InputClass "Wacom USB tablet class"
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: Applying InputClass "Wacom tablet class"
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) Using input driver 'wacom' for 'Wacom Cintiq 22HD Pen eraser'
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: always reports core events
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (--) Wacom Cintiq 22HD Pen eraser: maxX=95440 maxY=53860 maxZ=2047 resX=200000 resY=200000  tilt=enabled
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (II) XINPUT: Adding extended input device "Wacom Cintiq 22HD Pen eraser" (type: ERASER, id 23)
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: (accel) keeping acceleration scheme 1
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: (accel) acceleration profile 0
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: (accel) acceleration factor: 2.000
Apr 15 06:34:31 DAX /usr/lib/gdm3/gdm-x-session: (**) Wacom Cintiq 22HD Pen eraser: (accel) acceleration threshold: 4

I guess I have missed something obvious somewhere but I don't see anything I could try. I would be happy about any hints where to look further.

I have the following script to define the button mappings of my Wacom Intuos S 2: /usr/local/bin/wacom_intuos_s_2_pad_button_mapping.sh

#!/bin/bash

export DISPLAY=:0
export XAUTHORITY=/home/scriptim/.Xauthority
/usr/bin/sleep 1 # wait for device to be ready
/usr/bin/xsetwacom set 'Wacom Intuos S 2 Pad pad' Button 1 'key -'
/usr/bin/xsetwacom set 'Wacom Intuos S 2 Pad pad' Button 3 'key +'
/usr/bin/xsetwacom set 'Wacom Intuos S 2 Pad pad' Button 8 'key +Ctrl z -Ctrl'
/usr/bin/xsetwacom set 'Wacom Intuos S 2 Pad pad' Button 9 'key +Ctrl +Shift z -Ctrl -Shift'

This script works fine if I run it manually. My goal is to run this script automatically whenever the pad is plugged in. I tried that with the following udev rule: /etc/udev/rules.d/10-wacom_intuos_s_2_pad.rules

ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="033b", RUN+="/usr/local/bin/wacom_intuos_s_2_pad_button_mapping.sh"

**However, the script does not map the buttons if I plug in the pad.** --- Im running Arch Linux (5.5.10-arch1-1)

$ lsusb
...
Bus 004 Device 015: ID 056a:033b Wacom Co., Ltd CTL-490 [Intuos Draw (S)]
...

$ udevadm info -a -n hidraw0
...
  looking at parent device '/devices/pci0000:00/0000:00:10.0/usb4/4-2':
    KERNELS=="4-2"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{authorized}=="1"
    ATTRS{bcdDevice}=="0100"
    ATTRS{bmAttributes}=="80"
    ATTRS{bMaxPower}=="498mA"
    ATTRS{manufacturer}=="Wacom Co.,Ltd."
    ATTRS{quirks}=="0x0"
    ATTRS{maxchild}=="0"
    ATTRS{bNumInterfaces}==" 3"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{devpath}=="2"
    ATTRS{ltm_capable}=="no"
    ATTRS{busnum}=="4"
    ATTRS{devnum}=="15"
    ATTRS{tx_lanes}=="1"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{speed}=="12"
    ATTRS{version}==" 2.00"
    ATTRS{product}=="Intuos PS"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{idVendor}=="056a"
    ATTRS{configuration}==""
    ATTRS{devspec}=="(null)"
    ATTRS{urbnum}=="174"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{removable}=="unknown"
    ATTRS{rx_lanes}=="1"
    ATTRS{idProduct}=="033b"
...

$ udevadm test --action="add" /devices/pci0000:00/0000:00:10.0/usb4/4-2
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

Load module index
Parsed configuration file /usr/lib/systemd/network/99-default.link
Created link configuration context.
Reading rules file: /usr/lib/udev/rules.d/10-dm.rules
Reading rules file: /etc/udev/rules.d/10-wacom_intuos_s_2_pad.rules
...
Reading rules file: /usr/lib/udev/rules.d/65-libwacom.rules
...
Reading rules file: /usr/lib/udev/rules.d/wacom.rules
Invalid inotify descriptor.
DEVPATH=/devices/pci0000:00/0000:00:10.0/usb4/4-2
DEVNAME=/dev/bus/usb/004/015
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=56a/33b/100
TYPE=0/0/0
BUSNUM=004
DEVNUM=015
MAJOR=189
MINOR=398
ACTION=add
SUBSYSTEM=usb
ID_VENDOR=Wacom_Co._Ltd.
ID_VENDOR_ENC=Wacom\x20Co.\x2cLtd.
ID_VENDOR_ID=056a
ID_MODEL=Intuos_PS
ID_MODEL_ENC=Intuos\x20PS
ID_MODEL_ID=033b
ID_REVISION=0100
ID_SERIAL=Wacom_Co._Ltd._Intuos_PS
ID_BUS=usb
ID_USB_INTERFACES=:030000:030102:
ID_VENDOR_FROM_DATABASE=Wacom Co., Ltd
ID_MODEL_FROM_DATABASE=CTL-490 [Intuos Draw (S)]
ID_PATH=pci-0000:00:10.0-usb-0:2
ID_PATH_TAG=pci-0000_00_10_0-usb-0_2
USEC_INITIALIZED=4102997566
run: '/usr/local/bin/wacom_intuos_s_2_pad_button_mapping.sh'
Unload module index
Unloaded link configuration context.

$ journalctl -xe
Mar 22 17:38:55 scriptim systemd-udevd: 1-1: Process '/usr/local/bin/wacom_intuos_s_2_pad_button_mapping.sh' failed with exit code 255.

Hello, I received this device as pictured some years ago, but was never able to figure out what drivers to use for it. My computer does not have the AT connector or serial port, but I do have a serial-USB adapter, as well as an AT keyboard connector-ps/2 adapter. If I plug in the serial to USB adapter part, linux detects the *adapter* and creates an entry for /dev/ttyUSB0, but the LED on the device does not light up. If I plug in the ps/2 connector with a ps/2 purple (keyboard) to USB adapter, the LED lights up, but if the AT K/B-USB is not plugged in, no device entry is created. I tried doing cat /dev/ttyUSB0 but that produces no output when clicking on the pen's buttons or scribbling with it on the pad. So how do I get this device to work in linux? I would love to use it to do simple drawing in gimp for example. I figure it is a pad designed specifically to generate Chinese characters, not really for drawing, but that shouldn't make a difference (though maybe it helps as a clue for someone to figure this out). Searching for "sunflower tablet" or other combinations yielded no success or even clues. And no, I don't read Chinese. Thanks in advance for any help.

I'm facing a really odd issue with a Wacom STU-530 device on Ubuntu 16.04. If I connect the tablet in any port it will start as USB 1.1 (really slow) because it loads the driver: **ohci-pci** [ 230.708046] usb 4-1: new full-speed USB device number 3 using ohci-pci [ 230.883203] usb 4-1: New USB device found, idVendor=056a, idProduct=00a5 [ 230.883217] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 230.883226] usb 4-1: Product: STU-530 [ 230.883234] usb 4-1: Manufacturer: Wacom Co.,Ltd. [ 230.883242] usb 4-1: SerialNumber: 8LZQ000683 [ 230.896179] input: Wacom Co.,Ltd. STU-530 Pen as /devices/pci0000:00/0000:00:12.0/usb4/4-1/4-1:1.0/0003:056A:00A5.0009/input/input20 [ 230.896691] wacom 0003:056A:00A5.0009: hidraw2: USB HID v1.10 Device [Wacom Co.,Ltd. STU-530] on usb-0000:00:12.0-1/input0 But if I instead connect a (really cheap usb hub) and then the tablet into the usb hub, the correct driver **ehci-pci** is configured and the tablet runs at usb 2.0: [ 335.120117] usb 1-1.1: new full-speed USB device number 5 using ehci-pci [ 335.214488] usb 1-1.1: New USB device found, idVendor=056a, idProduct=00a5 [ 335.214501] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 335.214511] usb 1-1.1: Product: STU-530 [ 335.214519] usb 1-1.1: Manufacturer: Wacom Co.,Ltd. [ 335.214527] usb 1-1.1: SerialNumber: 8LZQ000683 [ 335.221870] input: Wacom Co.,Ltd. STU-530 Pen as /devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1.1/1-1.1:1.0/0003:056A:00A5.000A/input/input23 [ 335.222255] wacom 0003:056A:00A5.000A: hidraw2: USB HID v1.10 Device [Wacom Co.,Ltd. STU-530] on usb-0000:00:12.2-1.1/input0 Is there a way to force the usage of ehci-pci when I connect the tablet? Maybe using udev? PD: The device runs at 2.0 in other computers without problem. > ADDITIONAL INFORMATION: I'm executing the DemoButtons (Java) from the Wacom's SDK . It just open a window and let me interact with the tablet. Cases: 1) If I connect directly the tablet to the "PC" the software won't work, will end with error LIBUSB -99 Error. 2) If I connect the tablet through the cheap USB 2.0 HUB the software will run without problems. 3) The computer has (2/two) USB 3.0 ports, I've repeated the first two tests on them and the tablet only will work if the hub is in the middle. When connecting the tablet to the 3.0 port the BUS Class = root_hub with driver xhci_hcd will handle the device but the driver will be usbhid / 12M (so the device is still USB 1.1). I've already fixed the Wacom's software by changing an internal timeout of LIBUSB_BULK_TRANSFER so the software will run correctly no matter if the tablet is connected directly or through the hub. The thing is, I would need to find a way to understand why the device is running slower in this hardware since from 3000 computers only in ~350 this error appears, all of them are the same model, same version, same vendor, same O.S (like clones). Maybe is something related to an specific chiptset or low quality usb chipset? All the info from hwinfo, lsusb, lsusb -t are the same in the computers (compared by vimdiff). > WHAT I KNOW: - libusb_bulk_transfer is running slower (for some unknown reason) - The O.S is handling the device as USB 1.1 when it clearly works as 2.0 - In about 3,000 PC's with same HW/SW this error only will be present in about ~350. (Same bios versions/same O.S and software installed). Regards. M.

Just updated my PC from the last LTS Ubuntu distro to 18.04LTS, and the stylus on my Wacom Wireless Bamboo tablet immediately lost all button function. The system seems to be tracking the stylus itself, as moving it over the pad causes the cursor to move around the screen, but touching the stylus to the pad and/or clicking the button on the stylus body gets no response. The touchpad function on the tablet itself, on the other hand, responds to finger drags and taps as cursor movement and clicks, respectively. The A/B buttons at the foot of the tablet do not respond, same as the stylus buttons. Deets as follows: **Tablet Model:** Wacom Bamboo Pad (Wireless), CTH-300/K **System:** Ubuntu 18.04.1 LTS, 64-bit **Devices > Wacom Tablet:** Displays "No stylus found / Please move your stylus to the proximity of the tablet to configure it" and doesn't respond to stylus cursor movement in that area. Tablet > Wacom Bamboo Pad Wireless > Tracking Mode is "Tablet (absolute)". Trying to use "Map Buttons..." to set the A/B tablet buttons doesn't work; they display on screen for mapping but don't respond to being pressed. **libwacom-list-local-devices:** *One point I noticed:* Libwacom lists the tablet stylus as 0xfffff;0xffffe, which are the codes for a default standard stylus and a stylus with an eraser. The stylus for the Bamboo Pad doesn't have an eraser or a rocker button, and should be set as type 0xffffd. Not sure if this means it's related to this bug or not. [Device] Name=Wacom Bamboo Pad Wireless DeviceMatch=usb:056a:0319; Class=Bamboo Width=4 Height=3 IntegratedIn= Layout=bamboo-pad.svg Styli=0xfffff;0xffffe; [Features] Reversible=false Stylus=true Ring=false Ring2=false Touch=true TouchSwitch=false StatusLEDs= NumStrips=0 Buttons=2 [Buttons] Left= Right= Top= Bottom=A;B; Touchstrip= Touchstrip2= OLEDs= Ring= Ring2= EvdevCodes=0x110;0x111; RingNumModes=0 Ring2NumModes=0 StripsNumModes=0 --------------------------------------------------------------- [Device] Name=Wacom Bamboo Pad Wireless DeviceMatch=usb:056a:0319; Class=Bamboo Width=4 Height=3 IntegratedIn= Layout=bamboo-pad.svg Styli=0xfffff;0xffffe; [Features] Reversible=false Stylus=true Ring=false Ring2=false Touch=true TouchSwitch=false StatusLEDs= NumStrips=0 Buttons=2 [Buttons] Left= Right= Top= Bottom=A;B; Touchstrip= Touchstrip2= OLEDs= Ring= Ring2= EvdevCodes=0x110;0x111; RingNumModes=0 Ring2NumModes=0 StripsNumModes=0 --------------------------------------------------------------- **xinput --list:** *Also lists an eraser that isn't there* ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® 2.4GHz Transceiver v7.0 id=9 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® 2.4GHz Transceiver v7.0 id=10 [slave pointer (2)] ⎜ ↳ Wacom Wireless Bamboo PAD Pen stylus id=11 [slave pointer (2)] ⎜ ↳ Wacom Wireless Bamboo PAD Finger touch id=15 [slave pointer (2)] ⎜ ↳ Wacom Wireless Bamboo PAD Pen eraser id=12 [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)] ↳ Microsoft Microsoft® 2.4GHz Transceiver v7.0 id=8 [slave keyboard (3)] ↳ Microsoft Microsoft® 2.4GHz Transceiver v7.0 id=13 [slave keyboard (3)] ↳ Microsoft Microsoft® 2.4GHz Transceiver v7.0 id=14 [slave keyboard (3)] **xinput props:** *Noted that there are far more buttons listed than the stylus actually has.* /usr/share/libwacom$ xinput --list-props "Wacom Wireless Bamboo PAD Pen stylus" Device 'Wacom Wireless Bamboo PAD Pen stylus': Device Enabled (139): 1 Coordinate Transformation Matrix (141): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 Device Accel Profile (270): 0 Device Accel Constant Deceleration (271): 1.000000 Device Accel Adaptive Deceleration (272): 1.000000 Device Accel Velocity Scaling (273): 10.000000 Device Node (262): "/dev/input/event5" Wacom Tablet Area (299): 0, 0, 10690, 6680 Wacom Rotation (300): 0 Wacom Pressurecurve (301): 0, 0, 100, 100 Wacom Serial IDs (302): 793, 1, 2, 0, 0 Wacom Serial ID binding (303): 0 Wacom Pressure Threshold (304): 26 Wacom Sample and Suppress (305): 2, 4 Wacom Enable Touch (306): 1 Wacom Hover Click (307): 1 Wacom Enable Touch Gesture (308): 0 Wacom Touch Gesture Parameters (309): 0, 0, 250 Wacom Tool Type (310): "STYLUS" (292) Wacom Button Actions (311): "Wacom button action 0" (312), "Wacom button action 1" (313), "Wacom button action 2" (314), "None" (0), "None" (0), "None" (0), "None" (0), "Wacom button action 3" (315) Wacom button action 0 (312): 1572865 Wacom button action 1 (313): 1572866 Wacom button action 2 (314): 1572867 Wacom button action 3 (315): 1572872 Wacom Pressure Recalibration (316): 1 Wacom Panscroll Threshold (317): 1209 Device Product ID (263): 1386, 793 Wacom Debug Levels (318): 0, 0 **xinput test "Wacom Wireless Bamboo PAD Pen stylus":** *Pen movement:* motion a=7676 a[1] =3667 a[2] =0 a=0 a=0 a=-900 motion a=7663 a[1] =3660 a[2] =0 a=0 a=0 a=-900 motion a=7656 a[1] =3650 a[2] =0 a=0 a=0 a=-900 motion a=7657 a[1] =3642 a[2] =0 a=0 a=0 a=-900 motion a=7669 a[1] =3637 a[2] =0 a=0 a=0 a=-900 motion a=7688 a[1] =3635 a[2] =0 a=0 a=0 a=-900 (etc.) *Pen "click"/touch:* motion a=7658 a[1] =3641 a[2] =31164 a=0 a=0 a=-900 *Pen button click:* No noticeable response ----------------- If anyone has any ideas on how to proceed, I'd appreciate it. I'd like to try to remove the extra button mapping, reassign libwacom's styli code for the tablet, and/or find out exactly what the button action codes correspond to, but I'm having difficulty finding information on how to do any of that. (And I'd rather not kill what little functionality I still have.) I've also had issues with assigning persistent settings to this tablet in the past , though I'm not sure if that has anything to do with what's going on now.

I currently use a Dell Latitude 7350. As I'm a teacher, I want to record myself when correcting exercices or tests. I think it's more interesting than a plain typesetted corrected document : I can *say* things I would not write otherwise, and pupils cand more easily perceive the paths one mind should follow in order to answer questions in the most efficient way. But I have two major flaws, with my Dell - whose screen is tactile and supports an active stylus : - the software I use is not palm detection ready (I use Xournal to annotate by hand the PDF documents containing exercices and tests). I bought graphic designer's gloves, but two of them put one over the other are not sufficient to prevent palm detection ; - I cannot record my voice : the embedded microphone records as well hit sounds from the stylus - that are very annoying - and the jack for external headset with microphone is absolutely not handled by any kernel from Ubuntu 16.04 to 18.04. I asked a question for this peculiar problem, with absolutely no success : https://askubuntu.com/questions/1166866/sound-recording-issue-with-at-least-all-ubuntu-version-since-16-04-and-broadwe . I also Recently, I was given a Fujitsu Lifebook T4215 - an old Tablet PC running under Windows XP. It also has a stylus, but the screen is not tactile : it comes with integrated Wacom technology, especially a passive stylus. I installed Debian 10 with LXDE, in order to cope with the old Core Duo T7200 and 2 GB of RAM. Everything is fine, the sytlus is well handled by the system... but I cannot write with it as it is detected as far as 1 cm from the screen ! So writings are completely invaded by parasitic traits : reading them is at least unbearable. I'm going to think I'm cursed. Does anyone has an idea for, say, setting the detection distance for the stylus, or forcing contact with the screen before reacting to any action of the stylus ? Thanks in advance...

I have a udev rule 80-wacom.rules

SUBSYSTEM=="usb", ACTION=="add", RUN+="/usr/local/bin/wacom.sh"

My understanding is that it will run wacom.sh whenever any USB device is plugged in. I verified that it was indeed triggering by logging the time of execution in a file.

#!/bin/bash

    /usr/bin/date >> /tmp/udev.log;
    /usr/bin/xsetwacom set /usr/bin/xsetwacom --list |grep -i stylus |awk {'print $6'} MapToOutput HEAD-0;
    /usr/bin/xsetwacom set /usr/bin/xsetwacom --list |grep -i eraser |awk {'print $6'} MapToOutput HEAD-0

I have verified that it is writing the timestamp to the log file whenever a device is plugged in, but the crucial other two lines of code are not executing. When I execute the script directly, the timestamp appears in the log file, and the other two lines of code execute as expected. So the udev rule runs. The script runs. But the script as run by the udev rule does not perform as expected. I have tried adding a delay at the start of the script, but this does not resolve the issue. I am at my wit's end. Any insight would be enormously appreciated.

Say I have the following setup: - Linux Kernel - input-wacom kernel driver - xf86-input-wacom X11 driver - Wacom tablet How is input latency distributed among these various components? Are there any bottlenecks? If one wanted to make software patches to reduce latency (even by a couple of milliseconds), which parts of the "pipeline" should one look at first?

I recently got an ThinkPad X1 Yoga (3rd generation) with an integrated stylus. Debian Buster (10 RC1) is installed. I'm using the Cinnamon desktop environment. The stylus works nicely as a generic pointing device, but it seems the pressure sensitivity of the stylus is not detected. I enabled the stylus/eraser devices in Gimp to test. But in tutorials there sometimes seems to be a pressure device as well. There is no pressure device listed for me. In Xournal, if I set the program to recognize pressure, the text looks a bit different, but I am not sure if it is actually using the pressure sensitivity. What can be done to fix or at least further debug this problem?

I have a ThinkPad Yoga 370 with an active AES stylus. I run the latest Arch Linux-based Manjaro 4.14.48-2-MANJARO. To get the pen to work in e.g. xournal I installed libinput 1.11.0-1 and xf86-input-wacom 0.36.1-1 and the pen works now. However my problem comes undeterministically after some time using it. When I write, at some point driver issues arise, where when I move the pen close to the display, an event is triggered that moves the mouse pointer according to where the pen is, without the pen touching the display. This is normal behaviour. The problem is that on the instance this pen is in range event is fired, for some reason a pen touched the display event is fired instead, so that a click is issued. When I hover over a button that button is pressed, when I hover over my document in xournal a dot is drawn. Repeatedly moving the pen to and from the display makes the problem go away for a while, but it always returns.