Bug 215484 - Dolphin crashed in Kubuntu Karmic
Summary: Dolphin crashed in Kubuntu Karmic
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-11-20 21:58 UTC by mrl586
Modified: 2009-12-14 16:00 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 mrl586 2009-11-20 21:58:43 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-15-generic x86_64
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f97838eaaa8 in QObject::killTimer (this=0x2daf9d0, id=0) at kernel/qobject.cpp:1514
#6  0x00007f97838f6c43 in QTimer::setInterval (this=0x2daf9d0, msec=200) at kernel/qtimer.cpp:362
#7  0x00007f97838f6d49 in QTimer::start (this=0x2daf9d0, msec=0) at kernel/qtimer.cpp:214
#8  0x00007f9786918737 in KIO::CopyJobPrivate::slotResultConflictCreatingDirs (this=0x2813d90, job=<value optimized out>) at ../../kio/kio/copyjob.cpp:948
#9  0x00007f9786912da7 in KIO::CopyJob::qt_metacall (this=0x333de70, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff441a72c0) at ./copyjob.moc:115
#10 0x00007f97838f1ddc in QMetaObject::activate (sender=0x3352d70, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x90a10) at kernel/qobject.cpp:3113
#11 0x00007f9784aecb22 in KJob::result (this=0x2daf9d0, _t1=0x3352d70) at ./kjob.moc:188
#12 0x00007f9784aece9f in KJob::emitResult (this=0x3352d70) at ../../kdecore/jobs/kjob.cpp:304
#13 0x00007f9786942e33 in KIO::SimpleJob::slotFinished (this=0x3352d70) at ../../kio/kio/job.cpp:477
#14 0x00007f97869439b2 in KIO::StatJob::slotFinished (this=0x3352d70) at ../../kio/kio/job.cpp:823
#15 0x00007f9786942745 in KIO::StatJob::qt_metacall (this=0x3352d70, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff441a75b0) at ./jobclasses.moc:234
#16 0x00007f97838f1ddc in QMetaObject::activate (sender=0x3299f40, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x90a10) at kernel/qobject.cpp:3113
#17 0x00007f9786a03b31 in KIO::SlaveInterface::dispatch (this=0x3299f40, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#18 0x00007f9786a003e3 in KIO::SlaveInterface::dispatch (this=0x3299f40) at ../../kio/kio/slaveinterface.cpp:91
#19 0x00007f97869f31fd in KIO::Slave::gotInput (this=0x3299f40) at ../../kio/kio/slave.cpp:322
#20 0x00007f97869f531c in KIO::Slave::qt_metacall (this=0x3299f40, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff441a7970) at ./slave.moc:76
#21 0x00007f97838f1ddc in QMetaObject::activate (sender=0x3288cf0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x90a10) at kernel/qobject.cpp:3113
#22 0x00007f978690ff77 in KIO::ConnectionPrivate::dequeue (this=0x335d810) at ../../kio/kio/connection.cpp:82
#23 0x00007f978691009d in KIO::Connection::qt_metacall (this=0x3288cf0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x2a59900) at ./connection.moc:73
#24 0x00007f97838ec0f9 in QObject::event (this=0x3288cf0, e=0x31069e0) at kernel/qobject.cpp:1111
#25 0x00007f9783d6fefc in QApplicationPrivate::notify_helper (this=0x2611b70, receiver=0x3288cf0, e=0x31069e0) at kernel/qapplication.cpp:4056
#26 0x00007f9783d771ce in QApplication::notify (this=0x7fff441a8320, receiver=0x3288cf0, e=0x31069e0) at kernel/qapplication.cpp:4021
#27 0x00007f97850a4e56 in KApplication::notify (this=0x7fff441a8320, receiver=0x3288cf0, event=0x31069e0) at ../../kdeui/kernel/kapplication.cpp:302
#28 0x00007f97838dcc2c in QCoreApplication::notifyInternal (this=0x7fff441a8320, receiver=0x3288cf0, event=0x31069e0) at kernel/qcoreapplication.cpp:610
#29 0x00007f97838dd80a in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x25e84d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#30 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x25e84d0) at kernel/qcoreapplication.cpp:1247
#31 0x00007f9783905533 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#32 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210
#33 0x00007f977f3fabbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#34 0x00007f977f3fe588 in ?? () from /lib/libglib-2.0.so.0
#35 0x00007f977f3fe6b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#36 0x00007f97839051a6 in QEventDispatcherGlib::processEvents (this=0x25e7d20, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#37 0x00007f9783e044be in QGuiEventDispatcherGlib::processEvents (this=0x2daf9d0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#38 0x00007f97838db532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#39 0x00007f97838db904 in QEventLoop::exec (this=0x7fff441a8270, flags=) at kernel/qeventloop.cpp:201
#40 0x00007f97838ddab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#41 0x00000000004394e5 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-11-21 03:35:28 UTC
This looks related to bug 214477 / bug 192976 / bug 199532.
- Do you remember what were you doing when the application crashed ?
 - Copying or moving some file ? Did you got the "file conflicts" dialog to select "skip" or "overwrite". Did you manually stopped that transfer? - Do you have some network/drive problems at that time ?
Thanks
Comment 2 mrl586 2009-12-11 06:31:04 UTC
I copying some files and folder. Yes, I got file conflicts dialog and I think that I select overwrite. No, program stop this fransfer itself. No network/drive problem.
Comment 3 David Faure 2009-12-14 16:00:21 UTC

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