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 606161 - crash in evolution when reply mail with images
crash in evolution when reply mail with images
Status: RESOLVED DUPLICATE of bug 606344
Product: GtkHtml
Classification: Other
Component: Editing
3.29.x
Other Linux
: Normal normal
: ---
Assigned To: Srinivasa Ragavan
Srinivasa Ragavan
Depends on:
Blocks:
 
 
Reported: 2010-01-05 22:18 UTC by Lucian Langa
Modified: 2010-01-08 21:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Lucian Langa 2010-01-05 22:18:20 UTC
Related to the commit: http://git.gnome.org/browse/gtkhtml/commit/?id=b505c8faa1a6ccc32d14713cd1d47d3d9731c739

I'm getting a crash when I reply a mail with images inside.
Crash is in :
g_signal_emit (editor, signals[URI_REQUESTED], 0, url, stream)
from editor_url_requested_cb().
Do we need to call URI_REQUEST if class->uri_request was removed ?

Below is relevant stack trace:

  • #9 IA__g_closure_invoke
    at gclosure.c line 767
  • #10 signal_emit_unlocked_R
    at gsignal.c line 3285
  • #11 IA__g_signal_emit_valist
    at gsignal.c line 2980
  • #12 IA__g_signal_emit
    at gsignal.c line 3037
  • #13 IA__g_closure_invoke
    at gclosure.c line 767
  • #14 signal_emit_unlocked_R
    at gsignal.c line 3247
  • #15 IA__g_signal_emit_valist
    at gsignal.c line 2980
  • #16 IA__g_signal_emit
    at gsignal.c line 3037
  • #17 html_engine_url_requested_cb
    at gtkhtml.c line 502
  • #18 IA__g_closure_invoke
    at gclosure.c line 767
  • #19 signal_emit_unlocked_R
    at gsignal.c line 3247
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2980
  • #21 IA__g_signal_emit_by_name
    at gsignal.c line 3074
  • #22 html_image_factory_register
    at htmlimage.c line 1459

Comment 1 Lucian Langa 2010-01-08 21:44:59 UTC

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