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.
I just installed a new Slackware64 14.2 on 2 laptops a few days ago, and am using the "default" KDE desktop. On both computers, after some period of time, the keyboard totally hangs -- I can type nothing. The mouse still moves, but clicking on anything has no effect. I have to power down the computer or, if I am ssh'd in from some other computer I can `shutdown -r now`.
This kind of makes these systems unusable. Any idea what's up and how I can fix it?
mfoley,
Did you happen to verify your install medium by checking the md5sum?
The same symptoms on 2 different (they are different, yes?) machines suggests a problem with the software. Could be that the install medium was corrupt somehow.
mfoley,
Did you happen to verify your install medium by checking the md5sum?
The same symptoms on 2 different (they are different, yes?) machines suggests a problem with the software. Could be that the install medium was corrupt somehow.
I used the same backup tarfile to create the 2nd machine installation.
However ... I booted the 2nd machine and noticed that USB devices were not being found during the boot process -- boot delaying trying to communicate with USB. When the machine came up, no mouse/keyboard. I rebooted and same thing. So, I tried booting the Huge kernel instead of the generic. It's been 2 days with no problem and 8+ hours of constant use today on 2 screen will lots of windows open including Firefox, a few Konsole's and a WIN7 Virtual Machine. I'll give this another day or two, then I'll try rerunning mkinitrd and switch back to the generic kernel. I'll post results.
dijetlo: I don't believe I'm running the application as root. What makes you think I'm doing so?
Interestingly, I do have additional "X Error: BadWindow (invalid Window parameter) 3" errors in my ~/.xsession-errors file, but no mouse/keyboard hangs so far.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.