Bug 439058 - KDEinit5 crashes in FileNameSearchProtocol::searchDirectory()
Summary: KDEinit5 crashes in FileNameSearchProtocol::searchDirectory()
Status: RESOLVED DUPLICATE of bug 438187
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.83.0
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-23 09:53 UTC by m.wege
Modified: 2021-08-03 10:30 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
crash-report (7.47 KB, text/vnd.kde.kcrash-report)
2021-06-23 09:53 UTC, m.wege 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description m.wege 2021-06-23 09:53:37 UTC 
Created attachment 139609 [details]
crash-report

KDEinit5 keeps crashing & Baloo might be the reason. There is no way to report it to KDEinit5, but the crash report contains "kio_filenamesearch.cpp" more than once so expect it to be related to the search in KDE.
Comment 1 tagwerk19 2021-06-23 10:35:17 UTC 
(In reply to m.wege from comment #0)
> KDEinit5 keeps crashing & ...
I'd gently nudge this one away from baloo... I think if there was an issue there, the crash info would mention baloosearch.so.

Filenamesearch.so and baloosearch.so are distinct things - or I'm pretty sure, let me know if otherwise!

I notice that Dolphin "drops back" to filenamesearch when baloo is not enabled or when doing searches of folders that baloo is not indexing.
Comment 2 m.wege 2021-06-23 11:22:45 UTC 
So where do I have to report this to?
Comment 3 tagwerk19 2021-06-23 11:44:03 UTC 
(In reply to m.wege from comment #2)
> So where do I have to report this to?
Sorry, still learning :-)

Searches get me Bug 438187 and Bug 438259. I'm guessing it not generally clear where to file these...
Comment 4 postix 2021-08-03 10:30:04 UTC 
Looks like a duplicate and if so, it has been fixed in 5.85. :)

*** This bug has been marked as a duplicate of bug 438187 ***