From kde-bugs-dist  Sat Jun 30 22:33:02 2001
From: owner () bugs ! kde ! org (Stephan Kulow)
Date: Sat, 30 Jun 2001 22:33:02 +0000
To: kde-bugs-dist
Subject: Bug#27929: marked as done (kcontrol crashes at start after Migration from Corel) by Waldo Bastian <b
X-MARC-Message: https://marc.info/?l=kde-bugs-dist&m=99394377701425

Your message with subj: Bug#27929: kcontrol crashes at start after Migration from Corel

I guess the control center tries to load modules compiled for the other 
version which will not work. Not much we can do about that.

The backtrace isn't very informative either so I close this report.

Cheers,
Waldo

On Saturday 30 June 2001 09:22 am, Jeffrey Winter wrote:
> Package: kcontrol
> Version: v1.9.8 (KDE 2.0.1)
> Severity: normal
> Compiler: gcc version 2.95.2 20000220 (Debian GNU/Linux)
> OS: Linux 2.2.18pre21 i686 (Debian Package 4:2.0.1-0.potato5)
>
> This might not be a bug, but a configuration issue, because ...
>
> I have been migrating from Corel Linux to a pure KDE (2.0.1), in a
> piece-by-piece manner. This has been painful, but the xdm and most apps run
> smoothly.  kcontrol, however, crashes upon load.
>
> I get signal 11, SIGSEGV.  The KDE crash handler reports only limited
> backtrace, attached at the end of this report.
>
> My old Corel kcontrol does function, though obviously out of sync with
> display aspects. Interestingly, it no longer does MDI; rather, it raises
> new windows for each config. element.
> ==========================================
> (no debugging symbols found)...0x40b3bd19 in ?? ()
> #0  0x40b3bd19 in ?? ()
> #1  0x403f0d70 in ?? ()
> #2  <signal handler called>
> #3  0x8482 in ?? ()
> #4  0x4003b46d in ?? ()
> #5  0x4003acb5 in ?? ()
> #6  0x4002fab0 in ?? ()
> #7  0x4002d744 in ?? ()
> #8  0x4002c8cd in ?? ()
> #9  0x4002cb8e in ?? ()
> #10 0x40ad7a42 in ?? ()

-- 
As a first step to embrace the GPL, 
Microsoft now too has added ideological statements to its EULA.

has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 30 Jun 2001 16:23:25 +0000
Received: (qmail 22827 invoked from network); 30 Jun 2001 16:23:25 -0000
Received: from smtp7vepub.gte.net (HELO smtp7ve.mailsrvcs.net) (206.46.170.28)
  by max.tat.physik.uni-tuebingen.de with SMTP; 30 Jun 2001 16:23:25 -0000
Received: from jeffer ([138.88.42.183])
	by smtp7ve.mailsrvcs.net (8.9.1/8.9.1) with SMTP id QAA38984535
	for submit@bugs.kde.org; Sat, 30 Jun 2001 16:22:22 GMT
Date: Sat, 30 Jun 2001 16:22:22 GMT
Message-Id: <200106301622.QAA38984535@smtp7ve.mailsrvcs.net>
Subject: kcontrol crashes at start after Migration from Corel
From: Jeffrey Winter <jeffersonlinux@yahoo.com>
To: submit@bugs.kde.org
X-Spam-Rating: max.tat.physik.uni-tuebingen.de 300/1000/N

Package: kcontrol
Version: v1.9.8 (KDE 2.0.1)
Severity: normal
Compiler: gcc version 2.95.2 20000220 (Debian GNU/Linux)
OS: Linux 2.2.18pre21 i686 (Debian Package 4:2.0.1-0.potato5)

This might not be a bug, but a configuration issue, because ...

I have been migrating from Corel Linux to a pure KDE (2.0.1), in a piece-by-piece manner. 
This has been painful, but the xdm and most apps run smoothly.  kcontrol, however, crashes 
upon load.

I get signal 11, SIGSEGV.  The KDE crash handler reports only limited backtrace, attached
at the end of this report.

My old Corel kcontrol does function, though obviously out of sync with display aspects.  
Interestingly, it no longer does MDI; rather, it raises new windows for each config. element.
==========================================
(no debugging symbols found)...0x40b3bd19 in ?? ()
#0  0x40b3bd19 in ?? ()
#1  0x403f0d70 in ?? ()
#2  <signal handler called>
#3  0x8482 in ?? ()
#4  0x4003b46d in ?? ()
#5  0x4003acb5 in ?? ()
#6  0x4002fab0 in ?? ()
#7  0x4002d744 in ?? ()
#8  0x4002c8cd in ?? ()
#9  0x4002cb8e in ?? ()
#10 0x40ad7a42 in ?? ()