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 609705 - SIGSEGV on double-clicking an e-mail address.
SIGSEGV on double-clicking an e-mail address.
Status: RESOLVED DUPLICATE of bug 605811
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-02-12 01:38 UTC by David Ronis
Modified: 2013-09-13 01:05 UTC
See Also:
GNOME target: 2.30.x
GNOME version: 2.29/2.30



Description David Ronis 2010-02-12 01:38:09 UTC
This is on today's git/master of evo and friends.   I wanted to e-mail someone (not a reply with the sender's e-mail copied) and double clicked on the higlighted From:  e-mail address.   Evo hangs, which after running in gdb gives the following backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb56da710 (LWP 7672)]
0xb578ce8d in mempcpy () from /lib/libc.so.6
(gdb) thread apply bt  all bt full

Thread 1 (Thread 0xb56da710 (LWP 7672))

  • #0 mempcpy
    from /lib/libc.so.6
  • #1 _IO_default_xsputn_internal
    from /lib/libc.so.6
  • #2 vfprintf
    from /lib/libc.so.6
  • #3 vsprintf
    from /lib/libc.so.6
  • #4 vsnprintf
    at vsnprintf.c line 135
  • #5 _dbus_printf_string_upper_bound
    at dbus-sysdeps-unix.c line 3228
  • #6 _dbus_string_append_printf_valist
    at dbus-string.c line 1255
  • #7 dbus_set_error
    at dbus-errors.c line 384
  • #8 dbus_set_error_from_message
    at dbus-message.c line 3616
  • #9 dbus_connection_send_with_reply_and_block
    at dbus-connection.c line 3478
  • #10 _g_daemon_vfs_get_mount_info_sync
  • #11 g_daemon_file_get_path
    at gdaemonfile.c line 178
  • #12 IA__g_file_get_path
    at gfile.c line 447
  • #13 expand_macro_single
    at gdesktopappinfo.c line 537
  • #14 expand_macro
  • #15 g_desktop_app_info_launch_uris
    at gdesktopappinfo.c line 735
  • #16 IA__g_app_info_launch_uris
    at gappinfo.c line 572
  • #17 IA__g_app_info_launch_default_for_uri
    at gappinfo.c line 632
  • #18 IA__gtk_show_uri
    at gtkshow.c line 73
  • #19 e_show_uri
    at e-util.c line 133
  • #20 web_view_link_clicked
    at e-web-view.c line 730
  • #21 mail_display_link_clicked
    at e-mail-display.c line 264
  • #22 IA__g_cclosure_marshal_VOID__STRING
    at gmarshal.c line 496
  • #23 g_type_class_meta_marshal
    at gclosure.c line 878
  • #24 IA__g_closure_invoke
    at gclosure.c line 767
  • #25 signal_emit_unlocked_R
    at gsignal.c line 3173
  • #26 IA__g_signal_emit_valist
    at gsignal.c line 2976
  • #27 IA__g_signal_emit
    at gsignal.c line 3033
  • #28 button_release_event
    at gtkhtml.c line 2064
  • #29 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #30 g_type_class_meta_marshal
    at gclosure.c line 878
  • #31 IA__g_closure_invoke
    at gclosure.c line 767
  • #32 signal_emit_unlocked_R
    at gsignal.c line 3281
  • #33 IA__g_signal_emit_valist
    at gsignal.c line 2986
  • #34 IA__g_signal_emit
    at gsignal.c line 3033
  • #35 gtk_widget_event_internal
    at gtkwidget.c line 4941
  • #36 IA__gtk_propagate_event
    at gtkmain.c line 2442
  • #37 IA__gtk_main_do_event
    at gtkmain.c line 1647
  • #38 gdk_event_dispatch
    at gdkevents-x11.c line 2372
  • #39 IA__g_main_context_dispatch
    at gmain.c line 1960
  • #40 g_main_context_iterate
    at gmain.c line 2591
  • #41 IA__g_main_loop_run
    at gmain.c line 2799
  • #42 IA__gtk_main
    at gtkmain.c line 1219
  • #43 main
    at main.c line 611

Comment 1 Milan Crha 2010-02-12 12:35:10 UTC
There is really something strange with your system, as this is just another instance of bug #605811, see the top few frames are matching, only from here is DBus invoked from non-Evolution library, the gio/gvfs (while calling g_file_get_path). I'm marking this as a duplicate of the above mentioned bug.

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