Bug 485645 - Virtual folders have problems with Unread messages in F10 version
Summary: Virtual folders have problems with Unread messages in F10 version
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 10
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-15 20:37 UTC by Joshua Rosen
Modified: 2009-02-15 22:39 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-02-15 22:39:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 563947 0 None None None Never

Description Joshua Rosen 2009-02-15 20:37:34 UTC
Description of problem:
In the F10 version the virtual folders feature doesn't work reliably. Here are a few examples,

The Unread mail folder will indicate that there are unread messages but when you look in the folder there is nothing in it.

Other virtual folders will indicate that there are unread message (as indicated by the Bold title and an unread message error count), but if you look in the folder there will be no new messages.

When you convert a database from and older version of Evolution it will indicated that there are thousands of unread messages in the various virtual folders.

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




How reproducible: 100%


Steps to Reproduce:
1. Just keep Evolution open and wait for new mail
2.
3.
  
Actual results: Sometimes the messages appear in the Unread folders and sometimes they don't.  Exiting and restarting Evolution will usually fix the problems.


Expected results:


Additional info: This is an F10 problem only, the version on F9 doesn't have this issue although the F9 version crashes on occasion.

Comment 1 Matthew Barnes 2009-02-15 22:39:26 UTC
http://bugzilla.gnome.org/show_bug.cgi?id=563947


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