I was restoring a degraded raid on my home partition, box #2 below, when I started getting disk full errors. I found by using du and df that it was nepomuk that was filling up my home partition in 2 places. In the first place, I was getting a file that was building up rapidly called .xession-errors. I found by googling that I could do this: rm .xsession-errors ; ln -s /dev/null .xsession-errors That is a temporary fix to send the continuously increasing errors into the void. My disk was full and it was the nepomuk subdirectory of the ./.kde4 directory that was filling up. I deleted this and had to reboot all the way (not just log out and log back in) to get my fill system to recognize that my home partition was not full anymore. So the thing I am wondering is, what do I do about nepomuk for now? I like the idea of what it does, and I find the rapid search from indexed files rather helpful. On my other computers I do not have this problem. So I would rather not be so drastic as to uninstall it. I was going to put down which version of nepomuk I am running, but I found that it is not a specific package. -- G.O. Box #1: 12.1 | KDE 4.8.4 | AMD Phenom IIX4 | 64 | ATI Radeon HD 3300 | 16GB Box #2: 12.1 | KDE 4.8.4 | AMD Athlon X3 | 64 | nVidia C61 GeForce 7025 | 4GB Laptop: 12.1 | KDE 4.8.4 | Core i7-2620M | 64 | Intel HD Graphics 3000 | 8GB learning openSUSE and loving it -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org