Bug 508403 – crash in Tasks: Sendin an 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 508403 - crash in Tasks: Sendin an Email


Summary:	crash in Tasks: Sendin an Email


Status:	RESOLVED DUPLICATE of bug 449996

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-01-09 23:49 UTC by e1337life
Modified:	2008-02-05 08:34 UTC

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

Description e1337life 2008-01-09 23:49:16 UTC

What were you doing when the application crashed?
Sendin an 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: Permissive
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: stylish

Memory status: size: 132743168 vsize: 132743168 resident: 41619456 share: 24199168 rss: 41619456 rss_rlim: 4294967295
CPU usage: start_time: 1199921258 rtime: 2086 utime: 1890 stime: 196 cutime:1 cstime: 4 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 -1209100576 (LWP 3025)]
[New Thread -1314079856 (LWP 3453)]
[New Thread -1271313520 (LWP 3449)]
[New Thread -1219851376 (LWP 3164)]
[New Thread -1303590000 (LWP 3162)]
[New Thread -1230087280 (LWP 3048)]
(no debugging symbols found)
0x00476402 in __kernel_vsyscall ()

+ Trace 184729

Thread 1 (Thread -1209100576 (LWP 3025))

#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 ??
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 ??
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_container_forall
from /usr/lib/libgtk-x11-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 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_widget_unparent
from /usr/lib/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib/libgtk-x11-2.0.so.0
#32 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#33 ??
from /lib/libgobject-2.0.so.0
#34 g_closure_invoke
from /lib/libgobject-2.0.so.0
#35 ??
from /lib/libgobject-2.0.so.0
#36 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#37 g_signal_emit
from /lib/libgobject-2.0.so.0
#38 gtk_container_remove
from /usr/lib/libgtk-x11-2.0.so.0
#39 ??
from /usr/lib/libgtk-x11-2.0.so.0
#40 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#41 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#42 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib/evolution/2.10/libeutil.so.0
#44 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#45 g_closure_invoke
from /lib/libgobject-2.0.so.0
#46 ??
from /lib/libgobject-2.0.so.0
#47 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#48 g_signal_emit
from /lib/libgobject-2.0.so.0
#49 ??
from /usr/lib/libgtk-x11-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 /lib/libgobject-2.0.so.0
#53 g_closure_invoke
from /lib/libgobject-2.0.so.0
#54 ??
from /lib/libgobject-2.0.so.0
#55 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#56 g_signal_emit
from /lib/libgobject-2.0.so.0
#57 ??
from /usr/lib/libgtk-x11-2.0.so.0
#58 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#59 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#60 ??
from /usr/lib/libgdk-x11-2.0.so.0
#61 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#62 ??
from /lib/libglib-2.0.so.0
#63 g_main_loop_run
from /lib/libglib-2.0.so.0
#64 bonobo_main
from /usr/lib/libbonobo-2.so.0
#65 main
#0 __kernel_vsyscall



----------- .xsession-errors (1331 sec old) ---------------------
[00000348] cdda access error: cannot read sector 1651
[00000348] cdda access error: could not read block 1652 from disc
[00000348] cdda access error: cannot read sector 1652
[00000348] cdda access error: could not read block 1653 from disc
[00000348] cdda access error: cannot read sector 1653
[00000348] cdda access error: could not read block 1654 from disc
[00000348] cdda access error: cannot read sector 1654
[00000348] cdda access error: could not read block 1655 from disc
[00000348] cdda access error: cannot read sector 1655
[00000348] cdda access error: could not read block 1656 from disc
[00000348] cdda access error: cannot read sector 1656
[00000348] cdda access error: could not read block 1657 from disc
[00000348] cdda access error: cannot read sector 1657
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2008-02-05 08:34:17 UTC

Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.

*** This bug has been marked as a duplicate of 449996 ***