Re: Frequent "disk full" crashes with KDE Nepomuk

[T Elcor <telcor@yahoo.com>]

--- On Sun, 12/25/11, Chris Bell <chrisbell@chrisbell.org.uk> wrote:

> I have now deselected nepomuk and
> cleared the index
> and log files, and the approx. 6% use of / appears stable
> at the moment.
>    The files cleared are
> 
> #
> /home/username/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-virtuoso.db
> 
> #
> /home/username/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-virtuoso-temp.db
> 
> #
> /home/username/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-virtuoso.log


Nepomuk may still be running though. In my experience it's not that easy to kill. Check

$ ps -A u | grep -i nepomuk

You may also want to consider removing/renaming the "/usr/share/autostart/nepomukserver.desktop" file, it may start nepomuk next time you restart KDE.

Does anybody use nepomuk at all? I've not met such a person yet.