GNOME Bugzilla – Bug 666764
SQL error migrating folders
Last modified: 2012-01-20 10:33:54 UTC
I'm getting lots of "GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory." logs in my .xsession-errors related to IMAP & Folder migration. GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: no such table: mem.INBOX/PERSO/zzz digging into it gives me: Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x98d4ce "GLib", log_level=<optimized out>, format=0x990e68 "GError set over the top of a previous GError or uninitialized memory.\nThis indicates a bug in someone's code. You must ensure an error is NULL before it's set.\nThe overwriting error message was: %s", args1=0xb05fdc9c "\210B3\201\210\024a\200`\231", <incomplete sequence \332>) at /build/buildd/glib2.0-2.31.7+git20111222.3f3e141e/./glib/gmessages.c:765 765 in /build/buildd/glib2.0-2.31.7+git20111222.3f3e141e/./glib/gmessages.c (gdb) bt
+ Trace 229331
I get one log per folder, each time evolution rechecks that IMAP account, over and over again. It's been doing that for weeks. The SQL error here is 'no such table', most probably meaning the migration has already been done. Maybe the 'DROP TABLE' there should be a 'DROP TABLE IF EXISTS' like at some other places in the camel code. This is with evolution 3.2.2 and a pretty recent glib & gnome stack. I didn't try evolution 3.3.x yet, but looking at trunk, camel-db.c doesn't seem to have changed.
From which evolution version did you upgrade to 3.2.2 ? Regenerating folder db might help. You can follow steps mentioned in faq wiki [1] [1] http://live.gnome.org/Evolution/FAQ#Why_do_I_get_an_error_.22Summary_and_folder_mismatch.2C_even_after_a_sync.22.3F
I'm a long time evolution user. I used all the versions that Ubuntu shipped over the years. Looking at my logs: 2.30.3 -> 2.32.0 -> 2.32.2 -> 3.0.0 -> 3.0.2 -> 3.1.2 -> 3.1.3 -> 3.1.4 -> 3.1.5 -> 3.1.92 -> 3.2.0 -> 3.2.1 -> 3.2.2 I looked at my .ibex.index files locally, I just have a few (Draft, Outbox, Sent & Templates) but the warnings I'm seeing are all about my IMAP folders, and there's no .ibex.index there (just a cmeta & a journal file per folder)
I can confirm this. The issue is that the "<tablename>_version" has set old version, and the code to migrate doesn't count with an issue of a nonexistent table.
Created attachment 205688 [details] [review] eds patch for evolution-data-server; This fixes it for me.
Created commit cf05b71 in eds master (3.3.5+)