Bug 207694

Summary:	kget crash
Product:	[Applications] kget	Reporter:	sergio <sergio.pastorino>
Component:	general	Assignee:	KGet authors <kget>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	faure, finex
Priority:	NOR	Keywords:	investigated, triaged
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description sergio 2009-09-17 16:52:45 UTC

Version:           4.2.4 (KDE 4.2.4) (using 4.2.4 (KDE 4.2.4), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.29-sabayon

Applicazione: KGet (kget), segnale SIGSEGV

Thread 1 (Thread 0xb6782700 (LWP 8829)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6e12d10 in nanosleep () from /lib/libc.so.6
#2  0xb6e12b4f in sleep () from /lib/libc.so.6
#3  0xb7e7b228 in ?? () from /usr/kde/4.2/lib/libkdeui.so.5
#4  0x00000000 in ?? ()

Comment 1 David Faure 2009-09-17 16:57:07 UTC

This is a kget crash, not a konqueror crash.

Unfortunately the backtrace contains no useful information.
You'll have to install debug packages and get it to crash again.

Comment 2 FiNeX 2009-09-17 16:59:17 UTC

Hi, this backtrace is not useful. You should explain how to exactly reproduce the crash (if it is reproducible).

How did you have the crash? what were you exactly doing before the crash?

Moreover if you can reproduce the bug you should install debug enabled packages and paste the complete backtrace.
Please read this page for more information about generating an useful backtrace:

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

Many thanks

Comment 3 FiNeX 2009-09-17 17:01:53 UTC

Set to "NEEDSINFO/BACKTRACE"

Comment 4 Andrew Crouthamel 2018-09-20 03:17:52 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Andrew Crouthamel 2018-10-21 05:01:46 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!