How to: Install Evolution 2.30 on Ubuntu 10.04 Lucid Lynx
For some reason unbeknown to me, the developers of Ubuntu 10.04 updated Gnome desktop environment to version to 2.30 but left the Evolution version as 2.28. I think that this version of Evolution is really buggy and the decision was a very bad idea. In this article I will show you how to upgrade your Evolution version to 2.30 and install the Evolution-mapi client so that you can connect to a Microsoft Exchange 2007 server.
To do this we will be using unofficial Ubuntu packages created and maintained by Jacob Zimmerman. The packages are located on his PPA page.
Step 1:
Install Jacob’s PPA package repository on your system. Open up a terminal session and type the following:
sudo add-apt-repository ppa:jacob/evo230
This will install Jacob’s PPA repository for Evolution 2.30. It will also import the security key.
Step 2:
Update your computer’s repository information.
In the same terminal windows type:
sudo apt-get update
Step 3:
Next type to upgrade Evolution from 2.28 to 2.30:
sudo apt-get install evolution
apt will respond by telling you that there are several packages that need installed, upgrade, and removed. Hit the “Y” key to continue.
Now sit back and relax as apt upgrades to Evolution 2.30.
Extra:
If you are in a corporate/school environment that uses Microsoft Exchange 2007 for its email server you can install the evolution-mapi package to allow Evolution to communicate with the server. Remember this is still a very experimental package, however I have found that it is far better in version 2.30 than it ever was is 2.28.
Type this to install evolution-mapi
apt-get install evolution-mapi
This will also need you to hit “Y” to install becuase there are several new packages that get installed to support Evolution-mapi
You should now be able to fire up Evolution and configure it for you email environment.
Note about mapi-plugin:
Note:
The first time that I open Evolution after upgrading I just got a gray screen. To fix this all I did was reboot.
Hi just wanted to say that I got a grey screen as well, and a reboot did not fix it. Any suggestions ?
Using ubuntu 10.04 on a HP mini 2133
yeah same here.. how can i undo the update
I haven’t tried this but to undo this update you could just remove evolution and its dependencies and then remove this repository. Then reinstall evolution for the main Ubuntu repositories. Your setting shouldn’t be affected.
I did this on a clean installation of 10.04 without having Evolution configured before I upgraded. I dont know if this is what is causing the issues.
I did this, in an effort to fix the (apparently common) problem of Evolution 2.28 crashing repeatedly.
Using these instructions to upgrade to 2.28 solved the crashing problem, but introduced new bugs. For instance, opening a new message no longer changes the “read” flag. Messages remain in “unread” status unless I manually mark each one as “read”. Rather annoyingly cumbersome. Also, I have my calendar set to a 7-day week view. Every time I restart Evolution 2.30, it goes back to a 5-day week view. The only way to get it back is to edit the settings again.
These seem minor, perhaps, but in hindsight, I’d rather be dealing with the crashing problem. If I knew how to easily revert back to 2.28, I would.
I have not used the Ubuntu system that I have Evolution 2.30 installed on recently but I will look and see if I have the same issues that you do. I would encourage you to file some bug reports with the Evolution team at https://bugzilla.gnome.org/enter_bug.cgi?product=Evolution.
Jacob’s PPA repository for Evolution 2.30 stopped the development of evolution-mapi. Latest compile failed.
I do see that the latest compile of the mapi plugin failed to compile. I sent a note to the maintainer asking about this. I will let you know what I find out. Thanks
Here is the response from the evo230 maintainer about the evolution-mapi plug-in
Hi Terry
I’m sorry that I had to remove the mapi package from the PPA for the moment. The latest version doesn’t build properly on lucid, and besides many people experienced problems with that package that could only be solved by upgrading openchange to version 0.10, which is also not possible for dependency reasons. Hope you understand.
Kind regards
Jacob
I will keep you posted if anything changes