Suse/NovellThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
The Problem...
When starting KDE, just before the bouncing gear comes on, all keyboards go dead, but just for one user.
The History...
I have been using Open SuSE 11.1 since last Xmass. Last Friday it worked fine. Monday, no keyboard!?
The Experiments...
Used mouse to reboot--No good.
Plug in 2nd keyboard to USB--No good.
Boot to SuSE 10.3--OK.
Boot to SuSE 11.1 run level 3--OK
Start kde as root--OK
Create new user "test" and log in to kde--OK
Start kde as me while pressing Caps Lock furiously--Caps Lock light on and off furiously on both keyboards till the bouncing gear comes on, then nothing, what so ever. Like they are not plugged in.
hmm...bad user config? why!? Where?!!
Exit via mouse.
In tty, do "ls -lR | grep '2009-06-26' > last_changed_files.txt". Not quite 900 lines. Umph
The Question...
How do I find what is wrong and make it right?
I have solved my own problem. I turns out KDE has a "slow key" mode that is activated when the shift key is held down for more than 10 seconds. Holding the shift key down another 10 seconds reactivate the keyboard.
This appears to be some kind of "feature" that has been tripping people up for some years.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.