Comment 3 for bug 1247668

@Sebastian:

I firmly disagree with setting "Importance: Low".

Sure you might say that geez if pressing a key did something else, you can just undo that action, press some magic sequence of keys, and you're okay. No security problem, no data loss (actually I'm not even sure about these)...

But for me, this is a bug that's causing a constant high amount of stress. I mean, I hit this once a couple of minutes, each time adding a little bit of frustration for not being able to use the most basic input device that I'm using all the time.

Heck, ever since I started using computers, which was the ZX Spectrum almost 30 years ago, through DOS and Windows 95 and other Windowses, and my first Slackware Linux with kernel 2.0 in 1996, sometimes using other non-Linux Unices too, now for the first time ever we've reached a point where certain keys on the keyboard, under certain circumstances, fail to do the only thing that they need to do: emit the correct symbol.

If pressing 'A' would, 1 out of 100 times, insert a 'B' instead of 'A', would you say it's "low" because you can backspace and type it again? I'd say it's critical.

I've learned touch typing a long time ago, I'm often looking at a piece of paper of something like that when typing, knowing that the computer does what I'm telling it to do. It's unacceptable if, for the first time ever after using computers for 30 years, I need to verify on the screen that each keypress does indeed what it needs to do.

I'd say if, with the NumLock turned on, trying to insert a digit '7' moves the cursor Home instead, it's CRITICAL. It's the very essential of every computer that the keys need to do what they are intended to do, no exceptions, no excuses!