| Summary: | baloo_file does not provide a bug reporting address | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Dan Dascalescu <ddascalescu+kde> |
| Component: | general | Assignee: | baloo-bugs-null |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | nate, tagwerk19 |
| Priority: | NOR | ||
| Version First Reported In: | 5.85.0 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Dan Dascalescu
2021-08-30 20:01:57 UTC
(In reply to Dan Dascalescu from comment #0) > I'm 90% sure I've reported this already... Maybe Bug 433779 > What happens is that at startup, I get this crash dialog but can't do much > useful with it: > > "We're sorry, baloo_file closed unexpectedly... Just to eliminate one possibility. Might you be caught by Bug 431664? In which case a "balooctl purge" and rebuild of the index will solve it... *** This bug has been marked as a duplicate of bug 433779 *** |