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-14-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: Transfered 235MB with 1600 files to folder on Lacie NAS, instant crash, seems to seg where it polls number of files and calculating transfer -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #5 0x00007f5f79e64987 in KDirListerCache::slotUpdateResult (this=0x20e1a10, j=<value optimized out>) at ../../kio/kio/kdirlister.cpp:1539 #6 0x00007f5f79e66d73 in KDirListerCache::qt_metacall (this=0x20e1a10, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffe398b870) at ./kdirlister_p.moc:102 #7 0x00007f5f76de5ddc in QMetaObject::activate (sender=0x26526e0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x20d6020) at kernel/qobject.cpp:3113 #8 0x00007f5f77fe0af2 in KJob::result (this=0x26dec80, _t1=0x26526e0) at ./kjob.moc:188 #9 0x00007f5f77fe0e6f in KJob::emitResult (this=0x26526e0) at ../../kdecore/jobs/kjob.cpp:304 #10 0x00007f5f79e36d93 in KIO::SimpleJob::slotFinished (this=0x26526e0) at ../../kio/kio/job.cpp:477 #11 0x00007f5f79e36ed0 in KIO::ListJob::slotFinished (this=0x26526e0) at ../../kio/kio/job.cpp:2408 #12 0x00007f5f79e3e9d9 in KIO::ListJob::qt_metacall (this=0x26526e0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffe398bba0) at ./jobclasses.moc:764 #13 0x00007f5f76de5ddc in QMetaObject::activate (sender=0x25b4b90, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x20d6020) at kernel/qobject.cpp:3113 #14 0x00007f5f79ef7a81 in KIO::SlaveInterface::dispatch (this=0x25b4b90, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175 #15 0x00007f5f79ef4333 in KIO::SlaveInterface::dispatch (this=0x25b4b90) at ../../kio/kio/slaveinterface.cpp:91 #16 0x00007f5f79ee714d in KIO::Slave::gotInput (this=0x25b4b90) at ../../kio/kio/slave.cpp:322 #17 0x00007f5f79ee926c in KIO::Slave::qt_metacall (this=0x25b4b90, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffe398bf60) at ./slave.moc:76 #18 0x00007f5f76de5ddc in QMetaObject::activate (sender=0x261aa00, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x20d6020) at kernel/qobject.cpp:3113 #19 0x00007f5f79e03f57 in KIO::ConnectionPrivate::dequeue (this=0x1ebaf90) at ../../kio/kio/connection.cpp:82 #20 0x00007f5f79e0407d in KIO::Connection::qt_metacall (this=0x261aa00, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x21e9590) at ./connection.moc:73 #21 0x00007f5f76de00f9 in QObject::event (this=0x261aa00, e=0x24342a0) at kernel/qobject.cpp:1111 #22 0x00007f5f77263efc in QApplicationPrivate::notify_helper (this=0x1ec2c70, receiver=0x261aa00, e=0x24342a0) at kernel/qapplication.cpp:4056 #23 0x00007f5f7726b1ce in QApplication::notify (this=0x7fffe398c910, receiver=0x261aa00, e=0x24342a0) at kernel/qapplication.cpp:4021 #24 0x00007f5f78598ab6 in KApplication::notify (this=0x7fffe398c910, receiver=0x261aa00, event=0x24342a0) at ../../kdeui/kernel/kapplication.cpp:302 #25 0x00007f5f76dd0c2c in QCoreApplication::notifyInternal (this=0x7fffe398c910, receiver=0x261aa00, event=0x24342a0) at kernel/qcoreapplication.cpp:610 #26 0x00007f5f76dd180a in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x1e904d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #27 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x1e904d0) at kernel/qcoreapplication.cpp:1247 #28 0x00007f5f76df9533 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #29 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210 #30 0x00007f5f728eebbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #31 0x00007f5f728f2588 in ?? () from /lib/libglib-2.0.so.0 #32 0x00007f5f728f26b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #33 0x00007f5f76df91a6 in QEventDispatcherGlib::processEvents (this=0x1e8fd20, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #34 0x00007f5f772f84be in QGuiEventDispatcherGlib::processEvents (this=0x26dec80, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #35 0x00007f5f76dcf532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #36 0x00007f5f76dcf904 in QEventLoop::exec (this=0x7fffe398c860, flags=) at kernel/qeventloop.cpp:201 #37 0x00007f5f76dd1ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #38 0x0000000000439555 in _start () Reported using DrKonqi
This looks a lot like bug 197851 - Does Dolphin always crash when trying to repeat the situation ? Thanks
the symptoms of 197851 are different, this is not a MS Shared directory & my bug happened after i started transferring, i can log in as per normal and do whatever i want, but the debug trace looks very similar. I tried to repeat the bug but it didn't happen again, still this system is a fresh kubuntu install.
Hi, Has there been trouble replicating this? Regards, helpdesk -----Original Message----- From: bugzilla_noreply@kde.org [mailto:bugzilla_noreply@kde.org] On Behalf Of Dario Andres Sent: Tuesday, December 15, 2009 8:42 AM To: helpdesk@ipfocus.com.au Subject: [Bug 214918] Transfering Data to Lacie NAS, files were ranging from1KB to 25MB in total 235MB many sub folders[KDirListerCache::slotUpdateResult] https://bugs.kde.org/show_bug.cgi?id=214918 Dario Andres <andresbajotierra@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Transfering Data to Lacie |Transfering Data to Lacie |NAS, files were ranging |NAS, files were ranging |from 1KB to 25MB in total |from 1KB to 25MB in total |235MB many sub folders |235MB many sub folders | |[KDirListerCache::slotUpdat | |eResult]
I couldn't check it as I don't have the hardware, but may be some other developer can do it. Regards
This does look like the exact same crash as bug 197851 to me (which I'm about to fix). Are you sure you're not accessing the NAS via a samba share, using a smb: URL? That would be pretty equivalent to a MS Windows share.
Waiting for feedback.