When running kmail, it is set to get my mail at start-up, which works. When I try to select a message, however, the program locks up, no response, no active icons on the program menu, for around (subjective impression) 30 seconds, then the message is selected. If I try to open the message, click another message or click on a different directory (trash, sent, etc), the same thing happens. If I try to close the program, even, it fails to respond and the window manager asks whether it should terminate the program. If I decline, the program will close of its own accord within about 30 seconds. I was thinking it could be akonadi, but kaddressbook also uses akonadi and it works fine. Could it be virtuoso/nepomuk? I have email indexing disabled, or, as it is called, suspended. Reproducible: Always Actual Results: The software is close to being unusable in this state. It is close to pointless to sit for half a minute, just to select an email, wait another half a minute to click it and have it open, wait another half a minute before being able to click ŕespond', waiti another half a minute after closing it to be able to delete it, etc. I am using pop, not imap https://bugzilla.redhat.com/show_bug.cgi?id=1011125
FYI... I just added several back-traces of KMail to the Fedora Bugzilla entry noted above by Peter.
Please enable kmail2 in kdebugdialog, start KMail from terminal and post here what it prints.
Created attachment 82705 [details] annoted kmail debug output Started up kmail from the command line w/"--nofork", and have annotated the output with comments where appropriate. Only notable slow downs in this output are: - takes ~15s to load up the tree-view of folders, and - takes ~30s to display an HTML formatted e-mail message For reference, this is on a Core2 Quad Q9650 @ 3Ghz, w/8GB of RAM (e.g. a machine that I'd expect has more than enough horsepower to run kmail quickly)
I have installed all of the updates as they have appeared in the fedora repos and the status of this bug is unchanged: kmail still locks up. Nothing has been resolved.
This was fixed ages ago. We got kde-4.12.3 today.