<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.kde.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugs.kde.org/"
          
          maintainer="sysadmin@kde.org"
>

    <bug>
          <bug_id>113329</bug_id>
          
          <creation_ts>2005-09-26 01:07:33 +0000</creation_ts>
          <short_desc>KMail crash on startup</short_desc>
          <delta_ts>2008-05-16 10:44:16 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>10</classification_id>
          <classification>Unmaintained</classification>
          <product>kmail</product>
          <component>general</component>
          <version>unspecified</version>
          <rep_platform>Compiled Sources</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>NOR</priority>
          <bug_severity>crash</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Josh Berry">des</reporter>
          <assigned_to name="kdepim bugs">pim-bugs-null</assigned_to>
          <cc>aroth</cc>
    
    <cc>blin</cc>
    
    <cc>carn0048</cc>
    
    <cc>esorensendea</cc>
    
    <cc>f.heem</cc>
    
    <cc>fhimpe</cc>
    
    <cc>glen</cc>
    
    <cc>hub</cc>
    
    <cc>itlistuser</cc>
    
    <cc>Jean-Damien.Durand</cc>
    
    <cc>jeff.causey</cc>
    
    <cc>jens-bugs.kde.org</cc>
    
    <cc>julian</cc>
    
    <cc>kde-bugreport</cc>
    
    <cc>kde-bugzilla</cc>
    
    <cc>kde</cc>
    
    <cc>kde</cc>
    
    <cc>kden</cc>
    
    <cc>mactas</cc>
    
    <cc>marcus</cc>
    
    <cc>marvinoid</cc>
    
    <cc>michael.seiwert</cc>
    
    <cc>opensource</cc>
    
    <cc>pentek.imre</cc>
    
    <cc>rm</cc>
    
    <cc>Ronny.Standtke</cc>
    
    <cc>rpolli</cc>
          
          <cf_commitlink></cf_commitlink>
          <cf_versionfixedin></cf_versionfixedin>
          <cf_sentryurl></cf_sentryurl>
          <votes>76</votes>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>376095</commentid>
    <comment_count>0</comment_count>
    <who name="Josh Berry">des</who>
    <bug_when>2005-09-26 01:07:34 +0000</bug_when>
    <thetext>Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 3.4 
OS:                Linux

Sometimes when I start KMail, it crashes after displaying the password dialog for my first IMAP account, but before displaying the dialog for my second IMAP.  (It usually displays both at the same time.)

This has been occurring sporadically for the past week or so in KDE 3.5 SVN.

Here&apos;s the backtrace:

Using host libthread_db library &quot;/lib/libthread_db.so.1&quot;.
`system-supplied DSO at 0xffffe000&apos; has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1251199312 (LWP 7929)]
[KCrash handler]
#4  0xb7ce4e4b in KMFolder::noContent (this=0x11)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmfolder.cpp:280
#5  0xb7d80e4d in KMAcctImap::processNewMail (this=0x83b5a30, 
    interactive=true)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmacctimap.cpp:315
#6  0xb7d21c14 in KMail::AccountManager::processNextCheck (this=0x83a4bc8, 
    _newMail=232)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/accountmanager.cpp:196
#7  0xb7d21d82 in KMail::AccountManager::singleCheckMail (this=0x83a4bc8, 
    account=0x83b5a30, interactive=true)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/accountmanager.cpp:125
#8  0xb7d21f22 in KMail::AccountManager::checkMail (this=0x83a4bc8, 
    _interactive=true)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/accountmanager.cpp:312
#9  0xb7e51f87 in KMMainWidget::slotCheckMail (this=0x8455588)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmmainwidget.cpp:793
#10 0xb7e66779 in KMMainWidget::qt_invoke (this=0x8455588, _id=49, 
    _o=0xbf8dd1f0) at kmmainwidget.moc:467
#11 0xb73006f6 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#12 0xb7640256 in QSignal::signal () from /usr/qt/3/lib/libqt-mt.so.3
#13 0xb731a075 in QSignal::activate () from /usr/qt/3/lib/libqt-mt.so.3
#14 0xb73216a7 in QSingleShotTimer::event () from /usr/qt/3/lib/libqt-mt.so.3
#15 0xb729e8de in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#16 0xb729ea6d in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#17 0xb789f98c in KApplication::notify (this=0xbf8ded60, receiver=0x84c70f8, 
    event=0xbf8dd6c0)
    at /net/seme/srv/alnath/kde/KDE/kdelibs/kdecore/kapplication.cpp:550
#18 0xb7292550 in QEventLoop::activateTimers ()
   from /usr/qt/3/lib/libqt-mt.so.3
#19 0xb724b346 in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#20 0xb72b4851 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#21 0xb729db69 in QApplication::enter_loop () from /usr/qt/3/lib/libqt-mt.so.3
#22 0xb7488c9f in QDialog::exec () from /usr/qt/3/lib/libqt-mt.so.3
#23 0xb6187a3c in KIO::PasswordDialog::getNameAndPassword (user=@0xbf8ddae0, 
    pass=@0x11, keep=0xbf8dda0f, prompt=@0xbf8dda70, readOnly=false, 
    caption=@0xb776df40, comment=@0xbf8dda50, label=@0x11)
    at /net/seme/srv/alnath/kde/KDE/kdelibs/kio/kio/passdlg.cpp:353
#24 0xb7d75a15 in KMail::ImapAccountBase::makeConnection (this=0x83b5a30)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/imapaccountbase.cpp:285
#25 0xb7d7db79 in KMAcctImap::makeConnection (this=0x11)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmacctimap.cpp:547
#26 0xb7d9b0de in KMFolderImap::listDirectory (this=0x83a7690)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmfolderimap.cpp:705
#27 0xb7c8b98e in KMFolderTree::slotFolderExpanded (this=0x84b0508, 
    item=0xb7fb6128)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmfoldertree.cpp:1449
#28 0xb7c9262f in KMFolderTree::qt_invoke (this=0x84b0508, _id=139134216, 
    _o=0xbf8ddca0) at kmfoldertree.moc:479
#29 0xb73006f6 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#30 0xb7652801 in QListView::expanded () from /usr/qt/3/lib/libqt-mt.so.3
#31 0xb73e42ed in QListViewItem::setOpen () from /usr/qt/3/lib/libqt-mt.so.3
#32 0xb7c8f658 in KMFolderTree::addDirectory (this=0x84b0508, fdir=0x8372d6c, 
    parent=0x0)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmfoldertree.cpp:695
#33 0xb7c8fb55 in KMFolderTree::reload (this=0x84b0508, openFolders=false)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmfoldertree.cpp:535
#34 0xb7e62d92 in KMMainWidget::readConfig (this=0x8455588)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmmainwidget.cpp:401
#35 0xb7e63a22 in KMMainWidget (this=0x8455588, parent=0x11, 
    name=0x11 &lt;Address 0x11 out of bounds&gt;, aGUIClient=0x11, 
    actionCollection=0x8456de8, config=0x11)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmmainwidget.cpp:172
#36 0xb7c30cea in KMMainWin (this=0x8456598)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmmainwin.cpp:42
#37 0xb7dc2f89 in KMKernel::openReader (this=0xbf8dec80, onlyCheck=false)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmkernel.cpp:349
#38 0xb7dc30ac in KMKernel::action (this=0xbf8dec80, mailto=false, 
    check=false, to=@0x11, cc=@0x11, bcc=@0x11, subj=@0x11, body=@0x11, 
    messageFile=@0x11, attachURLs=@0x11)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmkernel.cpp:1798
#39 0xb7dc918b in KMKernel::handleCommandLine (this=0xbf8dec80, 
    noArgsOpensReader=true)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/kmkernel.cpp:302
#40 0x0804a53a in KMailApplication::newInstance (this=0xbf8ded60)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/main.cpp:62
#41 0xb794d713 in KUniqueApplication::processDelayed (this=0xbf8ded60)
    at /net/seme/srv/alnath/kde/KDE/kdelibs/kdecore/kuniqueapplication.cpp:444
#42 0xb794d8d5 in KUniqueApplication::qt_invoke (this=0xbf8ded60, _id=18, 
    _o=0x11) at kuniqueapplication.moc:86
#43 0xb73006f6 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#44 0xb7640256 in QSignal::signal () from /usr/qt/3/lib/libqt-mt.so.3
#45 0xb731a075 in QSignal::activate () from /usr/qt/3/lib/libqt-mt.so.3
#46 0xb73216a7 in QSingleShotTimer::event () from /usr/qt/3/lib/libqt-mt.so.3
#47 0xb729e8de in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#48 0xb729ea6d in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#49 0xb789f98c in KApplication::notify (this=0xbf8ded60, receiver=0x83728b8, 
    event=0xbf8dea10)
    at /net/seme/srv/alnath/kde/KDE/kdelibs/kdecore/kapplication.cpp:550
#50 0xb7292550 in QEventLoop::activateTimers ()
   from /usr/qt/3/lib/libqt-mt.so.3
#51 0xb724b346 in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#52 0xb72b4851 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#53 0xb72b47aa in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#54 0xb729db43 in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#55 0x0804a6c2 in main (argc=17, argv=0x11)
    at /net/seme/srv/alnath/kde/KDE/kdepim/kmail/main.cpp:110</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>376819</commentid>
    <comment_count>1</comment_count>
    <who name="Thiago Macieira">thiago</who>
    <bug_when>2005-09-28 04:55:52 +0000</bug_when>
    <thetext>*** Bug 113444 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>378019</commentid>
    <comment_count>2</comment_count>
    <who name="Mathieu Jobin">opensource</who>
    <bug_when>2005-10-01 19:00:25 +0000</bug_when>
    <thetext>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&lt;KMFolder&gt;::operator KMFolder*() const () from /usr/kde/3.5/lib/libkmailprivate.so
(gdb) bt
#0  0xb7c6afd8 in QGuardedPtr&lt;KMFolder&gt;::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&lt;&lt;(kdbgstream&amp; (*)(kdbgstream&amp;)) ()
#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)                                                

</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>384037</commentid>
    <comment_count>3</comment_count>
    <who name="Josh Berry">des</who>
    <bug_when>2005-10-24 07:23:58 +0000</bug_when>
    <thetext>Ping?  This bug is still here...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>386318</commentid>
    <comment_count>4</comment_count>
    <who name="Andreas Roth">aroth</who>
    <bug_when>2005-11-01 14:22:32 +0000</bug_when>
    <thetext>In Beta2 3.4.92 the bug is present. It only happens, when no new mails are inbox. On my machine i can&apos;t start kontact or kmail unless there are unread mails in my inbox. I configured kmail with 5 imap accounts.
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>386615</commentid>
    <comment_count>5</comment_count>
    <who name="Tommi Tervo">tommi.tervo</who>
    <bug_when>2005-11-02 15:49:49 +0000</bug_when>
    <thetext>*** Bug 115508 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>391918</commentid>
    <comment_count>6</comment_count>
    <who name="Tommi Tervo">tommi.tervo</who>
    <bug_when>2005-11-21 14:41:49 +0000</bug_when>
    <thetext>*** Bug 116815 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>393592</commentid>
    <comment_count>7</comment_count>
    <who name="Tommi Tervo">tommi.tervo</who>
    <bug_when>2005-11-28 15:50:09 +0000</bug_when>
    <thetext>*** Bug 117159 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>394109</commentid>
    <comment_count>8</comment_count>
    <who name="Tommi Tervo">tommi.tervo</who>
    <bug_when>2005-11-30 11:20:50 +0000</bug_when>
    <thetext>*** Bug 117337 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>395760</commentid>
    <comment_count>9</comment_count>
    <who name="Spencer Shimko">spencer</who>
    <bug_when>2005-12-05 15:28:53 +0000</bug_when>
    <thetext>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. </thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>399747</commentid>
    <comment_count>10</comment_count>
    <who name="Thiago Macieira">thiago</who>
    <bug_when>2005-12-19 00:07:32 +0000</bug_when>
    <thetext>*** Bug 118603 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>399895</commentid>
    <comment_count>11</comment_count>
    <who name="Tom Chance">telex4</who>
    <bug_when>2005-12-19 12:27:11 +0000</bug_when>
    <thetext>Can you clarify your steps to solve the problem? I&apos;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&apos;d be handy to know a way of resolving this so I can continue using it...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>400913</commentid>
    <comment_count>12</comment_count>
    <who name="Thiago Macieira">thiago</who>
    <bug_when>2005-12-22 19:37:31 +0000</bug_when>
    <thetext>*** Bug 118865 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>400916</commentid>
    <comment_count>13</comment_count>
    <who name="Thiago Macieira">thiago</who>
    <bug_when>2005-12-22 19:39:29 +0000</bug_when>
    <thetext>*** Bug 116734 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>400919</commentid>
    <comment_count>14</comment_count>
    <who name="Thiago Macieira">thiago</who>
    <bug_when>2005-12-22 19:40:15 +0000</bug_when>
    <thetext>*** Bug 118468 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>401303</commentid>
    <comment_count>15</comment_count>
    <who name="Thiago Macieira">thiago</who>
    <bug_when>2005-12-24 13:55:04 +0000</bug_when>
    <thetext>*** Bug 118954 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>401305</commentid>
    <comment_count>16</comment_count>
    <who name="Thiago Macieira">thiago</who>
    <bug_when>2005-12-24 13:55:57 +0000</bug_when>
    <thetext>*** Bug 118014 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>401307</commentid>
    <comment_count>17</comment_count>
    <who name="Imre Péntek">pentek.imre</who>
    <bug_when>2005-12-24 14:02:09 +0000</bug_when>
    <thetext>*** This bug has been confirmed by popular vote. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>401318</commentid>
    <comment_count>18</comment_count>
    <who name="Juha Tuomala">tuju</who>
    <bug_when>2005-12-24 14:32:57 +0000</bug_when>
    <thetext>How about changing the bug version to 3.5? It&apos;s out now and people using the latest stable relase are reporting duplicates as they don&apos;t see this during the report process when other bugs releated bugs are listed.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>403494</commentid>
    <comment_count>19</comment_count>
    <who name="Jens">jens-bugs.kde.org</who>
    <bug_when>2006-01-04 10:34:52 +0000</bug_when>
    <thetext>Hello, I&apos;m having this bug too and it only appeared after updating from 3.4.2 to 3.5.0. Is it possbile that SuSE&apos;s 3.4 RPMs have a &quot;private&quot; fix for this bug? Maybe somebody from SuSE can comment?

Thanks!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>403521</commentid>
    <comment_count>20</comment_count>
    <who name="Jens">jens-bugs.kde.org</who>
    <bug_when>2006-01-04 14:11:19 +0000</bug_when>
    <thetext>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 &quot;enable subscriptions&quot;.

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 &quot;INBOX.&quot; as a prefix and before, the &quot;Inbox&quot; was shown as a normal folder. Now, INBOX (&quot;Posteingang&quot;) 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.
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>403695</commentid>
    <comment_count>21</comment_count>
    <who name="Sylvain Garneau">s.garneau</who>
    <bug_when>2006-01-05 02:07:05 +0000</bug_when>
    <thetext>Samething here. After upgrading to kde 3.5, kmail crashes, 2-3 seconds after I start it.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>403754</commentid>
    <comment_count>22</comment_count>
    <who name="Carsten Burghardt">burghardt</who>
    <bug_when>2006-01-05 11:47:05 +0000</bug_when>
    <thetext>&gt; Update: After deleting .kde/share/apps/kmail (which seems to contain an
&gt; IMAP cache, although I never used IMAP cached accounts) KMail started up
&gt; OK.


Of course, this contains the headers.

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


The settings are obviously lost.

&gt; Anotther thing: KMail 1.9 seems to ignore the IMAP folder prefix setting
&gt; which I had defined before (and which is still set in the account
&gt; setting). Courier IMAP (which I use) uses &quot;INBOX.&quot; as a prefix and before,
&gt; the &quot;Inbox&quot; was shown as a normal folder. Now, INBOX (&quot;Posteingang&quot;) is
&gt; shown as a parent folder and all IMAP folders are subfolders of this one,
&gt; 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&apos;t change for 3.5
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>403762</commentid>
    <comment_count>23</comment_count>
    <who name="Jens">jens-bugs.kde.org</who>
    <bug_when>2006-01-05 11:59:21 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>405406</commentid>
    <comment_count>24</comment_count>
    <who name="Thiago Macieira">thiago</who>
    <bug_when>2006-01-12 03:49:59 +0000</bug_when>
    <thetext>*** Bug 119913 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>405673</commentid>
    <comment_count>25</comment_count>
    <who name="Marcus D. Hanwell">marcus</who>
    <bug_when>2006-01-13 03:20:28 +0000</bug_when>
    <thetext>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&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>405675</commentid>
    <comment_count>26</comment_count>
    <who name="John Myers">electronerd</who>
    <bug_when>2006-01-13 03:30:08 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>405676</commentid>
    <comment_count>27</comment_count>
    <who name="Marcus D. Hanwell">marcus</who>
    <bug_when>2006-01-13 03:38:15 +0000</bug_when>
    <thetext>That could be the case for causing the crashes. At work I use the same version of kmail but don&apos;t have the 3rd account set up which is the one with all the big folders. It hasn&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>405677</commentid>
    <comment_count>28</comment_count>
    <who name="John Myers">electronerd</who>
    <bug_when>2006-01-13 03:48:43 +0000</bug_when>
    <thetext>I should also mention that once triggered, the crashes on startup usually go away if I send myself some mail (with the &apos;mail&apos; command or something) so that I have new mail that KMail hasn&apos;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)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>405688</commentid>
    <comment_count>29</comment_count>
    <who name="Juha Tuomala">tuju</who>
    <bug_when>2006-01-13 06:56:47 +0000</bug_when>
    <thetext>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&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>406244</commentid>
    <comment_count>30</comment_count>
    <who name="Patrick Audley">paudley</who>
    <bug_when>2006-01-15 03:15:27 +0000</bug_when>
    <thetext>I see this crash occasionally and have verified that it&apos;s only with automatic checks on.  I have 100+ folders with between 3000-5000 messages so it&apos;s possible that it&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>406248</commentid>
    <comment_count>31</comment_count>
    <who name="Marcus D. Hanwell">marcus</who>
    <bug_when>2006-01-15 03:40:05 +0000</bug_when>
    <thetext>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 :)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>408559</commentid>
    <comment_count>32</comment_count>
    <who name="Marcus D. Hanwell">marcus</who>
    <bug_when>2006-01-24 11:52:23 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>408594</commentid>
    <comment_count>33</comment_count>
    <who name="Thomas Beinicke">Merlin-TC</who>
    <bug_when>2006-01-24 14:14:34 +0000</bug_when>
    <thetext>I have been experiencing it for a long time as well.
Sometimes it doesn&apos;t occur for days but it keeps returning.
The crash is also on a &quot;per folder basis&quot; 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&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>409278</commentid>
    <comment_count>34</comment_count>
    <who name="Tommi Tervo">tommi.tervo</who>
    <bug_when>2006-01-27 09:36:32 +0000</bug_when>
    <thetext>*** Bug 117844 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>409730</commentid>
    <comment_count>35</comment_count>
    <who name="Juha Tuomala">tuju</who>
    <bug_when>2006-01-29 11:52:09 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>409752</commentid>
    <comment_count>36</comment_count>
    <who name="Marcus D. Hanwell">marcus</who>
    <bug_when>2006-01-29 14:27:24 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>416958</commentid>
    <comment_count>37</comment_count>
    <who name="Tommi Tervo">tommi.tervo</who>
    <bug_when>2006-02-24 11:31:31 +0000</bug_when>
    <thetext>*** Bug 122588 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>416969</commentid>
    <comment_count>38</comment_count>
    <who name="Tommi Tervo">tommi.tervo</who>
    <bug_when>2006-02-24 11:57:30 +0000</bug_when>
    <thetext>*** Bug 122564 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>417813</commentid>
    <comment_count>39</comment_count>
    <who name="ratko">ratko</who>
    <bug_when>2006-02-27 14:13:40 +0000</bug_when>
    <thetext>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 &quot;/lib/tls/libthread_db.so.1&quot;.
[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...
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>417848</commentid>
    <comment_count>40</comment_count>
    <who name="">monstermunch</who>
    <bug_when>2006-02-27 17:18:51 +0000</bug_when>
    <thetext>I can confirm that this bug still exists on Suse 10 with KDE 3.5.1. It&apos;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? :-(</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>417849</commentid>
    <comment_count>41</comment_count>
    <who name="">monstermunch</who>
    <bug_when>2006-02-27 17:19:02 +0000</bug_when>
    <thetext>I can confirm that this bug still exists on Suse 10 with KDE 3.5.1. It&apos;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? :-(</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>431461</commentid>
    <comment_count>42</comment_count>
    <who name="Timo Weingärtner">timo</who>
    <bug_when>2006-04-16 21:54:40 +0000</bug_when>
    <thetext>The procedure described in #40 (and #41) works for me too. KMail 4:3.5.2-1 on Debian testing/unstable.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>432993</commentid>
    <comment_count>43</comment_count>
    <who name="Tommi Tervo">tommi.tervo</who>
    <bug_when>2006-04-21 21:03:48 +0000</bug_when>
    <thetext>*** Bug 126022 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>453380</commentid>
    <comment_count>44</comment_count>
    <who name="Imre Péntek">pentek.imre</who>
    <bug_when>2006-07-13 08:30:30 +0000</bug_when>
    <thetext>Still present in kmail 1.9.3
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>457163</commentid>
    <comment_count>45</comment_count>
    <who name="Andreas Kling">info</who>
    <bug_when>2006-07-31 23:23:10 +0000</bug_when>
    <thetext>*** Bug 118161 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>457167</commentid>
    <comment_count>46</comment_count>
    <who name="Andreas Kling">info</who>
    <bug_when>2006-07-31 23:24:10 +0000</bug_when>
    <thetext>*** Bug 117935 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>457169</commentid>
    <comment_count>47</comment_count>
    <who name="Andreas Kling">info</who>
    <bug_when>2006-07-31 23:24:20 +0000</bug_when>
    <thetext>*** Bug 122982 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>457171</commentid>
    <comment_count>48</comment_count>
    <who name="Andreas Kling">info</who>
    <bug_when>2006-07-31 23:24:43 +0000</bug_when>
    <thetext>*** Bug 130246 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>457173</commentid>
    <comment_count>49</comment_count>
    <who name="Andreas Kling">info</who>
    <bug_when>2006-07-31 23:24:58 +0000</bug_when>
    <thetext>*** Bug 130574 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>457178</commentid>
    <comment_count>50</comment_count>
    <who name="Andreas Kling">info</who>
    <bug_when>2006-07-31 23:29:23 +0000</bug_when>
    <thetext>*** Bug 115887 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>458581</commentid>
    <comment_count>51</comment_count>
    <who name="Tommi Tervo">tommi.tervo</who>
    <bug_when>2006-08-07 08:57:20 +0000</bug_when>
    <thetext>*** Bug 131957 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>461755</commentid>
    <comment_count>52</comment_count>
    <who name="Andreas Kling">info</who>
    <bug_when>2006-08-20 09:47:10 +0000</bug_when>
    <thetext>*** Bug 132638 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>461757</commentid>
    <comment_count>53</comment_count>
    <who name="Andreas Kling">info</who>
    <bug_when>2006-08-20 09:47:31 +0000</bug_when>
    <thetext>*** Bug 132669 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>461900</commentid>
    <comment_count>54</comment_count>
    <who name="Ralph Moenchmeyer">rm</who>
    <bug_when>2006-08-20 22:04:58 +0000</bug_when>
    <thetext> 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. </thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>461950</commentid>
    <comment_count>55</comment_count>
    <who name="Nathaniel Taylor">kden</who>
    <bug_when>2006-08-21 00:12:53 +0000</bug_when>
    <thetext>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&apos;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&apos;s ssl or tls to help root out the problem -- it&apos;s a very time-wasting problem for me, and very annoying.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>462090</commentid>
    <comment_count>56</comment_count>
    <who name="Sebastian Reitenbach">itlistuser</who>
    <bug_when>2006-08-21 16:47:25 +0000</bug_when>
    <thetext>my kmail is connected to a cyrus imapd via SSL too.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>462094</commentid>
    <comment_count>57</comment_count>
    <who name="John Myers">electronerd</who>
    <bug_when>2006-08-21 17:17:58 +0000</bug_when>
    <thetext>This problem suddenly stopped for me around 3.5.3, IIRC. (but I don&apos;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...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>462368</commentid>
    <comment_count>58</comment_count>
    <who name="Tommi Tervo">tommi.tervo</who>
    <bug_when>2006-08-22 15:45:38 +0000</bug_when>
    <thetext>*** Bug 132796 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>462663</commentid>
    <comment_count>59</comment_count>
    <who name="Tommi Tervo">tommi.tervo</who>
    <bug_when>2006-08-23 14:37:11 +0000</bug_when>
    <thetext>*** Bug 120725 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>463148</commentid>
    <comment_count>60</comment_count>
    <who name="Ralph Moenchmeyer">rm</who>
    <bug_when>2006-08-25 09:43:26 +0000</bug_when>
    <thetext>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?  </thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>463188</commentid>
    <comment_count>61</comment_count>
    <who name="Imre Péntek">pentek.imre</who>
    <bug_when>2006-08-25 11:59:48 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>463195</commentid>
    <comment_count>62</comment_count>
    <who name="Julian Mehnle">julian</who>
    <bug_when>2006-08-25 12:28:26 +0000</bug_when>
    <thetext>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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>464136</commentid>
    <comment_count>63</comment_count>
    <who name="Carsten Burghardt">burghardt</who>
    <bug_when>2006-08-29 13:02:47 +0000</bug_when>
    <thetext>*** Bug 133172 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>464304</commentid>
    <comment_count>64</comment_count>
    <who name="Elan Ruusamäe">glen</who>
    <bug_when>2006-08-29 19:16:40 +0000</bug_when>
    <thetext>my setup is 1 disconnected imap, 1 online imap, but i don&apos;t think the disconnected imap has role here as my default startup folder was online imap. changing the folder to open at startup &quot;resolved&quot; 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&apos;s top from my kcrashdialog. note i avoided the crash by changing default startup folder. but if i &quot;enter&quot; the broke imap account the backtrace is:

Using host libthread_db library &quot;/lib/tls/libthread_db.so.1&quot;.
[KCrash handler]
#6  0xb7294735 in QMap&lt;KPIM::ProgressItem*, bool&gt;::detach (this=0x887aa88)
    at /usr/include/qt/qmap.h:739
#7  0xb7294137 in QMap&lt;KPIM::ProgressItem*, bool&gt;::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&apos;d be happy to provide more information to get this ProgressItem related bug resolved finally (i&apos;ve kept the corrupted imap account for this purpose).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>506213</commentid>
    <comment_count>65</comment_count>
    <who name="Tommi Tervo">tommi.tervo</who>
    <bug_when>2007-02-03 16:59:34 +0000</bug_when>
    <thetext>*** Bug 138369 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>508431</commentid>
    <comment_count>66</comment_count>
    <who name="Ralph Moenchmeyer">rm</who>
    <bug_when>2007-02-11 18:13:30 +0000</bug_when>
    <thetext>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 -&gt; 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. </thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>516249</commentid>
    <comment_count>67</comment_count>
    <who name="Stephan Kulow">coolo</who>
    <bug_when>2007-03-20 09:40:04 +0000</bug_when>
    <thetext>you lost your bad luck - that&apos;s about everything that has changed ;(</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>516322</commentid>
    <comment_count>68</comment_count>
    <who name="Will Stephenson">wstephenson</who>
    <bug_when>2007-03-20 19:47:09 +0000</bug_when>
    <thetext>SVN commit 644705 by wstephens:

Don&apos;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-&gt;processNewMail(interactive);
+          bool ok = imapFolder-&gt;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-&gt;incCompletedItems();
               mMailCheckProgressItem-&gt;updateProgress();
             }
+            // since the list of folders might have been updated at this point, mMailCheckFolders may be invalid, so break
+            break;
           }
         }
       }
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>516409</commentid>
    <comment_count>69</comment_count>
    <who name="Stephan Kulow">coolo</who>
    <bug_when>2007-03-21 08:08:17 +0000</bug_when>
    <thetext>SVN commit 644877 by coolo:

Don&apos;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-&gt;processNewMail(interactive);
+          bool ok = imapFolder-&gt;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-&gt;incCompletedItems();
               mMailCheckProgressItem-&gt;updateProgress();
             }
+            // since the list of folders might have been updated at this point, mMailCheckFolders may be invalid, so break
+            break;
           }
         }
       }
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>541195</commentid>
    <comment_count>70</comment_count>
    <who name="Thomas McGuire">mcguire</who>
    <bug_when>2007-08-16 18:19:50 +0000</bug_when>
    <thetext>*** Bug 148874 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>601535</commentid>
    <comment_count>71</comment_count>
      <attachid>24788</attachid>
    <who name="Erwin Mueller">funnyacc</who>
    <bug_when>2008-05-16 10:43:20 +0000</bug_when>
    <thetext>Created attachment 24788
The kcrash file from debuger</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>601536</commentid>
    <comment_count>72</comment_count>
    <who name="Erwin Mueller">funnyacc</who>
    <bug_when>2008-05-16 10:44:16 +0000</bug_when>
    <thetext>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&apos;s fine.

Have added the kcrash file.</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>24788</attachid>
            <date>2008-05-16 10:43:20 +0000</date>
            <delta_ts>2008-05-16 10:43:20 +0000</delta_ts>
            <desc>The kcrash file from debuger</desc>
            <filename>kmail.kcrash</filename>
            <type>text/plain</type>
            <size>4846</size>
            <attacher name="Erwin Mueller">funnyacc</attacher>
            
              <data encoding="base64">KG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQp
CihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5k
KQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3Vu
ZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91
bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZv
dW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBm
b3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMg
Zm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xz
IGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9s
cyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJv
bHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1i
b2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3lt
Ym9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5
bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBz
eW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcg
c3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5n
IHN5bWJvbHMgZm91bmQpCltUaHJlYWQgZGVidWdnaW5nIHVzaW5nIGxpYnRocmVhZF9kYiBlbmFi
bGVkXQpbTmV3IFRocmVhZCAweGI1OGMzNmMwIChMV1AgMjcyNDIpXQpbTmV3IFRocmVhZCAweGIz
YjRmYjkwIChMV1AgMjcyNDYpXQpbTmV3IFRocmVhZCAweGI0MzUwYjkwIChMV1AgMjcyNDUpXQpb
TmV3IFRocmVhZCAweGI0YjUxYjkwIChMV1AgMjcyNDQpXQpbTmV3IFRocmVhZCAweGI1MzUyYjkw
IChMV1AgMjcyNDMpXQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcg
c3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5n
IHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2lu
ZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dp
bmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdn
aW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVn
Z2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1
Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVi
dWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRl
YnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBk
ZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8g
ZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5v
IGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihu
byBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoo
bm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkK
KG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQp
CihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5k
KQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3Vu
ZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91
bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZv
dW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBm
b3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xzIGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMg
Zm91bmQpCihubyBkZWJ1Z2dpbmcgc3ltYm9scyBmb3VuZCkKKG5vIGRlYnVnZ2luZyBzeW1ib2xz
IGZvdW5kKQoobm8gZGVidWdnaW5nIHN5bWJvbHMgZm91bmQpCltLQ3Jhc2ggaGFuZGxlcl0KIzYg
IDB4YjczYTVjMjggaW4gUU1hcFByaXZhdGVCYXNlOjpyZW1vdmVBbmRSZWJhbGFuY2UgKCkKICAg
ZnJvbSAvdXNyL2xpYi9saWJxdC1tdC5zby4zCiM3ICAweGI3ZDI2YzY1IGluIEtNYWlsOjpJbWFw
QWNjb3VudEJhc2U6OnJlbW92ZUpvYiAoKQogICBmcm9tIC91c3IvbGliL2xpYmttYWlscHJpdmF0
ZS5zbwojOCAgMHhiN2Q0ZjE4ZSBpbiBLTUZvbGRlckltYXA6OnNsb3RMaXN0Rm9sZGVyUmVzdWx0
ICgpCiAgIGZyb20gL3Vzci9saWIvbGlia21haWxwcml2YXRlLnNvCiM5ICAweGI3ZDUyYTFjIGlu
IEtNRm9sZGVySW1hcDo6cXRfaW52b2tlICgpIGZyb20gL3Vzci9saWIvbGlia21haWxwcml2YXRl
LnNvCiMxMCAweGI3MGVkZjZkIGluIFFPYmplY3Q6OmFjdGl2YXRlX3NpZ25hbCAoKSBmcm9tIC91
c3IvbGliL2xpYnF0LW10LnNvLjMKIzExIDB4YjVkNjM5ZWUgaW4gS0lPOjpKb2I6OnJlc3VsdCAo
KSBmcm9tIC91c3IvbGliL2xpYmtpby5zby40CiMxMiAweGI1ZGE5OTlkIGluIEtJTzo6Sm9iOjpl
bWl0UmVzdWx0ICgpIGZyb20gL3Vzci9saWIvbGlia2lvLnNvLjQKIzEzIDB4YjVkYTliMGUgaW4g
S0lPOjpTaW1wbGVKb2I6OnNsb3RGaW5pc2hlZCAoKSBmcm9tIC91c3IvbGliL2xpYmtpby5zby40
CiMxNCAweGI1ZGE5ZTYzIGluIEtJTzo6TGlzdEpvYjo6c2xvdEZpbmlzaGVkICgpIGZyb20gL3Vz
ci9saWIvbGlia2lvLnNvLjQKIzE1IDB4YjVkNzYzODMgaW4gS0lPOjpTaW1wbGVKb2I6OnNsb3RF
cnJvciAoKSBmcm9tIC91c3IvbGliL2xpYmtpby5zby40CiMxNiAweGI1ZGE5NTVkIGluIEtJTzo6
U2ltcGxlSm9iOjpxdF9pbnZva2UgKCkgZnJvbSAvdXNyL2xpYi9saWJraW8uc28uNAojMTcgMHhi
NWRiZTY4MiBpbiBLSU86Okxpc3RKb2I6OnF0X2ludm9rZSAoKSBmcm9tIC91c3IvbGliL2xpYmtp
by5zby40CiMxOCAweGI3MGVkZWQxIGluIFFPYmplY3Q6OmFjdGl2YXRlX3NpZ25hbCAoKSBmcm9t
IC91c3IvbGliL2xpYnF0LW10LnNvLjMKIzE5IDB4YjVkNjAzMTAgaW4gS0lPOjpTbGF2ZUludGVy
ZmFjZTo6ZXJyb3IgKCkgZnJvbSAvdXNyL2xpYi9saWJraW8uc28uNAojMjAgMHhiNWRhOGUwZSBp
biBLSU86OlNsYXZlSW50ZXJmYWNlOjpkaXNwYXRjaCAoKSBmcm9tIC91c3IvbGliL2xpYmtpby5z
by40CiMyMSAweGI1ZGNhZGJhIGluIEtJTzo6U2xhdmVJbnRlcmZhY2U6OmRpc3BhdGNoICgpIGZy
b20gL3Vzci9saWIvbGlia2lvLnNvLjQKIzIyIDB4YjVkNzFlN2MgaW4gS0lPOjpTbGF2ZTo6Z290
SW5wdXQgKCkgZnJvbSAvdXNyL2xpYi9saWJraW8uc28uNAojMjMgMHhiNWRhMDIzOCBpbiBLSU86
OlNsYXZlOjpxdF9pbnZva2UgKCkgZnJvbSAvdXNyL2xpYi9saWJraW8uc28uNAojMjQgMHhiNzBl
ZGY2ZCBpbiBRT2JqZWN0OjphY3RpdmF0ZV9zaWduYWwgKCkgZnJvbSAvdXNyL2xpYi9saWJxdC1t
dC5zby4zCiMyNSAweGI3MGVlOWYwIGluIFFPYmplY3Q6OmFjdGl2YXRlX3NpZ25hbCAoKSBmcm9t
IC91c3IvbGliL2xpYnF0LW10LnNvLjMKIzI2IDB4Yjc0MThlNTAgaW4gUVNvY2tldE5vdGlmaWVy
OjphY3RpdmF0ZWQgKCkgZnJvbSAvdXNyL2xpYi9saWJxdC1tdC5zby4zCiMyNyAweGI3MTBiYTAw
IGluIFFTb2NrZXROb3RpZmllcjo6ZXZlbnQgKCkgZnJvbSAvdXNyL2xpYi9saWJxdC1tdC5zby4z
CiMyOCAweGI3MDkwMThhIGluIFFBcHBsaWNhdGlvbjo6aW50ZXJuYWxOb3RpZnkgKCkgZnJvbSAv
dXNyL2xpYi9saWJxdC1tdC5zby4zCiMyOSAweGI3MDkwZjc2IGluIFFBcHBsaWNhdGlvbjo6bm90
aWZ5ICgpIGZyb20gL3Vzci9saWIvbGlicXQtbXQuc28uMwojMzAgMHhiNzc0MGVjMiBpbiBLQXBw
bGljYXRpb246Om5vdGlmeSAoKSBmcm9tIC91c3IvbGliL2xpYmtkZWNvcmUuc28uNAojMzEgMHhi
NzA4NGE0NyBpbiBRRXZlbnRMb29wOjphY3RpdmF0ZVNvY2tldE5vdGlmaWVycyAoKQogICBmcm9t
IC91c3IvbGliL2xpYnF0LW10LnNvLjMKIzMyIDB4YjcwM2YxZDAgaW4gUUV2ZW50TG9vcDo6cHJv
Y2Vzc0V2ZW50cyAoKSBmcm9tIC91c3IvbGliL2xpYnF0LW10LnNvLjMKIzMzIDB4YjcwYTZiODAg
aW4gUUV2ZW50TG9vcDo6ZW50ZXJMb29wICgpIGZyb20gL3Vzci9saWIvbGlicXQtbXQuc28uMwoj
MzQgMHhiNzBhNmExNiBpbiBRRXZlbnRMb29wOjpleGVjICgpIGZyb20gL3Vzci9saWIvbGlicXQt
bXQuc28uMwojMzUgMHhiNzA4ZmNmZiBpbiBRQXBwbGljYXRpb246OmV4ZWMgKCkgZnJvbSAvdXNy
L2xpYi9saWJxdC1tdC5zby4zCiMzNiAweDA4MDRhMmVkIGluID8/ICgpCiMzNyAweGJmZjFjNzkw
IGluID8/ICgpCiMzOCAweGJmZjFjOTgwIGluID8/ICgpCiMzOSAweDAwMDAwMDAwIGluID8/ICgp
Cg==
</data>

          </attachment>
      

    </bug>

</bugzilla>