Version: (using Devel) OS: Linux Installed from: Compiled sources First a short question: Is it a new way to piss of users to not let them post crash reports against the latest KDE 3.5 version or is this just an error? This bug is new since 3.5.10 and KMail crashes always when it starts to fetch emails, so it's not usable here. http://websvn.kde.org/?view=rev&revision=800206 will be the problem, I guess. Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb565b6d0 (LWP 9257)] [New Thread 0xb3807b90 (LWP 9261)] [New Thread 0xb4008b90 (LWP 9260)] [New Thread 0xb4809b90 (LWP 9259)] [New Thread 0xb500ab90 (LWP 9258)] [KCrash handler] #6 0xb693d234 in KMime::decodeRFC2047String (src=@0xbf8ceacc, usedCS=0xbf8cea28, defaultCS=@0xbf8cea20, forceCS=false) at kmime_util.cpp:198 #7 0xb693d334 in KMime::decodeRFC2047String (src=@0xbf8ceacc) at kmime_util.cpp:241 #8 0xb7f1319c in KPIM::normalizeAddressesAndDecodeIDNs (str=@0xbf8ceb68) at email.cpp:867 #9 0xb7b7218c in KMMessage::from (this=0x9a81198) at kmmessage.cpp:1998 #10 0xb7b721ef in KMMessage::fromStrip (this=0x9a81198) at kmmessage.cpp:2016 #11 0xb7cc8dc8 in KMMsgBase::asIndexString (this=0x9a81198, length=@0xbf8ceddc) at kmmsgbase.cpp:1342 #12 0xb7d20a60 in KMFolderMaildir::addMsgInternal (this=0x8eb8c58, aMsg=0x9a81198, index_return=0x0, stripUid=false) at kmfoldermaildir.cpp:491 #13 0xb7d213f2 in KMFolderMaildir::addMsg (this=0x8eb8c58, aMsg=0x9a81198, index_return=0x0) at kmfoldermaildir.cpp:354 #14 0xb7c6b7b0 in FolderStorage::moveMsg (this=0x8eb8c58, aMsg=0x9a81198, aIndex_ret=0x0) at folderstorage.cpp:617 #15 0xb7c48c75 in KMFolder::moveMsg (this=0x8eb7310, msg=0x9a81198, index_return=0x0) at kmfolder.cpp:423 #16 0xb7c995e2 in KMFilterMgr::process (this=0x9050378, msg=0x9a81198, set=KMFilterMgr::Inbound, account=true, accountId=2097321245) at kmfiltermgr.cpp:283 #17 0xb7bfb180 in KMAccount::processNewMsg (this=0x8f15038, aMsg=0x9a81198) at kmaccount.cpp:251 #18 0xb7d25b80 in KMail::PopAccount::slotProcessPendingMsgs (this=0x8f15038) at popaccount.cpp:326 #19 0xb7d26265 in KMail::PopAccount::processRemainingQueuedMessages ( this=0x8f15038) at popaccount.cpp:818 #20 0xb7d27d35 in KMail::PopAccount::slotJobFinished (this=0x8f15038) at popaccount.cpp:667 #21 0xb7d29448 in KMail::PopAccount::slotResult (this=0x8f15038) at popaccount.cpp:1039 #22 0xb7d29725 in KMail::PopAccount::qt_invoke (this=0x8f15038, _id=9, _o=0xbf8cf744) at popaccount.moc:120 #23 0xb7276979 in QObject::activate_signal (this=0x8f68fe8, clist=0x972a970, o=0xbf8cf744) at kernel/qobject.cpp:2359 #24 0xb61edaaf in KIO::Job::result (this=0x8f68fe8, t0=0x8f68fe8) at jobclasses.moc:162 #25 0xb61f422c in KIO::Job::emitResult (this=0x8f68fe8) at job.cpp:235 #26 0xb61f46b6 in KIO::SimpleJob::slotFinished (this=0x8f68fe8) at job.cpp:601 #27 0xb61f4df9 in KIO::TransferJob::slotFinished (this=0x8f68fe8) at job.cpp:971 #28 0xb61f2a2d in KIO::TransferJob::qt_invoke (this=0x8f68fe8, _id=17, _o=0xbf8cfa78) at jobclasses.moc:1071 #29 0xb7276979 in QObject::activate_signal (this=0x97fad40, clist=0x9a17368, o=0xbf8cfa78) at kernel/qobject.cpp:2359 #30 0xb72775cd in QObject::activate_signal (this=0x97fad40, signal=6) at kernel/qobject.cpp:2328 #31 0xb61db091 in KIO::SlaveInterface::finished (this=0x97fad40) at slaveinterface.moc:226 #32 0xb61dcae5 in KIO::SlaveInterface::dispatch (this=0x97fad40, _cmd=104, rawdata=@0xbf8cfc90) at slaveinterface.cpp:243 #33 0xb61dd1b2 in KIO::SlaveInterface::dispatch (this=0x97fad40) at slaveinterface.cpp:173 #34 0xb61d801d in KIO::Slave::gotInput (this=0x97fad40) at slave.cpp:300 #35 0xb61d9fde in KIO::Slave::qt_invoke (this=0x97fad40, _id=4, _o=0xbf8cfdb4) at slave.moc:113 #36 0xb7276979 in QObject::activate_signal (this=0x97fab98, clist=0x97fafd8, o=0xbf8cfdb4) at kernel/qobject.cpp:2359 #37 0xb72774d2 in QObject::activate_signal (this=0x97fab98, signal=2, param=19) at kernel/qobject.cpp:2452 #38 0xb75abc10 in QSocketNotifier::activated (this=0x97fab98, t0=19) at .moc/release-shared-mt/moc_qsocketnotifier.cpp:85 #39 0xb729437f in QSocketNotifier::event (this=0x97fab98, e=0xbf8d0078) at kernel/qsocketnotifier.cpp:261 #40 0xb7218017 in QApplication::internalNotify (this=0xbf8d0270, receiver=0x97fab98, e=0xbf8d0078) at kernel/qapplication.cpp:2638 #41 0xb7218b91 in QApplication::notify (this=0xbf8d0270, receiver=0x97fab98, e=0xbf8d0078) at kernel/qapplication.cpp:2361 #42 0xb77a9076 in KApplication::notify (this=0xbf8d0270, receiver=0x97fab98, event=0xbf8d0078) at kapplication.cpp:550 #43 0xb720ccf1 in QEventLoop::activateSocketNotifiers (this=0x8cf67c0) at kernel/qapplication.h:499 #44 0xb71c743a in QEventLoop::processEvents (this=0x8cf67c0, flags=4) at kernel/qeventloop_x11.cpp:386 #45 0xb722e6f0 in QEventLoop::enterLoop (this=0x8cf67c0) at kernel/qeventloop.cpp:201 #46 0xb722e576 in QEventLoop::exec (this=0x8cf67c0) at kernel/qeventloop.cpp:148 #47 0xb7217aaf in QApplication::exec (this=0xbf8d0270) at kernel/qapplication.cpp:2761 #48 0x0804ab59 in main (argc=1162170960, argv=0xbf8cc378) at main.cpp:110 #49 0xb6dd4fdc in __libc_start_main () from /lib/libc.so.6 #50 0x0804a961 in _start ()
As a workaround reversing the relevant code in kmmessage.cpp not to use the rawheader, I got KMail working again. Remains the question, which email triggered the bug. Highly likely is an email in my spam folder, so if anyone is interested, I'm fine to tar up my spam emails from today and make them available.
*** Bug 175190 has been marked as a duplicate of this bug. ***
After looking at 230 spam mails that triggers this bug in your kmail version, I can say that in kmail 1.10.0 (kde 4.1.72) this bug is no longer present. Thanks for your spam mails (now you can delete them :-) ).
*** Bug 165874 has been marked as a duplicate of this bug. ***