Bug 173184

Summary:	Kget crashes when closing individual download windows
Product:	[Applications] kget	Reporter:	Mauro Civitillo <maurocivi>
Component:	general	Assignee:	KGet bugs <kget-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	crash
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Mauro Civitillo 2008-10-20 10:52:57 UTC

Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Slackware Packages

When I click con the "close" button (on the title bar) of a download, KGet crashes with the followin message (translated from italian language):

This backtrace seems to be useless.
Probably the packages you are using have been compiled without support for correct backtraces or the stack frame has been severely damaged during the crash.

(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 0xb62726d0 (LWP 3396)]
(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)
(no debugging symbols found)
(no debugging symbols found)
0xb668a77b in __nanosleep_nocancel () from /lib/libc.so.6
[Current thread is 0 (process 3396)]

Thread 1 (Thread 0xb62726d0 (LWP 3396)):
#0  0xb668a77b in __nanosleep_nocancel () from /lib/libc.so.6
#1  0xb668a5ba in sleep () from /lib/libc.so.6
#2  0xb7e8a9bd in ?? () from /usr/lib/libkdeui.so.5
#3  0x00000001 in ?? ()
#4  0x00000000 in ?? ()
#0  0xb668a77b in __nanosleep_nocancel () from /lib/libc.so.6

Comment 1 Pino Toscano 2008-10-20 12:45:47 UTC

Hello,

as the message says, the backtrace is not useful. You can find in
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
instructions on how to get a more detailed one.

Thanks!

Comment 2 Lukas Appelhans 2008-12-13 14:37:33 UTC

I will close this, since we cannot fix it with the current information. Please reopen it if you get a better backtrace.

Lukas