Bug 1007321 - Evolution show another message
Summary: Evolution show another message
Alias: None
Product: Fedora
Classification: Fedora
Component: libsoup
Version: 19
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-09-12 09:26 UTC by Mikhail
Modified: 2013-09-16 00:28 UTC (History)
6 users (show)

Fixed In Version: libsoup-2.42.2-3.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-09-16 00:28:48 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 708006 0 None None None Never

Description Mikhail 2013-09-12 09:26:45 UTC
Description of problem:
Evolution show another message

Demonstration video: https://docs.google.com/file/d/0B0nwzlfiB4aQMkF5S1lDMjJTMWs/edit?usp=sharing

Comment 1 Milan Crha 2013-09-12 10:18:48 UTC
Thanks for a bug report. It seems the local cache got confused for some reason. I see in that the message preview's Subject, From and basically all other headers shown there do not match with values from the message list above the preview. Could you close evolution and go to:
(you might have there only one folder with uid-like name) and search the cache for all messages which contain some part of the message source from the end of the video, please? You'll probably find two messages. Please delete them from the cache and then run evolution and select the bad message. the evolution-ews will redownload the message (one of those deleted will reappear), this time with correct content hopefully. I would also try to locate the original message, to which the body belongs, and check whether both messages show the right values in message preview (the second message should be also redownloaded from the server).

Comment 2 Mikhail 2013-09-12 11:16:36 UTC
Yeah, removing "another" message from cache solve this problem.
But, I would like to know how it occurs? I can't reproduce this again, but i have some messages with same symptoms.

Comment 3 Milan Crha 2013-09-12 15:57:43 UTC
I agree with you, I would like to know what happened too. If you do not mind, I would move the investigation into a new upstream bug report. Can I?

Comment 4 Mikhail 2013-09-12 22:00:10 UTC
Yes of course.

Comment 5 Milan Crha 2013-09-13 07:28:44 UTC
Thanks, I moved th9is upstream as [1]. I also asked the first question for you there.


Comment 6 David Woodhouse 2013-09-13 13:09:28 UTC
Reopening. We have a patch, and would like it in the Fedora package please (not sure if/when there'll be another upstream release). If we could have a fix for https://bugzilla.gnome.org/show_bug.cgi?id=703186 in the Fedora update too, since that's also biting my Evolution-EWS users, that would be much appreciated.


Comment 7 David Woodhouse 2013-09-13 14:01:54 UTC
This scratch build of libsoup should fix it:

I've shipped this to my internal users already. Happy to push it as a Fedora update if that's OK...

Comment 8 Fedora Update System 2013-09-13 14:55:31 UTC
libsoup-2.42.2-3.fc19 has been submitted as an update for Fedora 19.

Comment 9 Fedora Update System 2013-09-14 02:34:04 UTC
Package libsoup-2.42.2-3.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libsoup-2.42.2-3.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2013-09-16 00:28:48 UTC
libsoup-2.42.2-3.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.