Bug 478279 – crash in Tasks: Launching Evolution with...

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 478279 - crash in Tasks: Launching Evolution with...


Summary:	crash in Tasks: Launching Evolution with...


Status:	RESOLVED DUPLICATE of bug 339602

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-09-19 07:14 UTC by james
Modified:	2007-09-29 10:57 UTC

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

Description james 2007-09-19 07:14:06 UTC

Version: 2.10

What were you doing when the application crashed?
Launching Evolution within an NX session. Set up with 1 account only. (local Maildir)


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (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 XFree86 Project, Inc
X Vendor Release: 40300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 113238016 vsize: 113238016 resident: 36765696 share: 30408704 rss: 36765696 rss_rlim: 4294967295
CPU usage: start_time: 1190185953 rtime: 93 utime: 83 stime: 10 cutime:1 cstime: 2 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 -1208871200 (LWP 27899)]
[New Thread -1272161392 (LWP 27939)]
[New Thread -1236272240 (LWP 27918)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 163931

Thread 2 (Thread -1272161392 (LWP 27939))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 ??
#5 <signal handler called>
#6 camel_index_add_name
from /usr/lib/libcamel-1.2.so.10
#7 camel_folder_summary_info_new_from_parser
from /usr/lib/libcamel-provider-1.2.so.10
#8 camel_folder_summary_add_from_parser
from /usr/lib/libcamel-provider-1.2.so.10
#9 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#10 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#11 camel_local_summary_check
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#12 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#13 camel_folder_refresh_info
from /usr/lib/libcamel-provider-1.2.so.10
#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 ??
from /lib/libglib-2.0.so.0
#18 start_thread
from /lib/libpthread.so.0
#19 clone
from /lib/libc.so.6

Comment 1 james 2007-09-26 13:25:47 UTC

The bug appears to be some sort of an issue with the XML config in ~/.evolution/mail/config/folder-tree-expand-state.xml. Once the issue occurs, evolution will crash upon every start until this file is deleted. Alternately, it seems that you can remove the empty </node> tag which appears within the XML. Having said that, I've also noticed that this tag seems to always be placed within the file, even when evolution isn't crashing.

Comment 2 Tobias Mueller 2007-09-29 10:57:17 UTC

Thanks for the bug report. 

Is this issue reproduceable for you?

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 339602 ***