Bug 102290

Summary: crash when reconnecting to imaps after lost connection
Product: [Unmaintained] kmail Reporter: Allen Smith <lazlor>
Component: IMAPAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash    
Priority: NOR    
Version: 1.7.1   
Target Milestone: ---   
Platform: RedHat Enterprise Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Allen Smith 2005-03-23 16:55:06 UTC
Version:           1.7.1 (using KDE KDE 3.3.1)
Installed from:    RedHat RPMs
OS:                Linux

I left my system overnight and my imap connections were dropped at some point. When I typed in my passwords and clicked on the inbox of one of my imaps accounts, I got this backtrace (sorry don't have complete symbols):

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208326464 (LWP 6554)]
[KCrash handler]
#4  0x04b4a631 in QObject::receivers () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#5  0x059650dc in KPIM::ProgressItem::progressItemProgress ()
   from /usr/lib/libkdepim.so.1
#6  0x0596519b in KPIM::ProgressItem::setProgress ()
   from /usr/lib/libkdepim.so.1
#7  0x0602670d in KMAcctImap::postProcessNewMail ()
   from /usr/lib/libkmailprivate.so.0
#8  0x06026a82 in KMAcctImap::qt_invoke () from /usr/lib/libkmailprivate.so.0
#9  0x04b4d329 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#10 0x05fba878 in FolderStorage::numUnreadMsgsChanged ()
   from /usr/lib/libkmailprivate.so.0
#11 0x06040062 in KMFolderImap::slotStatResult ()
   from /usr/lib/libkmailprivate.so.0
#12 0x06040262 in KMFolderImap::qt_invoke ()
   from /usr/lib/libkmailprivate.so.0
#13 0x04b4d3a0 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#14 0x055e620d in KIO::Job::result () from /usr/lib/libkio.so.4
#15 0x055e6280 in KIO::Job::emitResult () from /usr/lib/libkio.so.4
#16 0x055e8884 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.4
#17 0x055f5bb8 in KIO::StatJob::slotFinished () from /usr/lib/libkio.so.4
#18 0x055eb154 in KIO::StatJob::qt_invoke () from /usr/lib/libkio.so.4
#19 0x04b4d3a0 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x04b4da7a in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x055d4f3c in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.4
#22 0x055d7b36 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#23 0x055d672f in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#24 0x055d2706 in KIO::Slave::gotInput () from /usr/lib/libkio.so.4
#25 0x055d2a8f in KIO::Slave::qt_invoke () from /usr/lib/libkio.so.4
#26 0x04b4d3a0 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#27 0x04b4d932 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x04e7f1c0 in QSocketNotifier::activated ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#29 0x04b68425 in QSocketNotifier::event ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#30 0x04aee849 in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#31 0x04aee9da in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#32 0x050663b8 in KApplication::notify () from /usr/lib/libkdecore.so.4
#33 0x04ae2d04 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#34 0x04a9eb8e in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#35 0x04b03e75 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#36 0x04b03dce in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#37 0x04aeda4b in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#38 0x0804a2f8 in ?? ()
#39 0xbfe70950 in ?? ()
#40 0xbfe70860 in ?? ()
#41 0x00000000 in ?? ()
Comment 1 Carsten Burghardt 2005-05-22 22:41:42 UTC
We need either a way to reproduce or a complete backtrace. Please update to 3.4 and see if you can reproduce it.