[dolphin] [Bug 463641] Dolphin crashes while navigating filesystem (Other programs running in background)
classabbyamp
bugzilla_noreply at kde.org
Thu Jan 26 02:50:18 GMT 2023
https://bugs.kde.org/show_bug.cgi?id=463641
classabbyamp <dev+kde at placeviolette.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
CC| |dev+kde at placeviolette.net
--- Comment #3 from classabbyamp <dev+kde at placeviolette.net> ---
I believe I am experiencing this bug as well, but it happens when hovering over
one of a few directories. None of the directories involved have many entries.
The backtrace seems to indicate that baloo is to blame, like the linked bug
(#402064) in the original reporter's message says.
dolphin: 22.12.1
baloo: 5.101.0
baloo-widgets: 22.12.1
lmdb: 0.9.29
qt5: 5.15.7
Operating system: Linux 6.1.7 x86_64
Windowing system: X11 (bspwm)
Distribution: Void Linux
here's the backtrace from gdb:
#0 0x00007ffff414e85a in mdb_node_search (mc=mc at entry=0x7fffffffac50,
key=key at entry=0x7fffffffb020, exactp=exactp at entry=0x7fffffffac4c) at mdb.c:5341
#1 0x00007ffff415265e in mdb_cursor_set (mc=mc at entry=0x7fffffffac50,
key=key at entry=0x7fffffffb020, data=data at entry=0x7fffffffb030,
op=op at entry=MDB_SET, exactp=exactp at entry=0x7fffffffac4c) at mdb.c:6157
#2 0x00007ffff4152c40 in mdb_get (txn=<optimized out>, dbi=<optimized out>,
key=0x7fffffffb020, data=0x7fffffffb030) at mdb.c:5812
#3 0x00007ffff5fd30e0 in Baloo::DocumentDataDB::get(unsigned long long) ()
from /usr/lib/libKF5BalooEngine.so.5
#4 0x00007ffff5fe9631 in Baloo::Transaction::documentData(unsigned long long)
const () from /usr/lib/libKF5BalooEngine.so.5
#5 0x00007ffff77fd6c2 in Baloo::File::load() () from /usr/lib/libKF5Baloo.so.5
#6 0x00007ffff79e5418 in Baloo::FileFetchJob::doStart (this=0x5555559437f0) at
../src/filefetchjob.cpp:43
#7 0x00007ffff5cdbe61 in QObject::event (this=0x5555559437f0,
e=0x555555b12db0) at kernel/qobject.cpp:1347
#8 0x00007ffff696320f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#9 0x00007ffff5caf99a in QCoreApplication::notifyInternal2
(receiver=0x5555559437f0, event=0x555555b12db0) at
kernel/qcoreapplication.cpp:1064
#10 0x00007ffff5cb23d1 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0x0, data=0x555555687af0) at
kernel/qcoreapplication.cpp:1821
#11 0x00007ffff5d07f43 in postEventSourceDispatch (s=0x555555698450) at
kernel/qeventdispatcher_glib.cpp:277
#12 0x00007ffff3a66b2b in g_main_dispatch (context=0x7fffe8005010) at
../glib/gmain.c:3444
#13 g_main_context_dispatch (context=0x7fffe8005010) at ../glib/gmain.c:4162
#14 0x00007ffff3a66dd8 in g_main_context_iterate
(context=context at entry=0x7fffe8005010, block=block at entry=0x1,
dispatch=dispatch at entry=0x1, self=<optimized out>) at ../glib/gmain.c:4238
#15 0x00007ffff3a66e8f in g_main_context_iteration (context=0x7fffe8005010,
may_block=may_block at entry=0x1) at ../glib/gmain.c:4303
#16 0x00007ffff5d075cf in QEventDispatcherGlib::processEvents
(this=0x55555584b8f0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#17 0x00007ffff5cae33b in QEventLoop::exec (this=this at entry=0x7fffffffb690,
flags=..., flags at entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#18 0x00007ffff5cb65d0 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#19 0x000055555559fecd in ?? ()
#20 0x00007ffff544120c in __libc_start_call_main
(main=main at entry=0x55555559ec60, argc=argc at entry=0x2,
argv=argv at entry=0x7fffffffb948) at ../sysdeps/nptl/libc_start_call_main.h:58
#21 0x00007ffff54412bc in __libc_start_main_impl (main=0x55555559ec60,
argc=0x2, argv=0x7fffffffb948, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffb938) at ../csu/libc-start.c:381
#22 0x00005555555a0321 in ?? ()
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list