| Summary: | Bluetooth keyboard is configured as mouse with wrong layout | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Cedric Sodhi <manday> | ||||
| Component: | Input/evdev | Assignee: | Peter Hutterer <peter.hutterer> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> | ||||
| Severity: | normal | ||||||
| Priority: | medium | ||||||
| Version: | unspecified | ||||||
| Hardware: | Other | ||||||
| OS: | All | ||||||
| Whiteboard: | 2011BRB_Reviewed | ||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
Just a quick idea: Wouldn't it solve all of those problems alltogether if EvDev had an option which allowed us to *explicitly* specify as which type (mouse, touchscreen, touchpad, keyboard) a device should be configured? Then we don't have to rely on possibly ambiguous information based upon the mere capabilities any longer. This is a mass change of bugs. Bugs assigned to me that haven't been updated in the last 3 years are closed as WONTFIX, because, well, let's at least be honest about it. Please do not re-open unless you have a really good reason to do so (e.g. you're fixing it yourself). If it hasn't been fixed in the last 3 years, it probably won't be fixed anytime soon either. Sorry. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 53134 [details] Xorg log of the two events, starting X and attaching USB kbd Attached you the Xorg.0.log for the following problem: A bluetooth keyboard (Microsoft Bluetooth Mobile Keyboard 6000) is paired and works fine in TTY. X.org is started. The keyboard layout is english. An USB keyboard is attached, too. The layout of *both* keyboards becomes german, as it is configured in the InputClass section. As you can see in the log, there is some strange things going on with the keyboard being configured as both, a mouse and a keyboard. Is this perhaps the same problem that the eGalax had? That evdev is blindly trying to derive the type of hardware from the capabilities it shows in udev, respectively that udev cannot report a "real type" but only capabilities? Just as an idea.