Application that crashed: kget Version of the application: 2.3.0 KDE Version: 4.3.00 (KDE 4.3.0) Qt Version: 4.5.2 Operating System: Linux 2.6.30-1-686-bigmem i686 What I was doing when the application crashed: After restarting KDE, Kget tries to download an already finished download from scratch. After cancellation, Kget crashes. -- Backtrace: Application: KGet (kget), signal: Segmentation fault [KCrash Handler] #6 0xb795589a in TransferHandler::changesFlags(TransferObserver*) const () from /usr/lib/libkgetcore.so.4 #7 0xb7948a3e in TransferTreeModel::timerEvent(QTimerEvent*) () from /usr/lib/libkgetcore.so.4 #8 0xb6a47b6f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #9 0xb6f1c7d4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #10 0xb6f2493e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #11 0xb7e1700d in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #12 0xb6a3796b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #13 0xb6a66301 in ?? () from /usr/lib/libQtCore.so.4 #14 0xb6a628a0 in ?? () from /usr/lib/libQtCore.so.4 #15 0xb5fdb368 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #16 0xb5fde8c3 in ?? () from /usr/lib/libglib-2.0.so.0 #17 0xb5fdea48 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #18 0xb6a627f8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #19 0xb6fbbf85 in ?? () from /usr/lib/libQtGui.so.4 #20 0xb6a35fba in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #21 0xb6a36402 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #22 0xb6a38859 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #23 0xb6f1c657 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #24 0x0809f6b5 in _start () Reported using DrKonqi
- Can you reproduce the crash at will again ? Thanks
*** Bug 204839 has been marked as a duplicate of this bug. ***
Should be fixed in latest trunk... Lukas