Bug 488417 – crash in Tasks: 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 488417 - crash in Tasks: starting evolution


Summary:	crash in Tasks: starting evolution


Status:	RESOLVED DUPLICATE of bug 364700

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:	2007-10-19 20:23 UTC by fedora7
Modified:	2008-04-04 13:55 UTC

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

Description fedora7 2007-10-19 20:23:54 UTC

Version: 2.10

What were you doing when the application crashed?
starting evolution			


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 104689664 vsize: 104689664 resident: 7208960 share: 548864 rss: 7208960 rss_rlim: 4294967295
CPU usage: start_time: 1192820920 rtime: 1343 utime: 266 stime: 1077 cutime:130 cstime: 49 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 -1208861968 (LWP 2775)]
[New Thread -1219597424 (LWP 2892)]
[New Thread -1261950064 (LWP 2803)]
[New Thread -1240577136 (LWP 2801)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 171530

Thread 2 (Thread -1219597424 (LWP 2892))

#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 em_junk_sa_check_junk
from /usr/lib/evolution/2.10/plugins/liborg-gnome-sa-junk-plugin.so
#7 ??
from /usr/lib/evolution/2.10/libeutil.so.0
#8 e_plugin_invoke
from /usr/lib/evolution/2.10/libeutil.so.0
#9 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#10 camel_junk_plugin_check_junk
from /usr/lib/libcamel-1.2.so.10
#11 ??
from /usr/lib/libcamel-provider-1.2.so.10
#12 e_sexp_term_eval
from /usr/lib/libedataserver-1.2.so.9
#13 e_sexp_eval
from /usr/lib/libedataserver-1.2.so.9
#14 camel_filter_search_match
from /usr/lib/libcamel-provider-1.2.so.10
#15 camel_filter_driver_filter_message
from /usr/lib/libcamel-provider-1.2.so.10
#16 camel_filter_driver_filter_folder
from /usr/lib/libcamel-provider-1.2.so.10
#17 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#18 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#19 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#20 ??
from /lib/libglib-2.0.so.0
#21 ??
from /lib/libglib-2.0.so.0
#22 start_thread
from /lib/libpthread.so.0
#23 clone
from /lib/libc.so.6



----------- .xsession-errors ---------------------
** (nm-applet:2654): WARNING **: <WARN>  nma_dbus_init(): org.freedesktop.DBus.Error.NoServer raised:
 Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
** (nm-applet:2654): WARNING **: <WARN>  nma_dbus_init(): org.freedesktop.DBus.Error.NoServer raised:
 Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
--------------------------------------------------

Comment 1 Akhil Laddha 2008-04-04 13:55:38 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 364700 ***