Bug 759754 - xinput can't use device names instead of device ID
Summary: xinput can't use device names instead of device ID
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-apps
Version: 16
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-03 16:04 UTC by Lothar Gesslein
Modified: 2012-07-24 02:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-24 02:11:44 UTC
Type: ---


Attachments (Terms of Use)

Description Lothar Gesslein 2011-12-03 16:04:33 UTC
User-Agent:       Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.9.168 Version/11.52

The Logitech Nano USB receiver registers itself as both an keyboard and a mouse device with the same name.

I want to remap some buttons on my mouse, but can't do that with xinput without having too look up the device ID manually. The device ID might change, and of course the device name is not unique so I can't use that either.

xinput does have support to use "keyboard:" or "pointer:" as a prefix to specify which device is meant, but this does not work with {get,set}-button-maps.





Reproducible: Always

Actual Results:  
$ xinput get-button-map "Logitech USB Receiver"
Warning: There are multiple devices named "Logitech USB Receiver".
To ensure the correct one is selected, please use the device ID instead.

Expected Results:  
I would like to do "xinput get-button-map "pointer:Logitech USB Receiver"". Prefixing works with "xinput list-props "pointer:Logitech USB Receiver"" for example, but not with get/set-button-maps.

Comment 1 Peter Hutterer 2012-04-09 23:27:04 UTC
missing feature in xinput since it seems to only support the pointer/keyboard prefixes for XI2 calls. Please file this bug upstream on https://bugs.freedesktop.org/enter_bug.cgi?product=xorg under the app/xinput component.


Note You need to log in before you can comment on or make changes to this bug.