Bug 478220 – crash in Tasks: checking 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 478220 - crash in Tasks: checking mail


Summary:	crash in Tasks: checking mail


Status:	RESOLVED DUPLICATE of bug 440388

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-19 00:09 UTC by lancephillips
Modified:	2007-10-07 18:31 UTC

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

Description lancephillips 2007-09-19 00:09:32 UTC

Version: 2.10

What were you doing when the application crashed?
checking mail


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 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: 149377024 vsize: 149377024 resident: 55193600 share: 40665088 rss: 55193600 rss_rlim: 4294967295
CPU usage: start_time: 1190159727 rtime: 1279 utime: 1214 stime: 65 cutime:44 cstime: 21 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 -1208351008 (LWP 26345)]
[New Thread -1307280496 (LWP 26525)]
[New Thread -1242432624 (LWP 26523)]
[New Thread -1263547504 (LWP 26472)]
[New Thread -1285227632 (LWP 26392)]
[New Thread -1253057648 (LWP 26385)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 163882

Thread 1 (Thread -1208351008 (LWP 26345))

#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_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 pango_attr_list_unref
from /usr/lib/libpango-1.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_object_unref
from /lib/libgobject-2.0.so.0
#13 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#14 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#20 ??
from /lib/libgobject-2.0.so.0
#21 g_closure_invoke
from /lib/libgobject-2.0.so.0
#22 ??
from /lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#24 g_signal_emit
from /lib/libgobject-2.0.so.0
#25 ??
from /usr/lib/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib/libgtk-x11-2.0.so.0
#27 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#28 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib/libgtk-x11-2.0.so.0
#34 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#35 ??
from /lib/libgobject-2.0.so.0
#36 g_closure_invoke
from /lib/libgobject-2.0.so.0
#37 ??
from /lib/libgobject-2.0.so.0
#38 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#39 g_signal_emit
from /lib/libgobject-2.0.so.0
#40 ??
from /usr/lib/libgtk-x11-2.0.so.0
#41 ??
from /usr/lib/libgtk-x11-2.0.so.0
#42 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#43 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#44 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#45 ??
from /usr/lib/libgtk-x11-2.0.so.0
#46 ??
from /usr/lib/libgtk-x11-2.0.so.0
#47 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#48 ??
from /usr/lib/libgtk-x11-2.0.so.0
#49 ??
from /usr/lib/libgtk-x11-2.0.so.0
#50 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#51 ??
from /lib/libgobject-2.0.so.0
#52 g_closure_invoke
from /lib/libgobject-2.0.so.0
#53 ??
from /lib/libgobject-2.0.so.0
#54 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#55 g_signal_emit
from /lib/libgobject-2.0.so.0
#56 ??
from /usr/lib/libgtk-x11-2.0.so.0
#57 ??
from /usr/lib/libgtk-x11-2.0.so.0
#58 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#59 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#60 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#61 ??
from /usr/lib/libgtk-x11-2.0.so.0
#62 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#63 ??
from /usr/lib/libgtk-x11-2.0.so.0
#64 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#65 ??
from /lib/libgobject-2.0.so.0
#66 g_closure_invoke
from /lib/libgobject-2.0.so.0
#67 ??
from /lib/libgobject-2.0.so.0
#68 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#69 g_signal_emit
from /lib/libgobject-2.0.so.0
#70 ??
from /usr/lib/libgtk-x11-2.0.so.0
#71 ??
from /usr/lib/libgtk-x11-2.0.so.0
#72 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#73 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#74 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#75 ??
from /usr/lib/libgtk-x11-2.0.so.0
#76 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#77 ??
from /usr/lib/libgtk-x11-2.0.so.0
#78 ??
from /usr/lib/libgtk-x11-2.0.so.0
#79 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#80 ??
from /lib/libgobject-2.0.so.0
#81 g_closure_invoke
from /lib/libgobject-2.0.so.0
#82 ??
from /lib/libgobject-2.0.so.0
#83 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#84 g_signal_emit
from /lib/libgobject-2.0.so.0
#85 ??
from /usr/lib/libgtk-x11-2.0.so.0
#86 ??
from /usr/lib/libgtk-x11-2.0.so.0
#87 ??
from /usr/lib/libgtk-x11-2.0.so.0
#88 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#89 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#90 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#91 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#92 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#93 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#94 ??
from /lib/libglib-2.0.so.0
#95 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#96 ??
from /lib/libglib-2.0.so.0
#97 g_main_loop_run
from /lib/libglib-2.0.so.0
#98 bonobo_main
from /usr/lib/libbonobo-2.so.0
#99 main
#0 __kernel_vsyscall



----------- .xsession-errors (53 sec old) ---------------------
** Message: <info>  Deactivating the current VPN connection.
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:26345): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:26345): DEBUG: mailto URL program: evolution
(evolution:26345): 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...
(evolution:26345): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8f7c008'
(evolution:26345): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8f7c128'
(evolution:26345): e-data-server-DEBUG: Loading categories from "/home/Lance/.evolution/categories.xml"
(evolution:26345): e-data-server-DEBUG: Loaded 29 categories
--------------------------------------------------

Comment 1 Suman Manjunath 2007-09-23 13:57:43 UTC

is this a dupe of bug #440388 ?

Comment 2 Tobias Mueller 2007-10-07 18:31:24 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 440388 ***