GNOME Bugzilla – Bug 601125
Cannot retrieve my saved email
Last modified: 2009-11-08 19:40:48 UTC
Created attachment 147195 [details] Output with the --debug option set Evolution was working fine until I upgraded from Ubuntu 9.04 to 9.10. When I first brought evolution up after upgrading, I could retrieve all my email, but when I tried to create new email or reply to an email, evolution would crash. Since there were problems with the upgrade, I tried things to complete that upgrade (see https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/474543). Now when I bring up evolution, the title bar for any email folder shows the correct number of email messages, but where there should be a list of email messages it says "There are no messages in this folder". For some folders, it also says "Unable to retrieve message [?]". Now evolution does not crash when I try to create a new email. My contacts and calendar show up fine. One time only, it did crash: ** (evolution:2270): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:2270): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ... ** (evolution:2270): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:2270): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed Segmentation fault Thanks for your help - of course this is critical for me!
Created attachment 147201 [details] Core file after right click a mail folder, and go to properties. Had to split into xaa, xab and xac. Rest in next too attachments.
Created attachment 147202 [details] 2nd part after split
Created attachment 147203 [details] 3rd and final part after split.
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
This must be an Ubuntu upgrade problem: Evolution was suppose to go to 2.28.x, but some dependency is blocking it. Most libraries did get upgraded, so there must be some incompatibility when executing 2.26.x. Sorry for the unnecessary bug report - I'm changing this to "resolved" "invalid".