This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
it_services:problems [2014/06/12 09:55] florido [Very slow graphical interface on workstation] |
it_services:problems [2014/06/12 17:13] florido |
||
---|---|---|---|
Line 6: | Line 6: | ||
==== Disable Desktop Effects in KDE ==== | ==== Disable Desktop Effects in KDE ==== | ||
+ | |||
+ | - Click on the KDE icon and search for ''Desktop Effects'' | ||
+ | - Disable effects as in this picture: | ||
+ | {{http://mschlander.files.wordpress.com/2011/01/effects.png?w=720}} | ||
+ | |||
+ | The above picture belongs to this blog you might want to have a read: | ||
+ | http://mschlander.wordpress.com/2011/01/23/kde-is-slow-for-dummies/ | ||
==== NVIDIA video card issues ==== | ==== NVIDIA video card issues ==== | ||
Line 21: | Line 28: | ||
</code> | </code> | ||
+ | ===== System becomes unresponsive and crashes ===== | ||
+ | |||
+ | ==== Akonadi+nepomuk eating all CPU power and memory ==== | ||
+ | |||
+ | You can spot this if you login to a terminal and run ''top''. You'll see processes that contain ''akonadi'' in the name taking over 100% of all cores and memory. | ||
+ | |||
+ | To solve this problem, | ||
+ | - Login on terminal or ssh to any machine with your user. | ||
+ | - cd into your home folder, and run the following:<code bash> | ||
+ | rm -rf .local/share/akonadi | ||
+ | rm -rf .config/akonadi | ||
+ | rm .kde4/share/config/akonadi* | ||
+ | </code> | ||
+ | - logout and try to login graphically. Akonadi should not freak out | ||
+ | anymore. | ||
+ | |||
+ | ==== nfs4 mount problems ==== | ||
+ | |||
+ | Due to incompatibility trough versions on nfs4, if in the logs such an error appears: | ||
+ | <code io> | ||
+ | Jun 12 13:57:55 balder automount[3145]: umount_autofs_indirect: ask umount returned busy /nfs | ||
+ | </code> | ||
+ | |||
+ | then it seemed more stable to switch to nfs3. This is done in '/etc/nfsmount.conf'. Please ask the administrator for such a fix. |