| Summary: | Crashes multiple times at boot giving me a horribly annoying popup | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | udumbutt |
| Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | tagwerk19 |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.114.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
udumbutt
2024-01-20 03:19:37 UTC
(In reply to udumbutt from comment #0) > #10 0x00007fbd940887f7 in Baloo::DocumentDB::del(unsigned long long) () from > /usr/lib/libKF5BalooEngine.so.5 > #11 0x00007fbd9409ecd0 in Baloo::WriteTransaction::removeDocument(unsigned > long long) () from /usr/lib/libKF5BalooEngine.so.5 I can see that Baloo is trying to remove the entry for a deleted file, but the trace does not show what file. It *might* be possible to see more with debugging, you can turn on debugging by creating a qtlogging.ini file: mkdir -p ~/.config/QtProject vi ~/.config/QtProject/qtlogging.ini and adding [rules] kf.baloo=true kf.baloo.engine=true You can also ensure that any log or error messages sent to stderr get copied to the journal by editing the kde-baloo unit file: systemctl edit --user kde-baloo and add line: [Service] StandardError=journal and saving the override. |