Version: 2.1.0 (using 4.1.00 (KDE 4.1.0), Kubuntu packages) Compiler: gcc OS: Linux (i686) release 2.6.24-21-generic When KDE "global progress tracking" is enabled and switched to "show every single download", when kget is downloading a file changing it to "show overall progress" would crash kget. Backtrace: Program: KGet (kget), sygnał SIGSEGV (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb5f76940 (LWP 13938)] [KCrash handler] #6 0xb7692ec9 in QMetaObject::indexOfSignal () from /usr/lib/libQtCore.so.4 #7 0xb76a2807 in QObject::disconnect () from /usr/lib/libQtCore.so.4 #8 0xb786ea3d in KJobTrackerInterface::unregisterJob (this=0x8421450, job=0x83952a8) at /build/buildd/kde4libs-4.1.0/kdecore/jobs/kjobtrackerinterface.cpp:82 #9 0xb7d8c5f4 in KAbstractWidgetJobTracker::unregisterJob (this=0x8421450, job=0x83952a8) at /build/buildd/kde4libs-4.1.0/kdeui/jobs/kabstractwidgetjobtracker.cpp:50 #10 0xb7d8f179 in KWidgetJobTracker::unregisterJob (this=0x8421450, job=0x83952a8) at /build/buildd/kde4libs-4.1.0/kdeui/jobs/kwidgetjobtracker.cpp:93 #11 0xb7bcfc5c in ?? () from /usr/lib/kde4/lib/libkgetcore.so.4 #12 0xb7bb95f2 in KGet::reloadKJobs () from /usr/lib/kde4/lib/libkgetcore.so.4 #13 0x0808de75 in ?? () #14 0x0808fb3d in ?? () #15 0xb76a14f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0xb76a1bc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #17 0xb7cfdf93 in KConfigDialog::settingsChanged (this=0x8494cb0, _t1=@0xbf8fac08) at /build/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kdeui/kconfigdialog.moc:103 #18 0xb7cfe537 in KConfigDialog::KConfigDialogPrivate::_k_settingsChangedSlot (this=0x85af938) at /build/buildd/kde4libs-4.1.0/kdeui/dialogs/kconfigdialog.cpp:243 #19 0xb7cfe7b5 in KConfigDialog::qt_metacall (this=0x8494cb0, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbf8face8) at /build/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kdeui/kconfigdialog.moc:86 #20 0x080627af in _start () #0 0xb7f08410 in __kernel_vsyscall () Hope this helps. ;)
This is a duplicate of bug 168006
*** This bug has been marked as a duplicate of 168006 ***