https://bugs.kde.org/show_bug.cgi?id=397488
--- Comment #2 from Matthew Wheaton <mwheat5...@gmail.com> --- Thanks for changing the status which enabled me to find this ticket. Without an email, I would not have known how to find it. I was able to recover from this situation by running 'balooctl disable' as root and as the primary user (my user id), then rebooting. I initially re-enabled baloo for my userid once I got a good boot, and just now I re-enabled baloo for root. No issues. I hope this helps. Matt -- You are receiving this mail because: You are watching all bug changes.
