Bug 462698 – crash in Tasks: TRying to send 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 462698 - crash in Tasks: TRying to send mail


Summary:	crash in Tasks: TRying to send mail


Status:	RESOLVED DUPLICATE of bug 426807

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:	2007-08-02 06:42 UTC by noeljambo
Modified:	2007-08-02 20:55 UTC

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

Description noeljambo 2007-08-02 06:42:13 UTC

Version: 2.10

What were you doing when the application crashed?
TRying to send 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.20-2925.11.fc7xen #1 SMP Mon Jun 11 16:21:08 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: 164765696 vsize: 164765696 resident: 63488000 share: 43679744 rss: 63488000 rss_rlim: 4294967295
CPU usage: start_time: 1186035441 rtime: 2102 utime: 1512 stime: 590 cutime:8 cstime: 24 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208224032 (LWP 3980)]
[New Thread -1284633712 (LWP 4164)]
[New Thread -1246663792 (LWP 4032)]
[New Thread -1257546864 (LWP 4031)]
(no debugging symbols found)
0x00c59402 in __kernel_vsyscall ()

+ Trace 152254

Thread 1 (Thread -1208224032 (LWP 3980))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/nosegneg/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 ??
from /usr/lib/libpango-1.0.so.0
#11 ??
from /usr/lib/libpango-1.0.so.0
#12 g_object_unref
from /lib/libgobject-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /lib/libgobject-2.0.so.0
#17 ??
from /lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#19 g_signal_emit
from /lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib/libgtk-x11-2.0.so.0
#25 ??
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#27 ??
from /usr/lib/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_widget_unparent
from /usr/lib/libgtk-x11-2.0.so.0
#36 ??
from /usr/lib/libgtk-x11-2.0.so.0
#37 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#38 ??
from /lib/libgobject-2.0.so.0
#39 g_closure_invoke
from /lib/libgobject-2.0.so.0
#40 ??
from /lib/libgobject-2.0.so.0
#41 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#42 g_signal_emit
from /lib/libgobject-2.0.so.0
#43 gtk_container_remove
from /usr/lib/libgtk-x11-2.0.so.0
#44 ??
from /usr/lib/libgtk-x11-2.0.so.0
#45 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#46 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#47 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#48 ??
from /usr/lib/evolution/2.10/libeutil.so.0
#49 ??
from /usr/lib/evolution/2.10/libeutil.so.0
#50 ??
from /lib/libglib-2.0.so.0
#51 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#52 ??
from /lib/libglib-2.0.so.0
#53 g_main_loop_run
from /lib/libglib-2.0.so.0
#54 bonobo_main
from /usr/lib/libbonobo-2.so.0
#55 main
#0 __kernel_vsyscall



----------- .xsession-errors (52 sec old) ---------------------
(evolution:3980): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9102120'
(evolution:3980): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9102240'
(evolution:3980): 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?)
(evolution:3980): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9102480'
(evolution:3980): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x91025a0'
(evolution:3980): 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?)
(evolution:3980): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x91027e0'
(evolution:3980): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9102900'
--------------------------------------------------

Comment 1 Susana 2007-08-02 20:55:50 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 426807 ***