Bug 170787

Summary:	crash after changing kget settings
Product:	[Applications] kget	Reporter:	masat <yankuic>
Component:	general	Assignee:	KGet authors <kget>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	uwolfer
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Other
Latest Commit:		Version Fixed In:

Description masat 2008-09-10 04:07:51 UTC

Version:            (using KDE 4.1.1)
OS:                Other
Installed from:    Unspecified

Application: KGet (kget), signal SIGSEGV
[?1034h(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 0xb63ea6d0 (LWP 7087)]
(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)
(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  0xb786bf9a in KJob::percent () from /usr/lib/libkdecore.so.5
#7  0xb7ccdd92 in KGet::reloadKJobs () from /usr/lib/libkgetcore.so.4
#8  0x0808f472 in _start ()
#0  0xffffe430 in __kernel_vsyscall ()

Comment 1 Urs Wolfer 2008-09-10 18:56:08 UTC

How can you reproduce this crash exactly?

The posted backtrace is unusable; please see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Comment 2 Urs Wolfer 2008-09-14 11:40:10 UTC

Comment by masat (masat, please try to answer in the bugtracker directely instead of writing a private mail :) ):
This crash report was generated after I try to configure Kget. For example enabling o disabling  KDE global progress tracking. It fixed after upgrade to KDE 4.1.2 "release 33.1" 

Sorry if I didn't explain my self, I newbie in linux and I cant write English very well 

regards
yan

Comment 3 Urs Wolfer 2008-09-14 11:41:05 UTC


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