[Bug 862483] [NEW] Unable to read mail after resume due to akonadi hang

Scott Kitterman ubuntu at kitterman.com
Thu Sep 29 15:24:08 UTC 2011

Public bug reported:

I few times since upgrading this laptop to KDE 4.7 (and moving from Kmail to
Kmail2) I've been unable to read email via imap.  When I click on a message it
says "Retrieving folder contents, please wait" indefinitely.

I tried exiting kmail and restarting it, but still had the same problem.  After
stopping and starting akonadi using the Akonadi Server Configuration KCM, then
it was able to read mail (without restarting kmail2 again).

Note: Akonadi version is actually 1.6.1, but I didn't see that option under
application version.

Reproducible: Sometimes

Steps to Reproduce:
Suspend laptop, resume laptop, check mail provided via an imap resource.

Actual Results:  
"Retrieving folder contents, please wait"

Expected Results:  
Mail retrieved so I can read it.

Kmail/Kontact cannot reliably retrieve email after a suspend resume cycle.  Sometimes after resume, instead of displaying messages, "Retrieving folder contents, please wait" will be persistently displayed.  If this occurs, use the Akonadi Server Configuration control module to restart Akonadi.  That should resolve this issue.  Restarting Kontact/Kmail will not. To access the control module use the search function in Kickoff (K menu) or Quicksand (alt-F2) to find it.

** Affects: akonadi
     Importance: Unknown
         Status: Unknown

** Affects: ubuntu-release-notes
     Importance: Undecided
         Status: New

** Affects: akonadi (Ubuntu)
     Importance: Undecided
         Status: New

** Bug watch added: KDE Bug Tracking System #283037

** Also affects: akonadi via
   Importance: Unknown
       Status: Unknown

** Also affects: ubuntu-release-notes
   Importance: Undecided
       Status: New

You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to akonadi in Ubuntu.

  Unable to read mail after resume due to akonadi hang

To manage notifications about this bug go to:

More information about the kubuntu-bugs mailing list