https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #10 from Matt Fagnani <matthew.fagn...@utoronto.ca> --- 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: I ran balooctl start in konsole which showed the following error messages and crash. KCatalog being used without a Q*Application instance. Some translations won't work mdb.c:2127: Assertion 'rc == 0' failed in mdb_page_dirty() KCrash: Attempting to start /usr/bin/baloo_file from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash: Application 'baloo_file' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 5 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... QSocketNotifier: Invalid socket 12 and type 'Exception', disabling... QSocketNotifier: Invalid socket 11 and type 'Read', disabling... QSocketNotifier: Invalid socket 14 and type 'Read', disabling... The error messages also occurred when I ran baloo_file -h. Christoph, the patch suggested by Stefan in comments 39 and 41 at https://bugs.kde.org/show_bug.cgi?id=389848#c39 was applied by Jan Staněk on Nov 5 in the lmdb-0.9.22-4.fc29 update which I upgraded to that day https://bugzilla.redhat.com/show_bug.cgi?id=1645114 I didn't see any baloo_file 5.51 crashes with the lmdb-libs-0.9.22-4.fc29 update on Nov 5-7. After I upgrading to KF5 5.52 on Nov 8, I've seen this crash six times. 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 balooctl start. Some change to how lmdb-libs handles the exception from the failed assertion around mdb_assert_fail at mdb.c:1542 or mdb_page_dirty at mdb.c:2128 so that the abort signal isn't made might prevent the crashes at least. If baloo_file were able to handle that exception from the failed assertion, then it might be able to fix or recreate the index. I'm not familiar enough with baloo or lmdb to know how if or how those changes could be properly made. -- Backtrace (Reduced): #8 0xb7207b36 in __libc_signal_restore_set (set=0x72a7c24c) at ../sysdeps/unix/sysv/linux/internal-signals.h:84 #9 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 #10 0xb71f1374 in __GI_abort () at abort.c:79 #11 0xb7618b20 in mdb_assert_fail (env=0xd159d0, expr_txt=expr_txt@entry=0xb761b02f "rc == 0", func=func@entry=0xb761b920 <__func__.7063> "mdb_page_dirty", line=2127, file=0xb761b010 "mdb.c") at mdb.c:1542 #12 0xb760da24 in mdb_page_dirty (txn=0xd16c30, mp=<optimized out>) at mdb.c:2128 -- You are receiving this mail because: You are watching all bug changes.
