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 387050 - Not showing read/unread count for search folders correctly
Not showing read/unread count for search folders correctly
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.8.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[vfolders]
Depends on: 556116
Blocks: 543389
 
 
Reported: 2006-12-18 04:11 UTC by Akhil Laddha
Modified: 2010-06-28 16:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Akhil Laddha 2006-12-18 04:11:09 UTC 
Please describe the problem:
When we create a search folder and mails are filtered in it.But
unmatched search folder doesn't show count of unread mails.When we click
on it then it shows count of unread mails.
When we delete the search folder and all mails are deleted from it.Now
unmatched search folder doesn't have any mail and still it is showing
count of unread mails.This counting will disappear only after restarting
evolution.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:
It should show read/unread count correctly for both newly created search folder and unmatched search folder.

Does this happen every time?
Yes

Other information:
Comment 1 André Klapper 2006-12-18 18:16:32 UTC 
Akhil,
please NEVER confirm your own bug reports (the status field indicates the general status of a bug, e.g. if it has been triaged).
i'm 100% sure that this is a duplicate, have you searched for this one (hint: status whiteboard = "evolution[vfolders]")?
Comment 2 Akhil Laddha 2006-12-19 06:50:24 UTC 
Next time i will never do such type of mistake.
Before filing bug i searched for it by putting summary in search.But i could not find this bug.I have also tried with status whiteboard.
Comment 3 André Klapper 2010-06-28 16:12:46 UTC 
I assume it's obsolete nowadays, plus we have new shiny bugs for this. :-P