Bug 342765 - Message list shows read messages as unread
Summary: Message list shows read messages as unread
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 4.14.2
Platform: Fedora RPMs Linux
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-12 13:17 UTC by Flavio Leitner
Modified: 2015-01-15 11:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Flavio Leitner 2015-01-12 13:17:28 UTC
I was using 4.14.2 and it was fine.  After a distro upgrade, I got the 4.14.3 version which even after opening the message in an external window, the message list shows as Unread.

If I select the message and mark as Read it doesn't change anything.

It looks like the folder is in Read-Only mode, but if you quit and start kmail again, the messages show the correct status.


Reproducible: Always

Steps to Reproduce:
1. Just try to read a message in a local folder


Actual Results:  
message status remains as Unread

Expected Results:  
message status moves to Read

I think this is high priority because it's impossible to manage a high volume of emails if all them remains with Unread status.
Comment 1 Flavio Leitner 2015-01-12 13:21:33 UTC
Sorry, I thought kmail got upgrade but checking yum.log the package is still the same.
kmail-4.14.3-1.fc21.x86_64

These ones got changed though:
Jan 12 09:45:24 Updated: 6:kdelibs-common-4.14.3-8.fc21.x86_64
Jan 12 09:45:24 Updated: 6:kdelibs-webkit-4.14.3-8.fc21.x86_64
Jan 12 09:45:28 Updated: 6:kdelibs-4.14.3-8.fc21.x86_64
Comment 2 Flavio Leitner 2015-01-12 13:35:32 UTC
Downgrading those three packages resolves the issue:
Jan 12 11:28:41 Installed: 6:kdelibs-common-4.14.3-1.fc21.x86_64
Jan 12 11:28:42 Installed: 6:kdelibs-webkit-4.14.3-1.fc21.x86_64
Jan 12 11:28:46 Installed: 6:kdelibs-4.14.3-1.fc21.x86_64
Comment 3 Christoph Feck 2015-01-14 14:56:09 UTC
Rex, any way to get the diff between kdelibs-4.14.3-1.fc21 and kdelibs-4.14.3-8.fc21?
Comment 4 Rex Dieter 2015-01-14 15:01:56 UTC
The primary relevant suspect to me would be the kolab KRecursiveFilterProxyModel.patch (included since 4.13.3-5)

from here,
# https://obs.kolabsys.com/package/view_file/Kontact:4.13:Development/kdelibs/0001-KRecursiveFilterProxyModel-Fixed-the-model.patch

I was asked by kolab folks (aseigo in particular) to include it while they work on getting it upstreamed.

%changelog
* Mon Dec 29 2014 Rex Dieter <rdieter@fedoraproject.org> 6:4.14.3-8
- pull in candidate fix for "kde deamon crash on wakeup" (kde#288410)

* Sat Dec 20 2014 Rex Dieter <rdieter@fedoraproject.org> - 6:4.14.3-7
- borrow Drop-Nepomuk-from-KParts-LINK_INTERFACE_LIBRARIES.patch from obs
- start work to support -nepomuk, -nepomuk-devel subpkgs (wip)

* Thu Dec 18 2014 Rex Dieter <rdieter@fedoraproject.org> - 6:4.14.3-6
- kill uri/ fake mimetypes (#587573, kde#269045)
- own fake mimetype dirs, e.g. mime/all/ (#907667)

* Tue Dec 09 2014 Rex Dieter <rdieter@fedoraproject.org> - 6:4.14.3-5
- pull in Kolab KRecursiveFilterProxyModel.patch

* Fri Dec 05 2014 Rex Dieter <rdieter@fedoraproject.org> - 6:4.14.3-4
- Requires: kde-l10n

* Tue Nov 25 2014 Rex Dieter <rdieter@fedoraproject.org> - 6:4.14.3-3
- rebuild (openexr)

* Fri Nov 21 2014 Rex Dieter <rdieter@fedoraproject.org> - 6:4.14.3-2
- No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) (#1056769)
- use upstream _DEFAULT_SOURCE commit/patch instead

* Sat Nov 08 2014 Rex Dieter <rdieter@fedoraproject.org> 4.14.3-1
- 4.14.3
Comment 5 Rex Dieter 2015-01-14 16:18:22 UTC
I cannot reproduce the problem reported here.

$ rpm -q kdelibs kmail
kdelibs-4.14.3-8.fc20.i686
kmail-4.14.3-1.fc20.i686

Specifically, using kmail against my gmail account (via imap), messages get marked as read as expected, I can also manually mark it read/unread and it's folder status updates as expected.

That said, the status did not change until (initial) folder synchronization completed.
Comment 6 Flavio Leitner 2015-01-15 11:03:18 UTC
I did the package upgrade again and it is working okay now.
I will close this bug and re-open if I can reproduce again.
Thanks for the help!