https://bugs.kde.org/show_bug.cgi?id=387672
--- Comment #23 from marty <l3e...@gmail.com> --- Have had same issue for awhile. Found the following suggestion that solved problem: Baloo is currently disabled. To enable, please run "balooctl enable" After running "balooctl enable" problem hasn't recurred (am up to fc28 now). ref: https://bbs.archlinux.org/viewtopic.php?id=193169 On Sat, Jun 30, 2018 at 3:22 AM, Eric L. <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=387672 > > Eric L. <ewl+...@lavar.de> changed: > > What |Removed |Added > ------------------------------------------------------------ > ---------------- > Status|UNCONFIRMED |CONFIRMED > Ever confirmed|0 |1 > > --- Comment #22 from Eric L. <ewl+...@lavar.de> --- > Small update and a workaround: calling `find $HOME -name \*baloo* | xargs > rm > -fr` (or similar) solved the issue (at least for now). I seems to work > again > after I had to kill KDE once because it would hang while trying to log-out > (`sudo systemctl restart sddm` in a separate console). Hope this helps > others. > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.