GNOME Bugzilla – Bug 643476
upgrade 2.30.3 → 2.32.2: calendar entries lost
Last modified: 2011-03-02 15:00:40 UTC
Dear Evolution developers, in Debian Sid/unstable I upgraded Evolution from 2.30.3 to 2.32.2. I stopped closed Evolution beforehand and ran `evolution --force-shutdown`. After the upgrade I executed `evolution` and there were messages shown on the terminal after `Migrating cached data` and then I could read my messages but switching to the calender all my entries were gone. The following messages were displayed on the console. (evolution:31956): libecal-WARNING **: Unmatched error name org.gnome.evolution.dataserver.calendar.CalFactory.NoSuchCal (evolution:31956): libecal-WARNING **: Unmatched error name org.gnome.evolution.dataserver.calendar.CalFactory.NoSuchCal (evolution:31956): libecal-WARNING **: Cannot get cal from factory: No backend factory for 'local' of 'VJOURNAL' (evolution:31956): libecal-WARNING **: Cannot get cal from factory: No backend factory for 'local' of 'VJOURNAL' (evolution:31956): calendar-gui-CRITICAL **: load_cal_source_thread: assertion `cal != NULL' failed (evolution:31956): calendar-modules-CRITICAL **: e_memo_shell_sidebar_add_source: assertion `client != NULL' failed (evolution:31956): libecal-WARNING **: Unmatched error name org.gnome.evolution.dataserver.calendar.CalFactory.NoSuchCal (evolution:31956): libecal-WARNING **: Cannot get cal from factory: No backend factory for 'local' of 'VTODO' (evolution:31956): calendar-gui-CRITICAL **: load_cal_source_thread: assertion `cal != NULL' failed (evolution:31956): libecal-WARNING **: Unmatched error name org.gnome.evolution.dataserver.calendar.CalFactory.NoSuchCal (evolution:31956): libecal-WARNING **: Cannot get cal from factory: No backend factory for 'local' of 'VEVENT' (evolution:31956): calendar-gui-CRITICAL **: load_cal_source_thread: assertion `cal != NULL' failed (evolution:31956): libecal-WARNING **: Unmatched error name org.gnome.evolution.dataserver.calendar.CalFactory.NoSuchCal (evolution:31956): libecal-WARNING **: Cannot get cal from factory: No backend factory for 'local' of 'VEVENT' (evolution:31956): calendar-modules-CRITICAL **: e_cal_shell_sidebar_add_source: assertion `client != NULL' failed (evolution:31956): libecal-WARNING **: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "getCacheDir" with signature "" on interface "org.gnome.evolution.dataserver.calendar.Cal" doesn't exist […] Bug 634897 or bug 632962 seem to deal with something similar, but it says that these are solved in Evolution 2.32.2. I also do not think this is related to an old version of EDS running since I executed `evolution --force-shutdown` beforehand. This is report #615824 in the Debian BTS [1]. Thanks, Paul [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615824
After a couple of restarts of Evolution no migration messages regarding the calendar are shown anymore. The calendar data also seems to have been migrated successfully. $ ls ~/.local/share/evolution/calendar/ 1176813954.5800.4@doe 1176813999.5800.7@doe system 1176813972.5800.5@doe 1245305294.6383.0@doe The calender entries are still *not* shown and I have problems using the calandar module as reported in bug 643498. The error messages pasted above also do *not* show up anymore.
Thanks for a bug report. The problem was that evolution --force-shutdown doesn't stop e-calendar-factory and e-addressbook-factory, so you had running newer evolution with older factories, which don't know "local". There are done some steps in 2.91.90 to avoid this in future releases. I take this as fixed on your side, and move on to bug #643498 with the rest of this.
(In reply to comment #2) > Thanks for a bug report. The problem was that evolution --force-shutdown > doesn't stop e-calendar-factory and e-addressbook-factory, How can these be stopped, so I can tell the package maintainers? > so you had running > newer evolution with older factories, which don't know "local". There are done > some steps in 2.91.90 to avoid this in future releases. I take this as fixed on > your side, and move on to bug #643498 with the rest of this. Thank you, much appreciated.
with 2.32.x and below with kill or pkill or some DBus foo, as those are DBus processes.