FS#72157 - ShuttlePRO V2 buttons not recognized anymore

Attached to Project: Arch Linux
Opened by Dirk (dsohler) - Friday, 17 September 2021, 05:52 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 19 September 2021, 08:24 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After one of the recent updates I noticed that my previously working (since 2018) ShuttlePRO V2 jog dial for video editing does not work anymore (jog dials scroll but none of the buttons are recognized).

# grep "ShuttlePRO" /var/log/Xorg.0.log
[ 13.315] (II) config/udev: Adding input device Contour Design ShuttlePRO v2 (/dev/input/event9)
[ 13.315] (**) Contour Design ShuttlePRO v2: Applying InputClass "evdev keyboard catchall"
[ 13.315] (**) Contour Design ShuttlePRO v2: Applying InputClass "libinput keyboard catchall"
[ 13.315] (II) Using input driver 'libinput' for 'Contour Design ShuttlePRO v2'
[ 13.370] (**) Contour Design ShuttlePRO v2: always reports core events
[ 13.371] (II) event9 - Contour Design ShuttlePRO v2: is tagged by udev as: Keyboard
[ 13.371] (II) event9 - Contour Design ShuttlePRO v2: device is a keyboard
[ 13.371] (II) event9 - Contour Design ShuttlePRO v2: device removed
[ 13.371] (II) libinput: Contour Design ShuttlePRO v2: needs a virtual subdevice
[ 13.371] (II) XINPUT: Adding extended input device "Contour Design ShuttlePRO v2" (type: MOUSE, id 15)
[ 13.371] (**) Contour Design ShuttlePRO v2: (accel) selected scheme none/0
[ 13.371] (**) Contour Design ShuttlePRO v2: (accel) acceleration factor: 2.000
[ 13.371] (**) Contour Design ShuttlePRO v2: (accel) acceleration threshold: 4
[ 13.372] (II) event9 - Contour Design ShuttlePRO v2: is tagged by udev as: Keyboard
[ 13.372] (II) event9 - Contour Design ShuttlePRO v2: device is a keyboard
[ 13.384] (**) Contour Design ShuttlePRO v2: Applying InputClass "evdev keyboard catchall"
[ 13.384] (**) Contour Design ShuttlePRO v2: Applying InputClass "libinput keyboard catchall"
[ 13.384] (II) Using input driver 'libinput' for 'Contour Design ShuttlePRO v2'
[ 13.384] (**) Contour Design ShuttlePRO v2: always reports core events
[ 13.384] (II) libinput: Contour Design ShuttlePRO v2: is a virtual subdevice
[ 13.384] (II) XINPUT: Adding extended input device "Contour Design ShuttlePRO v2" (type: KEYBOARD, id 17)

Also, the ShuttlePRO V2 jog dial has 15 buttons and 2 dials. evtest shows only those events being supported, so all button events are missing:

Event type 0 (EV_SYN)
Event type 2 (EV_REL)
Event code 7 (REL_DIAL)
Event code 8 (REL_WHEEL)
Event code 11 (REL_WHEEL_HI_RES)


Additional info:

Attached screenshot shows the configuration in Kdenlive. I also created an issue for Kdenlive but I don’t really think that’s a Kdenlive issue.

* https://bugs.kde.org/show_bug.cgi?id=442338


Involved libraries and applications:

* xorg-server 1.20.13-2
* libevdev 1.11.0-1
* xf86-input-evdev 2.10.6-2
* xf86-input-libinput 1.1.0-1
* kdenlive 21.08.1-1

$ uname -rms
Linux 5.14.5-arch1-1 x86_64

$ lsusb | grep Shuttle
Bus 005 Device 002: ID 0b33:0030 Contour Design, Inc. ShuttlePro v2

$ lsusb | grep Controller
Bus 006 Device 004: ID 045e:028e Microsoft Corp. Xbox360 Controller

$ cat /etc/udev/rules.d/99-ShuttlePRO.rules
ATTRS{name}=="Contour Design ShuttlePRO v2" MODE="0644"


Steps to reproduce:

1. run pacman -Syu
2. Plug in a ShuttlePRO V2
3. Try using the buttons
   config.png (170.7 KiB)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 19 September 2021, 08:24 GMT
Reason for closing:  None
Additional comments about closing:  use IRC and forum for generic support or do the suggested downgrade
Comment by Andreas Radke (AndyRTR) - Saturday, 18 September 2021, 09:13 GMT
Please find out what package breaks it. We had libinput and kernel updates and probably more. Downgrade one by one and check again.
Comment by Dirk (dsohler) - Saturday, 18 September 2021, 14:34 GMT
So you mean I should individually downgrade hundreds of packages one by one on a production machine?

I’d also be happy with a configuration option that allows me to set manually up the button associations.