Comment 14 for bug 1038573

I stepped through the entire upgrade process in a VM without reproducing this bug. I wonder if it's somehow specific to running upgrades on metal; that is, if compiz is running at the time?

The error message in question is indeed showing up from evolution-alarm-notify (as per bug 965686); but I'm not sure what more can be done than stopping evolution during the upgrade process to try and avoid this showing up (as is already being done, and appears to work properly). Users can still open it back up like I did and most likely trigger evolution-alarm-notify showing up again until the point in the upgrade when it breaks.

The error reads:
"""
An error occurred while loading or saving configuration information for evolution-alarm-notify. Some of your configuration settings may not work properly. [Details] [ OK ]
"""

It seems to happen because gconf gets restarted; or in any case things change (possibly the changes in GConf policy semantics?) and the notifier can't call method GetIOR on org.gnome.GConf (doesn't exist with signature "")

If a meeting notification happens during that time and isn't clicked; clicking it after upgrade will fail finding the glade XML file, as expected because it's been migrated to gtkbuilder since Natty or so.

This remains an unrelated problem to the actual font rendering issue that is reported here; and the rendering needs further investigation. I'll move on to testing the upgrade on actual hardware, with and without desktop effects enabled.