Bug 519760 – crash in Tasks: reading 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 519760 - crash in Tasks: reading email


Summary:	crash in Tasks: reading email


Status:	RESOLVED DUPLICATE of bug 433573

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-03-01 16:36 UTC by babycarrot
Modified:	2008-03-04 15:20 UTC

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

Description babycarrot 2008-03-01 16:36:41 UTC

What were you doing when the application crashed?
reading email


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 143904768 vsize: 143904768 resident: 35274752 share: 20971520 rss: 35274752 rss_rlim: 4294967295
CPU usage: start_time: 1204387973 rtime: 983 utime: 919 stime: 64 cutime:1 cstime: 7 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 -1208727840 (LWP 5609)]
[New Thread -1305605232 (LWP 5855)]
[New Thread -1210827888 (LWP 5854)]
[New Thread -1256629360 (LWP 5634)]
[New Thread -1245734000 (LWP 5631)]
(no debugging symbols found)
0x00364402 in __kernel_vsyscall ()

+ Trace 190969

Thread 1 (Thread -1208727840 (LWP 5609))

#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/libbonoboui-2.so.0
#12 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /lib/libgobject-2.0.so.0
#14 ??
from /lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#16 g_signal_emit
from /lib/libgobject-2.0.so.0
#17 ??
from /usr/lib/libbonoboui-2.so.0
#18 ??
from /usr/lib/libbonoboui-2.so.0
#19 bonobo_ui_xml_rm
from /usr/lib/libbonoboui-2.so.0
#20 bonobo_ui_engine_xml_rm
from /usr/lib/libbonoboui-2.so.0
#21 ??
from /usr/lib/libbonoboui-2.so.0
#22 _ORBIT_skel_small_Bonobo_UIContainer_removeNode
from /usr/lib/libbonobo-2.so.0
#23 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#24 Bonobo_UIContainer_removeNode
from /usr/lib/libbonobo-2.so.0
#25 ??
from /usr/lib/libbonoboui-2.so.0
#26 bonobo_ui_component_rm
from /usr/lib/libbonoboui-2.so.0
#27 gal_view_menus_unmerge
from /usr/lib/evolution/2.10/libmenus.so.0
#28 ??
from /usr/lib/evolution/2.10/libmenus.so.0
#29 g_object_unref
from /lib/libgobject-2.0.so.0
#30 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#31 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#32 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#33 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#34 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#35 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#36 ??
from /lib/libglib-2.0.so.0
#37 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#38 ??
from /lib/libglib-2.0.so.0
#39 g_main_loop_run
from /lib/libglib-2.0.so.0
#40 bonobo_main
from /usr/lib/libbonobo-2.so.0
#41 main
#0 __kernel_vsyscall

Comment 1 Akhil Laddha 2008-03-04 15:20:19 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 433573 ***