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 485305 - crash in Evolution Mail: Typing an email address ...
crash in Evolution Mail: Typing an email address ...
Status: RESOLVED DUPLICATE of bug 458670
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 486735 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-10-10 08:35 UTC by tc270
Modified: 2007-10-23 11:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
stack trace (13.28 KB, text/plain)
2007-10-23 08:24 UTC, growler
Details

Description tc270 2007-10-10 08:35:27 UTC
What were you doing when the application crashed?
Typing an email address into the "To" box


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

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Flat-Blue

Memory status: size: 93122560 vsize: 93122560 resident: 13307904 share: 6086656 rss: 13307904 rss_rlim: 4294967295
CPU usage: start_time: 1192002517 rtime: 74 utime: 64 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-data-server-1.10'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb734e6b0 (LWP 4393)]
[New Thread 0xb7007b90 (LWP 8674)]
[New Thread 0xb5770b90 (LWP 8671)]
[New Thread 0xb5f70b90 (LWP 4445)]
[New Thread 0xb7047b90 (LWP 4394)]
(no debugging symbols found)
0xb75c0801 in waitpid () from /lib/libc.so.6

Thread 2 (Thread 0xb7007b90 (LWP 8674))

  • #0 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_mutex_lock_86
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
    from /usr/lib/evolution-data-server-1.2/extensions/libebookbackendldap.so
  • #9 ??
  • #10 ??
  • #11 <signal handler called>
  • #12 ??
  • #13 ??
    from /usr/lib/evolution-data-server-1.2/extensions/libebookbackendldap.so
  • #14 ??
  • #15 ??
  • #16 ??
    from /usr/lib/evolution-data-server-1.2/extensions/libebookbackendldap.so
  • #17 ??
    from /usr/lib/libedata-book-1.2.so.2
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 e_book_backend_stop_book_view
    from /usr/lib/libedata-book-1.2.so.2


----------- .xsession-errors (21 sec old) ---------------------
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x220005a specified for 0x2200292 (Adobe Read).
adding certinfo Robin Walker <rdhw@cam.ac.uk>
adding certinfo Robin Walker <rdhw@cam.ac.uk>
adding certinfo Robin Walker <rdhw@cam.ac.uk>
in emp_apps_open_in
adding certinfo Robin Walker <rdhw@cam.ac.uk>
adding certinfo Robin Walker <rdhw@cam.ac.uk>
adding certinfo Robin Walker <rdhw@cam.ac.uk>
adding certinfo Robin Walker <rdhw@cam.ac.uk>
evolution-shell-Message: Killing old version of evolution-data-server...
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
evolution-shell-Message: Killing old version of evolution-data-server...
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
--------------------------------------------------
Comment 1 palfrey 2007-10-15 12:15:48 UTC
*** Bug 486735 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2007-10-15 22:46:13 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Comment 3 growler 2007-10-23 08:24:08 UTC
Created attachment 97705 [details]
stack trace

Here's stack trace you requested. Happened when I was entering address into To field

Strange enough, it's the first time I've got this bug after installing debug libraries. Before that it was appearing much more often. Also, with debug libraries the bug crushes all the suite (before only data-backend was affected)
Comment 4 André Klapper 2007-10-23 10:23:03 UTC
hmm, the last stacktrace still misses a lot of calls:

  • #4 <signal handler called>
  • #5 ??
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 ??
  • #8 ??
    from /usr/lib/libedataserverui-1.2.so.8
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 get_entry_substring
    at e-name-selector-entry.c line 520

dbg-packages for glib2, gtk2 and evolution-data-server are installed, i guess?
Comment 5 growler 2007-10-23 10:34:08 UTC
Oops, my fault, sorry. I've installed -dbg for version 1.2 of gtk. As for evolution data server, yes, -dbg version is installed:
ii  evolution-data-server        1.10.3-1                     evolution database backend server
ii  evolution-data-server-common 1.10.3-1                     architecture independent files for Evolution Data Server
ii  evolution-data-server-dbg    1.10.3-1                     evolution database backend server with debugging symbols

I've just installed libgtk2.0-0-dbg and libglib2.0-0-dbg. Hope it will not take that long to hit the bug again.
Comment 6 growler 2007-10-23 11:13:38 UTC
It did it aagain! I hope this one will help:

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

System: Linux 2.6.23-et64 #1 SMP PREEMPT Sun Oct 14 18:10:22 MSD 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 140410880 vsize: 140410880 resident: 56594432 share: 21221376 rss: 56594432 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193127501 rtime: 3251 utime: 3072 stime: 179 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xf67f16b0 (LWP 26579)]
[New Thread 0xf17feb90 (LWP 26863)]
[New Thread 0xf50ffb90 (LWP 26859)]
[New Thread 0xf33ffb90 (LWP 26635)]
[New Thread 0xf3dfab90 (LWP 26610)]
[New Thread 0xf48feb90 (LWP 26608)]
[New Thread 0xf5960b90 (LWP 26601)]
[New Thread 0xf6161b90 (LWP 26599)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xf67f16b0 (LWP 26579))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/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 IA__g_utf8_offset_to_pointer
    at /tmp/buildd/glib2.0-2.14.1/glib/gutf8.c line 302
  • #6 get_entry_substring
    at e-name-selector-entry.c line 520
  • #7 entry_activate
    at e-name-selector-entry.c line 1402
  • #8 user_focus_out
    at e-name-selector-entry.c line 1464
  • #9 _gtk_marshal_BOOLEAN__BOXED
    at /tmp/buildd/gtk+2.0-2.10.13/gtk/gtkmarshalers.c line 84
  • #10 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.14.1/gobject/gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2440
  • #12 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2209
  • #13 IA__g_signal_emit
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2243
  • #14 gtk_widget_event_internal
    at /tmp/buildd/gtk+2.0-2.10.13/gtk/gtkwidget.c line 3915
  • #15 do_focus_change
    at /tmp/buildd/gtk+2.0-2.10.13/gtk/gtkwindow.c line 4782
  • #16 _gtk_window_set_has_toplevel_focus
    at /tmp/buildd/gtk+2.0-2.10.13/gtk/gtkwindow.c line 7783
  • #17 gtk_window_focus_out_event
    at /tmp/buildd/gtk+2.0-2.10.13/gtk/gtkwindow.c line 4816
  • #18 _gtk_marshal_BOOLEAN__BOXED
    at /tmp/buildd/gtk+2.0-2.10.13/gtk/gtkmarshalers.c line 84
  • #19 g_type_class_meta_marshal
    at /tmp/buildd/glib2.0-2.14.1/gobject/gclosure.c line 567
  • #20 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.14.1/gobject/gclosure.c line 490
  • #21 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2478
  • #22 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2209
  • #23 IA__g_signal_emit
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2243
  • #24 gtk_widget_event_internal
    at /tmp/buildd/gtk+2.0-2.10.13/gtk/gtkwidget.c line 3915
  • #25 IA__gtk_main_do_event
    at /tmp/buildd/gtk+2.0-2.10.13/gtk/gtkmain.c line 1553
  • #26 gdk_event_dispatch
    at /tmp/buildd/gtk+2.0-2.10.13/gdk/x11/gdkevents-x11.c line 2318
  • #27 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 2061
  • #28 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 2694
  • #29 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 2898
  • #30 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #31 main
    at main.c line 611
  • #0 __kernel_vsyscall

Comment 7 André Klapper 2007-10-23 11:27:30 UTC
thanks for the great trace!

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 Evolution version 2.12.0.


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