GNOME Bugzilla – Bug 618415
evolution-mapi loses connection after running for a couple of hours
Last modified: 2010-05-12 21:32:59 UTC
Forwarding from a Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=591236 Description of problem: evolution-mapi loses connection after running for a couple of hours. An Evolution restart is required to send or receive new messages, or to create/edit calendar events. Version-Release number of selected component (if applicable): evolution-mapi-0.30.1-1.fc13.x86_64 evolution-2.30.1-3.fc13.x86_64 How reproducible: always Steps to Reproduce: 1. open evolution 2. leave running for a few hours 3. Actual results: new mail and existing (non-cached) mail cannot be read. Expected results: evolution should stay connected. Additional info: This happens with both calendar and mail events, sometimes independently. e.g., I won't be able to add or edit calendar events but I can still send receive mail. When I try to access a message when this happens, the following is output on the console: Thread 0 > Get folder info(0x239cba0:mbox:/home/username/.evolution/mail/local, 'Templates') = uri: mbox:/home/username/.evolution/mail/local#Templates full_name: Templates flags: 00000008 < 0 > Thread 0 > CamelStore('mbox:/home/username/.evolution/mail/local'):get_folder('Templates', 0) = 0x239a5f0 < 0 > Thread 0 > Get folder info(0x239cba0:mbox:/home/username/.evolution/mail/local, 'Templates') = uri: mbox:/home/username/.evolution/mail/local#Templates full_name: Templates flags: 00000008 < 0 > Thread 0 > CamelStore('mbox:/home/username/.evolution/mail/local'):get_folder('Templates', 0) = 0x239a5f0 < 0 > Thread 0 > Get folder info(0x239cba0:mbox:/home/username/.evolution/mail/local, 'Templates') = uri: mbox:/home/username/.evolution/mail/local#Templates full_name: Templates flags: 00000008 < 0 > Thread 0 > CamelStore('mbox:/home/username/.evolution/mail/local'):get_folder('Templates', 0) = 0x239a5f0 < 0 > CamelException.set(0x7feb2c17e740, 301, 'Could not get message')
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 608327 ***