Kioworker and tags protocol troubles after fresh install

I have a recently fresh installed KDE neon,
After a few updates and software installations I am expreciencing some troubles: (i try to translate from my language to english)

Continuosly I get the error “kioworker closed unespectedly”
The porcess for the tags protocol died unespectedly"

Are those troubles relationed?
What ought Ido to solve this ?

Thanks in advanced

Sorry this is happening. I think this was fixed recently, but without a backtrace, there’s no 100% way to be sure. So if you can get a backtrace of the crash, we can either investigate it, or confirm whether it’s already fixed.

See Guidelines and HOWTOs/Debugging/How to create useful crash reports - KDE Community Wiki

Really it’s a little complicated to get a backtrace.

I have updated the system via pkcon amd apt dist-upgrade (i made a snapshot before).
Pkcon says there’s nothing to update. But at the tray, the discover icon is shown and several paquets are to be updated . If I choose upgrade (sorry, my system is not in english) i get an error : “aborted due to failure (flatpack system operation DEploy not allowed for user”

Of course my user is sudoer.

The two other imortant bugs in my system are:
kioworker closed unespectedly
The process for the tags protocol died unespectedly

Both when launching Dolphin.

update:
Maybe it can help:

Application: kioworker (kioworker), signal: Aborted

[KCrash Handler]

#4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=123815511216768) at ./nptl/pthread_kill.c:44

#5 __pthread_kill_internal (signo=6, threadid=123815511216768) at ./nptl/pthread_kill.c:78

#6 __GI___pthread_kill (threadid=123815511216768, signo=signo@entry=6) at ./nptl/pthread_kill.c:89

#7 0x0000709c0f842476 in __GI_raise (sig=sig@entry=6) at …/sysdeps/posix/raise.c:26

#8 0x0000709c0f8287f3 in __GI_abort () at ./stdlib/abort.c:79

#9 0x0000709c0aef2418 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0

#10 0x0000709c0aee4e25 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0

#11 0x0000709c0aee7a1d in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0

#12 0x0000709c0aee80ca in mdb_cursor_get () from /lib/x86_64-linux-gnu/liblmdb.so.0

#13 0x0000709c0b85783b in Baloo::PostingDB::fetchTermsStartingWith(QByteArray const&) () from /lib/x86_64-linux-gnu/libKF6BalooEngine.so.6

#14 0x0000709c0b85ba10 in Baloo::Transaction::fetchTermsStartingWith(QByteArray const&) const () from /lib/x86_64-linux-gnu/libKF6BalooEngine.so.6

#15 0x0000709c0b8ce28d in Baloo::TagListJob::start() () from /lib/x86_64-linux-gnu/libKF6Baloo.so.6

#16 0x0000709c0f5d8a75 in KJob::exec() () from /lib/x86_64-linux-gnu/libKF6CoreAddons.so.6

#17 0x0000709c103b3e9c in ?? () from /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kio/tags.so

#18 0x0000709c103b6847 in ?? () from /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kio/tags.so

#19 0x0000709c10292fc8 in ?? () from /lib/x86_64-linux-gnu/libKF6KIOCore.so.6

#20 0x0000709c102915d6 in ?? () from /lib/x86_64-linux-gnu/libKF6KIOCore.so.6

#21 0x0000709c1033dbaa in ?? () from /lib/x86_64-linux-gnu/libKF6KIOCore.so.6

#22 0x0000709c103b8e2a in kdemain () from /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kio/tags.so

#23 0x00005667ea75c5a0 in ?? ()

#24 0x0000709c0f829d90 in __libc_start_call_main (main=main@entry=0x5667ea75c3c0, argc=argc@entry=5, argv=argv@entry=0x7ffe5c59d3c8) at …/sysdeps/nptl/libc_start_call_main.h:58

#25 0x0000709c0f829e40 in __libc_start_main_impl (main=0x5667ea75c3c0, argc=5, argv=0x7ffe5c59d3c8, init=, fini=, rtld_fini=, stack_end=0x7ffe5c59d3b8) at …/csu/libc-start.c:392

#26 0x00005667ea75c885 in ?? ()

[Inferior 1 (process 17445) detached]

Finally I installed again.

Now, new troubles have appeared.
I open a new treath

This looks familiar… sadly

I’ve been getting it occasionally. When it happens, it happens in a sequence of crashes. 6, 7 or 8 times one after another. Another time, another reboot, everything seems stable. I haven’t really found a pattern.

What I do see on occasion are errors when I move the mouse cursor from the Files panel to the Places panel (and back again). When that happens, the behaviour is repeatable and you get a coredumpctl shows a collection of dumps.