Bug 178812 - KGet crashes when options are changed
Summary: KGet crashes when options are changed
Status: RESOLVED DUPLICATE of bug 168006
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-26 17:01 UTC by Geert Poels
Modified: 2008-12-26 17:28 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 Geert Poels 2008-12-26 17:01:51 UTC
Version:           2.1.3 (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

KGet crashed when I change for example the number of simulteous downloads or another option like expandable transfer details.
Important to note : downloads were in progress at that moment.
It's not reproducable all the time, yet very often.
Ubuntu 8.10, default package through synaptic

Application: KGet (kget), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb602f6c0 (LWP 6218)]
[New Thread 0xb454cb90 (LWP 6223)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb7772020 in QObject::disconnect () from /usr/lib/libQtCore.so.4
#7  0xb791f06d in KJobTrackerInterface::unregisterJob ()
   from /usr/lib/libkdecore.so.5
#8  0xb7ef1624 in KAbstractWidgetJobTracker::unregisterJob ()
   from /usr/lib/libkdeui.so.5
#9  0xb7ef43cc in KWidgetJobTracker::unregisterJob ()
   from /usr/lib/libkdeui.so.5
#10 0xb7d18309 in ?? () from /usr/lib/libkgetcore.so.4
#11 0xb7cfd152 in KGet::reloadKJobs () from /usr/lib/libkgetcore.so.4
#12 0x08092542 in _start ()
#0  0xb80cd430 in __kernel_vsyscall ()
Comment 1 FiNeX 2008-12-26 17:24:06 UTC
Hi! If you can reproduce the crash with a more recent KDE version, you should install the debug enabled packages and provide a new backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 2 Dario Andres 2008-12-26 17:28:06 UTC

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