Bug 421619 – crash in Evolution: I had just wrote out a p...

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 421619 - crash in Evolution: I had just wrote out a p...


Summary:	crash in Evolution: I had just wrote out a p...


Status:	RESOLVED DUPLICATE of bug 370496

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-22 20:15 UTC by jschavey
Modified:	2007-04-02 22:44 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description jschavey 2007-03-22 20:15:54 UTC

What were you doing when the application crashed?
I had just wrote out a page long email... Was trying to add contacts to the To line.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 261496832 vsize: 0 resident: 261496832 share: 0 rss: 88502272 rss_rlim: 0
CPU usage: start_time: 1174525354 rtime: 0 utime: 11066 stime: 0 cutime:10517 cstime: 0 timeout: 549 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233332560 (LWP 19922)]
[New Thread -1385215072 (LWP 20003)]
[New Thread -1326466144 (LWP 19956)]
[New Thread -1317987424 (LWP 19943)]
[New Thread -1309201504 (LWP 19942)]
[New Thread -1308935264 (LWP 19941)]
[New Thread -1300542560 (LWP 19940)]
[New Thread -1292149856 (LWP 19939)]
[New Thread -1269613664 (LWP 19935)]
[New Thread -1261220960 (LWP 19934)]
[New Thread -1251374176 (LWP 19933)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 121243

Thread 1 (Thread -1233332560 (LWP 19922))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 e_name_selector_entry_set_contact_list_editor_func
from /usr/lib/libedataserverui-1.2.so.8
#11 e_name_selector_entry_set_contact_list_editor_func
from /usr/lib/libedataserverui-1.2.so.8
#12 _gtk_marshal_VOID__STRING_INT_POINTER
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#17 gtk_entry_new
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_editable_insert_text
from /usr/lib/libgtk-x11-2.0.so.0
#19 _gtk_entry_reset_im_context
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_cclosure_marshal_VOID__STRING
from /usr/lib/libgobject-2.0.so.0
#21 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#25 gtk_im_multicontext_append_menuitems
from /usr/lib/libgtk-x11-2.0.so.0
#26 g_cclosure_marshal_VOID__STRING
from /usr/lib/libgobject-2.0.so.0
#27 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#31 gtk_im_context_simple_new
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_im_context_simple_new
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_im_context_filter_keypress
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_im_multicontext_new
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_im_context_filter_keypress
from /usr/lib/libgtk-x11-2.0.so.0
#36 gtk_entry_new
from /usr/lib/libgtk-x11-2.0.so.0
#37 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#38 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#39 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#40 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#41 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#42 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#43 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#44 gtk_window_propagate_key_event
from /usr/lib/libgtk-x11-2.0.so.0
#45 gtk_window_activate_key
from /usr/lib/libgtk-x11-2.0.so.0
#46 bonobo_window_remove_popup
from /usr/lib/libbonoboui-2.so.0
#47 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#48 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#49 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#50 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#51 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#52 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#53 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#54 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#55 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#56 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#57 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#58 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#59 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#60 bonobo_main
from /usr/lib/libbonobo-2.so.0
#61 main
#0 __kernel_vsyscall

Comment 1 palfrey 2007-04-02 22:44:03 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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