I know this is something that should be reported upstream, but first I wanted to check here if I'm the only one experiencing it.

My dolphin (from latest slackware64-current) crashes when I try to search stuff in the / directory.
I was specifically searching for a library header file, and even something as simple as "*.h" searched from within /usr/include triggers a bad crash and the infamous drkonqi dialog.

I thought it had something to do with baloo, so i tried disabling systemwide search from the settings, rebooting etc., but the issue is still there no matter what i try.

No problem searching stuff in my home, hidden folders are not included but there's a toggle for that in the settings and I'm personally ok with it since i rarely mess with config files in my home, nor do i need baloo to index all the .git folders (hopefully there's some kind of blacklist for that stuff only??)

So, steps to reproduce:

1) open dolphin
2) go to / directory
3) hit Ctrl+F and type whatever

Expected results:
- some results are shown based on the input text

What happens:
- drkonqi krash

I really hope it's something on my system, because this seems to me like a very basic need.
I know i can just use bash and two hundred different tools to locate stuff, thats what i did, but still this should not be so broken out of the box in my opinion.

Fails here also. This a fully up updated current X64.

I got this message:

Just wondering, this is running as a regular user, could that be part of the problem?

FWIW, I started dolphin as root, and tried to find fstab. I got a 'KCrash handler'.

Yes thats the one I'm facing.
Looking around the forums people only suggest to recreate the baloo index, but I know that helps only if baloo tries
to index some strange files and fails corrupting the database. My baloo instance is in check, no issues there.

Me too but I know in my case theirs substantially more wrong that I caused recently on my Main. When I get a chance later today I'll boot up one or some of my alternates and see if they crash on search as well or not.

Same here. The search starts but stopped with "The process for the filenamesearch protocol died unexpectedly."

Subsiquent searches elsewhere end with the same result, one must exit dolphin the start it again for search to work again from other locations. At least that is what I see here.

Is this still happening after last nights updates?

Yes. Just tested, fails on the /home/$user/ also.

This is probably the bug: https://bugs.kde.org/show_bug.cgi?id=437153
It has already been fixed upstream: https://invent.kde.org/frameworks/ki...0979ed897a8094
The patch will be in the kio-5.83 package, that should be released... tomorrow: https://community.kde.org/Schedules/Frameworks

2 members found this post helpful.

Unfortunately it looks like we are hitting a different bug, since it still crashes with kio-5.83.

10/10 could reproduce
(up-to-date -current64)

Dolphin doesn't crash anymore, but the search mechanism seems to understand only RE.
As the OP, if I search for "*.h" inside /usr, it keeps searching and doesn't return any result.
If I search for ".h", it will return anything with an "h" preceded by any character.
Searching for "\.h$" will return .h files.
I'm an Xfce user so I don't know if that would be configurable in KDE.

still hitting this after a full upgrade to latest current.
Seems related to which directories are added to the baloo file search, if I add /usr for example and let it index it
then i can search from within /usr but not from /