Bug 473132 - Ballo crashes on every login into kde
Summary: Ballo crashes on every login into kde
Status: RESOLVED DUPLICATE of bug 393583
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.104.0
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-08-08 07:37 UTC by Vadim Smilansky
Modified: 2023-08-13 15:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vadim Smilansky 2023-08-08 07:37:09 UTC
Application: baloo_file_extractor (5.104.0)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.0-26-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.04
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
Ballo crashes on every login into kde
and even on unlock or after back from sleep

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#7  0x00007f9572c3c406 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007f9572c2287c in __GI_abort () at ./stdlib/abort.c:79
#9  0x00007f95733a5418 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0
#10 0x00007f9573397e25 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0
#11 0x00007f957339fc86 in mdb_cursor_del () from /lib/x86_64-linux-gnu/liblmdb.so.0
#12 0x00007f95733a10cb in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0
#13 0x00007f95743a7a74 in Baloo::PositionDB::del(QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#14 0x00007f95743b77e2 in Baloo::WriteTransaction::commit() () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#15 0x00007f95743abb1d in Baloo::Transaction::commit() () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#16 0x00005570e09f315c in ?? ()
#17 0x00007f95736f7a26 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f95736e7bf5 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f95736bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f9573714201 in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f9573714b34 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f957231549d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f9572370178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f95723141b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f9573714e7a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007f95736b97cb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x00007f95736c1c1a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x00005570e09e8f99 in ?? ()
#29 0x00007f9572c23a90 in __libc_start_call_main (main=main@entry=0x5570e09e82b0, argc=argc@entry=1, argv=argv@entry=0x7ffc0d6bed58) at ../sysdeps/nptl/libc_start_call_main.h:58
#30 0x00007f9572c23b49 in __libc_start_main_impl (main=0x5570e09e82b0, argc=1, argv=0x7ffc0d6bed58, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc0d6bed48) at ../csu/libc-start.c:360
#31 0x00005570e09e90b5 in ?? ()
[Inferior 1 (process 12036) detached]

Reported using DrKonqi
Comment 1 Nicolas Fella 2023-08-13 15:12:09 UTC

*** This bug has been marked as a duplicate of bug 393583 ***