Application: dolphin (15.08.3) Qt Version: 5.5.1 Operating System: Linux 4.2.6-1-CHAKRA x86_64 Distribution: "Chakra" -- Information about the crash: It crashes when I select file with a mouse drag. In this case the file are not in the top level folder of the view (i.e. it shows a tree, and these files a few levels down) and in the course of the drag I cause the window to scroll. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5f08a47800 (LWP 18156))] Thread 3 (Thread 0x7f5ef33e5700 (LWP 18157)): #0 0x00007f5f0845b18d in poll () from /usr/lib/libc.so.6 #1 0x00007f5efd1bbae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x00007f5efd1bd757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x00007f5ef4b04329 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x00007f5f03250b7e in ?? () from /usr/lib/libQt5Core.so.5 #5 0x00007f5f0130a464 in start_thread () from /usr/lib/libpthread.so.0 #6 0x00007f5f0846412d in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f5eebf53700 (LWP 18158)): #0 0x00007f5f084706af in __libc_enable_asynccancel () from /usr/lib/libc.so.6 #1 0x00007f5f0845b182 in poll () from /usr/lib/libc.so.6 #2 0x00007f5efd6a9ca4 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x00007f5efd6a9dbc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x00007f5f034885ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #5 0x00007f5f0342f5ba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #6 0x00007f5f0324bbd4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x00007f5f03250b7e in ?? () from /usr/lib/libQt5Core.so.5 #8 0x00007f5f0130a464 in start_thread () from /usr/lib/libpthread.so.0 #9 0x00007f5f0846412d in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f5f08a47800 (LWP 18156)): [KCrash Handler] #6 0x00007f5efab4c2b9 in mdb_txn_abort () from /usr/lib/liblmdb.so #7 0x00007f5efab4c2c7 in mdb_txn_abort () from /usr/lib/liblmdb.so #8 0x00007f5efab4c2c7 in mdb_txn_abort () from /usr/lib/liblmdb.so #9 0x00007f5efab4c2c7 in mdb_txn_abort () from /usr/lib/liblmdb.so #10 0x00007f5eff5bca37 in Baloo::Database::open(Baloo::Database::OpenMode) () from /usr/lib/libKF5BalooEngine.so.5 #11 0x00007f5f05ace576 in Baloo::File::load() () from /usr/lib/libKF5Baloo.so.5 #12 0x00007f5f06069e96 in ?? () from /usr/lib/libKF5BalooWidgets.so.5 #13 0x00007f5f03461231 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #14 0x00007f5f03d2298c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x00007f5f03d27e66 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x00007f5f03431beb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #17 0x00007f5f03433fe6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #18 0x00007f5f03488183 in ?? () from /usr/lib/libQt5Core.so.5 #19 0x00007f5efd6a9a1d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #20 0x00007f5efd6a9d08 in ?? () from /usr/lib/libglib-2.0.so.0 #21 0x00007f5efd6a9dbc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #22 0x00007f5f0348858f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #23 0x00007f5f0342f5ba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #24 0x00007f5f0343757c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #25 0x00007f5f0877d0c4 in kdemain () from /usr/lib/libkdeinit5_dolphin.so #26 0x00007f5f0839b610 in __libc_start_main () from /usr/lib/libc.so.6 #27 0x0000000000400789 in _start () Reported using DrKonqi
Thanks for the bug report. Looks like a Baloo issue. Could you try to hide the Information Panel (e.g., by pressing F11) and check if that works around the crash?
*** This bug has been marked as a duplicate of bug 365758 ***