Bug 221189

Summary: Dolphin crashed while viewing folder contents
Product: [Applications] dolphin Reporter: Sam <kingsamses+kde>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sam 2010-01-04 00:29:18 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.31.9-174.fc12.x86_64 x86_64

What I was doing when the application crashed:
I was viewing a folder full of files in Dolphin, trying to decide which to open. I was absent-mindedly moving my mouse rapidly in circles over the icons (Dolphin was in Icon View), when Dolphin crashed. I don't know exactly what caused it and further folder-viewing and mouse-circling has produced no further crashes, so I hope the backtrace is helpful.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
The current source language is "auto; currently asm".
[KCrash Handler]
#5  QMutex::lock (this=0x1000000000016639) at thread/qmutex.cpp:152
#6  0x0000003c62c40229 in mutex_lock (mutex=<value optimized out>) at qdbusthread.cpp:69
#7  0x00000035df80ba5d in _dbus_connection_lock (connection=0x1663d01) at dbus-connection.c:355
#8  0x00000035df81d25d in _dbus_pending_call_get_connection_and_lock (pending=0x7fea5c002760) at dbus-pending-call.c:307
#9  0x00000035df80f40e in reply_handler_timeout (data=0x7fea5c002760) at dbus-connection.c:3156
#10 0x0000003c62c19137 in q_dbus_timeout_handle (timeout=<value optimized out>) at ./qdbus_symbols_p.h:172
#11 QDBusConnectionPrivate::timerEvent (timeout=<value optimized out>) at qdbusintegrator.cpp:1023
#12 0x0000003c6234e08e in QObject::event (this=0x165f370, e=0x7fff8ae2cbc0) at kernel/qobject.cpp:1074
#13 0x0000003c6358f65c in QApplicationPrivate::notify_helper (this=0x1674240, receiver=0x165f370, e=0x7fff8ae2cbc0) at kernel/qapplication.cpp:4065
#14 0x0000003c635968ce in QApplication::notify (this=<value optimized out>, receiver=0x165f370, e=0x7fff8ae2cbc0) at kernel/qapplication.cpp:4030
#15 0x0000003c64c11a66 in KApplication::notify (this=0x7fff8ae2cf10, receiver=0x165f370, event=0x7fff8ae2cbc0) at /usr/src/debug/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302
#16 0x0000003c6233ee6c in QCoreApplication::notifyInternal (this=0x7fff8ae2cf10, receiver=0x165f370, event=0x7fff8ae2cbc0) at kernel/qcoreapplication.cpp:610
#17 0x0000003c623698d2 in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213
#18 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:580
#19 0x0000003c6236729d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#20 0x000000362a63922e in g_main_dispatch (context=<value optimized out>) at gmain.c:1960
#21 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2513
#22 0x000000362a63cc18 in g_main_context_iterate (context=0x166d120, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#23 0x000000362a63cd3a in IA__g_main_context_iteration (context=0x166d120, may_block=1) at gmain.c:2654
#24 0x0000003c623671e6 in QEventDispatcherGlib::processEvents (this=0x16457b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#25 0x0000003c63621ffe in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#26 0x0000003c6233d772 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#27 0x0000003c6233db44 in QEventLoop::exec (this=0x7fff8ae2ce60, flags=...) at kernel/qeventloop.cpp:201
#28 0x0000003c6233fcd9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0x0000000000437025 in _start ()

This bug may be a duplicate of or related to bug 216959

Reported using DrKonqi
Comment 1 Pino Toscano 2010-01-04 11:44:07 UTC

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