| Summary: | Crash on startup of computer every time. | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | arch.freaque <arch.freaque> |
| Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | tagwerk19 |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.108.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
attachment-3299263-0.html
sig_arch.png |
||
|
Description
arch.freaque@disroot.org
2023-08-22 22:13:37 UTC
(In reply to arch.freaque@disroot.org from comment #0) > ... Artix Linux ... Maybe worth looking at Bug 472540 That talked about a crash when baloo was trying to "clean up" the index after files were deleted. Don't see that here. If the index is not large, you could try the referenced python consistency check script. Created attachment 161219 [details] attachment-3299263-0.html I tried that and then rebooted but I still had baloo fail. " Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted [KCrash Handler] #4 0x00007ff941a8e83c in () at /usr/lib/libc.so.6 #5 0x00007ff941a3e668 in raise () at /usr/lib/libc.so.6 #6 0x00007ff941a264b8 in abort () at /usr/lib/libc.so.6 #7 0x00007ff94212891e in () at /usr/lib/liblmdb.so #8 0x00007ff942126c2a in mdb_env_create () at /usr/lib/liblmdb.so #9 0x00007ff942134646 in () at /usr/lib/liblmdb.so #10 0x00007ff94212bd53 in () at /usr/lib/liblmdb.so #11 0x00007ff94212d9ac in () at /usr/lib/liblmdb.so #12 0x00007ff942131c8d in mdb_cursor_del () at /usr/lib/liblmdb.so #13 0x00007ff942133485 in () at /usr/lib/liblmdb.so #14 0x00007ff9430a8087 in Baloo::PostingDB::del(QByteArray const&) () at /usr/lib/libKF5BalooEngine.so.5 #15 0x00007ff9430b7720 in Baloo::WriteTransaction::commit() () at /usr/lib/libKF5BalooEngine.so.5 #16 0x00007ff9430ac15e in Baloo::Transaction::commit() () at /usr/lib/libKF5BalooEngine.so.5 #17 0x0000556efb77314d in () #18 0x00007ff9424d35f7 in () at /usr/lib/libQt5Core.so.5 #19 0x00007ff9424c3e2e in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #20 0x00007ff94249c438 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x00007ff9424eaaab in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #22 0x00007ff9424eb0e2 in () at /usr/lib/libQt5Core.so.5 #23 0x00007ff940f0fa31 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #24 0x00007ff940f6ccc9 in () at /usr/lib/libglib-2.0.so.0 #25 0x00007ff940f0d0e2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #26 0x00007ff9424eb25c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #27 0x00007ff94249b144 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #28 0x00007ff94249c5e3 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #29 0x0000556efb768d4e in () #30 0x00007ff941a27cd0 in () at /usr/lib/libc.so.6 #31 0x00007ff941a27d8a in __libc_start_main () at /usr/lib/libc.so.6 #32 0x0000556efb768e75 in () [Inferior 1 (process 3452) detached] " On 2023-08-23 02:28, bugzilla_noreply@kde.org wrote: > https://bugs.kde.org/show_bug.cgi?id=473658 > > tagwerk19@innerjoin.org changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |tagwerk19@innerjoin.org > > --- Comment #1 fromtagwerk19@innerjoin.org --- > (In reply toarch.freaque@disroot.org from comment #0) >> ... Artix Linux ... > Maybe worth looking at Bug 472540 > > That talked about a crash when baloo was trying to "clean up" the index after > files were deleted. Don't see that here. If the index is not large, you could > try the referenced python consistency check script. > Created attachment 161220 [details]
sig_arch.png
(In reply to arch.freaque@disroot.org from comment #2) > I tried that and then rebooted but I still had baloo fail. Just to confirm.... You ran the baloo-checkdb.py script and it showed clean and you still get a crash? I don't think the script corrects errors, it just flags that something is corrupt. I’ll have to see what it said again. It’s been some time since I did that.
Sent from my iPhone
> On Aug 28, 2023, at 2:49 AM, bugzilla_noreply@kde.org wrote:
>
> https://bugs.kde.org/show_bug.cgi?id=473658
>
> --- Comment #4 from tagwerk19@innerjoin.org ---
> (In reply to arch.freaque@disroot.org from comment #2)
>> I tried that and then rebooted but I still had baloo fail.
> Just to confirm....
>
> You ran the baloo-checkdb.py script and it showed clean and you still get a
> crash? I don't think the script corrects errors, it just flags that something
> is corrupt.
>
> --
> You are receiving this mail because:
> You reported the bug.
|