Bug 177243 - Kget Crash while changing settings
Summary: Kget Crash while changing settings
Status: RESOLVED DUPLICATE of bug 168006
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-08 18:38 UTC by Shashwat
Modified: 2008-12-08 19:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shashwat 2008-12-08 18:38:55 UTC
Version:           2.1.3 (using KDE 4.1.3)
OS:                Linux
Installed from:    Mandriva RPMs

Kget crashed 2 times . 1. While Changing settings

2. WHile closing KDE Global Process Tracking

Here is the back trace

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)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5f0b6d0 (LWP 3799)]
(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  0xb773831c in QObject::disconnect () from /usr/lib/libQtCore.so.4
#7  0xb78d9f3a in KJobTrackerInterface::unregisterJob ()
   from /usr/lib/libkdecore.so.5
#8  0xb7ea27c3 in KAbstractWidgetJobTracker::unregisterJob ()
   from /usr/lib/libkdeui.so.5
#9  0xb7ea579e in KWidgetJobTracker::unregisterJob ()
   from /usr/lib/libkdeui.so.5
#10 0xb7ce16f3 in ?? () from /usr/lib/libkgetcore.so.4
#11 0xb7ccc6ff in KGet::reloadKJobs () from /usr/lib/libkgetcore.so.4
#12 0x0808f2fa in _start ()


Hope it'll get fixed :)

Regards
Comment 1 FiNeX 2008-12-08 18:43:35 UTC
Is the backtrace the same for both crashes? If you can reproduce the crash, 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 Lukas Appelhans 2008-12-08 19:12:56 UTC

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