Bug 517466 – crash in Tasks: syncronizing my mail

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 517466 - crash in Tasks: syncronizing my mail


Summary:	crash in Tasks: syncronizing my mail


Status:	RESOLVED DUPLICATE of bug 431396

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-19 15:47 UTC by beaudrie
Modified:	2008-02-20 06:40 UTC

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

Description beaudrie 2008-02-19 15:47:10 UTC

Version: 2.10

What were you doing when the application crashed?
syncronizing my mail


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

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 147808256 vsize: 147808256 resident: 58195968 share: 33255424 rss: 58195968 rss_rlim: 4294967295
CPU usage: start_time: 1203434589 rtime: 2526 utime: 2313 stime: 213 cutime:1 cstime: 3 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 -1208568096 (LWP 20381)]
[New Thread -1295000688 (LWP 20605)]
[New Thread -1357157488 (LWP 20604)]
[New Thread -1346667632 (LWP 20602)]
[New Thread -1226888304 (LWP 20562)]
[New Thread -1274020976 (LWP 20538)]
[New Thread -1325687920 (LWP 20518)]
[New Thread -1336177776 (LWP 20517)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 189746

Thread 1 (Thread -1208568096 (LWP 20381))

#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 ??
from /usr/lib/libbonoboui-2.so.0
#25 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#26 g_closure_invoke
from /lib/libgobject-2.0.so.0
#27 ??
from /lib/libgobject-2.0.so.0
#28 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#29 g_signal_emit
from /lib/libgobject-2.0.so.0
#30 ??
from /usr/lib/libbonoboui-2.so.0
#31 ??
from /usr/lib/libbonoboui-2.so.0
#32 bonobo_ui_xml_rm
from /usr/lib/libbonoboui-2.so.0
#33 bonobo_ui_engine_xml_rm
from /usr/lib/libbonoboui-2.so.0
#34 ??
from /usr/lib/libbonoboui-2.so.0
#35 _ORBIT_skel_small_Bonobo_UIContainer_removeNode
from /usr/lib/libbonobo-2.so.0
#36 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#37 Bonobo_UIContainer_removeNode
from /usr/lib/libbonobo-2.so.0
#38 ??
from /usr/lib/libbonoboui-2.so.0
#39 bonobo_ui_component_rm
from /usr/lib/libbonoboui-2.so.0
#40 gal_view_menus_unmerge
from /usr/lib/evolution/2.10/libmenus.so.0
#41 ??
from /usr/lib/evolution/2.10/libmenus.so.0
#42 g_object_unref
from /lib/libgobject-2.0.so.0
#43 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#44 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#45 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#46 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#47 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#48 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#49 ??
from /lib/libglib-2.0.so.0
#50 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#51 ??
from /lib/libglib-2.0.so.0
#52 g_main_loop_run
from /lib/libglib-2.0.so.0
#53 bonobo_main
from /usr/lib/libbonobo-2.so.0
#54 main
#0 __kernel_vsyscall



----------- .xsession-errors (66 sec old) ---------------------
(evolution:20381): e-utils-WARNING **: No parent set, or default parent available for error dialog
(evolution:20381): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__beaudrie@https:__mail.ad.uab.edu_'
** (evolution:20381): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:20381): DEBUG: mailto URL program: evolution
(evolution:20381): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed
(evolution:20381): camel-CRITICAL **: camel_object_meta_set: assertion `CAMEL_IS_OBJECT (obj)' failed
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3801ed1 (Sick Leave); these messages lack timestamps and therefore suck.
(evolution:20381): Gdk-CRITICAL **: gdk_window_set_title: assertion `title != NULL' failed
(evolution:20381): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
--------------------------------------------------

Comment 1 Akhil Laddha 2008-02-20 06:40:34 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 ***