After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 404833 - Groups Showing Unread Messages on Startup
Groups Showing Unread Messages on Startup
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-1.0 betas
Other Linux
: Normal normal
: 1.0
Assigned To: Charles Kerr
Pan QA Team
: 406169 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-06 01:54 UTC by Frank Tabor
Modified: 2007-02-09 18:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
one-liner fix (809 bytes, patch)
2007-02-07 19:12 UTC, Charles Kerr
committed Details | Review

Description Frank Tabor 2007-02-06 01:54:17 UTC
Pan 0.122
After closing and restarting Pan, groups that had unread headers show bold and show a number for unread message, even though groups were showing as having no unread messages on closing.  As soon as the group is checked for new messages or opened, the counter is reset and the group name is changed to unbold or bold as the true state may be.
Comment 1 Duncan 2007-02-06 04:56:10 UTC
This was first reported on the user list/group and I confirmed I saw it too there.  Here's a link to the subthread.  No additional info ATM, however:

http://thread.gmane.org/gmane.comp.gnome.apps.pan.user/8322

Restating the problem in my own words, on pan restart (with fetch headers at pan start turned off), the message unread counts appear to reflect the last server update state, previous to any activity reading messages after that.  However, pan does retain the true state as well, since if one actually enters the group or updates headers, the counts reset to the correct state.  Thus, it appears one file is getting updated but the other one isn't.

This may be fixed in current SVN, with the patch at

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

I haven't updated and verified yet.
Comment 2 Duncan 2007-02-06 21:34:30 UTC
... And 404837's patch didn't fix it, as the bug is still in 0.123, now verified.
Comment 3 Charles Kerr 2007-02-07 02:19:45 UTC
#404837 is a totally different bug.
Comment 4 Charles Kerr 2007-02-07 19:10:37 UTC
Looks like this was caused by the patch in Bug #400814
Comment 5 Charles Kerr 2007-02-07 19:12:50 UTC
Created attachment 82101 [details] [review]
one-liner fix

This should fix it.
Comment 6 Christophe Lambin 2007-02-08 17:49:46 UTC
That does fix it. Weird, though: I didn't experience this problem when I applied that patch. Strange.
Comment 7 Charles Kerr 2007-02-08 19:39:02 UTC
Chris: #400814's bug only got tickled if you marked a group as read
while the group wasn't loaded, so reading news in a group wouldn't
be enough.  You'd have to, for example, mark a group as read from
the group pane's context menu without loading the group.
Comment 8 Christophe Lambin 2007-02-09 18:54:46 UTC
*** Bug 406169 has been marked as a duplicate of this bug. ***