GNOME Bugzilla – Bug 364463
Evolution Error - Lost connection to Evolution Exchange backend process
Last modified: 2008-07-14 09:38:51 UTC
Steps to reproduce: 1. Open Evolution 2. ... no further steps needed. Even though the client is now useless, no messages can be read, deleted, moved, etc.; ps -A | grep evolution shows that: 21524 ? 00:00:00 evolution-data- 21539 ? 00:00:00 evolution-alarm 22947 ? 00:00:01 evolution 22955 ? 00:00:00 evolution-excha what look like all processes are running. The Exchange server is working find for XP/Outlook clients. If you want a stack trace, please tell me specifically how, since nothing seems to be actually crashing. Stack trace: Other information:
I have just upgraded Evolution to 2.8.2.1 in Fedora Core 6 and this bug appered! Come on guys, please test the releases more carefully! Each second update release introduces show-stopping bug! Thank you for your hard work but please pay more attention to testing releases before releasing them.
I tried downgrading to 2.8.1.1 but I still get the same error! Can you please look into this. Maby is some dependency that is causing this error?!? # rpm -e evolution-connector # rpm -e evolution --nodeps # rpm -ivh evolution-2.8.1.1-3.fc6.i386.rpm # rpm -ivh evolution-connector-2.8.1-1.fc6.i386.rpm and still the same error message pops-up, even after a reboot.
Ok, now I have another situation; I installed a new clean Fedora Core 6 on new laptop, and did an "yum update" so evolution also got updated to latest 2.8.2.1 version. I don't have this bug on a new Fedora installation, but I still have it on my work laptop that has been gradually updated and also has evolution 2.8.2.1 version. Do you have any idea what could be causing these problems on my old fedora machine? Can you give me some pointers into what libraries I should pay attention... any help is appreciated. Thank you in advance.
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME 2.22.3.