Bug 471003 – crash in Evolution: Starting Evolution

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 471003 - crash in Evolution: Starting Evolution


Summary:	crash in Evolution: Starting Evolution


Status:	RESOLVED DUPLICATE of bug 339602

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-28 07:30 UTC by roger
Modified:	2007-10-07 19:07 UTC

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

Description roger 2007-08-28 07:30:16 UTC

Version: 2.12.x

What were you doing when the application crashed?
Starting Evolution


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.2 2007-08-15 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-suspend2-r1Y #13 SMP PREEMPT Sun Aug 26 19:29:41 PDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 89907200 vsize: 89907200 resident: 38191104 share: 25378816 rss: 38191104 rss_rlim: 4294967295
CPU usage: start_time: 1188286144 rtime: 211 utime: 181 stime: 30 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.12'

(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 -1247562016 (LWP 12112)]
[New Thread -1283441776 (LWP 12123)]
[New Thread -1272845424 (LWP 12122)]
[New Thread -1264415856 (LWP 12120)]
0xb7fb2410 in __kernel_vsyscall ()

+ Trace 158421

Thread 3 (Thread -1272845424 (LWP 12122))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_49
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 ??
#5 ??
#6 _dl_runtime_resolve
from /lib/ld-linux.so.2
#7 ??
from /usr/lib/libcamel-provider-1.2.so.10
#8 ??
#9 ??
#10 ??
#11 <signal handler called>
#12 camel_index_add_name
from /usr/lib/libcamel-1.2.so.10
#13 ??
#14 ??
#15 ??
#16 camel_folder_summary_info_new_from_parser
from /usr/lib/libcamel-provider-1.2.so.10
#17 ??



----------- .xsession-errors (10 sec old) ---------------------
bbdb: Synchronizing buddy list to contacts...
bbdb: Done syncing buddy list to contacts.
CalDAV Eplugin starting up ...
** (evolution-2.12:10429): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution-2.12:10429): DEBUG: mailto URL program: evolution
Generating profiling data in `eprofile.10429'
camel-Message: ++
(evolution-2.12:10429): e-data-server-WARNING **: Could not open converter for '_iso-2022-jp$ESC' to 'UTF-8' charset
Loading Spamassasin as the default junk plugin
No running windows found
CalDAV Eplugin starting up ...
** (evolution-2.12:12112): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution-2.12:12112): DEBUG: mailto URL program: evolution
Generating profiling data in `eprofile.12112'
--------------------------------------------------

Comment 1 Tobias Mueller 2007-10-07 19:07:56 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 339602 ***