Summary: | Baloo_File crashes on Start-Up | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Christian Wichmann Moesgaard <christian> |
Component: | general | Assignee: | Unassigned bugs <unassigned-bugs-null> |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | crash | CC: | stefan.bruens |
Priority: | NOR | Keywords: | drkonqi |
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/137495/events/b8332ba2ccd64b2fb0d34efeee9fbef2/ |
Description
Christian Wichmann Moesgaard
2025-02-22 21:20:49 UTC
Unfortunately, lmdb crashes if it encounters an error, instead of giving the caller any feedback (return code denoting failure). If such an error (crash) happens in the content indexer, baloo will handle it, but when this happens in the daemon (baloo_file) itself, the problem will reappear. Currently, you have to solve this manually by running "balooctl6 purge". |