Martin: That worked. I ran through the questions in the application,
restarted and the keyboard is working again at login.
output of xprop -root |grep NAMES.S
_XKB_RULES_NAMES(STRING) = "evdev", "apple_laptop", "us", "", ""
output of grep ^X /etc/default/console-setup
XKBMODEL="apple_laptop"
XKBL
Matt Griffin [2010-04-05 16:29 -]:
> output of grep ^X /etc/default/console-setup
> XKBMODEL="SKIP"
OK, thanks. This seems wrong, "SKIP" is not a valid keyboard layout.
To confirm that this is really the root problem, can you please do
sudo dpkg-reconfigure console-setup
to reset the mode
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
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
output of xprop -root |grep NAMES.S
_XKB_RULES_NAMES(STRING) = "evdev", "SKIP", "us", "", ""
output of grep ^X /etc/default/console-setup
XKBMODEL="SKIP"
XKBLAYOUT="us"
XKBVARIANT="U.S. English"
XKBOPTIONS=""
output of udevadm info --export-db|grep LAYOUT|sort -u
E: XKBLAYOUT=us
--
keyboard inp
** Changed in: gdm (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) => Martin Pitt
(pitti)
--
keyboard input broken at gnome login prompt after package updates
https://bugs.launchpad.net/bugs/548891
You received this bug notification because you are a member of Ubuntu
Desk
dlotton [2010-04-01 18:55 -]:
> _XKB_RULES_NAMES(STRING) = "evdev", "SKIP", "us", "",
> "terminate:ctrl_alt_bksp"
Ah! This was also confirmed by Charles Redman. The "SKIP" here
definitively looks fishy. It ought to be "pc105" or something
similar, unless "SKIP" is a real keyboard model used b
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
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
I just recently connected the dots, everyone who's having issues with the
onscreen keyboard, this is your problem.
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/526791
--
keyboard input broken at gnome login prompt after package updates
https://bugs.launchpad.net/bugs/548891
You receive
I have the same problem after updates on the latest VMware player on Win
7 64 and on the latest VMware fusion on Snow Leopard. Initial beta
install worked fine but updates killed the keyboard for the login
screen. I was able to use the on-screen keyboard to login after
enabling it and rebooting.
I've looked into it a bit, but could not reproduce under this
configuration:
VMware Player version 3.0.1 build-227600
Host is 64-bit Lucid system up to date as of today
Guest is 64-bit Lucid system up to date as of today
Tried both with and without VMware Tools installed.
VMware Tools version 8.1
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
Both my XP host and my Ubuntu guest are 32-bit. (As already noted,
keyboard doesn't work at login or in KDE, but works in Gnome is you use
the on-screen keyboard to log in.)
--
keyboard input broken at gnome login prompt after package updates
https://bugs.launchpad.net/bugs/548891
You received
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
I'm the guy who got the onscreen keyboard to work by waiting.
I'm using a Win7 x64 host, and an Ubuntu 10.4 x86 guest.
I don't believe that it was the waiting around specifically which made
the on-screen keyboard work, rather that having come back to it, it had
stopped freaking out, so...
Also,
One further note to the developer,
I did not specify in my original post that I was using 64-bit Ubuntu as
the guest OS and XP 32-bit as the host OS.
VMWare Player 3.0.1 build-227600
Host OS: Windows XP SP3 (32-bit)
Guest OS: Ubuntu 10.04 Beta (64-bit), Kernel 2.6.32-17-generic
It may be helpfu
I have the same problem here (Host: Windows XP, Guest, Ubuntu 10.04
beta, updated to latest as of 4/2/10). The keyboard doesn't work at all
at the login screen, but the mouse works fine. I can access the on-
screen keyboard to log in. If I log into KDE, the keyboard still
doesn't work at all.
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
Charles,
There's a user in a forum at the link below that had similar behavior
regarding the on-screen keyboard not working. This user said the on-
screen keyboard would come up, then close immediately. If they left it
alone for 15 minutes after boot, then they can get the on-screen
keyboard to
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
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_
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
* keyboard layout:
I have to be logged in via the on-screen keyboard in order to do the
Ctrl+Alt+F1. After logging in and Ctrl+Alt+F1 to get the terminal
screen I logged in and executed the requested 'sudo DISPLAY=:0 xprop
-root |grep NAMES.S' command. Here is the output:
_XKB_RULES_NAMES(STRI
Thanks. I see some potential problems here:
* keyboard layout:
- Can you please do Ctrl+Alt+F1, login, and give me the output of
sudo DISPLAY=:0 xprop -root |grep NAMES.S
* plymouth (splash screen):
- Does the keyboard start to work if you press Ctrl+Alt+F1 and then go back
to gdm w
Oops, I missed part of your first set of questions.
The 'caps lock' and 'num lock' keys do not appear to do anything while
at the Ubuntu login screen. The indicator LEDs do not respond to
pressing the respective keys.
--
keyboard input broken at gnome login prompt after package updates
https://
After getting logged in there are no issues at all with the keyboard. I only
see the problem at the login screen.
1) The keyboard does not appear to react at all to key presses at the Ubuntu
login screen.
2) I cannot Ctrl+Alt+F1 to get to a console when booted to the login screen
3) During
I use kvm extensively with lucid, and have so such problem, so I need
more information to see in which part of the stack the problem is.
What do you mean exactly with "the keyboard does no longer work"? It
does not react at all to key presses, it has the wrong layout and thus
entering your passwor
It looks like this bug is affecting many vmware users -
http://swiss.ubuntuforums.org/showthread.php?p=9056673
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)
--
keyboard input broken at gnome login prompt after package updates
https://b
** Package changed: ubuntu => gdm (Ubuntu)
--
keyboard input broken at gnome login prompt after package updates
https://bugs.launchpad.net/bugs/548891
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailin
30 matches
Mail list logo
