Bug 637252 – Crash with SIGSEGV when opening the name selector (clicking To, CC, in composer)

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 637252 - Crash with SIGSEGV when opening the name selector (clicking To, CC, in composer)


Summary:	Crash with SIGSEGV when opening the name selector (clicking To, CC, in composer)


Status:	RESOLVED FIXED

Product:	evolution
Classification:	Applications
Component:	Contacts
Version:	2.32.x (obsolete)
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	evolution-addressbook-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Duplicates:	653216 (view as bug list)
Depends on:
Blocks:

Reported:	2010-12-14 20:14 UTC by Mathieu Trudel-Lapierre
Modified:	2011-10-21 04:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Mathieu Trudel-Lapierre 2010-12-14 20:14:19 UTC

From downstream bug report:
https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/690181

When composing a message (either new or as reply/forward), clicking on any of the name-selector opening buttons: To, Cc, triggers a segfault.

See below for the trace:

+ Trace 225132

#0 ??
from /lib/libc.so.6
#1 search_changed
at e-name-selector-dialog.c line 892
#2 setup_name_selector_model
at e-name-selector-dialog.c line 1253
#3 e_name_selector_dialog_init
at e-name-selector-dialog.c line 266
#4 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#5 ??
from /usr/lib/libgobject-2.0.so.0
#6 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#7 g_object_new
from /usr/lib/libgobject-2.0.so.0
#8 e_name_selector_peek_dialog
at e-name-selector.c line 358
#9 composer_name_header_clicked
at e-composer-name-header.c line 228
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 ??
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 ??
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 ??
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib/libgtk-x11-2.0.so.0
#25 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#26 ??
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgdk-x11-2.0.so.0
#33 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#34 ??
from /lib/libglib-2.0.so.0
#35 g_main_loop_run
from /lib/libglib-2.0.so.0
#36 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#37 main
at main.c line 679

Comment 1 Fabio Durán Verdugo 2010-12-14 23:22:25 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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

Comment 2 Mathieu Trudel-Lapierre 2010-12-15 14:35:55 UTC

Sorry, no, I don't believe this is fixed in 2.32.1.

Please consider backporting the changes that could have been made in 2.91 or understanding why the other reporter no longer has the issue.

I'm still trying to find how to fix it, but without success yet.

Comment 3 Mathieu Trudel-Lapierre 2010-12-16 16:08:31 UTC

Got it, seems it's due to a patch from the gnome-2-91-1 branch applied to 2.32 by Ubuntu, so sorry for the noise. Backporting the rest of the definition of combobox_category as a GtkComboBoxText inline rather than in the .ui file fixes the problem, along with the changes below.

So, please consider applying the following changes to the gnome-2-91-1 branch:

 - changing cast from GTK_COMBO_BOX to GTK_COMBO_BOX_TEXT for calls to gtk_combo_box_text_append_text() and gtk_combo_box_text_get_active_text()
 - adding a redefinition of the GTK_COMBO_BOX_TEXT macro as GTK_COMBO_BOX for GTK versions lower than 2.23 in gtk_compat.h.

Comment 4 Milan Crha 2011-02-11 06:49:08 UTC

Evolution doesn't support gtk2 any more, it's only gtk3 now and the above changes are incorporated in some form already, thus I'm closing this bug report.

Comment 5 Akhil Laddha 2011-10-21 04:47:02 UTC

*** Bug 653216 has been marked as a duplicate of this bug. ***