Bug 212134 - Dolphin crash after canceled file copy
Summary: Dolphin crash after canceled file copy
Status: RESOLVED DUPLICATE of bug 192976
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-28 02:10 UTC by root
Modified: 2009-10-28 13:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description root 2009-10-28 02:10:57 UTC
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.30-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (squeeze)

What I was doing when the application crashed:
I cancelled a file copy via the notification and jobs system. A message that dolphin was unable to read the file appeared. As I clicked the Cancel button dolphin crashed. And yes, the file is really corrupt. The crash does not occur when I stop the copy only a short time after it started. The corruption of the file starts at 2,5GB. If I do not stop the copy the failed to read message will eventually appear and dolphin will not crash.

I'd like to mark this as a duplicate of 192976 but the assistant won't show it to me.
But I really love this crash handler :-)

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  0x00007f9d746b44a4 in QObject::killTimer (this=0x2c160e0, id=-1593771888) at kernel/qobject.cpp:1513
#6  0x00007f9d746c0623 in QTimer::setInterval (this=0x2c160e0, msec=200) at kernel/qtimer.cpp:362
#7  0x00007f9d746c0719 in QTimer::start (this=0x2c160e0, msec=-1593771888) at kernel/qtimer.cpp:214
#8  0x00007f9d77732f77 in KIO::CopyJobPrivate::slotResultConflictCopyingFiles (this=0x2c3fcf0, job=0x2c5af80) at ../../kio/kio/copyjob.cpp:1264
#9  0x00007f9d77733d14 in KIO::CopyJobPrivate::slotResultCopyingFiles (this=0x2c3fcf0, job=0x2c5af80) at ../../kio/kio/copyjob.cpp:1133
#10 0x00007f9d7772e9fc in KIO::CopyJob::qt_metacall (this=0x2c279b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa100fe70) at ./copyjob.moc:115
#11 0x00007f9d746bb682 in QMetaObject::activate (sender=0x2c5af80, from_signal_index=<value optimized out>, to_signal_index=7, argv=0x2c7a520) at kernel/qobject.cpp:3112
#12 0x00007f9d75914df2 in KJob::result (this=0x2c160e0, _t1=0x2c5af80) at ./kjob.moc:188
#13 0x00007f9d7591516f in KJob::emitResult (this=0x2c5af80) at ../../kdecore/jobs/kjob.cpp:304
#14 0x00007f9d77766c5b in KIO::FileCopyJob::slotResult (this=0x2c5af80, job=0x2c4f900) at ../../kio/kio/job.cpp:2202
#15 0x00007f9d7776216c in KIO::FileCopyJob::qt_metacall (this=0x2c5af80, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa1010000) at ./jobclasses.moc:673
#16 0x00007f9d746bb682 in QMetaObject::activate (sender=0x2c4f900, from_signal_index=<value optimized out>, to_signal_index=7, argv=0x2c7a520) at kernel/qobject.cpp:3112
#17 0x00007f9d75914df2 in KJob::result (this=0x2c160e0, _t1=0x2c4f900) at ./kjob.moc:188
#18 0x00007f9d7591516f in KJob::emitResult (this=0x2c4f900) at ../../kdecore/jobs/kjob.cpp:304
#19 0x00007f9d77762af0 in KIO::SimpleJob::slotFinished (this=0x2c4f900) at ../../kio/kio/job.cpp:477
#20 0x00007f9d7775d907 in KIO::SimpleJob::slotError (this=0x2c4f900, err=<value optimized out>, errorText=...) at ../../kio/kio/job.cpp:489
#21 0x00007f9d7775dada in KIO::SimpleJob::qt_metacall (this=0x2c4f900, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa10102f0) at ./jobclasses.moc:158
#22 0x00007f9d7775db06 in KIO::DirectCopyJob::qt_metacall (this=0x2c160e0, _c=2701195408, _id=46432144, _a=0x2c7a520) at ./job_p.moc:145
#23 0x00007f9d746bb682 in QMetaObject::activate (sender=0x259d500, from_signal_index=<value optimized out>, to_signal_index=6, argv=0x2c7a520) at kernel/qobject.cpp:3112
#24 0x00007f9d7781c4e6 in KIO::SlaveInterface::error (this=0x2c160e0, _t1=128, _t2=<value optimized out>) at ./slaveinterface.moc:153
#25 0x00007f9d7781fe49 in KIO::SlaveInterface::dispatch (this=0x259d500, _cmd=102, rawdata=<value optimized out>) at ../../kio/kio/slaveinterface.cpp:208
#26 0x00007f9d7781c7e2 in KIO::SlaveInterface::dispatch (this=0x259d500) at ../../kio/kio/slaveinterface.cpp:91
#27 0x00007f9d7780f24e in KIO::Slave::gotInput (this=0x259d500) at ../../kio/kio/slave.cpp:322
#28 0x00007f9d77811578 in KIO::Slave::qt_metacall (this=0x259d500, _c=QMetaObject::InvokeMetaMethod, _id=-1593833617, _a=0x7fffa10106f0) at ./slave.moc:76
#29 0x00007f9d746bb682 in QMetaObject::activate (sender=0x2968a60, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x2c7a520) at kernel/qobject.cpp:3112
#30 0x00007f9d7772b9c1 in KIO::ConnectionPrivate::dequeue (this=0x2993f00) at ../../kio/kio/connection.cpp:82
#31 0x00007f9d7772be1a in KIO::Connection::qt_metacall (this=0x2968a60, _c=QMetaObject::InvokeMetaMethod, _id=-1593833617, _a=0x2afafd0) at ./connection.moc:73
#32 0x00007f9d746b5f68 in QObject::event (this=0x2968a60, e=0x258fae0) at kernel/qobject.cpp:1110
#33 0x00007f9d74b7380d in QApplicationPrivate::notify_helper (this=0x251d490, receiver=0x2968a60, e=0x258fae0) at kernel/qapplication.cpp:4056
#34 0x00007f9d74b7b86a in QApplication::notify (this=0x7fffa1011140, receiver=0x2968a60, e=0x258fae0) at kernel/qapplication.cpp:4021
#35 0x00007f9d75ec543b in KApplication::notify (this=0x7fffa1011140, receiver=0x2968a60, event=0x258fae0) at ../../kdeui/kernel/kapplication.cpp:302
#36 0x00007f9d746a651c in QCoreApplication::notifyInternal (this=0x7fffa1011140, receiver=0x2968a60, event=0x258fae0) at kernel/qcoreapplication.cpp:610
#37 0x00007f9d746a7164 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x24f7f80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#38 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x24f7f80) at kernel/qcoreapplication.cpp:1247
#39 0x00007f9d746cef73 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#40 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210
#41 0x00007f9d705f612a in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#42 0x00007f9d705f9988 in ?? () from /lib/libglib-2.0.so.0
#43 0x00007f9d705f9b3c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#44 0x00007f9d746cebff in QEventDispatcherGlib::processEvents (this=0x24f7790, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#45 0x00007f9d74c0a64f in QGuiEventDispatcherGlib::processEvents (this=0x2c160e0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#46 0x00007f9d746a4de2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#47 0x00007f9d746a51b4 in QEventLoop::exec (this=0x7fffa10110b0, flags=...) at kernel/qeventloop.cpp:201
#48 0x00007f9d746a7424 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#49 0x000000000043953d in main (argc=6, argv=0x7fffa1011628) at ../../../../apps/dolphin/src/main.cpp:94

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

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-10-28 09:27:08 UTC
Thanks for the bug report!

> I'd like to mark this as a duplicate of 192976 but the assistant won't show it
> to me.

I agree, it looks like a duplicate. Note that you don't actually have to report a crash again if you know that it's a duplicate of something that has been reported already. If you want to raise more attention for the original report, you can vote for it.

> But I really love this crash handler :-)

I think Darío will be glad to hear that :-)

*** This bug has been marked as a duplicate of bug 192976 ***
Comment 2 Dario Andres 2009-10-28 13:02:08 UTC
Thanks for the comments :)
In any case, the crash handler in KDE4.4 now let the user select a custom bug report number to mark as possible duplicate or simply attach new information to it. 
Regards