Version: 1.13.5 (using KDE 4.5.0) OS: Linux After my computer has been put to slept and subsequently woken up, Kontact will go into a "special place" where KMail becomes unable to communicate with any servers - every operation will just hang forever saying "Getting new mail" etc. Closing Kontact and doing ps aux|grep kontact will reveal it's still running, and you will find you have to kill it to be able to start Kontact again. In KDE 4.4.5, the same problem existed, except here, when closing Kontact and then restarting it, it would crash on start, then you'd start it again, and it would start normally. Reproducible: Always Steps to Reproduce: As described :) Actual Results: As described :) OS: Linux (x86_64) release 2.6.34-zen1-daniel Compiler: cc
I have the exact same problem. When my laptop awakes from sleep (suspend to RAM), the WiFi network needs to reconnect and everything then works normally except for KMail. Most of the time KMail will appear to be working and will report that no new messages are found on the server (even though there *are* new messages, but I can't know that until later). However, if I switch IMAP folders, I just get the "Retrieving folder messages" page indefinitely, so then I know that something is wrong. When this happens, quitting KMail and restarting it does not work. If I just use "File -> Quit" the "kmail" process will remain running in the background (with no window). Only if I kill this process and start KMail again does it go back to normal...until the next time I close the lid on the laptop and put it back to sleep. As this happens several times a day, it is very annoying and I often miss e-mails for a day or two. I'm thinking of switching to a different MUA, as KMail (which I've used for about a decade on desktop systems) is more trouble than it's worth on a laptop. OS: Linux 2.6.38.8-32.fc15.x86_64 (Fedora 15 64-bit) KDE version: 4.6.3 KMail version: 1.13.7 (I'm not using Kontact, just standalone KMail)
I think you should consider KDEPIM abandonware for the time being until we see something Akonadi-based. Bugs don't seem to be fixed at all, and the suite is seriously alpha state. For instance, don't use IMAP, it'll more than likely destroy every email timestamp on the server. All my emails have had their timestamps destroyed on both company mail and GMail servers. Ever get a mail and a duplicate of it shortly after and blamed it on the server? Nope, that's KMail destroying the timestamp and then creating a duplicate on the server for you. Sorry, this isn't really the forum for this, just happened to be on the list and noticed your IMAP statement and wanted to warn you.
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.