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 348758 - Evolution crashes on show/hide attached JPEG image
Evolution crashes on show/hide attached JPEG image
Status: RESOLVED DUPLICATE of bug 316516
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-07-26 09:39 UTC by Assen Totin
Modified: 2006-07-26 11:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
A typical situation after Evo crash (163.47 KB, image/jpeg)
2006-07-26 09:42 UTC, Assen Totin
Details

Description Assen Totin 2006-07-26 09:39:48 UTC
Steps to reproduce:
1. Receive a message with an attached JPEG
2. Click on the arrow to open the image inside the message
3. Click the arrow to hide the image


Stack trace:


Other information:
Fedora Core 5 with latest updates. Bug is persistent (observer several times in the past few months), shows itself from time to time on different images from different mails and senders. The most annoying is that when Evo is restarted, all mail that has been re-classified (deleted, moved to different foldder etc.) now appears again in Inbox (and this usually means 100 and more messages!). The second problem is that when Evo is restarted, erroneous entries appear in the message list (i.e. message A has the subject and date of existing message B etc.). This makes reading mail difficult and filtering mail impossible. I have reported this before as a separate bug, but received no answer.
Comment 1 Assen Totin 2006-07-26 09:42:00 UTC
Created attachment 69650 [details]
A typical situation after Evo crash

Compare the sender, subject and date of the highlighted message (erroneous data) with the actual message below (accurate data).
Comment 2 Sergej Kotliar 2006-07-26 11:47:46 UTC
Thanks for your bug report?

The JPEG issue is already filed in bugzilla, and this is why I will close this bug report as a duplicate. As for things behaving badly AFTER the crash - you might want to file a separate bug report on that. I think it's already filed too, but I couldn't find it...
And generally, in bugzilla, always file only one issue per bug report, otherwise it becomes very difficult to track them down for the developers.



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