#2347 closed defect (fixed)
keyboard layout problem under ubuntu intrepid
| Reported by: | nemolivier | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 2.0.2 |
| Keywords: | keyboard layout | Cc: | |
| Guest type: | other | Host type: | other |
Description
Hello, I have a problem with my keybord, instead of azerty, it produce on the first line : ge:q In the log I can see :
Failed to recognize the keyboard mapping or to guess it based on 00:00:36.804 the keyboard layout.
under ubuntu intrepid-ibex.
I had this problem under ubuntu hardy with virtual box 1.5:3, the 2.0.2 from other sources solved it.
Testing intrepid ibex (i totally removed the old virtual box package and use the one from intrepid) the problem came back. My keyboard is a Typematrix 2030 ps2. Work well under linux. I tried with another keybord and solve the problem (but I way prefer my true ergonomic keyboard).
I tried to change the keyboard settings from « evdev » to « PC104 keys » or « generic ACPI » with no results.
Same with other keyboard but I find a « trick » : I unpluged/repluged the keyboard, edev don’t recognise it and it works (but i loose my french settings in gnome !).
So I don’t know if it’s an ubuntu bug or a virtual box one…
Regards.
Attachments (2)
Change History (11)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Of course, I am aventurous, so I compiled it and put the VBoxKeybord.so in /usr/lib/virtualbox/ I don’t know if works because one stroke kill the VM :D
Anyways the fact that when I « force » gnome (xorg ?) not to setup the layout it works.
comment:3 by , 16 years ago
nemolivier like me uses a new Dvorak based layout known as "French Bépo" (http://download.tuxfamily.org/dvorak/xkb/fr-dvorak-bepo-xkb-1.0rc2.tgz). I also had the same problem with VirtualBox 1.5.6 and I upgraded to 2.0.6 and my problem is gone (but the log still complains that it doesn't know of the keyboard mapping).
It is also probably a duplicate of #2052. I'm using debian sid with xorg 7.4 from Debian experimental and external Azerty keyboard. It looks like the guesses are better in this version if it can't identify the keyboard mapping.
comment:4 by , 16 years ago
VirtualBox currently uses two different heuristics to guess the keyboard layout, and will print information to the log if either of them fail. However, if this layout is not very widespread, it is probably not worth adding it to the software. Did I understand correctly that this issue is now resolved apart from the message in the log?
comment:5 by , 16 years ago
Well, the layout is gaining momentum but it's clearly a very small minority in France that is using it right now.
For me this issue is resolved in 2.0.6 but I don't know why. How does he fallback to Azerty if he can only see my Bépo layout? Or does it analyze the alternate layouts too?
comment:6 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
When keys on the keyboard are pressed, they send keycodes which do not depend on the current layout. The only problem for VirtualBox is to work out which X11 keycodes correspond to which keys (this is not set in stone). We have two methods for doing this, one of which involves looking at the keyboard layout, and which will fail if we don't know the layout. The guest system only sees PC scan codes, and has no idea about the host layout.
comment:7 by , 16 years ago
Hi there -- I'm seeing this problem with VirtualBox 2.1.0 under Intrepid; in a RHEL 5.2 guest, all the keys are scrambled. according to xorg I'm using:
(II) XINPUT: Adding extended input device "Microsoft Natural? Ergonomic Keyboard 4000"
(type: KEYBOARD)
() Option "xkb_rules" "evdev" () Microsoft Natural? Ergonomic Keyboard 4000: xkb_rules: "evdev" () Option "xkb_model" "pc105" () Microsoft Natural? Ergonomic Keyboard 4000: xkb_model: "pc105" () Option "xkb_layout" "ie" () Microsoft Natural? Ergonomic Keyboard 4000: xkb_layout: "ie" () Option "xkb_options" "lv3:ralt_switch" () Microsoft Natural? Ergonomic Keyboard 4000: xkb_options: "lv3:ralt_switch" () Microsoft Natural? Ergonomic Keyboard 4000: YAxisMapping: buttons 4 and 5 () Microsoft Natural? Ergonomic Keyboard 4000: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
Any suggestions? Since I already remap my keyboard to a US mapping using xmodmap after starting my session, I don't really need to use the "ie" XKB layout. if I change that, would it help?
This is almost certainly due to a bug which slipped into 2.0.2. If you are feeling adventurous, you can rebuild the VirtualBox keyboard handler (sources of the current version attached) and replace the one you have installed with the new version.