I've been observing the same bug since 4.6 RC1. If you install strigi- daemon, which is not even required by nepomuk to enable strigi indexing, it solves the problem. However, I believe it may then run strigi-daemon on top of nepomuk's strigi indexing which is obviously not a good workaround for a mere "notification bug".
-- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to strigi in ubuntu. https://bugs.launchpad.net/bugs/700753 Title: strigi says on login it isn’t started, but is indexing according to system settings -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
