evolution refuses to start

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

diffing a working and a non-working gconf I found out that evolution 2.10.1 uses an attribute "color" where 2.12 uses "color_spec". But changing these settings to "color" did not change anything.

Attached the gdb output.

I tracked down the source of the problem.

Evolution 2.12 had no problem with having 2 <properties> sections in the /apps/evolution/calendar/sources key (see below), while version 2.10.1 does not like that. As soon as I copied <property name="create_source" value="no"/> to the latter <properties> section and deleted the first section, everything went back to normal. Took me half a day for trail and error debugging.

Unfortunately nobody else will need this, since the bug does not occur anymore in Gutsy's Evolution version and probably nobody is as stupid as me, to use a production /home dir for both stable and testing release simultaneously. I do not know if it is valid gconf XML to have the same section twice in a key? Anyhow, Gusty's Evolution can handle it obviously. Well anyhow, if somebody else runs into the same problem, at least here is the answer.

Maybe still somebody feels obligated to fix this in Feisty's Evolution.

<?xml version="1.0"?>
<group uid="1152739267.20701.11@doroga" name="Contacts" base_uri="contacts://" readonly="no"><properties><property name="create_source" value="no"/></properties><source uid="1152739267.20701.12@doroga" name="Birthdays &amp; Anniversaries" relative_uri="/" color_spec="#DDBECE"><properties><property name="alarm" value="true"/><property name="delete" value="no"/></properties></source></group>

Thank you for your bug. Using a configuration not matching the version is not something supported. Closing since that works in gutsy and that doesn't look a candidate for a stable upload