Bug 446806 – crash in Tasks: writing a simple 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 446806 - crash in Tasks: writing a simple email (...


Summary:	crash in Tasks: writing a simple email (...


Status:	RESOLVED DUPLICATE of bug 438756

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-06-12 17:11 UTC by boaz88
Modified:	2007-06-13 11:53 UTC

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

Description boaz88 2007-06-12 17:11:29 UTC

What were you doing when the application crashed?
writing a simple email (via gmail)


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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 564711424 vsize: 564711424 resident: 25997312 share: 17108992 rss: 25997312 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181667567 rtime: 53 utime: 46 stime: 7 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496488032 (LWP 15733)]
[New Thread 1084229968 (LWP 15770)]
[New Thread 1178638672 (LWP 15761)]
(no debugging symbols found)
0x000000342ae0d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 140399

Thread 1 (Thread 46912496488032 (LWP 15733))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
#4 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#5 e_table_sorting_utils_tree_sort
from /usr/lib64/evolution/2.10/libetable.so.0
#6 ??
from /usr/lib64/evolution/2.10/libetable.so.0
#7 ??
from /usr/lib64/evolution/2.10/libetable.so.0
#8 ??
from /usr/lib64/evolution/2.10/libetable.so.0
#9 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#10 ??
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#12 g_signal_emit
from /lib64/libgobject-2.0.so.0
#13 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#14 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#15 ??
from /lib64/libglib-2.0.so.0
#16 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#17 ??
from /lib64/libglib-2.0.so.0
#18 g_main_loop_run
from /lib64/libglib-2.0.so.0
#19 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#20 main
#0 waitpid
from /lib64/libpthread.so.0
#13 ??
#0 poll
from /lib64/libc.so.6

Comment 1 André Klapper 2007-06-13 11:53:47 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 438756 ***