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 341396 - Marking all as read skips threads that are not expanded
Marking all as read skips threads that are not expanded
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.4.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-05-11 10:39 UTC by Choose to remain Anonymous
Modified: 2007-11-03 10:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Choose to remain Anonymous 2006-05-11 10:39:17 UTC 
Please describe the problem:
When viewing a usenet folder, if certain threads are not expanded ( i.e.
clicking triangle), when the user clicks Mark Read (after selecting all
messages), the count of unread messages includes messages in threads
that are not expanded.
I have Group By Threads selected.



Steps to reproduce:
1. open usenet folder with some unread messages. Un expand threads with
read messages.
2. Type Ctrl-A to select all messages and threads
3. Right Click to get a context menu and click Mark Read


Actual results:
All messages where threads are expanded (i.e. entire thread displayed)
are marked read. All messages where threads are not expanded are marked
unread (if not read already).


Expected results:
All messages in all threads marked read.


Does this happen every time?
Yes

Other information:
See Bug #335682 which notes that evo does not mark subfolder messages as read at
all.
Comment 1 André Klapper 2006-05-11 11:46:48 UTC 
correct, however there is a pretty easy workaround: "collapse all threads". :-)
to me, this is a duplicate of bug 257117.

*** This bug has been marked as a duplicate of 257117 ***
Comment 2 Srinivasa Ragavan 2006-08-23 07:00:24 UTC 
Andre: Wait this is not a duplicate. it is a broken feature. Some one has to fix it seriously. Marking messages with thread is horrible atm. Im reopening.