Bug 438923 – crash in Tasks: Something in the last up...

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 438923 - crash in Tasks: Something in the last up...


Summary:	crash in Tasks: Something in the last up...


Status:	RESOLVED DUPLICATE of bug 435388

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-05-16 16:12 UTC by tauist
Modified:	2007-05-17 05:38 UTC

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

Description tauist 2007-05-16 16:12:04 UTC

What were you doing when the application crashed?
Something in the last update of this system crashes evolution everytime it starts. PLEASE fix this


Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3142.fc7 #1 SMP Mon May 7 21:07:42 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 536498176 vsize: 536498176 resident: 24170496 share: 15994880 rss: 24170496 rss_rlim: 18446744073709551615
CPU usage: start_time: 1179331854 rtime: 103 utime: 66 stime: 37 cutime:1 cstime: 5 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 46912496446384 (LWP 7232)]
[New Thread 1084229952 (LWP 7259)]
(no debugging symbols found)
0x000000331180d82f in waitpid () from /lib64/libpthread.so.0

+ Trace 134472

Thread 1 (Thread 46912496446384 (LWP 7232))

#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
#10 ??
#0 select
from /lib64/libc.so.6

Comment 1 Akhil Laddha 2007-05-17 05:38:28 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 435388 ***