Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mouse device is auto-detected / Ability to exclude specific devices #67

Open
Rapha149 opened this issue Nov 24, 2024 · 0 comments
Open

Comments

@Rapha149
Copy link

I have the prolbem that mouseless detects my mouse as a keyboard device and for some reason I can't use my mouse while mouseless is running because of that. For now my temporary solution is to just specify all my keyboard devices but I would want mouseless to work immediately when I connect a new keyboard.

I can think of two possible solutions for this problem:

  1. Fix the auto-detection system so the mouse doesn't get detected.
  2. Add the ability to exclude specific devices in the configuration.

If it helps, here is the debug log regarding the auto-detection of keyboard devices. My mouse is /dev/input/event8: Logitech G502:

DEBU[15:44:35.743] Auto detected keyboard devices:              
DEBU[15:44:35.743] - /dev/input/event0: AT Translated Set 2 keyboard 
DEBU[15:44:35.743] - /dev/input/event6: Cherry GmbH CHERRY Corded Device 
DEBU[15:44:35.743] - /dev/input/event8: Logitech G502           
DEBU[15:44:35.743] - /dev/input/event9: Logitech Candy          
DEBU[15:44:36.159] opening the keyboard device /dev/input/event0 
DEBU[15:44:36.159] opening the keyboard device /dev/input/event8 
DEBU[15:44:36.159] opening the keyboard device /dev/input/event9 
DEBU[15:44:36.159] InputDevice /dev/input/event0 (fd 33)
  name AT Translated Set 2 keyboard
  phys isa0060/serio0/input0
  bus 0x0011, vendor 0x0001, product 0x0001, version 0xab83
  events EV_SYN 0, EV_KEY 1, EV_MSC 4, EV_LED 17 
DEBU[15:44:36.159] Device name: AT Translated Set 2 keyboard    
DEBU[15:44:36.159] Evdev protocol version: 65537                
DEBU[15:44:36.159] Device info: bus 0x0011, vendor 0x0001, product 0x0001, version 0xab83 
DEBU[15:44:36.159] InputDevice /dev/input/event9 (fd 35)
  name Logitech Candy
  phys usb-0000:0b:00.0-1.7.4/input2:7
  bus 0x0003, vendor 0x046d, product 0x405f, version 0x0111
  events EV_KEY 1, EV_MSC 4, EV_LED 17, EV_SYN 0 
DEBU[15:44:36.160] Device name: Logitech Candy                  
DEBU[15:44:36.160] Evdev protocol version: 65537                
DEBU[15:44:36.160] Device info: bus 0x0003, vendor 0x046d, product 0x405f, version 0x0111 
DEBU[15:44:36.159] opening the keyboard device /dev/input/event6 
DEBU[15:44:36.159] InputDevice /dev/input/event8 (fd 34)
  name Logitech G502
  phys usb-0000:0b:00.0-1.7.4/input2:1
  bus 0x0003, vendor 0x046d, product 0x407f, version 0x0111
  events EV_MSC 4, EV_LED 17, EV_SYN 0, EV_KEY 1, EV_REL 2, EV_ABS 3 
DEBU[15:44:36.160] Device name: Logitech G502                   
DEBU[15:44:36.160] Evdev protocol version: 65537                
DEBU[15:44:36.160] InputDevice /dev/input/event6 (fd 36)
  name Cherry GmbH CHERRY Corded Device
  phys usb-0000:0b:00.0-1.7.3/input0
  bus 0x0003, vendor 0x046a, product 0xc098, version 0x0111
  events EV_MSC 4, EV_LED 17, EV_SYN 0, EV_KEY 1 
DEBU[15:44:36.160] Device name: Cherry GmbH CHERRY Corded Device
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant