based on my past experience, it usualy happen because plasma* related config mess up.just remove or (better) renaming this files.~/.kde4/share/config/plasma-desktop-appletsrc~/.kde4/share/config/plasma-desktoprc~/.kde4/share/config/plasma-windowed-appletsrc~/.kde4/share/config/plasmarcsome files maybe dont exist on your box, just ignore it.
Intenta eliminar estas carpetas, haciendo antes copia de seguridad:.kde4/share/apps/amarok.kde4/share/config/amarok-appletsrc.kde4/share/config/amarok_homerc.kde4/share/config/amarokrc Todas están en tu directorio personal (/home/tu usuario). Luego desinstala Amarok y vuelve a instalarlo.
I've been experiencing a strange problem with Plasma locking up. Running system monitor it shows the KDE4 process using 20% CPU time, and Plasma around 10-15%. This seems way too much since on my six year old Laptop the cpu load of both processes is barely noticeable.
I got a request to also add the kwin-script of a package I maintain in the CCR.This is the first PKGBUILD .install file I wrote and the first time I work with kwin's API, so please tell me if I made errors or if I can release that to the public.After some rtfm, I figured out how to do it but I found no info how to activate a kwin-script in the commandline.I ended up doing it with sed:cp $HOME
When I installed Chakra about a month ago, I left my old ~/.kde4 config files from my previous installation (KDE 4.8.x on openSUSE) in place, thinking migrating from KDE 4.8.x to 4.8.x (it might even have been the same release; don't remember) was not a big thing and KDE could use the existing configuration.The result on log-in was a new ".kde4/share-new" directory with some applica
Ok I have been searching the forums trying to find a similar issue and have not been able to find the answer to my situation.
I was going to try a different plasma desktop downloaded the file and let yast2 do the work. Afterwards I did some messing around with the desktop. Sadly I realized I was in root when I did this instead of doing it through the cli as su.