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 678295 - IMAP folder "frozen"
IMAP folder "frozen"
Status: RESOLVED DUPLICATE of bug 655248
Product: evolution
Classification: Applications
Component: Mailer
3.2.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-06-18 09:15 UTC by Bastien Durel
Modified: 2012-09-12 08:35 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
bug-trigger message (1.83 KB, application/x-compressed-tar)
2012-06-18 09:15 UTC, Bastien Durel 		Details
blank window, wrong message in preview (141.63 KB, image/png)
2012-06-18 09:16 UTC, Bastien Durel 		Details

Description Bastien Durel 2012-06-18 09:15:04 UTC 
Created attachment 216651 [details]
bug-trigger message

Hello,

I'm using evolution 3.2.3 under ubuntu 12.04/i386, and since a few days, *one* of my IMAP folder is "frozen".
New messages appears in the messages pane, or are removed if I remove them from other MUA, but they cannot be displayed.

The preview pane always displays an old message, and opening other message in a new window shows a blank one (see screenshot).

Other folders works well, on same or other accounts.

Moving the old message from the folder "repairs" it (breaking the folder I put it into), but it's frozen again if the message is put back in the first one.

I also attached the message triggering the bug.
Comment 1 Bastien Durel 2012-06-18 09:16:29 UTC 
Created attachment 216652 [details]
blank window, wrong message in preview
Comment 2 André Klapper 2012-08-07 10:32:22 UTC 
Might be a duplicate of bug 655248...
Comment 3 Milan Crha 2012-09-12 08:35:45 UTC 
Thanks for a bug report. I agree with Andre, check bottom of the bug report for a workaround.

*** This bug has been marked as a duplicate of bug 655248 ***