Version: 1.10.90 (using 4.1.67 (KDE 4.1.67 (KDE 4.2 >= 20080918)), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS: Linux (x86_64) release 2.6.25-gentoo-r4 Well it usually work to delete a message, but this is the third email in 2 days that does this:after reading it I press delete, the busy cursor appears and then nothing happens no matter how long I wait. In console kmail goes like this : ail(7539)/kdepimlibs (kabc) KABC::StdAddressBook::self: kmail(7539) KMail::FancyHeaderStyle::format: Multiple / No addressees matched email address; Count is 0 kmail(7539) KMail::ObjectTreeParser::parseObjectTree: node OK, showOnlyOneMimePart: FALSE kmail(7539) KMail::ObjectTreeParser::processMailmanMessage: Sorry: Old style Mailman message but no delimiter found. kmail(7539) KMReaderWin::overrideCodec: mOverrideEncoding == ' "" ' kmail(7539) KMReaderWin::parseMsg: Finished parsing and displaying of message. kmail(7539)/kmail (storage internals) KMFolderMaildir::getDwString: KDE_fopen(abs_file= "/home/cuci/.kdesvn/share/apps/kmail/mail/.inbox.directory/python-tutor/cur/1222691729.3377.8Dp4W" , "r+") == stream == 0xeeded0 kmail(7539)/kmail (storage internals) KMFolderMaildir::getDwString: fclose(mIndexStream = 0xeeded0 ) kmail(7539) KMReaderWin::setMsg: ( 9224 , last 0 ) "Re: [Tutor] Hello and some questions." "Andre Engels" , readyToShow true kmail(7539) KMReaderWin::overrideCodec: mOverrideEncoding == ' "" ' kmail(7539)/kmail (storage internals) KMFolderIndex::openInternal: KDE_fopen(indexLocation()= "/home/cuci/.kdesvn/share/apps/kmail/mail/.trash.index" , "r+") == mIndexStream == 0x120d260 Any further info I can provide I'll be happy to do so
Further info: the message in question is in a folder with "thread messages" checked and it's a first thread message. If I first delete all the messages responding to it I can then safely delete that message to
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.