SlackwareThis Forum is for the discussion of Slackware 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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
While working, at random times, the keyboard just disappears. No way to type anything in, no cursor. Only the mouse keeps working.
The way I deal with it now is ending the KDE session (with the mouse) and starting a new KDE session.
I haven't been able to associate it with specific actions. It seems to happen randomly (or at least I haven't found any event linked to it).
(a) low power supply that suddenly turns keyboard off
(b) electromagnetic interference
(c) bad keyboard wires
(d) bad connection to the PS/2 socket
(e) bad motherboard or bad keyboard controller
(f) bad keyboard in general
Do "dmesg | tail" to know what actually happened when the keyboard hangs (of course after the keyboard functions back).
Or just create a script with the following code in it so that you can just click it with the mouse. Save this to a script with executable flags set and put it in the desktop or anywhere the mouse can reach.
Code:
#!/bin/sh
dmesg | tail
read
Last edited by konsolebox; 07-21-2009 at 11:31 PM.
Reason: added a suggestion
Thank you, konsolebox. I'm starting to rule out some of the causes:
(a) low power supply that suddenly turns keyboard off: I have a UPS. Not even a flicker.
(b) electromagnetic interference
(c) bad keyboard wires
(d) bad connection : Checked. All fine. Plus, it consistently gets fixed after reboot or on new X session.
(e) bad motherboard or bad keyboard controller
(f) bad keyboard in general
As for the log, I didn't see anything out of the ordinary before my initial post, but I'll run the script as you recommend.
Strange, this just began happening to me the other day as well.
I can still switch VT's and kill X, but I cannot use keyboard shortcuts or type into any text box. Switching to an empty VT and killing off lingering kde processes will let me log back in, but it is irritating. This doesn't happen with OpenBox on the same machine.
I don't know if you've figured it out yet, xri, but on my system, issuing a kill -9 on the pid of kded4 will restore use of the keyboard minus the keybindings. Of course I have to switch to a VT in order to do this, but upon switching back I can resume 'normal' work.
Thank you, konsolebox. I'm starting to rule out some of the causes:
(a) low power supply that suddenly turns keyboard off: I have a UPS. Not even a flicker.
No what I mean is the internal power supplies from the Power Supply Unit. External current won't really affect it since most PSUs contain large capacitors.
Sounds like a software issue then. I take it you don't see anything in /var/log/Xorg.0.log? Just to verify, it's not a wireless keyboard, is it? If you want to cheat, maybe try running a live CD from another distro and see if you have the same problem. If it works properly see what's different in your xorg.conf files and tweak your Slackware one accordingly.
I'm giving closure to this thread.
The keyboard freezing consistently occurs while using rdesktop with one particular service I use, when I inadvertently press the Shift or the Ctrl key while working in that program.
I deactivated all the slow keys and sticky keys activation on Kcontrol. After that, I've never experienced this problem again with my keyboard.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.