Bug 211163

Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-gentoo-r5 x86_64

What I was doing when the application crashed:
This issue appears to be a duplicate of bug 195988, but I'm using Qt-4.5.3.

I can reproduce the crash by selecting a file that would ordinarily display a thumbnail in the "Information" area. Instead of a preview, the default icon is shown and the crash occurs several seconds later. In ~/.xsession-errors, I found the following:

kdeinit4: preparing to launch /usr/bin/dolphin
[/usr/bin/nepomukservicestub] (ServerCore) new socket connection.
[/usr/bin/nepomukservicestub] (ServerCore) new socket connection.
kdeinit4: preparing to launch /usr/lib64/kde4/kio_trash.so
KCrash: Application 'dolphin' crashing...
kdeinit4: preparing to launch /usr/lib64/kde4/libexec/drkonqi
[/usr/bin/nepomukservicestub] Removing connection
Removing connection

This was working prior to upgrading to kde-4.3.2, but I believe I had all the nepomuk stuff disabled for then though. Regardless of nepomuk's behaviour, crashing on a DBUS timeout isn't the best...

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f6cbf5bbe6a in QMutex::lock (this=0x7f6cb00254b0) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:164
#6  0x00007f6cbf9a0969 in mutex_lock (mutex=0x7f6cb00254b0) at qdbusthread.cpp:69
#7  0x00007f6cb9bdb6ed in _dbus_connection_lock (connection=0x7f6cb000c740) at dbus-connection.c:355
#8  0x00007f6cb9bec85d in _dbus_pending_call_get_connection_and_lock (pending=0x7f6cb000bef0) at dbus-pending-call.c:309
#9  0x00007f6cb9bdfcbf in reply_handler_timeout (data=0x7f6cb00254b0) at dbus-connection.c:3116
#10 0x00007f6cbf981766 in QDBusConnectionPrivate::timerEvent (this=0x21df350, e=0x7fffa2f4fc60) at ./qdbus_symbols_p.h:172
#11 0x00007f6cbf6a0f63 in QObject::event (this=0x21df350, e=0x19) at kernel/qobject.cpp:1066
#12 0x00007f6cbea36bad in QApplicationPrivate::notify_helper (this=0x21f3230, receiver=0x21df350, e=0x7fffa2f4fc60) at kernel/qapplication.cpp:4065
#13 0x00007f6cbea3f47a in QApplication::notify (this=0x7fffa2f4ffa0, receiver=0x21df350, e=0x7fffa2f4fc60) at kernel/qapplication.cpp:4030
#14 0x00007f6cc04ab28b in KApplication::notify (this=0x7fffa2f4ffa0, receiver=0x21df350, event=0x7fffa2f4fc60)
    at /var/tmp/portage/kde-base/kdelibs-4.3.2-r1/work/kdelibs-4.3.2/kdeui/kernel/kapplication.cpp:302
#15 0x00007f6cbf692753 in QCoreApplication::notifyInternal (this=0x7fffa2f4ffa0, receiver=0x21df350, event=0x7fffa2f4fc60) at kernel/qcoreapplication.cpp:606
#16 0x00007f6cbf6ba75e in QTimerInfoList::activateTimers (this=0x21ee2a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 0x00007f6cbf6b73ed in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#18 0x00007f6cbb5846a0 in IA__g_main_context_dispatch (context=0x21ed520) at gmain.c:1824
#19 0x00007f6cbb587d38 in g_main_context_iterate (context=0x21ed520, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2455
#20 0x00007f6cbb587efc in IA__g_main_context_iteration (context=0x21ed520, may_block=1) at gmain.c:2518
#21 0x00007f6cbf6b735f in QEventDispatcherGlib::processEvents (this=0x21c5790, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:328
#22 0x00007f6cbeabc1ef in QGuiEventDispatcherGlib::processEvents (this=0x7f6cb00254b0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007f6cbf691152 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1561002288}) at kernel/qeventloop.cpp:149
#24 0x00007f6cbf6912ec in QEventLoop::exec (this=0x7fffa2f4ff10, flags={i = -1561002208}) at kernel/qeventloop.cpp:197
#25 0x00007f6cbf6932e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x0000000000439b65 in main (argc=5, argv=0x7fffa2f50488) at /var/tmp/portage/kde-base/dolphin-4.3.2-r1/work/dolphin-4.3.2/dolphin/src/main.cpp:94

Reported using DrKonqi