[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates

2010-04-05 Thread Charles Redman
The previous post was for a working machine with no updates installed. With updates installed and no longer working, the above becomes: xprop -root |grep NAMES.S _XKB_RULES_NAMES(STRING) = "evdev", "SKIP", "gb,us", "mac,", "" grep ^X /etc/default/console-setup XKBMODEL="SKIP" XKBLAYOUT="us" XKBVAR

[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates

2010-04-05 Thread Charles Redman
xprop -root |grep NAMES.S _XKB_RULES_NAMES(STRING) = "evdev", "macbook79", "gb,us", "mac,", "" grep ^X /etc/default/console-setup XKBMODEL="macbook79" XKBLAYOUT="gb" XKBVARIANT="mac" XKBOPTIONS="" udevadm info --export-db|grep LAYOUT|sort -u E: XKBLAYOUT=gb -- keyboard input broken at gnome

[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates

2010-04-05 Thread Charles Redman
This is definitely a problem with the guest not detecting the keyboard mappings or saving them. For some reason it insists on using American layout settings even if i log in an apply them system wide. The only way i can use my machine at this point in time is to set it to AutoLogin and then i am f

[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates

2010-04-05 Thread Charles Redman
After a little more research and VM building, this is what i find. I can reproduce this problem with Ubuntu as guest on the following operating systems. Ubuntu Karmic 64-bit Mac OSX Snow Leopard Windows XP Windows 7 VMWare ESXi 4.0 For the most part, the problem is identical. Everything works wi

[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates

2010-04-02 Thread Charles Redman
I have attached the Xorg logs from both the working and non-working VM's. There seems to be some issue with xkb creating xkm files at the end of the machine that is not working. ** Attachment added: "Xorg.log.tar.gz" http://launchpadlibrarian.net/42928275/Xorg.log.tar.gz -- keyboard input br

[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates

2010-04-02 Thread Charles Redman
My none-working setup is as follows: VMWare Fusion 3.0.2 build-232780 Host OS: Mac OSX 10.6.3 (32/64bit) Guest OS: Ubuntu 10.04 Beta (64-bit), Kernel Ubuntu 2.6.32-19.28-generic I have setup a second VM should anyone wish to check the differences, with a standard install of 10.04 beta1, no updat

[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates

2010-04-02 Thread Charles Redman
Thanks for that, i did read the thread beforehand, which was how i found this bug report. However i am not one of the lucky few that seems to have option of a onscreen keyboard to get me by. The best i can do is ssh. I may try something like nomachine to get me by for now. -- keyboard input broke

[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates

2010-04-02 Thread Charles Redman
Additionally when i run: setxkbmap gb Cannot open display "default display" or setxkbmap of any form i get this error message. I am running this from a ssh session. Attached is my dmesg output just incase. ** Attachment added: "Dmesg output from VM" http://launchpadlibrarian.net/42888764/dm

[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates

2010-04-02 Thread Charles Redman
Ok, i rebuilt the VM as it only takes about 10mins to recreate. I ran the following before the update: sudo DISPLAY=:0 xprop -root |grep NAMES.S _XKB_RULES_NAMES(STRING) = "evdev", "SKIP", "gb,us", "mac,", "" and then again after the update: sudo DISPLAY=:0 xprop -root |grep NAMES.S _XKB_RULES_

[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates

2010-04-01 Thread Charles Redman
Just to add to your woes and to add a bit of diversity. I would like to point out that this does not only apply to Ubuntu as VM on a Windows host. I have exactly the same problem with Lucid, running under VM Fusion on Mac OSX. Interestingly, i only built this machine today and only had this proble