Hi all,

The strangest thing just happened to me this morning. My keyboard just died on me when starting up KDE. I always boot in the shell and run startx from there. Yesterday everything was working great, participating in a huge newbie thread, and this morning couldn't type a thing in KDE.

So I got my other laptop which runs Slackware also, started up and got searching on LinuxQuestions for a solution, which I found quite fast. Although it's only like a 'bypass'. I renamed the .kde to .kdebackup, started X and got the nice working standard KDE without all the customization I had done. To me that's not that important, got it all fixed in the new 'environment'.

But I'd like to know from you guys if this is a known bug in KDE and if there is a patch for it so that this doesn't happen like every other two months.

Kind regards,

Eric

It could be due to hald not starting properly.

I could use the keyboard in console mode without a problem, the issue only arose when starting KDE. I rebooted four times, always with the same problem. When I moved the .kde directory all worked fine. Moving the backup back over the newly created gave me the same result.

So, as stated in another thread here on LQ it must have something to do with files or permissions changing all of a sudden. And that is in my opinion quite troublesome, that gets me worried

Kind regards,

Eric

Could be all that two finger typing you've been doing!

Jeeeh Skippy, you caught me !!

You've obviously not been following my HOWTO properly.

Hi,

I'll bet that you are using a non-US Keyboard.
You could try using a policy for your device;

Still learning and studying oh wise one

Hello onebuck,

Of course I'm using a non-US keyboard, I'm using a belgian azerty one and on other computers a spanish querty. I'll look into the policy thingy. Thanks a lot. What troubles me however is why it has been working for like an entire month without problems and all of a sudden fails on me. Could that have to do with an update?

Kind regards,

Eric

Hi,

Not always obvious that a non-us user will use a non-US keyboard.
I noticed your local but worded it because of the reference text.

Anything could be happening. I think the policy would insure that 'Hal' is not the issue for the kybd.

Hi onebuck,

You're right, it's not always obvious and you are correct stating it out. I put the policy in place and am waiting if this happens again. It's not that big of an issue but more of an annoyance. It's easy to repair but I'm just that kind of guy that wants to know why something happens even if I can resolve it in an easy way.

Thanks again for your pointer, it's much appreciated.

Kind regards,

Eric

Hi,

Intermittent problems can be a real pain!

It can be fun to trouble shoot but hitting that brick wall can sometimes enlighten one to the way as to solve the issue(s). Hard failures are always easier to fix.

Tell me about it, I have to work with Windows servers whole day long at the job. Talking about intermittent problems, Windows comes with a lot of them . Trying to include a W2003 server with Tomcat in a High Availability / Load Balancing cluster, that's a pain in the ass.