After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 728973 - [IMAPX] Recover after store summary version mismatch
[IMAPX] Recover after store summary version mismatch
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Mailer
3.12.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-04-25 20:14 UTC by Paul Menzel
Modified: 2014-05-09 10:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Paul Menzel 2014-04-25 20:14:53 UTC
Using Debian Sid/unstable with Evolution 3.12.0 from experimental the following warnings are printed to the terminal when starting Evolution. The errors were already present in version 3.8.5.

    (evolution:6465): camel-imapx-WARNING **: Unable to load store summary: Expected version (1), got (0)

    (evolution:6465): camel-WARNING **: Cannot load summary file: Erfolg

(»Erfolg« is German for »success«.) No idea if the second error results from the first error or if it is a separate issue.
Comment 1 Milan Crha 2014-05-09 07:33:10 UTC
Right, from bug #728976 comment #16:
> Did you switch between versions of evolution forth and back? It seems so,
> according to these warnings. Anyway, this warning is used with IMAPx accounts,
> thus it's for files stored at ~/.cache/evolution/mail/. The files and folders
> there can be safely deleted, that's only a local copy of server data, which can
> be downloaded again. The only counter part is that it'll take some time till
> all your folders summary is populated again (how long depends on your folder
> sizes).
> 
> I would expect that the summary will be recreated after this error, but it
> didn't do it for some reason. Though the reason seems to be, from the other set
> of runtime warnings, that the evolution wasn't able to connect to the server.
> CAMEL_DEBUG=imapx:io,imapx:conman may give more detailed information (running
> evolution with this environment variable set to this value).

Your answer for the first question was "yes". It doesn't change anything on a fact that the IMAP code should recover from this summary version mismatch, instead of reclaiming the error on console.
Comment 2 Milan Crha 2014-05-09 10:47:31 UTC
I did more testing on this and found out that IMAPx does fix the summary as expected, but only after it successfully connects to the server, not before. This means also states when evolution is offline or the respective account is disabled, when the summary is not corrected.

I made couple changes here, as there is no need to keep the broken summary, thus if the IMAPx recognizes failure in the summary load, then it vanishes it immediately, thus there is not error on the console the next run. I also changed the console messages slightly, for example a path to the broken file is shown as well, together with  a change to "Unknown error", if the failure reason would be "Success".

The version mismatch doesn't have any huge impact, apart of warnings being shown on a console and no usable folder list in offline mode.

Created commit 4b7c3ed in eds master (3.13.2+) [1]
Created commit 85499df in eds evolution-data-server-3-12 (3.12.2+)

[1] https://git.gnome.org/browse/evolution-data-server/commit/?id=4b7c3ed