| Summary: | baloo_file_extractor crashes when login | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | 23m448a32 |
| Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | joe.turpin, tagwerk19 |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.68.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
23m448a32
2022-03-01 05:08:56 UTC
Did you say 5.68.0? That's now really quite old. There's been loads of work done since then, you can have a look at Bug 431664 for a bit of history. You can try purging the index and reindexing (as per 431664) or upgrade if you can... Look like issues with 5.68.0 are flagged as "Unmaintained" (cf Bug 447157, different issue but 5.68.0) Maybe there should be a Baloo flatpak/snap that would allow people to move from older versions. Something minimal through, that updates just the Baloo functionality. Created attachment 147519 [details]
New crash information added by DrKonqi
baloo_file_extractor (5.68.0) using Qt 5.12.8
- What I was doing when the application crashed:
I logged into the KDE desktop and shortly thereafter the baloo_file_extractor crash was reported through a desktop notification.
-- Backtrace (Reduced):
#7 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#8 0x00007f7e04cfb859 in __GI_abort () at abort.c:79
#9 0x00007f7e04a25a83 in mdb_assert_fail (env=0x5562845486a0, expr_txt=expr_txt@entry=0x7f7e04a2802f "rc == 0", func=func@entry=0x7f7e04a28978 <__func__.7221> "mdb_page_dirty", line=line@entry=2127, file=0x7f7e04a28010 "mdb.c") at mdb.c:1542
#10 0x00007f7e04a1a6d5 in mdb_page_dirty (mp=<optimized out>, txn=0x556284549b90) at mdb.c:2114
#11 mdb_page_dirty (txn=0x556284549b90, mp=<optimized out>) at mdb.c:2114
(In reply to Joe Turpin from comment #3) > ... shortly thereafter the baloo_file_extractor crash was reported ... It seems to fit a pattern, the crash seems to happen when trying to remove a entry: > #19 0x00007f7e06445af9 in Baloo::DocumentDB::del (this=this@entry=0x7ffe557419e0, docId=<optimized out>, docId@entry=20274363055997009) at ./src/engine/documentdb.cpp:118 > #20 0x00007f7e06478239 in Baloo::WriteTransaction::removeDocument (this=0x556284548620, id=id@entry=20274363055997009) at ./src/engine/writetransaction.cpp:128 > #21 0x00007f7e06469987 in Baloo::Transaction::removeDocument (this=<optimized out>, id=id@entry=20274363055997009) at ./src/engine/transaction.cpp:266 I'm not a dump cracker so cannot say much more than that. However as mentioned above 5.68.0 is now "way old". Nothing to say that newer code deals better with these situations but it seems that such crash reports generally reference old(er) versions. Upgrade if you can... (See Bug 451245 for a brief discussion about alternatives) |