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 550998 - Evolution doesn't refresh the INBOX folder
Evolution doesn't refresh the INBOX folder
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-09-05 14:05 UTC by Lionel Dricot
Modified: 2008-10-14 07:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Attachments
Log of the issue (2.68 KB, text/plain)
2008-09-19 22:29 UTC, Lionel Dricot
  Details
more verbose log (92.67 KB, text/plain)
2008-09-20 13:07 UTC, Lionel Dricot
  Details
Complete log (no confidential) (205.33 KB, text/plain)
2008-09-21 18:05 UTC, Lionel Dricot
  Details
Proposed patch (523 bytes, patch)
2008-10-07 05:48 UTC, Srinivasa Ragavan
committed Details | Review

Description Lionel Dricot 2008-09-05 14:05:56 UTC
The last Evolution in Ubuntu Intrepid ( 2.23.91-0ubuntu1 ) doesn't refresh the INBOX of my IMAP account (it's a dovecot server).

If I check my mail with the webmail, all is fine. Evolution still display the list of my INBOX as it was a few days ago. If I try to retrieve one of those mail (now deleted) I get :

Unable to retrieve message
Could not find message body in FETCH response.

Note that other folders are working fine. It means that I see mail that are filtered to go in other folders (Once, one of my folder had the same problem).

The workaround so far : completely remove the IMAP account, remove the imap folder in .evolution and recreate the account again. It works for a few day and then, it's frozen again.


Ubuntu bug report : https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/265043
Comment 1 Lionel Dricot 2008-09-17 13:20:36 UTC
It's definitely not related to the server because this bug is now happening with my second IMAP accound (on a cyrus server).
Comment 2 Srinivasa Ragavan 2008-09-19 09:13:01 UTC
Can you get me a log of console starting with env CAMEL_DEBUG=all while you are seeing this issue?

Comment 3 Lionel Dricot 2008-09-19 22:29:34 UTC
Created attachment 119017 [details]
Log of the issue

I launched evolution with env CAMEL_DEBUG=all and all I have is essentially a bunch of those lines :

(evolution:5690): camel-WARNING **: Camel operation status stack non empty: 

(evolution:5690): camel-WARNING **: Camel operation status stack non empty: 

(evolution:5690): camel-WARNING **: Camel operation status stack non empty:




I attach the full log.
Comment 4 Srinivasa Ragavan 2008-09-20 09:37:42 UTC
Lionel, sure you ran with that. A normal start up would have atleast few 100 lines when you start with that.

export CAMEL_DEBUG=all
evolution

Comment 5 Lionel Dricot 2008-09-20 13:07:51 UTC
Created attachment 119033 [details]
more verbose log

Ok, I see what you mean.

I don't understand why but the command :
evolution > log.txt &2>1

still display a lot (really a lot) of output in the console and not in the log.txt. It's too much for the buffer of my terminal so I can't even copy/paste.

Can you help me to file all the output into one log.txt ?

I attach anyway the output that already go to log.txt.
Comment 6 Paul Bolle 2008-09-20 20:16:03 UTC
(In reply to comment #5)
> I don't understand why but the command :
> evolution > log.txt &2>1
> 
> still display a lot (really a lot) of output in the console and not in the
> log.txt.

try this:
    evolution > log.txt 2>&1
Comment 7 Lionel Dricot 2008-09-21 17:49:25 UTC
Created attachment 119121 [details]
Complete log (empty)

This log reflect the following operations :

1) Launching Evolution (and automatically go to inbox of the frimouvy0001 account)
2) Manual send & receive
3) Manually go to the ploum.net account

Hope it helps.
Comment 8 Lionel Dricot 2008-09-21 18:05:08 UTC
Created attachment 119122 [details]
Complete log (no confidential)

Argh, it seems that my previous attachment contains log of some of my confidential email. Could you please remove it ? This attachment was a bit changed to remove confidential parts.

What is very interesting is that those emails are fairly new and now displayed in Evolution ! (and that's the bug)
Comment 9 Lionel Dricot 2008-09-22 09:39:19 UTC
%s/now/not. 

The mails that you can see in the log are *not* displayed in Evolution. (gasp, I really should take some rest)
Comment 10 Philip Withnall 2008-09-22 20:44:48 UTC
Lionel: Just so you know, we couldn't delete that confidential attachment, but have hidden it from most people. Because of this, I've now made the bug itself more visible again.
Comment 11 Milan Crha 2008-09-23 08:48:01 UTC
I guess this is related:
CamelException.setv((nil), 2, 'Failed to cache : Aucun fichier ou dossier de ce type')
CamelException.setv(0x8c2617c, 2, 'Failed to cache : Aucun fichier ou dossier de ce type')
CamelException.setv(0x8c2617c, 303, 'Could not find message body in FETCH response.')
CamelException.setv(0x8c2617c, 2, 'Failed to cache : Aucun fichier ou dossier de ce type')

even not sure what that "Failed to cache:" wants to tell us. Anyway, are you able to compile yourself? There is a patch in bug #550478 which should help here, I guess.
Comment 12 Sebastien Bacher 2008-10-06 13:55:52 UTC
The issue seems to be evolution not handling correctly other clients changes, those steps trigger a similar issue on my intrepid installation:

- start evolution 2.24, select an imap folder which has one message
- select the message, it's previewed
- switch to an another mailbox
- connect using an another client and delete the message which is selected in the other mailbox
- switch back evolution 2.24 to this directory
- the mail which has been deleted on the server is still listed, you can't delete it, the warnings are displayed on the command line and the box is not updated when new messages arrive there
Comment 13 Srinivasa Ragavan 2008-10-07 05:48:36 UTC
Created attachment 120085 [details] [review]
Proposed patch

This should fix it. But iirc, I added to avoid a crash, dont remember much from my branch. So Seb, if you can run with it for 2-3 days, then I can push to stable/trunk

And Thanks a lot for all the support.
Comment 14 Srinivasa Ragavan 2008-10-13 06:44:47 UTC
Seb, does it work for you now? 
Comment 15 Srinivasa Ragavan 2008-10-14 07:22:39 UTC
Committed to stable/trunk