Bug 13671

Everytime I've dealt with one of these types of errors I've spent a lot of 
time working out what the problem has been and it's always been a 
packaging/configuration/installation error. Which means it's been a waste of 
my time looking at it and trying to reproduce the problem locally.

Having said that if _you_ are willing to spend some time investigating the 
problem then I'm willing to help you track down the problem.

1) Exit X and then restart KDE kill any suspicious looking processes hanging 
around and restart X. See if that helps.

2) Move the ~/Mail folder out of the way? Can you start KMail now? I think 
some mail clients put directories where KMail expects files. So KMail can't 
start up in this situation.

3) Recompile KMail with debugging turned on (configure --enable-debug when 
configuring kdenetwork). Run it in gdb when you get the error type 'bt' then 
type 'frame 4' to goto the KMFolderMgr::findOrCreate frame and then type 
'list' and send me the results of all that.

BFN
Don.

On Friday 27 October 2000 01:36 Michael Hipp wrote:
> Don
>
> Thank you for your note.
>
> But I cannot accept this answer.  As I know of several people who have
> compiled the sources directly and are experiencing the same problems.  To
> be sure I know of some who are also not experiencing the problems.  But
> there is a problem here and I respectfully suggest that you do not fall
> into the trap of just blaming it on the packager.  I do not believe that
> will stand up to a test of the facts/evidence.
>
> Thank you
> Michael Hipp
>
> Don Sanders wrote:
> > I hope you realize this is due to bad packaging and has nothing to do
> > with KDE/KMail. Please complain to package creator not us every other
> > packager creator managed to get this right for KDE2.
> >
> > BFN
> > Don.
> >
> > On Thursday 26 October 2000 23:48 Stephan Kulow wrote:
> > > Your message dated Thu 26 Oct 2000 23:37:06 +0200
> > > with message-id <00102623370607.03310@michael>
> > > and subject line Bug#13761: Kmail is Broke. Crashes.
> > > 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; 26 Oct 2000 21:08:12 +0000
> > > Received: (qmail 15436 invoked by uid 33); 26 Oct 2000 21:08:11 -0000
> > > Date: 26 Oct 2000 21:08:11 -0000
> > > Message-ID: <20001026210811.15435.qmail@master.kde.org>
> > > To: submit@bugs.kde.org
> > > Subject: Kmail is Broke.  Crashes.
> > > From: MHipp@RedMule.com
> > >
> > > Package: kmail
> > > Version: KDE 2.0 / Kmail 1.1.99
> > > Severity: crash
> > > Installed from: COL-2.4 RPMS
> > >
> > > I and a number of other people are experiencing that Kmail crashes
> > > every time we attempt to run it.  At first when building the /mail
> > > folder and then anytime we attempt to send or receive mail.  Bug is
> > > 100% repeatable.
> > >
> > > Here's what the crash handler says:
> > > (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)...0x2bb85c49 in __wait4 () from
> > > /lib/libc.so.6 #0  0x2bb85c49 in __wait4 () from /lib/libc.so.6
> > > #1  0x2bbe3a9c in __DTOR_END__ () from /lib/libc.so.6
> > > #2  0x2b2ac21e in KCrash::defaultCrashHandler ()
> > >    from /opt/kde2/lib/libkdecore.so.3
> > > #3  0x2bb14268 in __restore () from /lib/libc.so.6
> > > #4  0x80c527e in KMFolderMgr::findOrCreate ()
> > > #5  0x811135c in KMKernel::initFolders ()
> > > #6  0x8111a88 in KMKernel::init ()
> > > #7  0x8112da2 in main ()
> > > #8  0x2bb0d736 in __libc_start_main () from /lib/libc.so.6
> > >
> > > Thank you
> > > Michael Hipp
> > >
> > > (submitted via bugs.kde.org)
>
> --

http://x65.deja.com/getdoc.xp?AN=686700935&CONTEXT=972734784.519766025&hitnum=12

leads me to believe that the Caldera packages were in fact incorrectly built. 
Of course you may still have problems even with correctly built packages but 
I suggest you get correctly built packages to begin with or compile from 
source.

BFN
Don.

On Friday 27 October 2000 13:38 Don Sanders wrote:
> Everytime I've dealt with one of these types of errors I've spent a lot of
> time working out what the problem has been and it's always been a
> packaging/configuration/installation error. Which means it's been a waste
> of my time looking at it and trying to reproduce the problem locally.
>
> Having said that if _you_ are willing to spend some time investigating the
> problem then I'm willing to help you track down the problem.
>
> 1) Exit X and then restart KDE kill any suspicious looking processes
> hanging around and restart X. See if that helps.
>
> 2) Move the ~/Mail folder out of the way? Can you start KMail now? I think
> some mail clients put directories where KMail expects files. So KMail can't
> start up in this situation.
>
> 3) Recompile KMail with debugging turned on (configure --enable-debug when
> configuring kdenetwork). Run it in gdb when you get the error type 'bt'
> then type 'frame 4' to goto the KMFolderMgr::findOrCreate frame and then
> type 'list' and send me the results of all that.
>
> BFN
> Don.
>
> On Friday 27 October 2000 01:36 Michael Hipp wrote:
> > Don
> >
> > Thank you for your note.
> >
> > But I cannot accept this answer.  As I know of several people who have
> > compiled the sources directly and are experiencing the same problems.  To
> > be sure I know of some who are also not experiencing the problems.  But
> > there is a problem here and I respectfully suggest that you do not fall
> > into the trap of just blaming it on the packager.  I do not believe that
> > will stand up to a test of the facts/evidence.
> >
> > Thank you
> > Michael Hipp
> >
> > Don Sanders wrote:
> > > I hope you realize this is due to bad packaging and has nothing to do
> > > with KDE/KMail. Please complain to package creator not us every other
> > > packager creator managed to get this right for KDE2.
> > >
> > > BFN
> > > Don.
> > >
> > > On Thursday 26 October 2000 23:48 Stephan Kulow wrote:
> > > > Your message dated Thu 26 Oct 2000 23:37:06 +0200
> > > > with message-id <00102623370607.03310@michael>
> > > > and subject line Bug#13761: Kmail is Broke. Crashes.
> > > > 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; 26 Oct 2000 21:08:12 +0000
> > > > Received: (qmail 15436 invoked by uid 33); 26 Oct 2000 21:08:11 -0000
> > > > Date: 26 Oct 2000 21:08:11 -0000
> > > > Message-ID: <20001026210811.15435.qmail@master.kde.org>
> > > > To: submit@bugs.kde.org
> > > > Subject: Kmail is Broke.  Crashes.
> > > > From: MHipp@RedMule.com
> > > >
> > > > Package: kmail
> > > > Version: KDE 2.0 / Kmail 1.1.99
> > > > Severity: crash
> > > > Installed from: COL-2.4 RPMS
> > > >
> > > > I and a number of other people are experiencing that Kmail crashes
> > > > every time we attempt to run it.  At first when building the /mail
> > > > folder and then anytime we attempt to send or receive mail.  Bug is
> > > > 100% repeatable.
> > > >
> > > > Here's what the crash handler says:
> > > > (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)...0x2bb85c49 in __wait4 () from
> > > > /lib/libc.so.6 #0  0x2bb85c49 in __wait4 () from /lib/libc.so.6
> > > > #1  0x2bbe3a9c in __DTOR_END__ () from /lib/libc.so.6
> > > > #2  0x2b2ac21e in KCrash::defaultCrashHandler ()
> > > >    from /opt/kde2/lib/libkdecore.so.3
> > > > #3  0x2bb14268 in __restore () from /lib/libc.so.6
> > > > #4  0x80c527e in KMFolderMgr::findOrCreate ()
> > > > #5  0x811135c in KMKernel::initFolders ()
> > > > #6  0x8111a88 in KMKernel::init ()
> > > > #7  0x8112da2 in main ()
> > > > #8  0x2bb0d736 in __libc_start_main () from /lib/libc.so.6
> > > >
> > > > Thank you
> > > > Michael Hipp
> > > >
> > > > (submitted via bugs.kde.org)
> >
> > --

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