Re: New version, new error. dammit
Milan Crha via evolution-list <[email protected]>
| Newsgroups | gmane.comp.gnome.evolution.general |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 2022-09-14 at 12:44 -0500, Tim McConnell via evolution-list wrote: > Sep 14 03:09:56 DebianTim evolution-calen[3387]: GError set over the > top of a previous GError or uninitialized memory.#012This indicates a > bug in someone's code. You must ensure an error is NULL before it's > set.#012The overwriting error message was: SQLite error code '1': no > such table: ECacheObjects (statement:DELETE FROM ECacheObjects WHERE > ECacheState=3) Hi, it looks like your calendar cache(s) did not survive the update for some reason. I'd simply: $ evolution --force-shutdown and then $ mv ~/.cache/evolution ~/.cache/evolution.bad Supposing those messages are from the remote calendars/task lists/memo lists you've configured. The `mv` command moves everything remote, including mail accounts, and will force to reload all of that. You can keep the ~/.cache/evolution/mail/, if you want to, especially if there's no problem with it. By the way, those tables are ensured to be created after the calendar/tasks/memos list is opened, could it be the evolution- calendar-factory was not restarted after update? Though even then I'm not sure how that could break, unless playing with the ~/.cache/evolution while the processes had been running in the background (no, closing evolution doesn't close the evolution-data- server background processes, because some other apps can use them). Bye, Milan _______________________________________________ evolution-list mailing list [email protected] To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list