Bug 518692 – crash in Tasks:

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 518692 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 447591

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-25 20:04 UTC by Jon Day
Modified:	2008-02-26 13:14 UTC

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

Description Jon Day 2008-02-25 20:04:09 UTC

Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 129777664 vsize: 129777664 resident: 58294272 share: 33054720 rss: 58294272 rss_rlim: 4294967295
CPU usage: start_time: 1203969025 rtime: 757 utime: 694 stime: 63 cutime:31 cstime: 8 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 -1208523040 (LWP 7021)]
[New Thread -1221121136 (LWP 7096)]
[New Thread -1285575792 (LWP 7045)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 190434

Thread 1 (Thread -1208523040 (LWP 7021))

#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 /usr/lib/evolution/2.10/libetable.so.0
#6 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#7 e_tree_table_adapter_save_expanded_state
from /usr/lib/evolution/2.10/libetable.so.0
#8 e_tree_save_expanded_state
from /usr/lib/evolution/2.10/libetable.so.0
#9 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#10 message_list_set_folder
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#11 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#12 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#13 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#14 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#15 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#16 ??
from /lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#18 ??
from /lib/libglib-2.0.so.0
#19 g_main_loop_run
from /lib/libglib-2.0.so.0
#20 bonobo_main
from /usr/lib/libbonobo-2.so.0
#21 main
#0 __kernel_vsyscall



----------- .xsession-errors (31226 sec old) ---------------------
Resolving a931.v12924a.c12924.g.vm.akamaistream.net for AF_INET...
Connecting to server a931.v12924a.c12924.g.vm.akamaistream.net[72.246.97.71]: 1755...
Connected
file object, packet length = 1444 (1444)
unknown object
unknown object
unknown object
stream object, stream ID: 1
stream object, stream ID: 2
unknown object
data object
mmst packet_length = 1444
Cache size set to 64 KBytes

Cache fill:  0.00% (0 bytes)   
Cache fill:  0.00% (0 bytes)   
Cache fill:  0.00% (0 bytes)   
Cache fill:  0.00% (0 bytes)   
Cache fill:  0.00% (0 bytes)   
Cache fill:  0.00% (0 bytes)   
Cache f
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Tobias Mueller 2008-02-26 13:14:00 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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