| Summary: | Messages Not Being Marked as Read | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Le Sage <dlesage> |
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | bugzilla-redhat, lucilanga, mbarnes, mcrha |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-03 06:37:27 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
David Le Sage
2011-03-17 00:56:16 UTC
I'm having the exact same issue with evolution 3.0.1 in the 32-bit Fedora 15 distro. [root@toreador ~]# cat /etc/fedora-release Fedora release 15 (Lovelock) [root@toreador ~]# uname -a Linux toreador 2.6.38.6-27.fc15.i686 #1 SMP Sun May 15 17:57:13 UTC 2011 i686 i686 i386 GNU/Linux [root@toreador ~]# rpm -qa \*evolution\* | sort evolution-3.0.1-1.fc15.i686 evolution-data-server-3.0.1-1.fc15.i686 evolution-exchange-3.0.1-1.fc15.i686 evolution-help-3.0.1-1.fc15.noarch evolution-mapi-3.0.1-2.fc15.i686 evolution-NetworkManager-3.0.1-1.fc15.i686 evolution-perl-3.0.1-1.fc15.i686 evolution-pst-3.0.1-1.fc15.i686 evolution-rspam-0.2.0-1.fc15.i686 evolution-rss-0.2.90-22.20110424git.fc15.i686 evolution-sharp-0.21.1-12.fc15.i686 pidgin-evolution-2.7.11-2.fc15.i686 Thanks for a bug report. Is this dependant on the account type you see this in, please? Say, it does work properly when trying under On This Computer folders, but does not when trying under IMAP folders? (Or any other account types.) Also, what is the timeout for an automatic message mark as read? There used to be an option for it in Edit->Preferences->Mail Preferences, but someone decided to drop it, with no replacement. What a bad idea :( Please run gconf-editor and go to /apps/evolution/mail/display and check whether the option 'mark_seen' is checked and what value is in 'mark_seen_timeout' key. I have it checked and the value is 1500, which means that a message should be selected for about a second and half before it gets marked read automatically. There is one exception in mark-seen, when the new message is selected by evolution on a folder select in cases when the folder is chosen for the first time, but that might not be related here, I believe. Thanks for the response. I did some additional testing per your suggestions and have the results below. I have confirmed the issue happens the same in these different account types... * mapi * spool (mbox file) * local (aka "On This Computer") I verified that 'mark_seen' is -not- checked. If I -do- check it, messages do indeed get marked "read" when viewing in a preview pane or double-clicking to open in a separate window (the 'mark_seen' option functions as it should). However, that's not the option/functionality I'm looking for here. It is not desirable that messages get marked "read" (such as in a preview pane) unless I have actually double-clicked to open them in a full separate window. Previous functionality in evolution was that if 'mark_seen' was -not- checked, then messages would only be marked "read" when double-clicked to open them in a full separate window. Double-clicking a message has previously always marked it as "read", regardless of the 'mark_seen' option setting. (In reply to comment #3) > Double-clicking a message has previously always marked it as "read", > regardless of the 'mark_seen' option setting. Oh, I see, I'm sorry for my initial misunderstanding of the bug description. I can confirm this behaviour, double-clicking the message doesn't mark it as read when mark_seen is not checked. I'm moving this upstream, because this doesn't seem to be fedora specific issue. Please see [1] for any further updates. [1] https://bugzilla.gnome.org/show_bug.cgi?id=651761 |