Bug 480073 – crash in Email:

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 480073 - crash in Email:


Summary:	crash in Email:


Status:	RESOLVED DUPLICATE of bug 431396

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:	aklapper[fc7]

Depends on:
Blocks:

Reported:	2007-09-25 04:29 UTC by ReD
Modified:	2007-09-29 00:41 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description ReD 2007-09-25 04:29:37 UTC

Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 243650560 vsize: 243650560 resident: 93802496 share: 53911552 rss: 93802496 rss_rlim: 4294967295
CPU usage: start_time: 1190676429 rtime: 14626 utime: 13434 stime: 1192 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1208539424 (LWP 13495)]
[New Thread -1389479024 (LWP 16940)]
[New Thread -1378989168 (LWP 14480)]
[New Thread -1255965808 (LWP 13575)]
[New Thread -1341158512 (LWP 13533)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 165252

Thread 1 (Thread -1208539424 (LWP 13495))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free1
from /lib/libglib-2.0.so.0
#9 g_slist_free_1
from /lib/libglib-2.0.so.0
#10 g_slist_remove
from /lib/libglib-2.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit
from /lib/libgobject-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#21 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#23 bonobo_ui_engine_prune_widget_info
from /usr/lib/libbonoboui-2.so.0
#24 bonobo_ui_engine_prune_widget_info
from /usr/lib/libbonoboui-2.so.0
#25 bonobo_ui_engine_prune_widget_info
from /usr/lib/libbonoboui-2.so.0
#26 bonobo_ui_engine_prune_widget_info
from /usr/lib/libbonoboui-2.so.0
#27 ??
from /usr/lib/libbonoboui-2.so.0
#28 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#29 g_closure_invoke
from /lib/libgobject-2.0.so.0
#30 ??
from /lib/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#32 g_signal_emit
from /lib/libgobject-2.0.so.0
#33 ??
from /usr/lib/libbonoboui-2.so.0
#34 ??
from /usr/lib/libbonoboui-2.so.0
#35 ??
from /usr/lib/libbonoboui-2.so.0
#36 bonobo_ui_xml_rm
from /usr/lib/libbonoboui-2.so.0
#37 bonobo_ui_engine_xml_rm
from /usr/lib/libbonoboui-2.so.0
#38 bonobo_ui_engine_deregister_component
from /usr/lib/libbonoboui-2.so.0
#39 ??
from /usr/lib/libbonoboui-2.so.0
#40 _ORBIT_skel_small_Bonobo_UIContainer_deregisterComponent
from /usr/lib/libbonobo-2.so.0
#41 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#42 Bonobo_UIContainer_deregisterComponent
from /usr/lib/libbonobo-2.so.0
#43 bonobo_ui_component_unset_container
from /usr/lib/libbonoboui-2.so.0
#44 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#45 ??
from /usr/lib/libgtk-x11-2.0.so.0
#46 g_closure_invoke
from /lib/libgobject-2.0.so.0
#47 ??
from /lib/libgobject-2.0.so.0
#48 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#49 g_signal_emit
from /lib/libgobject-2.0.so.0
#50 ??
from /usr/lib/libgtk-x11-2.0.so.0
#51 ??
from /usr/lib/libgtk-x11-2.0.so.0
#52 ??
from /usr/lib/libgtk-x11-2.0.so.0
#53 ??
from /usr/lib/libgtk-x11-2.0.so.0
#54 ??
from /usr/lib/libgtk-x11-2.0.so.0
#55 ??
from /lib/libgobject-2.0.so.0
#56 g_closure_invoke
from /lib/libgobject-2.0.so.0
#57 ??
from /lib/libgobject-2.0.so.0
#58 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#59 g_signal_emit
from /lib/libgobject-2.0.so.0
#60 ??
from /usr/lib/libgtk-x11-2.0.so.0
#61 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#62 ??
from /usr/lib/libgdk-x11-2.0.so.0
#63 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#64 ??
from /lib/libglib-2.0.so.0
#65 g_main_loop_run
from /lib/libglib-2.0.so.0
#66 bonobo_main
from /usr/lib/libbonobo-2.so.0
#67 main
#0 __kernel_vsyscall



----------- .xsession-errors (27 sec old) ---------------------
(evolution:13495): libebook-WARNING **: invalid escape, passing it through
(evolution:13495): libebook-WARNING **: invalid escape, passing it through
(evolution:13495): libebook-WARNING **: invalid escape, passing it through
(evolution:13495): libebook-WARNING **: invalid escape, passing it through
(evolution:13495): libebook-WARNING **: invalid escape, passing it through
(evolution:13495): libebook-WARNING **: invalid escape, passing it through
(evolution:13495): libebook-WARNING **: invalid escape, passing it through
(evolution:13495): libebook-WARNING **: invalid escape, passing it through
--------------------------------------------------

Comment 1 Tobias Mueller 2007-09-29 00:41:12 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 431396 ***