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 478011 - crash in Evolution Mail: When composing an email,...
crash in Evolution Mail: When composing an email,...
Status: RESOLVED DUPLICATE of bug 458670
Product: evolution
Classification: Applications
Component: Contacts
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-18 11:31 UTC by rrotta
Modified: 2007-12-04 17:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description rrotta 2007-09-18 11:31:44 UTC 
What were you doing when the application crashed?
When composing an email, I enter email addresses in the To and Cc field and let them auto-complete from the address book. Then deleting and inserting new addresses until the auto-completion does stop to work. Before the crash in the email address dialog it is visible that there are some empty ("") addresses in the line which aren't visible in the compose window. I then try to delete them in the composer and most times evolution crashes on this. 

The camel debug message says:
(evolution:11194): e-data-server-ui-WARNING **: ENameSelectorEntry is out of sync with model!



Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22.1 #1 Sun Jul 22 20:55:25 CEST 2007 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 159481856 vsize: 159481856 resident: 37310464 share: 27369472 rss: 37310464 rss_rlim: 4294967295
CPU usage: start_time: 1190114046 rtime: 1039 utime: 955 stime: 84 cutime:5 cstime: 11 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 805755152 (LWP 11194)]
[New Thread 877532368 (LWP 11267)]
[New Thread 854639824 (LWP 11265)]
[New Thread 876877008 (LWP 11224)]
[New Thread 863028432 (LWP 11223)]
[New Thread 846251216 (LWP 11215)]
[New Thread 828372176 (LWP 11214)]
[New Thread 837862608 (LWP 11213)]
[New Thread 819590352 (LWP 11211)]
0x0fd505a4 in ?? () from /lib/libpthread.so.0

+ Trace 163731

Thread 1 (Thread 805755152 (LWP 11194))

  • #0 ??
    from /lib/libpthread.so.0
  • #1 ??
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 segv_redirect
    at main.c line 427
  • #4 <signal handler called>
  • #5 g_utf8_offset_to_pointer
    from /usr/lib/libglib-2.0.so.0
  • #6 get_entry_substring
    at e-name-selector-entry.c line 520
  • #7 entry_activate
    at e-name-selector-entry.c line 1402
  • #8 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emitv
    from /usr/lib/libgobject-2.0.so.0
  • #12 gtk_binding_entry_activate
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkbindings.c line 535
  • #13 binding_match_activate
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkbindings.c line 955
  • #14 gtk_bindings_activate_list
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkbindings.c line 1089
  • #15 IA__gtk_bindings_activate_event
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkbindings.c line 1166
  • #16 gtk_entry_key_press
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkentry.c line 2042
  • #17 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkmarshalers.c line 84
  • #18 ??
    from /usr/lib/libgobject-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 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkwidget.c line 3915
  • #24 IA__gtk_window_propagate_key_event
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkwindow.c line 4670
  • #25 gtk_window_key_press_event
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkwindow.c line 4700
  • #26 ??
    from /usr/lib/libbonoboui-2.so.0
  • #27 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkmarshalers.c line 84
  • #28 ??
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #30 ??
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #33 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkwidget.c line 3915
  • #34 IA__gtk_propagate_event
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkmain.c line 2315
  • #35 IA__gtk_main_do_event
    at /build/buildd/gtk+2.0-2.10.13/gtk/gtkmain.c line 1575
  • #36 gdk_event_dispatch
    at /build/buildd/gtk+2.0-2.10.13/gdk/x11/gdkevents-x11.c line 2318
  • #37 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #38 ??
    from /usr/lib/libglib-2.0.so.0
  • #39 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #40 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #41 main
    at main.c line 611
  • #0 ??
    from /lib/libpthread.so.0 


----------- .xsession-errors (406 sec old) ---------------------
(l)user is reading mail
(l)user is reading mail
(l)user is reading mail
(l)user is reading mail
(l)user is reading mail
Reading RSS articles...
Reading RSS articles...
(l)user is reading mail
(l)user is reading mail
(l)user is reading mail
(l)user is reading mail
(l)user is reading mail
BBDB spinning up...
(evolution:7311): e-data-server-ui-WARNING **: ENameSelectorEntry is out of sync with model!
--------------------------------------------------
Comment 1 palfrey 2007-12-04 17:06:46 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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