[Bug 59616] Re: keyboard not working after logging in via gdm due toslow keys feature being accidentally enabled

2010-03-19 Thread Lars Kruse
*** This bug is a duplicate of bug 41427 *** https://bugs.launchpad.net/bugs/41427 I had this issue with my keyboard not working, and I read this bug report and thought that this was it - but no! Although it gave me some clues. What happenden to me was that NUMLOCK was turned on (!!!) the

[Bug 59616] Re: keyboard not working after logging in via gdm due toslow keys feature being accidentally enabled

2008-07-28 Thread kko
*** This bug is a duplicate of bug 41427 *** https://bugs.launchpad.net/bugs/41427 ** This bug has been marked a duplicate of bug 41427 slow keys can turn on surreptitiously cause confusion. -- keyboard not working after logging in via gdm due toslow keys feature being accidentally

[Bug 59616] Re: keyboard not working after logging in via gdm due toslow keys feature being accidentally enabled

2008-06-03 Thread Juri Pakaste
Bryce: I suppose it's plausible the slow keys feature was the reason, although I as I said in the original report, this was related to playing with upstart/sysvinit. I'm pretty certain I didn't visit the slow keys dialog box, but at this point, three Ubuntu releases later, I can't really confirm

[Bug 59616] Re: keyboard not working after logging in via gdm due toslow keys feature being accidentally enabled

2008-05-28 Thread Martin von Wittich
I just tried it again, and I think I've found the underlying issue. As I disabled the option 'Keyboard Preferences' - 'Allow to turn accessibility features on and off from the keyboard', I had to reactivate this to test it. As I now know, the required action is to hold SHIFT for 8 seconds to

[Bug 59616] Re: keyboard not working after logging in via gdm due toslow keys feature being accidentally enabled

2008-05-24 Thread Bryce Harrington
Thanks Miguel, Martin, and ethanay for identifying and confirming the problem is with the slow keys accessibility feature; I've updated the title. @Juri, if you're still tracking this bug it would be helpful if you concur with this analysis. Could someone propose what the next step should be for