Version: (using KDE 4.4.1) Installed from: openSUSE RPMs I have an e-mail in IMAP-server that has been there for a while now. Today KMail started crashing every time it tries to display the message. Before this started happening I had a spam in my Inbox that I tried to move to my Spam folder, but as KMail crashed every time trying to do that, I moved it away with Thunderbird. Doing this, the message that crashes KMail now (while trying to display it) moved from 2nd place to 1st place in the message list. The error while crashing: kmail(8959)/kio (KIOJob) KIO::TransferJob::slotData: mimetype() not emitted when sending first data!; job URL = KUrl("imap://silver@myserv:143/INBOX/;UID=48460;SECTION=BODY.PEEK[1.1]") data size = 1772 kmail(8959) KMReaderWin::parseMsg: The root node is not yet processed! Danger! kmail(8959) KMReaderWin::parseMsg: The root node is not yet processed! Danger! kmail(8959)/kio (Slave) KIO::Slave::createSlave: createSlave "data" for KUrl("data:image/PNG;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAABCAMAAADpTH4XAAAASFBMVEUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD///+qqqoAAAD2cKDYAAAAGHRSTlMAAAAAAAAAAAAAAAAAAAAAAAAAAAD//wCysdQaAAAACXBIWXMAAA6cAAAOxAF19oSBAAAAC0lEQVQImWMQxQIAEU8BpQ0ofWgAAAAASUVORK5CYII=") kmail(8959)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on "local:/tmp/ksocket-silver/kmailOu8959.slave-socket" kmail(8959)/kio (KIOJob) KIO::TransferJob::slotData: mimetype() not emitted when sending first data!; job URL = KUrl("imap://silver@myserv:143/INBOX/;UID=48460;SECTION=BODY.PEEK[1.2]") data size = 3975 kmail(8959) KMReaderWin::parseMsg: The root node is not yet processed! Danger! *** KMail got signal 11 (Crashing) KCrash: Application 'kmail' crashing... sock_file=/home/silver/.kde4/socket-silver/kdeinit4__0
Please paste the backtrace you get when KMail crashes.
Created attachment 41515 [details] gdb backtrace
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!