The PC I wanted to have TC on is an old AMILO Mini Ui 3520 notebook, which has a faulty built-in keyboard. There are only two USB ports on it so to have an external mouse (for convenience) and a working keyboard, I bought a wireless keyboard-mouse combo USB dongle (Logitech K220). The problem
The keyboard part of the peripheral works without a problem, but the mouse has a weird issue. I can move the pointer and click on UI elements that expect a single-click interaction. However when I try to navigate the path selector dialog (where I have to double-click) it does not respond. It's like the second event is being dropped.
At first I ignored the problem and wanted to browse the filesystem in terminal, but after opening one I noticed that something is very wrong. If I click inside the terminal a question-mark character will appear. I guess some non-ASCII keyboard key event is fired along with the mouse event.Troubleshooting
- I tried using a generic wired USB mouse and keyboard and those work without a problem.
- I removed the batteries from the keyboard part, but the mouse still did not work as expected. (I wanted to rule out some stuck key or similar issue)
- The keyboard and mouse work perfectly on other PCs (Debian, Arch and Windows), so the hardware is not at fault.
- The touchpad works correctly regardless of the peripherals being connected or not.
- I have not found a report/question about an exactly same issue online, but I've tried a few things suggested for similar problems: legacy USB setting in BIOS, psmouse.proto=imps...
- I wanted to see what events X is processing, but there is no xev utility...
I've had my fair share of hardware compatibility issues using a variety of distors, but never have I expected to get stuck at a not working "basic" mouse. I don't know what or how to debug to get ahead.
I'm looking forward to hearing some insight or any ideas really.
Thanks in advance,