mark-all-as-read doesn't work when some messages are already marked as read

[Jamie Wilkinson]

I used to C-a C-k to mark all messages in a folder as read; now whenever i C-a,
some messages that are already marked as read are selected, and this seems to
adversely affect the Mark as Read option -- the menu option Edit->Mark as Read
is greyed out, and C-k does nothing.

Alt-e r works but this is more painful to type; it'd be nice if evolution
understood that when messages marked as read get asked to be marked as read
again, then that's okay, just like it used to.

Thanks.

http://bugzilla.gnome.org/show_bug.cgi?id=273658: http://bugzilla.gnome.org/show_bug.cgi?id=273658

[Jamie Wilkinson (jamie-anchor)]

Oh, fyi, evolution 2.2.1.1 from Hoary on i386 (why doens't bugzilla ask for
package and distro versions?)

[Sebastien Bacher (seb128)]

that works fine here. What sort of account do you use (imap/maildir/...)?

[Jamie Wilkinson (jamie-anchor)]

It's an (In reply to comment #2)
> that works fine here. What sort of account do you use (imap/maildir/...)?

imap (the server is dovecot), but that seems irrelevant; If I type C-a then
Edit->Mark as Read is greyed out, and C-k doesn't do anything -- I would have
thought that's an interface problem, not a backend problem :-)

[Sebastien Bacher (seb128)]

the interface actions depends of the server type and what you can do with it.
That works fine here. do you imap4v1 or the standard imap option?

[Jamie Wilkinson (jamie-anchor)]

(In reply to comment #4)
> the interface actions depends of the server type and what you can do with it.
> That works fine here. do you imap4v1 or the standard imap option?

It's "imap", not imap4v1.

Well, how 'bout that. It's working today. I'm sure I wasn't hallucinating when
I reported this though :-)

[Sebastien Bacher (seb128)]

do you consider this bug as fixed?

[Jamie Wilkinson (jamie-anchor)]

(In reply to comment #6)
> do you consider this bug as fixed?

I thought I did, but since my last message on this bug, I discovered that the
behaviour actually changes depending on which folder I'm in.

I have an IMAP server, using, as previously noted, the "imap" type in evolution.
 I use evo's filters to filter mail from INBOX into each of the other folders.

Depending on the folder, either C-k works, or it doesn't; in all cases A-e r
does work. I can see for each of the cases where C-k doesn't work, that "Mark
as Read" is greyed out when I look at the Edit menu.

So, it seems that Evo thinks for some folders, marking all selected messages as
read isn't possible, but for others it is.

I don't know what other information I can give you. The location of a folder
seems to have no bearing on wether it allows C-k or not. Perhaps there's some
IMAP flag I can look for on the server?

[Sebastien Bacher (seb128)]

seems to be the same issue as http://bugzilla.gnome.org/show_bug.cgi?id=273658

[Jamie Wilkinson (jamie-anchor)]

(In reply to comment #8)
> seems to be the same issue as http://bugzilla.gnome.org/show_bug.cgi?id=273658

Yep, I agree.

[Neilen Marias (ubuntu-bugzilla-chatsubo)]

> > seems to be the same issue as http://bugzilla.gnome.org/show_bug.cgi?id=273658
>
> Yep, I agree.

gnome.org is down today, so I can't verify. I think I can add some info though.
Firstly, I'm using straight MBOX storage, so I don't think the storage affects
matters. Secondly, it seems to be much more prevalent when threaded views are
being used.

If I press ctrl-h to select a thread, after having read the first item, mark as
read won't work. It's even grayed out on the edit menu. Right click-mark-as-read
still works though. On the other hand, if I read the first message, then use
shift-click to select the whole thread using the mouse, everything pans out
fine! It's too slow a method to be practical for me though.

[Sebastien Bacher (seb128)]

upstream thinks it's fixed, do you still have the issue?

[Daniel Robitaille (robitaille)]

No answer from initial reporter in 3 months, and it is marked as fixed upstream. I'll mark it as fixed in Ubuntu. Please feel free to re-open it if you still experience this bug. Thanks.