Comment 4 for bug 133658

My primary machines are on gutsy gibbon, so no problem testing on that.

I just tried your capslock/numlock idea, and they behave exactly the same as if I pressed any other key (well, except the fn key I guess). This is on a laptop, so for the numlock I had to use an external keyboard to type the lettered password, and for caps lock I actually activated it before suspending, so when I unsuspended the capslock deactivated when I first pressed it; and then I could type in the password without problems.

So, in short, it seems the system needs some kind of first keyboard stroke to "wake" the keyboard, no matter what that stroke is; however, if it's capslock/numlock, that first stroke will ALSO activate/deactivate caps/numlock.

Any idea where the root of the problem might lie?