KDE / dolphin: kioslave5 closed unexpectedly

Help
,
1

Hi KDE-users,

since a few weeks now and after an udate of kde-plasma with all packages I get an error-message when starting dolphin: “kioslave5 closed unexpectedly”

Code:	
Application: kioslave5 (kioslave5), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f09535e534c in ?? () from /usr/lib64/liblmdb.so.0
#5  0x00007f09535e923b in ?? () from /usr/lib64/liblmdb.so.0
#6  0x00007f09535e7882 in mdb_cursor_get () from /usr/lib64/liblmdb.so.0
#7  0x00007f0950874c3d in Baloo::PostingDB::fetchTermsStartingWith(QByteArray const&) () from /usr/lib64/libKF5BalooEngine.so.5
#8  0x00007f095087a160 in Baloo::Transaction::fetchTermsStartingWith(QByteArray const&) const () from /usr/lib64/libKF5BalooEngine.so.5
#9  0x00007f09509b4a03 in Baloo::TagListJob::start() () from /usr/lib64/libKF5Baloo.so.5
#10 0x00007f09547865fe in KJob::exec() () from /usr/lib64/libKF5CoreAddons.so.5
#11 0x00007f0955762ba2 in ?? () from /usr/lib64/qt5/plugins/kf5/kio/tags.so
#12 0x00007f095576606f in ?? () from /usr/lib64/qt5/plugins/kf5/kio/tags.so
#13 0x00007f095562d958 in ?? () from /usr/lib64/libKF5KIOCore.so.5
#14 0x00007f095562651d in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /usr/lib64/libKF5KIOCore.so.5
#15 0x00007f0955626fb6 in KIO::SlaveBase::dispatchLoop() () from /usr/lib64/libKF5KIOCore.so.5
#16 0x00007f095576704a in kdemain () from /usr/lib64/qt5/plugins/kf5/kio/tags.so
#17 0x00005561d079e374 in ?? ()
#18 0x00007f0954a65eea in ?? () from /lib64/libc.so.6
#19 0x00007f0954a65fa5 in __libc_start_main () from /lib64/libc.so.6
#20 0x00005561d079e5b1 in ?? ()
[Inferior 1 (process 4105) detached]

The error itsself is always shown on starting the dolphin filemanager and doing file operations within. Nevertheless all operations are working so the error message is simply driving me crazy. Can anybody please tell me what to do to get rid of it?

Thanks in advance
Wolfgang

2

That’s baloo crashing in fact as it was listing tags:/, that happens often in the background :confused:

3

Hi meven,

thanks a lot for your quick response, but is there a solution for this issue?

When I moved to KDE plasma in september 2023 everything was fine. The crashes appeared first with upgrading to baloo 5.113.0 (as far as I can remember) around december 2023. Since then you get this message every time you start dolphin - not really nice, isn’t it?

Best regards, Wolfgang

4

That’s a bug, no way around it. A crash always is, except sometimes there are workarounds.
Disabling baloo for instance would help. But this crash is not very important, it does not prevent to use baloo in fact, just accessing tags://.

You can report the bug so that it can be triaged.
Log in to KDE Bugtracking System for the tags component.

5

Hi meven,

thanks again for your answer, but John Little found a solution to stop those messages here on Kubuntu forums.

To stop the crashes, clear out the baloo directory, .local/share/baloo

I did so, and the crash message is gone.
So this problem is not really solved (what’s been the reason for the crashes???), but at the moment I’m content with this “solution”.

Best regards, Wolfgang