[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [frameworks-baloo] [Bug 387672] Baloo File Extraction Error
From:       marty <bugzilla_noreply () kde ! org>
Date:       2018-06-30 16:29:08
Message-ID: bug-387672-17878-eTb3JifOZA () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=387672

--- Comment #23 from marty <L3E2M1@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_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=387672
>
> Eric L. <ewl+kde@lavar.de> changed:
>
>            What    |Removed                     |Added
> ------------------------------------------------------------
> ----------------
>              Status|UNCONFIRMED                 |CONFIRMED
>      Ever confirmed|0                           |1
>
> --- Comment #22 from Eric L. <ewl+kde@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.=
[prev in list] [next in list] [prev in thread] [next in thread]