https://bugs.kde.org/show_bug.cgi?id=389848
--- Comment #37 from GregS <greg.shepp...@bigpond.com> --- (In reply to Don Curtis from comment #33) > (My DrKonqi crash report: Bug 396277) > In my case, this behaviour appeared after the following upgrade: > Qt Version: 5.6.2 upgraded to 5.9.4; > Frameworks Version: 5.32.0 upgraded to 5.45.0; > (Distribution upgrade from openSUSE Leap 42.3 to Leap 15.0). > ------------------------------------------------------------ > I noticed that, with the updated system version and, a "fresh" test user, > Baloo didn't crash. > Also not after I enabled the PIM plugin in the Digital Clock -- akonadi > started. > Also not with a user which doesn't use the Kontact PIM -- only digiKam and > Oracle's VirtualBox -- akonadi is not started for this user. > ------------------------------------------------------------ > For the case of the user which was suffering the Baloo crashes I did the > following from a VT with the Display Manager stopped: > 1. Removed the following files in '~/.config/': > baloorc > baloofilerc > baloofileinformationrc > 2. Removed the entire contents of '~/.local/share/baloo/': > index > index-lock > KDE PIM Kontact directories > 3. Restarted the Display Manager and logged in the user with the "Baloo > crashing issue". > ------------------------------------------------------------ > Baloo doesn't crash any more. > ------------------------------------------------------------ > My guess at the root cause: > * Outdated Baloo configuration files and an outdated index database cause > an exception with the current Baloo implementation. Tried this (Fedora 27 - has been a recurring issue since Fedora 22). So far, no more crashes. I guess the suggestion above WRT outdated files may be on the money. -- You are receiving this mail because: You are watching all bug changes.
