Bug 258110 - Number of unread messages does not update
Summary: Number of unread messages does not update
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 2.0.89
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-27 21:14 UTC by Alex Richardson
Modified: 2011-06-16 08:24 UTC (History)
4 users (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 Alex Richardson 2010-11-27 21:14:07 UTC
Version:           2.0.89 (using KDE 4.5.80) 
OS:                Linux

Sometimes, but not always it happens that after I read messages, the number of unread messages in the treeview remains exactly the same. Also the number in the tray icon is outdated. At the moment KMail2 is indicating I have 19 unread messages although I just read them. Pressing next message in KMail switches to the next folder that supposedly has unread messages, however no message is selected and the number of unread messages stays the same. While the messages were actually new everything worked as expected except for the fact that the numbers were not updated.

Reproducible: Sometimes




OS: Linux (x86_64) release 2.6.34.7-0.5-desktop
Compiler: gcc
Comment 1 Jakub Schmidtke 2010-12-10 01:39:45 UTC
In my case there is no systray unread message count at all, and unread message counts in the folderview don't decrease at all. Not sometimes, it happens every time. I have to quit kmail and start it again to get rid of unread message numbers from folder names.
I use IMAP accounts.
Comment 2 Ian Stanistreet 2010-12-10 11:09:45 UTC
This appears to be fixed in KMail 2.0.89. It now works as expected.

I too have no unread message count on the systray icon (is this by design?), but the correct count is shown in the systray tooltip and in the KMail folder view.
Comment 3 Jakub Schmidtke 2010-12-10 14:36:28 UTC
No it is not fixed in 2.0.89. The original bug was submitted for "2.0.89", how can you say that it has been fixed in 2.0.89??? It is not fixed.
Comment 4 Ian Stanistreet 2010-12-10 20:37:35 UTC
Oops - when I wrote my previous comment I meant to say KDE 4.5.85, not KMail 2.0.89.  It definitely works correctly now on Arch Linux, using KMail 2.0.89 and KDE 4.5.85.  It didn't work correctly on KDE 4.5.80.  Sorry for the mistake.
Comment 5 Ian Stanistreet 2010-12-10 20:49:47 UTC
OK, seems I spoke too soon.  It has just happened again, after working perfectly for the last couple of days.  It was happening every time in KDE 4.5.80.
Not entirely fixed after all, but it has only happened once so far in 4.5.85.
Comment 6 Andreas Schneider 2010-12-12 12:03:54 UTC
The same happens here, kmail2 2.0.89.
Comment 7 Tobias Koenig 2010-12-12 17:07:12 UTC
Hej,

can you update to most current SVN version, please?
I've commited a patch 3 days ago that should fix this issue.

Ciao,
Tobias
Comment 8 Jakub Schmidtke 2010-12-12 17:16:54 UTC
Which packages? I could update, but I would like to avoid recompiling the entire KDE. Is "kdepim-kmail" enough? Or "akonadi" should be updated as well?
Actually, I checked the packages I have, and akonadi is in 4.0.80 version. And there is no newer version available in ArchLinux.
Comment 9 Tobias Koenig 2010-12-13 17:25:20 UTC
Hej,

it's fixed in SVN trunk, no idea how current the available packages are for your distribution.

Ciao,
Tobias
Comment 10 Jakub Schmidtke 2010-12-13 17:30:20 UTC
They are not that current. So I have to build it from SVN. And I can do that, but I would like to know where in SVN that change was made, so I could only build and install that part, not the entire KDE. Was it the kmail? Or akonadi? The path to the commit, or at least a path to modified files would be sufficient.
Comment 11 Tobias Koenig 2010-12-13 17:52:39 UTC
Hej Jakub,

kdepimlibs/akonadi/monitor_p.cpp

Ciao,
Tobias
Comment 12 Jakub Schmidtke 2011-06-16 01:42:15 UTC
Just revisiting bugs I reported ;) I think this has been fixed a long time ago, haven't experienced any problems in the last few months.
Comment 13 Andreas Schneider 2011-06-16 08:24:38 UTC
This is fixed in KMail2 2.1.0 for me too. Closing.