Bug 653727 – evolution crash in search_changed when pressing “To:”

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 653727 - evolution crash in search_changed when pressing “To:”


Summary:	evolution crash in search_changed when pressing “To:”


Status:	RESOLVED DUPLICATE of bug 653216

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

Importance:	Normal major
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Duplicates:	653621 654873 (view as bug list)
Depends on:
Blocks:

Reported:	2011-06-30 10:24 UTC by Peter
Modified:	2011-08-26 08:45 UTC

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

Description Peter 2011-06-30 10:24:14 UTC

evolution-2.32.3 in Gentoo.

While composing new e-mail if I enter some text into To: field and then press “To:” to bring up a contact list evolution crash with the following backtrace:

(gdb) bt

+ Trace 227623

#0 __strcmp_ssse3
at ../sysdeps/x86_64/multiarch/../strcmp.S line 1691
#1 search_changed
at e-name-selector-dialog.c line 906
#2 setup_name_selector_model
at e-name-selector-dialog.c line 1267
#3 e_name_selector_dialog_init
at e-name-selector-dialog.c line 280
#4 g_type_create_instance
at gtype.c line 1885
#5 g_object_constructor
at gobject.c line 1615
#6 g_object_newv
at gobject.c line 1479
#7 g_object_new
at gobject.c line 1308
#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
at gclosure.c line 767
#11 signal_emit_unlocked_R
at gsignal.c line 3290
#12 g_signal_emit_valist
at gsignal.c line 2983
#13 g_signal_emit
at gsignal.c line 3040
#14 g_closure_invoke
at gclosure.c line 767
#15 signal_emit_unlocked_R
at gsignal.c line 3252
#16 g_signal_emit_valist
at gsignal.c line 2983
#17 g_signal_emit
at gsignal.c line 3040
#18 gtk_button_clicked
from /usr/lib64/libgtk-x11-2.0.so.0
#19 gtk_real_button_released
from /usr/lib64/libgtk-x11-2.0.so.0
#20 g_closure_invoke
at gclosure.c line 767
#21 signal_emit_unlocked_R
at gsignal.c line 3182
#22 g_signal_emit_valist
at gsignal.c line 2983
#23 g_signal_emit
at gsignal.c line 3040
#24 gtk_button_released
from /usr/lib64/libgtk-x11-2.0.so.0
#25 gtk_button_button_release
from /usr/lib64/libgtk-x11-2.0.so.0
#26 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib64/libgtk-x11-2.0.so.0
#27 g_closure_invoke
at gclosure.c line 767
#28 signal_emit_unlocked_R
at gsignal.c line 3290
#29 g_signal_emit_valist
at gsignal.c line 2993
#30 g_signal_emit
at gsignal.c line 3040
#31 gtk_widget_event_internal
from /usr/lib64/libgtk-x11-2.0.so.0
#32 gtk_widget_event
from /usr/lib64/libgtk-x11-2.0.so.0
#33 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#34 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#35 gdk_event_dispatch
from /usr/lib64/libgdk-x11-2.0.so.0
#36 g_main_dispatch
at gmain.c line 2441
#37 g_main_context_dispatch
at gmain.c line 3014
#38 g_main_context_iterate
at gmain.c line 3092
#39 g_main_loop_run
at gmain.c line 3300
#40 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#41 main
at main.c line 715


May be this is important but my address book is google address book. 

Ubuntu is also affected by this problem:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/683943

Comment 1 Peter 2011-06-30 10:24:37 UTC

And another similar bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=653621

Comment 2 Akhil Laddha 2011-06-30 13:08:40 UTC

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

Comment 3 Akhil Laddha 2011-07-19 01:27:00 UTC

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

Comment 4 Peter 2011-07-21 07:39:03 UTC

Actually now it started to crash every time I press To: and I'm unsure how to avoid this... Any ideas for workarounds?

Comment 5 Peter 2011-07-21 07:40:07 UTC

And having two duplicates, why this bug is UNCONFIRMED?

Comment 6 Milan Crha 2011-08-26 08:45:53 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 653216 ***