Bug 447328 – crash in Tasks: I had just booted to Lin...

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 447328 - crash in Tasks: I had just booted to Lin...


Summary:	crash in Tasks: I had just booted to Lin...


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-13 21:38 UTC by Paul-Erik Törrönen
Modified:	2007-06-14 11:36 UTC

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

Description Paul-Erik Törrönen 2007-06-13 21:38:05 UTC

What were you doing when the application crashed?
I had just booted to Linux, logged on, accepted to apply the updates and started Evolution.


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: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 680935424 vsize: 680935424 resident: 31715328 share: 17719296 rss: 31715328 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181770571 rtime: 86 utime: 74 stime: 12 cutime:0 cstime: 0 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 46912496463456 (LWP 3507)]
[New Thread 1147435344 (LWP 3560)]
[New Thread 1136945488 (LWP 3521)]
[New Thread 1126455632 (LWP 3520)]
[New Thread 1105209680 (LWP 3517)]
[New Thread 1094719824 (LWP 3516)]
(no debugging symbols found)
0x000000398060d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 140782

Thread 1 (Thread 46912496463456 (LWP 3507))

#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



----------- .xsession-errors ---------------------
(evolution:3507): camel-imap-provider-WARNING **: Unkown summary version
(evolution:3507): camel-imap-provider-WARNING **: Unkown summary version
(evolution:3507): camel-imap-provider-WARNING **: Unkown summary version
(evolution:3507): camel-imap-provider-WARNING **: Unkown summary version
(evolution:3507): camel-imap-provider-WARNING **: Unkown summary version
--------------------------------------------------

Comment 1 André Klapper 2007-06-14 11:36:43 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 ***