Tried invoking dolphin from konsole, This is the message when it crashed.

`Segmentation fault (core dumped)`

Thanks for the bug report. I cannot reproduce the problem. Unfortunately, we cannot do anything about this without a backtrace. You can try to get one with GDB, see https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB for details. Thanks.

Created attachment 95074 [details]
Backtrace.

Steps I followed:  Open Dolphin, navigate to random folder, hit Ctrl+A.  Repeated in gdb to provide backtrace.  

Debug package suggested by gdb unavailable in repos, sorry.

Running OpenSUSE Tumbleweed, latest snapshot available, no funny business with KDE-related repos.

Created attachment 95077 [details]
Valgrind output

Same procedure, now with Valgrind.  Hope this helps.

I'm also seeing an immediate crash when any multiple file selection is made using any method, selection marker, ctrl click, 'lasso' with mouse, or ctrl A.

openSUSE Tumbleweed
Dolphin Version 15.08.0
Using:
KDE Frameworks 5.14.0
Qt 5.5.0 (built against 5.4.2)

Crash reporter is not launched, the only error message appears to be:
paul@Orion-Tumble:~$ dmesg | grep -i dolphin
[  360.638024] dolphin[1744]: segfault at c ip 00007fea68d77180 sp 00007ffc9dae98e8 error 4 in liblmdb-0.9.14.so[7fea68d72000+13000]
paul@Orion-Tumble:~$

I'll try to retrieve a backtrace with GDB later...

(In reply to Paul from comment #5)
> I'll try to retrieve a backtrace with GDB later...

GDB backtrace - sorry only dolphin debug symbols installed.


paul@Orion-Tumble:~$ gdb dolphin

[snip]

(gdb) run
Starting program: /usr/bin/dolphin 
Missing separate debuginfos, use: zypper install glibc-debuginfo-2.22-4.1.x86_64
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
"Trying to convert empty KLocalizedString to QString."
KSambaShare: Could not find smb.conf!
Detaching after fork from child process 2270.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Permission denied
Detaching after fork from child process 2271.
Detaching after fork from child process 2272.
Detaching after fork from child process 2275.
Detaching after fork from child process 2276.
[New Thread 0x7fffcef3a700 (LWP 2264)]
[New Thread 0x7fffe0ce7700 (LWP 2263)]

Program received signal SIGSEGV, Segmentation fault.
0x00007fffe92f8180 in mdb_txn_begin () from /usr/lib64/liblmdb-0.9.14.so
Missing separate debuginfos, use: zypper install Mesa-debuginfo-11.0.2-123.1.x86_64 Mesa-

[snip]

(gdb) thread apply all backtrace

Thread 3 (Thread 0x7fffe0ce7700 (LWP 2263)):
#0  0x00007ffff78471cd in poll () from /lib64/libc.so.6
#1  0x00007fffeab24432 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007fffeab26007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007fffe303ae79 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007ffff1c5ca9f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x00007fffed6434a4 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff784fb5d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fffcef3a700 (LWP 2264)):
#0  0x00007ffff78471cd in poll () from /lib64/libc.so.6
#1  0x00007fffecf0f264 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fffecf0f36c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007ffff1e8133f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
    () from /usr/lib64/libQt5Core.so.5
#4  0x00007ffff1e2b47a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib64/libQt5Core.so.5
#5  0x00007ffff1c57c6c in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x00007ffff1c5ca9f in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x00007fffed6434a4 in start_thread () from /lib64/libpthread.so.0
#8  0x00007ffff784fb5d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ffff7fa28c0 (LWP 2259)):
#0  0x00007fffe92f8180 in mdb_txn_begin () from /usr/lib64/liblmdb-0.9.14.so
#1  0x00007ffff5677abf in Baloo::File::load() () from /usr/lib64/libKF5Baloo.so.5
#2  0x00007ffff5bfee63 in ?? () from /usr/lib64/libKF5BalooWidgets.so.5
#3  0x00007ffff1e5bb89 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#4  0x00007ffff2fa08fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /usr/lib64/libQt5Widgets.so.5
#5  0x00007ffff2fa5a06 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib64/libQt5Widgets.so.5
#6  0x00007ffff1e2db33 in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
   from /usr/lib64/libQt5Core.so.5
#7  0x00007ffff1e2fe56 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) ()
   from /usr/lib64/libQt5Core.so.5
#8  0x00007ffff1e80f33 in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x00007fffecf0f097 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#10 0x00007fffecf0f2c8 in ?? () from /usr/lib64/libglib-2.0.so.0
#11 0x00007fffecf0f36c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#12 0x00007ffff1e8133f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
    () from /usr/lib64/libQt5Core.so.5
#13 0x00007ffff1e2b47a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib64/libQt5Core.so.5
#14 0x00007ffff1e3311d in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#15 0x00007ffff7b6a801 in kdemain (argc=1, argv=<optimized out>)
    at /usr/src/debug/dolphin-15.08.0/src/main.cpp:146
#16 0x00007ffff7786610 in __libc_start_main () from /lib64/libc.so.6
#17 0x00000000004007f9 in _start () at ../sysdeps/x86_64/start.S:118
(gdb) quit

paul@Orion-Tumble:~$

Thanks. Looks like a Baloo issue.

I upgraded to 15.10 and the issue does not exist any more. Looks like the culprit was unknowingly settled.

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