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 595202 - USENET news message displayed in preview is different than message displayed in index (message list)
USENET news message displayed in preview is different than message displayed ...
Status: RESOLVED DUPLICATE of bug 724039
Product: evolution
Classification: Applications
Component: Mailer
2.26.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[nntp]
Depends on:
Blocks:
 
 
Reported: 2009-09-14 18:28 UTC by Adam Monsen
Modified: 2014-12-12 12:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Adam Monsen 2009-09-14 18:28:55 UTC
This one is a little tough to describe, and I don't really have a "clean" repro, but please have a look at this image:

  http://img215.imageshack.us/i/wrongmessageinpreview.png/

Notice that the highlighted message is from "Chandan.Rao...", but the message displayed in the preview window is from "John Woodlock".

The index/preview discontinuity seems to occur like so:
* open Evolution after booting computer
* try to read a new message in gmane.come.finance.mifos.devel
* Evolution displays a message similar to "cannot download message from server"
* from then on, all other new messages shown in the preview window don't match the message highlighted in the index

I marked it "major" because I don't know of a workaround, and this blocks me from replying directly to messages on this newsgroup via Evolution.

I'm using Evolution 2.26.1 on Ubuntu 9.04.
Comment 1 Milan Crha 2014-12-12 12:39:45 UTC
Thanks for a bug report. This particular one might be obsolete these days. I'll mark it as a duplicate of a more recent, because there was a similar issue, but in a completely different code than in times of 2.26.x.

*** This bug has been marked as a duplicate of bug 724039 ***