LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Mandriva (https://www.linuxquestions.org/questions/mandriva-30/)
-   -   Keyboard not responding in KDE (https://www.linuxquestions.org/questions/mandriva-30/keyboard-not-responding-in-kde-502200/)

nvargas 11-16-2006 08:40 AM

Keyboard not responding in KDE
 
I'm running Mandriva 2007 and my keyboard stopped responding in KDE. I log in, everything normal, type username and passwd, mouse works fine, my keyboard doesn't.

Right now I'm running on IceWM, and my keyboard runs just fine, so I know this must be KDE related.

Any help or hints will be INMENSELY appreciated.

nvargas 11-16-2006 10:29 AM

Don't know where I read this, but I moved my .kde directory to .kdeold and let KDE create a new profile. Now my keyboard is working, but have no title bars...

nvargas 11-16-2006 11:06 AM

Ok, now it is really getting weird. I read elsewhere in this site to run kwin to restore the title bars, and now I don't get title bars nor keyboard.

Plus, I get this error:

Quote:

QFont::setPointSize: Point size <= 0 (-3)
KWin: No window decoration plugin library was found.
KWin will now exit...
Suggestions?

rickst29 12-12-2006 01:28 AM

I had the same problem today, SOLUTION FOUND!
 
Sorry to here that KDE's "reconstruction" of your .kde Directory Tree messed things up.

If you've still got that .kde_old, do the following:

(1) Make an entirely new UserID (in MCC), and then log into it using a KDE Session. KDE does things on the *FIRST* session which it failed to do when you simply moved your old .kde (kde keeps some things about specific Users within /var, and this apparently messed up your hopeful re-initialization).

(2) Within IceWM, or from a SU Root Session within your NEW UserID: Restore your OLD $HOME/.kde Tree (ALL of it!).

(3) Still working as Root, copy just four files from the NEW UserID's ./kde/share/config into the broken UserID's ./kde/share/config:

kdeglobals
khotkeysrc
kickerrc
kwinrulesrc

Even just the /config Directory contains hundreds of files, but ONE OF THESE FOUR files is responsible. (Probably only one-- but when I had the problem, I searched for files within .kde/share/config which contained the string 'keyb' and got only these 4 files, so I replaced them all. Then I logged in as the 'broken' UID, with a KDE Session, and:

My previously busted KDE is now :D :D :D

And by the way, replacing kickerrc didn't destroy my previously created and very complicated panels, they were preserved.

(4) If you don't need it anymore, destroy the new UserID (and it's group) from MCC.


All times are GMT -5. The time now is 11:39 PM.