2.1.0 currupts keyboard settings after install guest addons

[abcuser]

Hi,
I have installed VirtualBox 2.1.0 on Windows XP SP3 host and Ubuntu 8.10 as guest.

Keyboard (non-US) is working OK on host and on guest before upgrading to 2.1.0 from 2.0.6 version. But after installing Guest Additions keyboard is working properly on host, but on Ubuntu US-keyboard is working despite my local language keyboard settings in guest.

I have remove guest additions by using info from this forum:

Code: Select all   Expand viewCollapse view

sudo find /etc -name "*vboxadd*" -exec rm {} \;
sudo find /etc -name "*vboxvfs*" -exec rm {} \;
sudo rm -r /usr/src/vboxadd-*
sudo rm -r /usr/src/vboxvfs-*
sudo rm /usr/sbin/vboxadd-timesync
sudo rm /lib/modules/`uname -r`/misc/vboxadd.ko
sudo rm /lib/modules/`uname -r`/misc/vboxvfs.ko

and after guest reboot my local language keyboard in guest is working again.

I reinstalled guest additions and US-keyboard reappeared again.
So it looks like a bug in guest additions.

Does anyone have the same problem? Is there any work-around?
Thanks

EDIT: I have reported a bug to: http://www.virtualbox.org/ticket/2793

[fixedwheel]

Hi,

Does anyone have the same problem? Is there any work-around?

found a thread in linux guests Ubuntu 8.10 on Vista : AZERTY to QUERTY (VirtualBox 2.1.0)

with 2.0.6 GA the keyboard worked ok for me on 2.1.0 host

[FeroS]

My host is WinXP and guest OS is Ubuntu 8.04.
After installing VirtualBox 2.1.0 and VBLinuxAdditions I cannot login to Ubuntu. I cannot type "e" and "n" characters. Unfortunately "e" is in my name
I have to boot with older kernel and with "repaired" X server. After this clear step I can type "e" and "n" characters and log in the Ubuntu. But now VBLinuxAddition does not work .

[Sasquatch]

There is a known issue with the GA breaking the keyboard layout on Linux Guests. It defaults to the US layout (qwerty). So either don't install the GA, or remind yourself that you must type on a US keyboard layout.

[abcuser]

Hi,
I have solved the problem. Work-around solution is described in bug report site:
http://www.virtualbox.org/ticket/2793#comment:5
Regards