Application that crashed: dolphin Version of the application: 1.3 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.2 Operating System: Linux 2.6.28-15-generic i686 Distribution: Ubuntu 9.04 What I was doing when the application crashed: I was performing a series of cut/paste operations throughout various directories on a SMB mounted share. Just before the crash, I believe I noticed that files were being pasted that were not "cut" immediately before, but in the previous cut operation. Then I got a message "Dolphin cannot set file permissions on file ..." which I hadn't seen during any of the previous operations (it does happen with this filesystem though). Then poof. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #6 KIO::Slave::deref (this=0xa054898) at /build/buildd/kde4libs-4.3.1/kio/kio/slave.cpp:242 #7 0xb7f65b3c in KIO::Slave::gotInput (this=0xa054898) at /build/buildd/kde4libs-4.3.1/kio/kio/slave.cpp:335 #8 0xb7f67fc3 in KIO::Slave::qt_metacall (this=0xa054898, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfb8ee18) at /build/buildd/kde4libs-4.3.1/obj-i486-linux-gnu/kio/slave.moc:76 #9 0xb68471b8 in QMetaObject::activate (sender=0x9eed388, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #10 0xb6847e42 in QMetaObject::activate (sender=0x9eed388, m=0xb8053880, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #11 0xb7e71697 in KIO::Connection::readyRead (this=0x9eed388) at /build/buildd/kde4libs-4.3.1/obj-i486-linux-gnu/kio/connection.moc:86 #12 0xb7e73003 in KIO::ConnectionPrivate::dequeue (this=0x9ca2960) at /build/buildd/kde4libs-4.3.1/kio/kio/connection.cpp:82 #13 0xb7e733e6 in KIO::Connection::qt_metacall (this=0x9eed388, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x9cde4d0) at /build/buildd/kde4libs-4.3.1/obj-i486-linux-gnu/kio/connection.moc:73 #14 0xb68408cb in QMetaCallEvent::placeMetaCall (this=0xa9998d0, object=0x9eed388) at kernel/qobject.cpp:477 #15 0xb68423b0 in QObject::event (this=0x9eed388, e=0xa9998d0) at kernel/qobject.cpp:1111 #16 0xb6a48d3c in QApplicationPrivate::notify_helper (this=0x9b16d98, receiver=0x9eed388, e=0xa9998d0) at kernel/qapplication.cpp:4056 #17 0xb6a5103e in QApplication::notify (this=0xbfb8f5c4, receiver=0x9eed388, e=0xa9998d0) at kernel/qapplication.cpp:3603 #18 0xb778f85d in KApplication::notify (this=0xbfb8f5c4, receiver=0x9eed388, event=0xa9998d0) at /build/buildd/kde4libs-4.3.1/kdeui/kernel/kapplication.cpp:302 #19 0xb6831bcb in QCoreApplication::notifyInternal (this=0xbfb8f5c4, receiver=0x9eed388, event=0xa9998d0) at kernel/qcoreapplication.cpp:610 #20 0xb6832825 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9af2b38) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #21 0xb6832a1d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #22 0xb685d6af in postEventSourceDispatch (s=0x9b12510) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #23 0xb5fadb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0xb5fb10eb in ?? () from /usr/lib/libglib-2.0.so.0 #25 0xb5fb1268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0xb685d2f8 in QEventDispatcherGlib::processEvents (this=0x9af2d10, flags={i = -1078397784}) at kernel/qeventdispatcher_glib.cpp:327 #27 0xb6aeaa75 in QGuiEventDispatcherGlib::processEvents (this=0x9af2d10, flags={i = -1078397736}) at kernel/qguieventdispatcher_glib.cpp:202 #28 0xb68301fa in QEventLoop::processEvents (this=0xbfb8f550, flags={i = -1078397672}) at kernel/qeventloop.cpp:149 #29 0xb6830642 in QEventLoop::exec (this=0xbfb8f550, flags={i = -1078397608}) at kernel/qeventloop.cpp:201 #30 0xb6832ae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #31 0xb6a48bb7 in QApplication::exec () at kernel/qapplication.cpp:3525 #32 0x0807aaff in main (argc=5, argv=0xbfb8f774) at /build/buildd/kdebase-4.3.1/apps/dolphin/src/main.cpp:94 This bug may be a duplicate of or related to bug 204403 Reported using DrKonqi
Merging with bug 191589. Thanks *** This bug has been marked as a duplicate of bug 191589 ***