[lucid] USB Keyboard not working (ie unable to input anything) in X

[Rafal-maj-it]

Keyboard does not work in X, after upgrade from 9.10 to 10.04.

All works, but the keyboard and mouse are 100% frozen (even capslock does nothing).
Computer works otherwise (via ssh and so on),
Sysrq+R (raw keyboard) allows to go back to ctrl+alt+f1 VT1 and then computer works.

Nothing special in dmesg or anything.

Confirmed on amd64 pc box by me.
On a laptop - identical problem, but after few reboots (different types) finally it worked.

Partial workaround: perhaps few reboots might help.
Other reporters (at http://ubuntuforums.org/showthread.php?t=1485671) say it might work if you wait few minutes.

[Ed (classicmacintosh)]

I am affected (but only the keyboard is broken, the mouse works 100%) in 32-bit Ubuntu 10.04 on a MacBookPro5,5

My fix is to add modprobe usbhid to /etc/init.d/gdm ( yes I know it's ugly but hey, it works! )

If anyone wants any more information (maybe dmesg, lsusb, lspci -vv, etc...) then just ask.

[Ed (classicmacintosh)]

Personally I think this bug should be critical as is directly prevents users from using Ubuntu.

[saiky (saiky-liu)]

I face same problem after upgrading to 10.04, any way to solve?

[Jorge Moraleda (jorge-moraleda)]

Confirmed on AMD-64 for me.

[Ed (classicmacintosh)]

I'm working on a temporary fix as I type this... so check back soon and a fix should be posted.

[Raphael Jolivet (raphael-jolivet)]

Same here.
I can ssh my system, but no mouse/keyboard.
Either from udb mouse/kb or PS2 ones.

I found this in the log of Xorg:

(II) config/udev: Adding input device Power Button (FF) (/dev/event0)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Power Button (CM) (/dev/event1)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Logitech USB Receiver (/dev/event4)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Logitech USB Receiver (/dev/event5)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Logitech USB Receiver (/dev/mouse1)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/event3)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Macintosh mouse button emulation (/dev/event2)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Macintosh mouse button emulation (/dev/mouse0)
(II) No input driver/identifier specified (ignoring)

Is it relevant ?

[mcelrath (bob+launchpad)]

This is a HAL problem. You can work around it by manually adding a keyboard section to your xorg.conf. and also adding 'Option "AutoAddDevices" "False"' to the "ServerFlags" section of your xorg.conf. Xorg/HAL will nuke the keyboard configuration you put in xorg.conf unless you add this option.

Unfortunately, adding this option means that xorg doesn't find my stylus (tablet pc), so I get either a stylus or a keyboard...

[Steve Schmechel (steveschmechel)]

I was running with Lucid successfully, but as of late June (after some Update Manager update) my USB keyboard would go dead after every logout (actually every time GDM restarts) until I unplug and re-plug in my keyboard.

It then works fine until, I logout again.

Has there been any progress on this issue?
Is it HAL-related or XOrg-related?
Has anyone come up with a work around?

[uxeng (listmail)]

Any updates on this issue?

I use `startx` and have a working keyboard in console outside of X. I'm getting similar messages in the Xorg log as shown in Raphael Jolivet's post. In an attempt to address this I generated a basic config using sudo X -configure and then had to add the Option "AutoAddDevices" "False" line to my xorg.conf before my mouse would work. My keyboard is still not working. I started out on Lucid beta and remember updating back in june after release and since then I can't use this install. I've also tried enabling Legacy USB support and dpkg-reconfigure console-setup (just in case).

[Ed (classicmacintosh)]

Is this problem fixed in 10.04.1 for everyone? It is for me.

Also everyone who can SSH into their box (if the problem is still there) can you get into a root prompt and type in modprobe usbhid and see if that fixes it.

I will try later and if it works for me will close the bug - does anyone else have the problem?

[Steve Schmechel (steveschmechel)]

I believe my problem had to do with a weird interaction of the "Assistive Technologies" propagated by one of my children messing with the settings available at the GDM login screen.

Interestingly, the problem would result with the keyboard going dead each time GDM restarted, but unplugging and reattaching the USB keyboard would cause things to work again.

I may file a bug on that, but I don't think I am affected by this bug.

Thank you for looking into this.

Steve

--- On Sun, 8/22/10, Ed <email address hidden> wrote:

> From: Ed <email address hidden>
> Subject: [Bug 582201] Re: [lucid] USB Keyboard not working (ie unable to input anything) in X
> To: <email address hidden>
> Date: Sunday, August 22, 2010, 4:56 AM
> Is this problem fixed in 10.04.1 for
> everyone? It is for me.
>
>
> Also everyone who can SSH into their box (if the problem is
> still there) can you get into a root prompt and type in
> modprobe usbhid and see if that fixes it.
>
> I will try later and if it works for me will close the bug
> - does anyone
> else have the problem?
>
> --
> [lucid] USB Keyboard not working (ie unable to input
> anything) in X
> https://bugs.launchpad.net/bugs/582201
> You received this bug notification because you are a direct
> subscriber
> of the bug.
>

[Mohamed Amine Ilidrissi (ilidrissi.amine)]

Since 2 reporters said the bug has been fixed for them, I'm marking this as Fix Released. Please re-open this if you're still affected by this bug.