Bug 110871 - new emails indicated but not shown
new emails indicated but not shown
Product: Red Hat Linux
Classification: Retired
Component: evolution (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Malcolm
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-11-24 18:18 EST by David Kaplan
Modified: 2007-04-18 12:59 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-01 22:02:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Kaplan 2003-11-24 18:18:06 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1)

Description of problem:
Sometimes, when I receive new emails, evolution indicates that they
are there (i.e. the number of unread emails increases), but they do
not appear in the list of email messages and goto next unread and goto
previous unread do not go to the unread emails.  

The only solution I have found for this problem is to close evolution
and reopen, after which the emails appears in the correct place and
are readable.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. read emails, sometimes it happens

Actual Results:  # of unread emails goes up, but emails do not appear
in list

Expected Results:  should appear

Additional info:

Restart of evolution fixes problem
Comment 1 Dave Malcolm 2004-09-20 23:18:13 EDT
I'm sorry this bug has remained so long without activity.

Is this still a problem for you?  evolution-1.2.2-5 is a really old
version these days.  

One possible cause might be that you have a saved search active on the
selected folder; clicking on the "Clear" button may fix this.
Comment 2 David Kaplan 2004-12-01 22:02:14 EST
I admire your persistence on this one, but time marches on....

I am just going to mark this as fixed in currentrelease.

Note You need to log in before you can comment on or make changes to this bug.