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 504051 - Warnings observed with opening Drafts message with emoticon images
Warnings observed with opening Drafts message with emoticon images
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.22.x (obsolete)
Other Linux
: Normal minor
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-12-17 14:51 UTC by Matthew Barnes
Modified: 2013-09-13 00:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
proposed gtkhtml patch (1.36 KB, patch)
2007-12-21 10:36 UTC, Milan Crha
committed Details | Review

Description Matthew Barnes 2007-12-17 14:51:49 UTC
Milan noticed this in bug #502205.  It doesn't seem to affect functionality at all though, so I'm calling the severity "minor".

Steps to Reproduce:
1) Run Evolution from a terminal.
2) Open a new HTML mail message and insert emoticon images [1].
3) Save the message to Drafts and close the window.
4) Reopen the message from Drafts to continue editing.

Actual Result:
A warning for each emoticon image:
(evolution:10984): gtkhtml-WARNING **: No such file or directory

Excepted Result:
No warning.

Additional Information:
It appears GtkHTML is trying to open the MIME Content-Id for the image as if it were a file URI.  As such, I'm not sure whether the problem is in Evolution or GtkHTML.  Leaving the component as Evolution for now.


[1] This step requires GtkHTML 2.17.5.  You can also do it on earlier
    versions by typing an ASCII emoticon (e.g. :-) ) and having it
    automatically converted to an image.
Comment 1 Milan Crha 2007-12-21 10:36:47 UTC
Created attachment 101392 [details] [review]
proposed gtkhtml patch

for gtkhtml;

I did a patch in gtkhtml itself, because the warning came from there. (See my stack trace from the previous bug). The patch contains another fix too. I just hope I got the meaning with that second fix.
Comment 2 Srinivasa Ragavan 2008-01-01 09:47:13 UTC
Looks fine to me. Commit to trunk.
Comment 3 Milan Crha 2008-01-02 12:08:16 UTC
Committed to trunk. Committed revision 8670.