Bug 201593

Summary: Dolphin crash after closing a window
Product: [Applications] dolphin Reporter: Markus Knetschke <markus.knetschke>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Markus Knetschke 2009-07-26 23:26:46 UTC
Application that crashed: dolphin
Version of the application: 1.3.80
KDE Version: 4.3.61 (KDE 4.3.61 (KDE 4.4 >= 20090717)) "release 3"
Qt Version: 4.5.2
Operating System: Linux 2.6.27.25-0.1-pae i686
Distribution: "openSUSE 11.1 (i586)"

What I was doing when the application crashed:
Dolphin crashed after closing one of three windows...
I can't remember if dolphin tried to generate a preview (reason of link to #187167 )

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  0xb662a0a9 in QMutex::lock (this=0x85535b8) at thread/qmutex.cpp:152
#7  0xb6723e17 in QCoreApplication::postEvent (receiver=0x85e3510, event=0x8182670, priority=0) at kernel/qcoreapplication.cpp:1020
#8  0xb67240dc in QCoreApplication::postEvent (receiver=0x85e3510, event=0x8182670) at kernel/qcoreapplication.cpp:973
#9  0xb67339c7 in QObject::deleteLater (this=0x85e3510) at kernel/qobject.cpp:2019
#10 0xb69c887e in QDragManager::timerEvent (this=0x81bb9d8, e=0xbff43890) at kernel/qdnd_x11.cpp:1267
#11 0xb673472f in QObject::event (this=0x81bb9d8, e=0xbff43890) at kernel/qobject.cpp:1075
#12 0xb693e7fc in QApplicationPrivate::notify_helper (this=0x80e9ad8, receiver=0x81bb9d8, e=0xbff43890) at kernel/qapplication.cpp:4056
#13 0xb6946aee in QApplication::notify (this=0xbff43b54, receiver=0x81bb9d8, e=0xbff43890) at kernel/qapplication.cpp:3603
#14 0xb769d1ad in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#15 0xb672416b in QCoreApplication::notifyInternal (this=0xbff43b54, receiver=0x81bb9d8, event=0xbff43890) at kernel/qcoreapplication.cpp:610
#16 0xb67535f6 in QTimerInfoList::activateTimers (this=0x80ec424) at kernel/qcoreapplication.h:213
#17 0xb674f980 in timerSourceDispatch (source=0x80ec3f0) at kernel/qeventdispatcher_glib.cpp:165
#18 0xb5f1c9c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb5f20083 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0xb5f20241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0xb674f8d8 in QEventDispatcherGlib::processEvents (this=0x80e91c0, flags={i = -1074513352}) at kernel/qeventdispatcher_glib.cpp:327
#22 0xb69decc5 in QGuiEventDispatcherGlib::processEvents (this=0x80e91c0, flags={i = -1074513304}) at kernel/qguieventdispatcher_glib.cpp:202
#23 0xb672278a in QEventLoop::processEvents (this=0xbff43ae0, flags={i = -1074513240}) at kernel/qeventloop.cpp:149
#24 0xb6722bd2 in QEventLoop::exec (this=0xbff43ae0, flags={i = -1074513176}) at kernel/qeventloop.cpp:201
#25 0xb6725079 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0xb693e677 in QApplication::exec () at kernel/qapplication.cpp:3525
#27 0x0807ab7f in _start ()

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

Reported using DrKonqi
Comment 1 Dario Andres 2009-07-28 02:45:22 UTC
Mh, the backtrace are pure Qt functions. Were you doing (or, did you do) some drag&drop operation?
Thanks
Comment 2 Dario Andres 2009-08-26 16:07:18 UTC
Marking as NEEDSINFO
Comment 3 Peter Penz 2010-11-21 11:38:02 UTC

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