Environment
- OS: Bazzite Linux
- Device: Razer Tartarus Pro
- OpenTartarus: (latest git build)
Description
When OpenTartarus is running, the Tartarus Pro scroll wheel stops working for both the desktop and other input remapping applications.
The keypad buttons continue to function normally, but the scroll wheel produces no usable events outside of OpenTartarus.
Expected behavior
The scroll wheel should continue to emit its events (or have them forwarded by OpenTartarus) so that:
- Desktop scrolling continues to work.
- Applications such as
input-remapper can detect and remap the scroll wheel.
evtest can observe the wheel events.
Actual behavior
As soon as OpenTartarus starts:
- The physical Tartarus device is grabbed exclusively.
evtest reports:
This device is grabbed by another process.
input-remapper no longer detects scroll wheel movement.- Desktop scrolling with the Tartarus wheel no longer works.
When OpenTartarus is closed:
- The scroll wheel immediately starts working again.
- Desktop scrolling is restored.
input-remapper can once again detect the wheel.
Additional information
The Tartarus exposes multiple input devices. The keyboard interface advertises both:
KEY_SCROLLUPKEY_SCROLLDOWN
However, while OpenTartarus is running, those events appear to be intercepted and are not forwarded to the virtual input device.
It appears that OpenTartarus is grabbing the physical device but is not forwarding the scroll wheel events, making the wheel unusable while the application is active.
If this is intentional, it would be useful to have an option to pass through or remap the scroll wheel in the same way as the other inputs.
Environment
Description
When OpenTartarus is running, the Tartarus Pro scroll wheel stops working for both the desktop and other input remapping applications.
The keypad buttons continue to function normally, but the scroll wheel produces no usable events outside of OpenTartarus.
Expected behavior
The scroll wheel should continue to emit its events (or have them forwarded by OpenTartarus) so that:
input-remappercan detect and remap the scroll wheel.evtestcan observe the wheel events.Actual behavior
As soon as OpenTartarus starts:
evtestreports:input-remapperno longer detects scroll wheel movement.When OpenTartarus is closed:
input-remappercan once again detect the wheel.Additional information
The Tartarus exposes multiple input devices. The keyboard interface advertises both:
KEY_SCROLLUPKEY_SCROLLDOWNHowever, while OpenTartarus is running, those events appear to be intercepted and are not forwarded to the virtual input device.
It appears that OpenTartarus is grabbing the physical device but is not forwarding the scroll wheel events, making the wheel unusable while the application is active.
If this is intentional, it would be useful to have an option to pass through or remap the scroll wheel in the same way as the other inputs.