Comment 4 for bug 883222

Nothing yet? This seems pretty darn urgent to me. Virtuoso is eating my hard disk space, my processor time, my power, and ultimately the usability of my computer. If bug #894841 isn't directly related, then it's coincidentally happening to me as well. I've also noted that Nepomuk is constantly (i.e. after every boot) wanting to do its "initial" indexing. Related?

Workaround (maybe): I've kill -9'd virtuoso-t, stopped Nepomuk ("qdbus org.kde.NepomukServer /nepomukserver quit"), and deleted soprano-virtuoso.log (actually I nuked its directory from orbit, just to be sure). And now I've turned off Nepomuk from System Settings. I suppose only time (and/or my next reboot) will tell whether it will stay dormant until it can be fixed.