Mark read / unread only works once in message window

Bug #777777 reported by Callum Macdonald
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: evolution

Open a read message in its own window, CTRL-SHIFT-K to mark as unread, now CTRL-K does not work.

Open an unread message in its own window, CTRL-K to mark as read, now CTRL-SHIFT-K does not work.

This can also be seen in the menus. Open an unread message and Message > Mark As > Read is available, Unread is greyed out. Click Read, now open the menu again, Read is still the only option available. It seems like when message status is changed, the message window doesn't update to notice the new state.

Note that the message is marked as read / unread, just that the menu does not change in the Evolution window. This applies when opening messages in separate windows, not while viewing messages in the preview pane.

Ubuntu 11.04
Evolution 2.32.2-0ubuntu7

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, are you using IMAP? this looks similar to bug 636980, may you please check and comment back? thanks.

Changed in evolution (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Callum Macdonald (chmac) wrote :

I read that bug before posting, it sounds similar but not the same. Yes, I am using IMAP, but this bug exists for me on both IMAP and local folders.

It's not quite the same as bug 636980 because mails are correctly marked as read after 1.5 seconds, or I can change their status once from within the message window. So the functionality appears to work, it's just that the menu doesn't activate / deactivate based on the message's status.

For example, if I open a read message in a new window then go to the main folder view and mark that message as unread, I still only have Message > Mark > Unread in the message window, even though the message is already unread.

Please let me know if I haven't explained clearly enough and I can create a screencast to demonstrate.

Revision history for this message
Callum Macdonald (chmac) wrote :

Can I change the bug status back to New instead of Incomplete? I'm assuming another person needs to confirm that it exists for them before it goes to Confirmed. I'll switch it in a few days I don't hear any objections.

Changed in evolution (Ubuntu):
status: Incomplete → New
Revision history for this message
Nick Jenkins (nickpj) wrote :

This has just been fixed upstream.
Mailing list discussion was here: http://mail.gnome.org/archives/evolution-list/2011-August/msg00084.html
Fix is here: http://git.gnome.org/browse/evolution/commit/?id=d33ed726f9562015b65c27360b02be0dfad7c11b
In general for Evolution bugs, I'd recommend logging it upstream at https://bugzilla.gnome.org/ as that'll get it seen by its developers and fixed faster.

Revision history for this message
Nick Jenkins (nickpj) wrote :

Sorry, just to clarify, fix should be in Evo 3.0.3+ or 3.2 - so will have to go to Ubuntu 11.10 or later to get the fix.

Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :

Bug from 2011. Version not longer supportet.
Change status to Invalid

Changed in evolution (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.