Re: Bug#825393: baloo-malfunctioning; was: krunner constantly crashes without visible reason
tags 825393 upstream
thanks
On Samstag, 28. Mai 2016 11:55:15 CEST Maria wrote:
> Dear Martin,
Dear Maria,
> thanks alot for your help - it's very kind of you!
You are welcome.
> The versions are as followed:
> * plasma-workspace Version: 4:5.4.3-2
> * libkf5runner5 Version: 5.16.0-1
[…]
> After the installation of plasma-workspace-dbg and another krunner crash
> the output indeed changed to potentially useful (I added the file) and
> the list of missing symbols added the following not available debug
>
> symbols to the list:
> > /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
> > /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
> > /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
> > /usr/lib/x86_64-linux-gnu/liblmdb.so.0
>
> Oh and after saving the output drkonqi crashed. So I added that
> crashreport as well.
You can help by browsing the upstream bug reports and checking which one
matches the issue you saw most closely:
https://bugs.kde.org/buglist.cgi?quicksearch=baloo%20krunner%20crash
You can do so, by checking the bug description and the backtrace for
similarities.
> 'balooctl' still has no manpage but is available now but I couldn't find
Feel free to report the missing manpage upstream as well (if not already
done).
> 'kde-config-baloo-advanced' anywhere in the systemsettings (or
> elsewehere) - but it installed some files which looked like 4 and not 5,
> so I deinstalled it again. 'balooctl --help' helped.
Yep, thats KDE 4 currently.
> After a new crash I saw 'baloo-kf5-dbg' filled the missing baloosymbols
> so I searched again for the rest of the symbols this time using
> "apt-cache search lmdb |grep dbg" and indeed found them. But I couldn't
>
> install them:
> > lmdb-dbg : Hängt ab von: liblmdb0 (= 0.9.18-1~bpo80+1) aber 0.9.18-4
> > soll installiert werden (depends on: [bla] but [bla] should be
> > installed)
You have a backports version of liblmdb0, which is older than the one it wants
to install. You can try aptitude whether it gives a good resolution. It
usually offers to change versions of dependent packages as needed. Carefully
review an offered solution tough, before you accept it.
> There are no instances running which contain the search string "baloo".
> '~/local/share/baloo/' only contains two files: index and index-lock
> Both have 8,0 KiB each. If I delete them, they are immediately restored.
> baloofilerc only contains "exclude filters=[xy]" and "exclude filters
> version=2" If I add "first run=true" and delete the files nothing
> changes. Same for deleting baloofilerc.
Hm, yes, I saw crashes also for *empty* database. Thus I am not surprised.
> Finally I noticed to having made the mistake running "balooctl start"
> "status" and "stop" as root, leading to error messages. Finally I
> noticed and running it as normal user started the indexing. But it
> didn't index fully - only 4077 of 41517 files were indexed.
Thats is a different issues. Please do not use this bug report for that.
Instead ask on debian-kde mailing list. That written baloo excludes quite some
files from indexing so thats expected behavior.
> Searching within Dolphin doesn't although it is also baloo:
Please do not add information to this bug report thats unrelated. And yes,
baloo affects Dolphin as well, as well as Kickoff menu (it also crashed as I
had the issues with the baloo database).
> Searching within kontact/kmail only works for the active folder in the
Again, please only add information that is relevant to *this* bug report, to
keep it manageable. Please use the user support mailing list for any other
questions. And file new bugs for any issues other than this one (if not
already done).
Thanks,
--
Martin
Reply to: