Summary: | Baloo crashes at log in | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | kenjite |
Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | christoph, tagwerk19 |
Priority: | NOR | Keywords: | drkonqi, qt6 |
Version: | 5.249.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
kenjite
2024-02-16 18:30:33 UTC
(In reply to kenjite from comment #0) > Core was generated by `/usr/lib/kf6/baloo_file_extractor'. > Program terminated with signal SIGABRT, Aborted. > ... > Thread 1 (Thread 0x7850acd41e00 (LWP 2495)): > [KCrash Handler] > ... > #18 0x00007850af578e41 in Baloo::DocumentUrlDB::del (this=<optimized out>, > id=<optimized out>) at > /usr/src/debug/baloo/baloo-5.249.0/src/engine/documenturldb.cpp:120 > #19 0x00007850af58cb3e in Baloo::WriteTransaction::removeDocument > (this=0x603c0e97a680, id=36135173649790487) at > /usr/src/debug/baloo/baloo-5.249.0/src/engine/writetransaction.cpp:133 I have to leave dumpcracking to someone else but it looks as if Baloo is trying to clear up entries in its index for deleted files. This is often a slow job, can easily be that it is not finished before you log out and it carries on when you log in again... If the index is corrupt, the only way out normally is to purge and reindex... We try to not delete the lock file now, perhaps this was just the result of a race condition because of the old lock file deletion. *** This bug has been marked as a duplicate of bug 389848 *** |