https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #12 from Matt Fagnani ---
(In reply to Stefan Brüns from comment #11)
> (In reply to Matt Fagnani from comment #10)
> > I read in another post that the failed assertion might indicate a corrupted
> > baloo index which seems likely as the cra
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #11 from Stefan Brüns ---
(In reply to Matt Fagnani from comment #10)
> I read in another post that the failed assertion might indicate a corrupted
> baloo index which seems likely as the crashes occur immediately on starting
> baloo_file or
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #10 from Matt Fagnani ---
Created attachment 116200
--> https://bugs.kde.org/attachment.cgi?id=116200&action=edit
New crash information added by DrKonqi
baloo_file (5.52.0) using Qt 5.11.1
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #9 from Christoph Feck ---
Matt, according to the duplicate, you need a fix in liblmdb.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #8 from Matt Fagnani ---
Created attachment 116198
--> https://bugs.kde.org/attachment.cgi?id=116198&action=edit
New crash information added by DrKonqi
baloo_file (5.52.0) using Qt 5.11.1
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=400498
Matt Fagnani changed:
What|Removed |Added
CC||matthew.fagn...@utoronto.ca
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #7 from Matt Fagnani ---
Nate, I'm inexperienced at interpreting such traces so I doubt that I'm more
familiar than you are at it.
Stefan, I've reassigned the Fedora report I filed on these crashes from
kf5-baloo to lmdb at https://bugzill
https://bugs.kde.org/show_bug.cgi?id=400498
Stefan Brüns changed:
What|Removed |Added
CC||stefan.bruens@rwth-aachen.d
|
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #5 from Nate Graham ---
Thanks Matt! It's always nice to learn from someone who's much better at
reading backtraces than I.
*** This bug has been marked as a duplicate of bug 389848 ***
--
You are receiving this mail because:
You are watc
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #4 from Matt Fagnani ---
While bug 389625 involves baloo and liblmdb.so.0, the crashing thread from the
trace in 389625 doesn't show mdb_assert_fail and the failed assertion rc == 0
in mdb_page_dirty at mdb.c in liblmdb.so. I think that maki
https://bugs.kde.org/show_bug.cgi?id=400498
Nate Graham changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC|
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #2 from Matt Fagnani ---
I ran gdb on baloo_file based on the instructions in the Retrieving a backtrace
when an uncaught exception is causing a crash section at
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #1 from Matt Fagnani ---
The crash might've been due to a failed assertion rc == 0 in mdb_page_dirty at
mdb.c:2127-2128 in liblmdb.so.0.0.0 in the lmdb-libs package.
A possible fix in the lmdb package was noted at the following report in
co
13 matches
Mail list logo
