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: I know this is a duplicate of bug #192976, but I love this crash handler... At any rate, I canceled a copy operation from my HDD to a USB flash drive from the notification icon in the system tray while Dolphin had a question dialog open asking whether to overwrite file(s). After canceling the job and then pressing "Overwrite All," Dolphin crashed. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #5 0x00007fc5d463faa4 in QObject::killTimer(int) () from /usr/lib/libQtCore.so.4 #6 0x00007fc5d464bc43 in QTimer::setInterval(int) () from /usr/lib/libQtCore.so.4 #7 0x00007fc5d464bd49 in QTimer::start(int) () from /usr/lib/libQtCore.so.4 #8 0x00007fc5d766c6b1 in ?? () from /usr/lib/libkio.so.5 #9 0x00007fc5d7667d87 in KIO::CopyJob::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #10 0x00007fc5d4646ddc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #11 0x00007fc5d5841af2 in KJob::result(KJob*) () from /usr/lib/libkdecore.so.5 #12 0x00007fc5d5841e6f in KJob::emitResult() () from /usr/lib/libkdecore.so.5 #13 0x00007fc5d7697d93 in KIO::SimpleJob::slotFinished() () from /usr/lib/libkio.so.5 #14 0x00007fc5d7698912 in KIO::StatJob::slotFinished() () from /usr/lib/libkio.so.5 #15 0x00007fc5d76976a5 in KIO::StatJob::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #16 0x00007fc5d4646ddc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #17 0x00007fc5d7758a81 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /usr/lib/libkio.so.5 #18 0x00007fc5d7755333 in KIO::SlaveInterface::dispatch() () from /usr/lib/libkio.so.5 #19 0x00007fc5d774814d in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5 #20 0x00007fc5d774a26c in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #21 0x00007fc5d4646ddc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #22 0x00007fc5d7664f57 in ?? () from /usr/lib/libkio.so.5 #23 0x00007fc5d766507d in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #24 0x00007fc5d46410f9 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #25 0x00007fc5d4ac4efc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #26 0x00007fc5d4acc1ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #27 0x00007fc5d5df9ab6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #28 0x00007fc5d4631c2c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #29 0x00007fc5d463280a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #30 0x00007fc5d465a533 in ?? () from /usr/lib/libQtCore.so.4 #31 0x00007fc5d014fbbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #32 0x00007fc5d0153588 in ?? () from /lib/libglib-2.0.so.0 #33 0x00007fc5d01536b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #34 0x00007fc5d465a1a6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #35 0x00007fc5d4b594be in ?? () from /usr/lib/libQtGui.so.4 #36 0x00007fc5d4630532 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #37 0x00007fc5d4630904 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #38 0x00007fc5d4632ab9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #39 0x0000000000439555 in _start () This bug may be a duplicate of or related to bug 211799 Reported using DrKonqi
> I know this is a duplicate of bug #192976 Agreed. Note that you don't have to report a bug again if you're sure that it's a duplicate - you can also vote for the old bug report if you want to raise attention for it, or you can add a comment if you have any additional information. *** This bug has been marked as a duplicate of bug 192976 ***