*** Bug 113444 has been marked as a duplicate of this bug. ***

I got this too....


kmail: KMFolderImap::processNewMail - waiting for connection: Kate
kmail: KMFolderImap::processNewMail - waiting for connection: Programming Notes
kmail: KMFolderImap::processNewMail - imapPath of Sent is empty!
kmail: slotListNamespaces - waiting for connection

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 11483)]
0xb7c6afd8 in QGuardedPtr<KMFolder>::operator KMFolder*() const () from /usr/kde/3.5/lib/libkmailprivate.so
(gdb) bt
#0  0xb7c6afd8 in QGuardedPtr<KMFolder>::operator KMFolder*() const () from /usr/kde/3.5/lib/libkmailprivate.so
#1  0xb7f8f83c in ?? () from /usr/kde/3.5/lib/libkmailprivate.so
#2  0x21eb4ab2 in ?? ()
#3  0xb7f8f83c in ?? () from /usr/kde/3.5/lib/libkmailprivate.so
#4  0xb7d75087 in KMAcctImap::processNewMail(bool) () from /usr/kde/3.5/lib/libkmailprivate.so
#5  0x00000001 in ?? ()
#6  0x0804ac50 in kdbgstream::operator<<(kdbgstream& (*)(kdbgstream&)) ()
#7  0xbffd27e0 in ?? ()
#8  0xb5fcb354 in QString::deref() () from /usr/qt/3/lib/libqt-mt.so.3
Previous frame inner to this frame (corrupt stack?)
(gdb)                                                

Ping?  This bug is still here...

In Beta2 3.4.92 the bug is present. It only happens, when no new mails are inbox. On my machine i can't start kontact or kmail unless there are unread mails in my inbox. I configured kmail with 5 imap accounts.

*** Bug 115508 has been marked as a duplicate of this bug. ***

*** Bug 116815 has been marked as a duplicate of this bug. ***

*** Bug 117159 has been marked as a duplicate of this bug. ***

*** Bug 117337 has been marked as a duplicate of this bug. ***

I have what appears to be the same problem but I also have to remove the stale kmail/lock before it will successfully start.  It starts fine when closed down properly, but after abnormal closure (crash etc.) I must have new mail and no lock file. 

*** Bug 118603 has been marked as a duplicate of this bug. ***

Can you clarify your steps to solve the problem? I've deleted all the kmail files in /tmp, deleted the file ~/.kde/share/apps/kmail/lock and sent myself some new mail that arrives in my inbox. When I start KMail it still crashes! It'd be handy to know a way of resolving this so I can continue using it...

*** Bug 118865 has been marked as a duplicate of this bug. ***

*** Bug 116734 has been marked as a duplicate of this bug. ***

*** Bug 118468 has been marked as a duplicate of this bug. ***

*** Bug 118954 has been marked as a duplicate of this bug. ***

*** Bug 118014 has been marked as a duplicate of this bug. ***

*** This bug has been confirmed by popular vote. ***

How about changing the bug version to 3.5? It's out now and people using the latest stable relase are reporting duplicates as they don't see this during the report process when other bugs releated bugs are listed.

Hello, I'm having this bug too and it only appeared after updating from 3.4.2 to 3.5.0. Is it possbile that SuSE's 3.4 RPMs have a "private" fix for this bug? Maybe somebody from SuSE can comment?

Thanks!

Update: After deleting .kde/share/apps/kmail (which seems to contain an IMAP cache, although I never used IMAP cached accounts) KMail started up OK. My accounts were all still there, only the icons and folder settings were gone. Plus I had to resubscribe to all IMAP folders, and KMail asked me for each account if I want to "enable subscriptions".

Anotther thing: KMail 1.9 seems to ignore the IMAP folder prefix setting which I had defined before (and which is still set in the account setting). Courier IMAP (which I use) uses "INBOX." as a prefix and before, the "Inbox" was shown as a normal folder. Now, INBOX ("Posteingang") is shown as a parent folder and all IMAP folders are subfolders of this one, regardless of what I specify in the account settings.

Maybe this is related to this bug.

Samething here. After upgrading to kde 3.5, kmail crashes, 2-3 seconds after I start it.

> Update: After deleting .kde/share/apps/kmail (which seems to contain an
> IMAP cache, although I never used IMAP cached accounts) KMail started up
> OK.


Of course, this contains the headers.

> My accounts were all still there, only the icons and folder settings
> were gone. Plus I had to resubscribe to all IMAP folders, and KMail asked
> me for each account if I want to "enable subscriptions".


The settings are obviously lost.

> Anotther thing: KMail 1.9 seems to ignore the IMAP folder prefix setting
> which I had defined before (and which is still set in the account
> setting). Courier IMAP (which I use) uses "INBOX." as a prefix and before,
> the "Inbox" was shown as a normal folder. Now, INBOX ("Posteingang") is
> shown as a parent folder and all IMAP folders are subfolders of this one,
> regardless of what I specify in the account settings.


This is ok, KMail now uses the namespace and the hack to display the
folders on the same level has been removed. There is already a wish to
change it but this won't change for 3.5

So what data in apps/kmail exactly caused the crash? I still have the folder, I can probably narrow it down given a starting point.

*** Bug 119913 has been marked as a duplicate of this bug. ***

This bug looks very similar to the bug 115020 which I have already added comments to. I find that after improper shutdown kmail crashes until I remove .kde/share/apps/kmail/imap/*, I don't need to delete the . files but I guess kmail finds some files missing and rebuilds the index? This seems to happen quite frequently and I would love to see this bug squashed.

I have 3 IMAP accounts set up (using BincIMAP on a remote server) with some pretty large folders in there too. I think they may spark the crash, but I am not sure.

large folders may be a commonality here. My lkml folder has 55771 messages, and my gentoo-user folder has 16871. And it does seem to have the most problems with the large folders.

That could be the case for causing the crashes. At work I use the same version of kmail but don't have the 3rd account set up which is the one with all the big folders. It hasn't crashed once yet. I can trigger the crash on start up bug by killing it off though, and then need to delete the files I mentioned to get back in.

I should also mention that once triggered, the crashes on startup usually go away if I send myself some mail (with the 'mail' command or something) so that I have new mail that KMail hasn't seen, and then open another client on the inbox. Somehow, this results in the imap cache being cleared, and KMail is able to start up again, though I have to re-sort several folders (especially the large ones)

Most of my crashes stopped when I disabled automated mail checks for my two account. I guess there might be some bug when there are concurrent events like manual UI activity and timer starts the mail check and that causes kmail to crash.

It still crashes quite frequently, but now I'm able to handle my mail. I also had to edit kmailrc manually before  those startup crashes stopped. Running kmail from shell and looking what it is doing when the crash happens helps a lot.

I see this crash occasionally and have verified that it's only with automatic checks on.  I have 100+ folders with between 3000-5000 messages so it's possible that it's size related.  On an odd note, I get it at work where all my accounts are IMAP and at home where I have a mix of DIMAP/IMAP (same four accounts as work though).   Since it always seems to corrupt either the kmailrc or the indices some sort of bad interaction in mail checking makes sense.

I can confirm earlier observations too, I do not need to remove any files if there is a new email waiting for me. It has encouraged me to fix bugs to get bug mail so I can get back into my mailbox :)

Doing some further testing, and it seems that sometimes I do need to remove some of the files in .kde/share/apps/kmail/imap to invalidate the cache. I have also tested kmail as included with KDE 3.5.1 and the same issues are present (I am a packager for KDE on Gentoo), that is with everything upgraded to KDE 3.5.1 too (one compiled with GCC 3.4.4, other with GCC 4.0.2, both amd64). This has got to be one of the worst bugs I have seen in kmail - if there is anything I can do to help diagnose it then please let me know.

I have been experiencing it for a long time as well.
Sometimes it doesn't occur for days but it keeps returning.
The crash is also on a "per folder basis" since I experience quite often that it crashes and then I restart it just to let it crash again until the crash has worked it's way through all folders. After that I can start it properly again but all my settings for the specific folders are gone. For example to sort per date and also marked as to-do.

*** Bug 117844 has been marked as a duplicate of this bug. ***

I feel that most of my crashes are somehow related to bug 110862. 

I do filtering (move messages to mailing list folders) for my inbox and sometimes some list fails and all its messages are left into folder. If I select one of those messages and press ctrl-j to apply all filters, kmail typically crashes. It also crashes during the filtering.

If then go and see the filter, it has lost its target folder. Insde the kmailrc, the folder in question has lost (a least) its ImapPath= setting. 

Fixing that and manually subscribing the folder with kmail brings it visible again and the filter is also fixed automatically.

Would it be possible that there is something what corrupts the kmailrc at runtime and causes all these crashes? Of course it should not crash even with rotten config file.

In my case I know it is not due to filtering - I do not use any kmail filters. They are IMAP folders filtered server side using procmail. Invalidating the cache by deleting a few of the files in imap/ causes kmail to rebuild its cache and I can start kmail again, although the folder settings are unfortunately lost.

*** Bug 122588 has been marked as a duplicate of this bug. ***

*** Bug 122564 has been marked as a duplicate of this bug. ***

Hi all.

My kmail also crashes on startup. I leave it running during day and when i come back home kde is crashed. After trying to run it again it crashes right after UI ha been rendered. After about 10 crashes, it starts, but has to download all headers again.

System is:
debian sid, kde 3.5.1, kmail 1.9.1, kontact 1.2.

Here is my backtrace.
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1241433280 (LWP 5128)]
[New Thread -1281524816 (LWP 5132)]
[New Thread -1273136208 (LWP 5131)]
[New Thread -1264747600 (LWP 5130)]
[New Thread -1256358992 (LWP 5129)]
[KCrash handler]
#5  0xb55c495c in KMFolder::noContent (this=0x68)
    at /tmp/buildd/kdepim-3.5.1/build-tree/kdepim-3.5.1/kmail/kmfolder.cpp:288
#6  0xb565cf04 in KMAcctImap::processNewMail (this=0x859b270, interactive=true)
    at /tmp/buildd/kdepim-3.5.1/build-tree/kdepim-3.5.1/kmail/kmacctimap.cpp:316
#7  0xb55fac2f in KMail::AccountManager::processNextCheck (this=0x859ae18, 
    _newMail=false)
    at /tmp/buildd/kdepim-3.5.1/build-tree/kdepim-3.5.1/kmail/accountmanager.cpp:196
#8  0xb55fae0e in KMail::AccountManager::singleCheckMail (this=0x859ae18, 
    account=0x859b270, interactive=true)
    at /tmp/buildd/kdepim-3.5.1/build-tree/kdepim-3.5.1/kmail/accountmanager.cpp:125
#9  0xb55fafbf in KMail::AccountManager::checkMail (this=0x859ae18, 
    _interactive=true)
    at /tmp/buildd/kdepim-3.5.1/build-tree/kdepim-3.5.1/kmail/accountmanager.cpp:312
#10 0xb571d907 in KMMainWidget::slotCheckMail (this=0x864b248)
    at /tmp/buildd/kdepim-3.5.1/build-tree/kdepim-3.5.1/kmail/kmmainwidget.cpp:793
#11 0xb5733d41 in KMMainWidget::qt_invoke (this=0x864b248, _id=49, 
    _o=0xbffff3b8) at kmmainwidget.moc:467
#12 0xb70aab57 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#13 0xb743b055 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#14 0xb70c8a40 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#15 0xb70d0354 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#16 0xb7040698 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#17 0xb70408b6 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#18 0xb7746d4e in KApplication::notify () from /usr/lib/libkdecore.so.4
#19 0xb6fd05e5 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#20 0xb703198c in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#21 0xb6fe435c in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#22 0xb7058da2 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#23 0xb7058ccb in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#24 0xb703f225 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#25 0x0805ae7b in main (argc=104, argv=0x68) at main.cpp:177
#26 0xb780bed0 in __libc_start_main () from /lib/tls/libc.so.6
#27 0x08058561 in _start () at ../sysdeps/i386/elf/start.S:119

i apologize if this is a debian thing...

I can confirm that this bug still exists on Suse 10 with KDE 3.5.1. It's a very annoying bug and it happens to me probably 10/20% of the time I start KMail (KMail displays for about half a second and crashes). If I quickly click on a folder, this stops it from crashing for some reason. Now I start Kmail and constantly click on the desktop where the folders are going to appear to get Kmail to start. Is there a temporary fix to this because it makes Kmail a pain to use and I really like it? :-(

I can confirm that this bug still exists on Suse 10 with KDE 3.5.1. It's a very annoying bug and it happens to me probably 10/20% of the time I start KMail (KMail displays for about half a second and crashes). If I quickly click on a folder, this stops it from crashing for some reason. Now I start Kmail and constantly click on the desktop where the folders are going to appear to get Kmail to start. Is there a temporary fix to this because it makes Kmail a pain to use and I really like it? :-(

The procedure described in #40 (and #41) works for me too. KMail 4:3.5.2-1 on Debian testing/unstable.

*** Bug 126022 has been marked as a duplicate of this bug. ***

Still present in kmail 1.9.3

*** Bug 118161 has been marked as a duplicate of this bug. ***

*** Bug 117935 has been marked as a duplicate of this bug. ***

*** Bug 122982 has been marked as a duplicate of this bug. ***

*** Bug 130246 has been marked as a duplicate of this bug. ***

*** Bug 130574 has been marked as a duplicate of this bug. ***

*** Bug 115887 has been marked as a duplicate of this bug. ***

*** Bug 131957 has been marked as a duplicate of this bug. ***

*** Bug 132638 has been marked as a duplicate of this bug. ***

*** Bug 132669 has been marked as a duplicate of this bug. ***

 I have Suse 9.3 and Suse 10.1 with KDE 3.5.4 and Kmail (Kontact version 1.2.3). On the server side there is an OX 5 instalation on a SLES 9 with cyrus imap. There are relatively many and large folders on the imap server. Kmail is setup for a TLS connection (which is recognized when testing the server). I use a disconnected imap (cachedimap) setup within Kmail. A check for new mails is performed every five minutes.   
 
Both installations lead to periodic crashes of Kmail during the opening of folders on the server and the synchronization. I could not recognize any specific pattern that lead to the bug, with one exception: 

The bug never occurs when I deactivate the TLS connection and use just an unencrypted connection to the cyrus server. Maybe, that helps to analyze the bug better.  

The error occurs both with SuSE 9.3 and SuSE 10.1. It did also occur with KDE 3.4. 

Interesting:  I too have two installations (detailed somewhere earlier) and had initially suspected as significant the difference that one used an NFS homedir and the other didn't, until someone else reported the same problem with a local homedir.
Now I see that the case without crashes is the one on the same network as the mailserver, using no encryption, while the bad installation is the remote one using ssl.  I shall try connecting by an ssh tunnel and see if that helps.  Perhaps others with this crash problem would try without kmail's ssl or tls to help root out the problem -- it's a very time-wasting problem for me, and very annoying.

my kmail is connected to a cyrus imapd via SSL too.

This problem suddenly stopped for me around 3.5.3, IIRC. (but I don't think it was the KDE upgrade that fixed it, sorry) I connect to a Dovecot IMAP server with TLS.

Oooh, my certificate on the server has expired sometime relatively recently (like within the past several months) though. I wonder if that may have something to do with it not having the problem...

*** Bug 132796 has been marked as a duplicate of this bug. ***

*** Bug 120725 has been marked as a duplicate of this bug. ***

Looking at my own comment 54 and comments 55, 56, 57 it seems to me that ssl/tls encryption is one of the causes for the bug. 

As I learned from a different bug with Thunderbird it may also be important to look at the processor architecture - I have a dual core Athlon X2 4800+ on the machine on which kmail runs. But this only for completeness. I do not know whether that plays any role. What happens if the basic kmail process runs on one core and the encryption/deciphering process in parallel on the other core - could some mismatch then lead to the error? Or can that be excluded?  

As I also use ssl/tls, this possibility cannot be excluded. But I have only one processor:
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 4
model name      : Mobile AMD Athlon(tm) 64 Processor 3000+
stepping        : 10
cpu MHz         : 800.000
cache size      : 1024 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow up ts fid vid ttp
bogomips        : 1605.62

And this crash occured.

I, too, experience the problem from time to time.  I am using KMail 1.9.1 on KDE 3.5.3.  I use several connected IMAP accounts as well as a single disconnected IMAP account.  In some of my mail folders I do have large amounts of messages (5,000 ~ 20,000).  I do NOT use mail filters.  This is my CPU:

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 7
model name      : Pentium III (Katmai)
stepping        : 3
cpu MHz         : 601.453
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips        : 1204.40

*** Bug 133172 has been marked as a duplicate of this bug. ***

my setup is 1 disconnected imap, 1 online imap, but i don't think the disconnected imap has role here as my default startup folder was online imap. changing the folder to open at startup "resolved" the crash. the online imap is over ssl.

it is odd that this bug has so many duplicates and reports but no actual words from developers who actually are willing to fix anything ;(

here's top from my kcrashdialog. note i avoided the crash by changing default startup folder. but if i "enter" the broke imap account the backtrace is:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[KCrash handler]
#6  0xb7294735 in QMap<KPIM::ProgressItem*, bool>::detach (this=0x887aa88)
    at /usr/include/qt/qmap.h:739
#7  0xb7294137 in QMap<KPIM::ProgressItem*, bool>::remove (this=0x887aa88, 
    k=@0xbfa63eb4) at /usr/include/qt/qmap.h:831
#8  0xb7291e21 in KPIM::ProgressItem::removeChild (this=0x887aa48, 
    kiddo=0x866dce8) at progressmanager.cpp:74
#9  0xb7291d9d in KPIM::ProgressItem::setComplete (this=0x866dce8)
    at progressmanager.cpp:60
#10 0xb7cd8393 in KMail::ImapAccountBase::removeJob (this=0x83274f0, 
    it=@0xbfa63f40) at imapaccountbase.cpp:1174
#11 0xb7c267d6 in KMail::ListJob::slotListResult (this=0x8686328, 
    job=0x86825b0) at listjob.cpp:183
#12 0xb7c27093 in KMail::ListJob::qt_invoke (this=0x8686328, _id=2, 
    _o=0xbfa64010) at listjob.moc:128

i'd be happy to provide more information to get this ProgressItem related bug resolved finally (i've kept the corrupted imap account for this purpose).

*** Bug 138369 has been marked as a duplicate of this bug. ***

Just an additional remark to my contributions from last year. I meanwhile run Opensuse 10.2 and KDE 3.5.6 on my old machine with the AMD Dual Core processor. 
I use kmail with a cachedimap and a connection to a cyrus imap server. From my bad experiences last year I first tried with TLS deactivated (see my previous comments).  
I some days ago tried to switch on TLS again. I did not get any error up to now. I checked again with the old SuSE 10.1 installation with KDE 3.5.4 -> There I sooner or later still get the kmail crash after some time.
So it seems to me that some things have changed since KE 3.5.5 or 3.5.6. 

you lost your bad luck - that's about everything that has changed ;(

SVN commit 644705 by wstephens:

Don't continue checking mail in the other folders when a local folder was removed, it causes a crash on startup.

There is still a bug that local folders are removed erroneously because their ImapPath somehow become empty, but at least they can be recovered with Refresh Folder List now.
CCBUG:113329


 M  +3 -1      kmacctimap.cpp  


--- branches/work/kmail_debug_imap/kmacctimap.cpp #644704:644705
@@ -342,7 +342,7 @@
         else {
           connect(imapFolder, SIGNAL(numUnreadMsgsChanged(KMFolder*)),
               this, SLOT(postProcessNewMail(KMFolder*)));
-          bool ok = imapFolder->processNewMail(interactive);
+          bool ok = imapFolder->processNewMail(interactive); // this removes the local kmfolderimap if its imapPath is somehow empty, and removing it calls createFolderList, invalidating mMailCheckFolders, and causing a crash
           if (!ok)
           {
             // there was an error so cancel
@@ -352,6 +352,8 @@
               mMailCheckProgressItem->incCompletedItems();
               mMailCheckProgressItem->updateProgress();
             }
+            // since the list of folders might have been updated at this point, mMailCheckFolders may be invalid, so break
+            break;
           }
         }
       }

SVN commit 644877 by coolo:

Don't continue checking mail in the other folders when a local folder
was removed, it causes a crash on startup.

There is still a bug that local folders are removed erroneously because
their ImapPath somehow become empty, but at least they can be recovered
with Refresh Folder List now.

And as the crash is gone, I consider the bug fixed 
BUG:113329


 M  +3 -1      kmacctimap.cpp  


--- branches/KDE/3.5/kdepim/kmail/kmacctimap.cpp #644876:644877
@@ -342,7 +342,7 @@
         else {
           connect(imapFolder, SIGNAL(numUnreadMsgsChanged(KMFolder*)),
               this, SLOT(postProcessNewMail(KMFolder*)));
-          bool ok = imapFolder->processNewMail(interactive);
+          bool ok = imapFolder->processNewMail(interactive); // this removes the local kmfolderimap if its imapPath is somehow empty, and removing it calls createFolderList, invalidating mMailCheckFolders, and causing a crash
           if (!ok)
           {
             // there was an error so cancel
@@ -352,6 +352,8 @@
               mMailCheckProgressItem->incCompletedItems();
               mMailCheckProgressItem->updateProgress();
             }
+            // since the list of folders might have been updated at this point, mMailCheckFolders may be invalid, so break
+            break;
           }
         }
       }

*** Bug 148874 has been marked as a duplicate of this bug. ***

Created attachment 24788 [details]
The kcrash file from debuger

I think I have the same bug with 1.9.9. I have one IMAP account and one SMTP account. Sometimes KMail crashes on startup, sometimes it's fine.

Have added the kcrash file.