On Wed, 18 Jul 2012 03:22, George Olson wrote:

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.

Below are the three steps I took to stop neponuk at all, most interesting for you is step (3). The rapid search you mention, is it just file finding (locate does a nice job) or really searching inside? For the later, take the time and configure strigi as precise as possible. Just index in the dirs you specify, just the filetypes you select. ==== My steps to disable nepomuk (fully) ==== (1) Info: /usr/lib{,64}/libnepomukquery.so.* is a part of libkde4-* for me (on my old system) "locate -i nepo" gives: /usr/lib64/libnepomuk.so.4 (link) /usr/lib64/libnepomuk.so.4.6.0 (file) /usr/lib64/libnepomukquery.so.4 (link) /usr/lib64/libnepomukquery.so.4.6.0 (file) /usr/lib64/libnepomukutils.so.4 (link) /usr/lib64/libnepomukutils.so.4.6.0 (file) That was all it took to have no error messages from kde, and no nepomuk working (mine was a runaway, and i did not need nepomuk at all) (2) Secure disposal of nepomuk (just ini/rc files) edit $HOME/.kde4/share/config/nepomukserverrc ---code--- [Basic Settings] Configured repositories=main Start Nepomuk=false [Service-nepomukstrigiservice] autostart=false [main Settings] Maximum memory=5 Storage Dir[$e]=$HOME/.kde4/share/apps/nepomuk/repository/main/ Used Soprano Backend=null rebuilt index for type indexing=false ---/code--- this or similar is what is should look like, pay attention to "Start Nepomuk=false" and "autostart=false", the entry "Used Soprano Backend=null" is a failsafe, it terminates nepomuk as it starts (... no backend avail...) and edit $HOME/.kde4/share/config/nepomukstrigirc ---code--- [General] exclude filters=lost+found,.*,*~,* exclude folders[$e]= folders[$e]=$HOME/not-there-dir index hidden folders=false index newly mounted=false ---/code--- this stops the strigi-service from doing anything. (3) disabling debug info of nepomuk (THE filler of .xsession-errors) start "/usr/bin/kdebugdialog" , then in the searchfield, enter "nepo", in the box below make sure thate are no enabled/activated options (disable the enabled ones), click "apply" button (you can use "Deselect All" if you do not need kde-debug-info at all) close kdebugdialog with "OK". I hope this give you a starting point. Keep in ming that some combinations of soprano and nepomuk are known to runaway for detailed info requests please include the output of "uname -ri" and "rpm -q libkde4 libsoprano4 soprano" And if you use repos other than install/update "zypper lr -Pu" gives the relevant info about the repos you use and their priority. -- Yamaban. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Onsdag den 18. juli 2012 09:22:51 George Olson skrev:

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.

Uninstalling it is rash and dangerous. Disabling strigi (the indexer) avoids most of the problems with Nepomuk - and still leaves kdepim, dolphin etc. fully functional. Since disabling strigi is not what you want, excluding certain dirs from indexing might do the trick - especially dirs with lots and lots of plaintext files - like e.g. version control checkouts and similar. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org