Bug 442742 – crash in Tasks: Re-sorting messages

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 442742 - crash in Tasks: Re-sorting messages


Summary:	crash in Tasks: Re-sorting messages


Status:	RESOLVED DUPLICATE of bug 431342

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-01 00:11 UTC by gsudduth
Modified:	2007-06-10 23:37 UTC

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

Description gsudduth 2007-06-01 00:11:37 UTC

What were you doing when the application crashed?
Re-sorting messages



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: Clearlooks
Icon Theme: SnowIsh-1.0

Memory status: size: 139718656 vsize: 139718656 resident: 26910720 share: 16175104 rss: 26910720 rss_rlim: 4294967295
CPU usage: start_time: 1180656597 rtime: 134 utime: 127 stime: 7 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208731936 (LWP 5941)]
[New Thread -1287083120 (LWP 5959)]
[New Thread -1253053552 (LWP 5957)]
[New Thread -1274033264 (LWP 5956)]
[New Thread -1263543408 (LWP 5955)]
[New Thread -1242563696 (LWP 5952)]
[New Thread -1230189680 (LWP 5951)]
(no debugging symbols found)
0x00121402 in __kernel_vsyscall ()

+ Trace 137114

Thread 1 (Thread -1208731936 (LWP 5941))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
#6 camel_message_info_ptr
from /usr/lib/libcamel-provider-1.2.so.10
#7 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#8 ??
from /usr/lib/evolution/2.10/libetable.so.0
#9 e_tree_model_value_at
from /usr/lib/evolution/2.10/libetable.so.0
#10 e_table_sorting_utils_tree_sort
from /usr/lib/evolution/2.10/libetable.so.0
#11 ??
from /usr/lib/evolution/2.10/libetable.so.0
#12 ??
from /usr/lib/evolution/2.10/libetable.so.0
#13 ??
from /usr/lib/evolution/2.10/libetable.so.0
#14 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /lib/libgobject-2.0.so.0
#16 ??
from /lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#18 g_signal_emit
from /lib/libgobject-2.0.so.0
#19 e_tree_model_node_changed
from /usr/lib/evolution/2.10/libetable.so.0
#20 e_tree_memory_thaw
from /usr/lib/evolution/2.10/libetable.so.0
#21 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#22 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#23 ??
from /lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#25 ??
from /lib/libglib-2.0.so.0
#26 g_main_loop_run
from /lib/libglib-2.0.so.0
#27 gtk_dialog_run
from /usr/lib/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib/libedataserverui-1.2.so.8
#29 ??
from /lib/libglib-2.0.so.0
#30 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#31 ??
from /lib/libglib-2.0.so.0
#32 g_main_loop_run
from /lib/libglib-2.0.so.0
#33 bonobo_main
from /usr/lib/libbonobo-2.so.0
#34 main
#0 __kernel_vsyscall

Comment 1 palfrey 2007-06-01 12:50:25 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 2 André Klapper 2007-06-10 23:37:39 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 431342 ***