keyboard sometimes not working after resume

[Martin Emrich]

After suspend and resume, sometimes the keyboard in X does not work. the mouse does work fine, but I cannot enter my password to unlock the screen. Switching VTs does not help either, I have to restart X using Ctrl-Alt-BS.

Running gutsy i386 on a Thinkpad T41p.

Ciao

Martin

[Id2ndR (id2ndr)]

Same trouble (Gutsy release).

I don't see the cursor on the password field. Actually I press enter (without entering password) until I can get the cursor in the field.
When doing this, and after unlocking the display, I saw the gnome-keyring dialog than promp my password to get the wireless key. (This is an other bug since NetworkManager seems to be already connected because I can see the 2 green rounds).

[Martin Emrich (emme)]

Hmm, that could be the cause here, too, as I often use WPA-protected wireless networks. I'll try your method next time it happens.

Ciao

Martin

[Martin Emrich (emme)]

It just happened, and your workaround worked: I hit enter to satisfy the keyring dialog that stole the focus from the unlock dialog, and then it worked again.

Ciao

Martin

[Id2ndR (id2ndr)]

I reported bug #155373 about NM. The trouble of focus is linked to it but is not the same trouble.

[Martin Emrich (emme)]

This is certainly not xserver-xorg-input-keyboard's fault.

[Markus Kienast (elias1884)]

I have seen this too on certain laptops!! Hereby confirm this bug. I'll check if this is still the case in Gutsy.

This bug would also benefit from resolving bug #3382.

[Markus Kienast (elias1884)]

As this bug seems to be hardware related I would say, this bug would also benefit from resolving bug #3382.

Please add your comment to the bug report if you feel this would be a good thing to solve.

[Id2ndR (id2ndr)]

I don't think this bug is hardware related. I don't remember having trouble in feisty.

[Markus Kienast (elias1884)]

On Sun, 2007-10-28 at 17:59 +0000, Id2ndR wrote:
> I don't think this bug is hardware related. I don't remember having
> trouble in feisty.
>
I had this trouble in Feisty, but only on certain Hardware. It was a
Fujitsu Siemens Laptop. Unfortunately, I don't have access to it right
now.

It is the Laptop of a friend that I setup. He is not the kind of user,
that believes he gets anything out of reporting bugs, unfortunately. So
I report his. The problem I am having now is, that if anybody would ask
me to attache hardware information to the bug, I could not. I see the
guy only every once in a while.

So what I am advocating is incorporating a feature into launchpad that
allows me to attache hardware profiles to my launchpad account of all
machines I am maintaining. So if one of my friends reports a bug to me
which happens to be hardware specific, I can easily attache the
necessary information to the bug report without having to have access to
the machine.

I would love a process, where I can use a tool to collect all hardware
information for a specific machine at once and attache it to my profile.
I would do that every time, I setup a machine for any of my friends. And
when they report a bug to me, I report it to launchpad and can simply
say, this happens on machine XY, query my profile for details.

[Id2ndR (id2ndr)]

I'm marking this bug as duplicate of bug #145123. I haven't encountred the trouble since this other bug was fixed.
As any comment if you still experiment this bug.