This looks like a bug with upstream. Again, kde appears to be pushing an half-finished tool without passing through a phase where only early adopters can try it.
I see the following issues: 1) No discoverable interface to switch the indexer off (adding your home to the exclude file list is less than intuitive) 2) When you add something to the exclude list, the database does not reduce in size. This wastes space and poses privacy issue. You may think that you have deleted something, but it may still live in the database. 3) By default the database seems to be readable by everybody on the system! This is a security hazard. If you have passwords in a file readable only by yourself, other users may be able to read your passwords by snooping into the database. 4) There is no tool to check what is indexed and what is not and to manually remove stuff from the database. 5) There is no nice interface to selectively decide what to index (typically, one may want to exclude home, but for a couple of dirs) Can this be reported upstream? Once finished baloo may turn out to be a nice tool. Getting rid of the virtuoso/strigi/nepomuk stuff seems a great idea. Having tags live with files as attributes rather than on a database also seems a good idea. But right now it seems really immature. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-baseapps in Ubuntu. https://bugs.launchpad.net/bugs/1295323 Title: Can't stop/remove baloo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baloo/+bug/1295323/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
