Bug 34803

Summary:	I dont think it is a problem with Kcontrol but I dont know what to pick, happened when I was working with the archiver ark (i think it's called that)
Product:	[Unmaintained] kcontrol	Reporter:	kddrake
Component:	general	Assignee:	Daniel Molkentin <molkentin>
Status:	CLOSED FIXED
Severity:	normal	CC:	hassansfouli2016
Priority:	NOR
Version First Reported In:	2.2.1
Target Milestone:	---
Platform:	RedHat Enterprise Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description kddrake 2001-11-12 02:44:10 UTC

(*** This bug was imported into bugs.kde.org ***)

Package:           kcontrol
Version:           2.2.1 (using KDE 2.2.1 )
Severity:          normal
Installed from:    RedHat RPMs
Compiler:          RedHat 7.2 
OS:                Linux
OS/Compiler notes: Not Specified

Happened when I was working with ark (an archiver) anyways here's some info I have no clue if it's even KDE related but #2  0x4064c838 in KCrash::defaultCrashHandler () at eval.c:41 might have something to do with it :) :

(no debugging symbols found)...(no debugging symbols found)...
0x40e9c669 in __wait4 () from /lib/i686/libc.so.6
#0  0x40e9c669 in __wait4 () from /lib/i686/libc.so.6
#1  0x40f18154 in __DTOR_END__ () from /lib/i686/libc.so.6
#2  0x4064c838 in KCrash::defaultCrashHandler () at eval.c:41
#3  <signal handler called>

(Submitted via bugs.kde.org)

Comment 1 Daniel Molkentin 2001-11-15 16:51:33 UTC

On Monday 12 November 2001 03:44 you wrote:

> Happened when I was working with ark (an archiver) anyways here's some
> info I have no clue if it's even KDE related but #2  0x4064c838 in
> KCrash::defaultCrashHandler () at eval.c:41 might have something to do with
> it :) :
>

No. It isn't. How should KCrash be related to KControl?
Please rereport the bug with a way to reproduce for ark.

</daniel>

-- 
Daniel Molkentin | The K Desktop Environment | http://www.kde.org 
KDE 3.0 -- Konquering your Desktop!