Problems with binding Express keys on the CTL-480 pad

[TonyFlury]

• Device name:

• Device model identifier:

• libwacom version: 2.2.0-1

• Ubuntu 22.04 LTS

• I understand that libwacom does affect whether the device works (see Troubleshooting)

I am trying to bind the 4 Xpress Keys on the Wacom tablet - the stylus works fine.

Using libinput-tools debug-events I can confirm that the express keys respond as keys 0 to 3 going clock wise from the lower left button - Lower left is 0, Upper Left is 1, Upper right is 2, lower right is 3.

xsetwacom says that Button 0 for that pad is not a valid button number.
xsetwacom set "Wacom Intuos S Pad pad" Button 0 "key 0" '0' is not a valid button number.
I don't know the relationship between the button numbers reported by libinput-tools and used by xsetwacom.

The tablet appears in the Ubuntu control panel, but mapping the buttons doesn't work at all correctly.

The layout is displayed correctly.
Clicking the upper left (button 1) results in the Upper right being configured (sometimes).
Clicking the bottom left (button 0) does nothing.
Clicking the Top right (button 2) does nothing.
Clicking the Bottom right (button 3) seems to work as expected.

I am not sure whether this is a numbering mismatch or something else

I am happy to provide further information and assist with debuging as neccessary.

[TonyFlury]

a second note - trying to use xsetwacom to set the key bindings :

• Binding Button 1, actually changes button 0 (as defined by libinput-tools) - bottom left.
• Binding Button 2 on xsetwacom appears to do nothing
• Binding button 3 on xsetwacom actually sets button 1 as defined by libinput tools - top left
• Binding button 4 on xsetwacom appears to do nothing.

[github-actions]

Hi, there. I'm a bot and have been asked to have a look at this.

libwacom is a bunch of text files with a C API, and the information in those text files
is static fixed information that we cannot get from the device (e.g. the model name or which
button will produce which event code). It does not affect functionality directly, if the
tablet does not work this is either an issue with the kernel drivers, xf86-input-wacom
(if using X) or libinput/the desktop environment (if using Wayland). Please file the
issue with the component that most likely applies.

See also https://github.com/linuxwacom/libwacom/wiki/Troubleshooting
See also https://github.com/linuxwacom/libwacom/wiki/Adding-a-new-device

---

This is an automated comment created by a bot. Responding to the bot or mentioning it won't have any effect.

[TonyFlury]

Thank you bot for replying to this without any explanation of why the library doesn't work as expected.

It would be nice to get some effective support - if the problem with recognising and mapping the buttons on the control panel isn't in libwacom, where is it ?

[whot]

mutter for the functionality, GNOME Settings for the GUI, or the equivalent components in other DEs.

for X the button mapping is handled in the xf86-input-wacom driver but if you're using that driver libinput is not in the picture (and the xf86-input-wacom driver doesn't use libwacom either).

the .tablet file for the device may need an EvdevCodes entry to map to the right codes (see libinput record for the codes sent) - once those are set the GUI tools should work correctly if they parse the libwacom tablet files.

xsetwacom only knows about the xf86-input-wacom driver, so it should be in line with whatever mapping is assigned by that (can't remember the details, unfortunately).