Bug 226164

Summary: Dolphin crashed while I copied files on the commandline
Product: [Applications] dolphin Reporter: lkorsager
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 lkorsager 2010-02-10 17:44:15 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-17-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I cancel copying in dolphin, and started using the commandline.
During the copy dolphin crashed.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  KIO::Slave::deref (this=0x9795580) at ../../kio/kio/slave.cpp:242
#7  0x003b7af6 in KIO::Slave::gotInput (this=0x9795580) at ../../kio/kio/slave.cpp:335
#8  0x003b9ee3 in KIO::Slave::qt_metacall (this=0x9795580, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbffe861c) at ./slave.moc:76
#9  0x051e9263 in QMetaObject::activate (sender=0x9513e00, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#10 0x051e9ec2 in QMetaObject::activate (sender=0x9513e00, m=0x4aa8a0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#11 0x002c1f97 in KIO::Connection::readyRead (this=0x9513e00) at ./connection.moc:86
#12 0x002c3d5e in KIO::ConnectionPrivate::dequeue (this=0x978fdb8) at ../../kio/kio/connection.cpp:82
#13 0x002c3e8e in KIO::Connection::qt_metacall (this=0x9513e00, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x9aebf50) at ./connection.moc:73
#14 0x051e1f0b in QMetaCallEvent::placeMetaCall (this=0x9ad4b60, object=0x9513e00) at kernel/qobject.cpp:477
#15 0x051e35fe in QObject::event (this=0x9513e00, e=0x9ad4b60) at kernel/qobject.cpp:1111
#16 0x05886f54 in QApplicationPrivate::notify_helper (this=0x9512218, receiver=0x9513e00, e=0x9ad4b60) at kernel/qapplication.cpp:4056
#17 0x0588e67c in QApplication::notify (this=0xbffe8ebc, receiver=0x9513e00, e=0x9ad4b60) at kernel/qapplication.cpp:3603
#18 0x008acbfa in KApplication::notify (this=0xbffe8ebc, receiver=0x9513e00, event=0x9ad4b60) at ../../kdeui/kernel/kapplication.cpp:302
#19 0x051d36cb in QCoreApplication::notifyInternal (this=0xbffe8ebc, receiver=0x9513e00, event=0x9ad4b60) at kernel/qcoreapplication.cpp:610
#20 0x051d42b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x94ebe48) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x94ebe48) at kernel/qcoreapplication.cpp:1247
#22 0x051d447d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#23 0x051fe3ff in QCoreApplication::sendPostedEvents (s=0x9514660) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#24 postEventSourceDispatch (s=0x9514660) at kernel/qeventdispatcher_glib.cpp:210
#25 0x03dd4e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0x03dd8730 in ?? () from /lib/libglib-2.0.so.0
#27 0x03dd8863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0x051fe02c in QEventDispatcherGlib::processEvents (this=0x94eba30, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#29 0x05927be5 in QGuiEventDispatcherGlib::processEvents (this=0x94eba30, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#30 0x051d1c79 in QEventLoop::processEvents (this=0xbffe8e14, flags=) at kernel/qeventloop.cpp:149
#31 0x051d20ca in QEventLoop::exec (this=0xbffe8e14, flags=...) at kernel/qeventloop.cpp:201
#32 0x051d453f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#33 0x05886dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#34 0x0807a745 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-10 20:49:02 UTC
This was tracked at bug 215328 (bug 191589) and fixed on KDE SC 4.4. 
Regards

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