+++ This bug was initially created as a clone of Bug #473012 +++

Description of problem:
Although the count of unread messages gets increased, the messages are not actually displayed in the list. Outlook shows messages just fine. These are the messages to which server side filter rules are applied.


Version-Release number of selected component (if applicable):
2.24.2-1.fc10

How reproducible:
Sometimes.

Steps to Reproduce:
1. Connect to Exchange.
2. Wait for messages that are filtered and delivered to folders.
3.
  
Actual results:
Messages not displayed (but count of unread increased)

Expected results:
Old Evo would show these messages just fine.

Additional info:
This is any intermittent problem. It doesn't always happen and after some time (minutes, hours), the messages in question mysteriously pop up.

--- Additional comment from bucky on 2008-12-23 00:07:13 EST ---

I have witnessed this bug myself in previous versions of evolution, but for me it was very intermittent, and I wasn't able to produce a recipe for the problem.

--- Additional comment from mjs on 2008-12-30 18:47:53 EST ---

I have now twice observed Evo updating the Inbox message list and having the count of messages and unread messages decrease before my eyes.

One can force the messages to reappear by deleting .evolution/exchange and .evolution/mail/exchange and starting evolution, but it takes forever to resync.

--- Additional comment from norman.r.weathers on 2009-01-27 12:39:35 EST ---

I have seen this as well.  I will have my Outlook open as well and can see where the message is delivered to the Exchange server and then see where "something" reads the message, because in Outlook the message will show up unread, then suddenly read.  No new message shows up in evolution, however.  Very frustrating.

--- Additional comment from idht4n on 2009-02-05 10:25:34 EST ---

I have seen something similar with both my Inbox and Sent Items folders.  Just now, after my semi-daily evolution crash, evolution shows only a single file in my Sent Items folder.  There are actually several hundred messages in the folder.  It crashed while refreshing that folder, so I suspect it left some summary info in a corrupt state.  I think if I delete .evolution/exchange and .evolution/mail/exchange, it would fix the problem, but like comment #2 says, that's very inconvenient.

--- Additional comment from bojan on 2009-02-16 22:22:55 EST ---

An additional piece of information. When this happens, Evo will briefly display "Unable to retrieve message" in the preview pane and then flick back to normal display of another message. Count of unread messages will go up, but they will not be visible in the folder in question.

--- Additional comment from bojan on 2009-02-21 00:15:11 EST ---

Still present in 2.24.4-1.

--- Additional comment from bojan on 2009-03-02 18:52:00 EST ---

Still present in 2.24.5-1.

--- Additional comment from bojan on 2009-03-22 08:32:26 EDT ---

And another piece of info. If more messages come into the folder, the messages that were not visible will appear.

--- Additional comment from bojan on 2009-05-14 19:48:34 EDT ---

Still a problem with Evo 2.26.1 in F-11.

--- Additional comment from mjs on 2009-07-28 17:15:31 EDT ---

Please see patch here: http://bugzilla.gnome.org/show_bug.cgi?id=581908.  Does this look like the same or a related problem?  If so, can we give this patch a try?

--- Additional comment from bojan on 2009-07-29 06:06:06 EDT ---

Regarding comment #10: yes, please.

Also note, upstream will not be fixing 2.26.x, so it's up to the distro maintainers to do it.

--- Additional comment from bojan on 2009-09-03 20:41:39 EDT ---

Could someone please backport this patch?

--- Additional comment from bojan on 2009-11-13 15:50:20 EST ---

I switched to F-12 (which hopefully has the fix), so I'm no longer interested in this bug, unless it re-emerges in new Evo.

--- Additional comment from idht4n on 2009-11-13 15:58:33 EST ---

I've seen this bug in the last week with up to date rawhide.

--- Additional comment from bojan on 2009-11-13 16:03:57 EST ---

OK, I'll keep an eye then. I thought it got fixed upstream, but apparently not.

--- Additional comment from bojan on 2009-11-18 00:10:26 EST ---

You are correct. This is still present in F-12.

--- Additional comment from triage.org on 2009-11-18 03:57:58 EST ---


This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from idht4n on 2010-06-03 14:09:40 EDT ---

I saw it in F-13 today.

--- Additional comment from idht4n on 2010-06-04 01:57:06 EDT ---

(In reply to comment #18)
> I saw it in F-13 today.    

What I saw today might be a different bug with similar symptoms.  All of the messages in my Inbox disappeared... I just get a message saying that "No message satisfies your search criteria.  Enter clear search with Search->Clear menu item or change it".  This is despite the fact that I didn't try to search and the Search->Clear menu item is greyed out.  If I delete ~/.evolution/exchange and ~/.evolution/mail/exchange and restart evolution, I can see my messages again.  This is happened at least 4 times to me today.  It's very similar to this old bug that I've seen periodically since fedora 10... evolution can't see messages in an exchange folder.  I'm pretty sure I've also seen the original bug symptoms in f13 too, but I'm not positive and I'm not sure if this is a different symptom of the same bug.

--- Additional comment from idht4n on 2010-06-04 13:51:46 EDT ---

(In reply to comment #19)
> (In reply to comment #18)
> > I saw it in F-13 today.    
> 
> What I saw today might be a different bug with similar symptoms.  

OK, I think I figured out what was going on although I'm not sure how it happened.  There are two gui widgets handling "search"... one that says "Show:" and one that says "Search:".  Somehow, the one that says "Show:" was getting changed to a different state.  I have never intentionally used that Show: combo box, so it was changed either by a bug or by some accidental keystroke or mouse gesture I made.  Since it happened so frequently yesterday, I suspect something changed in a recent update that changed something to do with the show: gui widget.

So, I think this means that I didn't see the bug yesterday.  I'm pretty sure I have seen it since the beginning of f13 alpha.  But come to think of it, the original bug symptoms would have looked practically identical to the Show: box being inadvertently set to "Read Messages".  I never look at that box and never try to change it, so at least some of the time that I saw this problem, it may have been related to a bad "Show:" filter.  I think this combo box should have mouse scroll wheel and any other shortcuts disabled by default.

--- Additional comment from idht4n on 2010-06-10 09:52:43 EDT ---

OK, today and yesterday I saw the problem of not seeing new messages in my exchange Inbox that was not related to the "Show:" box.  It looks just like the original bug except closing evolution and restarting is enough to get it to show the new message.  Sometimes just switching folders and returning to the Inbox is enough to get it to show the messages.  But when I tried that yesterday, evolution crashed.  I tried to report it with abrt, but even though
I had debuginfo-installed evolution, it said "Reporting disabled because the backtrace is unusable".  So I'll attach the backtrace here since it crashed at a time when it wasn't showing new messages so the crash may be related.

--- Additional comment from idht4n on 2010-06-10 09:56:59 EDT ---

Created attachment 422911 [details]
bactrace of crash that happened when new messages weren't being displayed

This happened after a suspend.  My VPN went down (so I'd expect it to not be able to get new messages) and after I brought the VPN up again I clicked on send/receive to get the new messages I know were there and it still didn't get the new messages.  I clicked on another exchange folder to see if evolution would figure out there were new messages when I switched back to the Inbox, but it crashed before opening the other folder.

--- Additional comment from triage.org on 2010-11-04 07:40:31 EDT ---


This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from idht4n on 2010-11-04 17:04:45 EDT ---

I've seen this problem or very similar ones in F13 and F14.

--- Additional comment from triage.org on 2010-12-05 02:05:49 EST ---


Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.