| Summary: | KDEinit5 crashes in FileNameSearchProtocol::searchDirectory() | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | m.wege |
| Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | kdelibs-bugs, nate, postix, tagwerk19 |
| Priority: | NOR | ||
| Version: | 5.83.0 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | crash-report | ||
(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. So where do I have to report this to? (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... 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 *** |
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.