Bug 1080845 - KCrash: Attempting to start /usr/bin/baloo_file from kdeinit
KCrash: Attempting to start /usr/bin/baloo_file from kdeinit
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma)
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: E-Mail List
E-mail List
Depends on:
  Show dependency treegraph
Reported: 2018-02-13 17:12 UTC by Niko Rostoveli
Modified: 2018-02-13 18:38 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

baloo_crash (2.61 KB, text/plain)
2018-02-13 17:12 UTC, Niko Rostoveli

Note You need to log in before you can comment on or make changes to this bug.
Description Niko Rostoveli 2018-02-13 17:12:34 UTC
Created attachment 760008 [details]

According to crash handler completely useless...but i couldn't debug it otherwise, so please see for whatever it worth crash output in attached text file.
Baloo_file crashing at the start of the system and when started manually (every time).
Will be glad to provide more info if told how...tried installing debug symbols but getting same "useless" remark from Kcrash.
Comment 1 Wolfgang Bauer 2018-02-13 18:08:43 UTC
Comment on attachment 760008 [details]

Well, apparently it crashes while accessing the database. Maybe it got corrupted somehow...
Does renaming the folder ~/.local/share/baloo/ help?
(baloo should reindex everything automatically afterwards)

Regarding the "useless" error from KCrash: you need to install debuginfo packages to "fix" that, at least libKF5BalooEngine5-debuginfo.
You'd need to enable the debug repo first in YaST->Software Repositories though.
(KCrash should actually be able to do that automatically then if you click on "Install debug symbols")
Comment 2 Niko Rostoveli 2018-02-13 18:38:39 UTC
Thank you Wolfgang, renaming directory was the right move! i guess your idea on corrupted DB was correct.
thanks again.