Bug 514950 – crash in Tasks: nada

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


Summary:	crash in Tasks: nada


Status:	RESOLVED DUPLICATE of bug 339602

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.10.x (obsolete)
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-07 11:12 UTC by lcarlos
Modified:	2008-02-08 13:56 UTC

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

Description lcarlos 2008-02-07 11:12:06 UTC

Version: 2.10

What were you doing when the application crashed?
nada


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.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 148893696 vsize: 148893696 resident: 45158400 share: 32718848 rss: 45158400 rss_rlim: 4294967295
CPU usage: start_time: 1202382693 rtime: 769 utime: 332 stime: 437 cutime:61 cstime: 13 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 -1208219936 (LWP 2856)]
[New Thread -1299260528 (LWP 2880)]
[New Thread -1250956400 (LWP 2866)]
[New Thread -1261446256 (LWP 2864)]
[New Thread -1228403824 (LWP 2860)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 188391

Thread 2 (Thread -1299260528 (LWP 2880))

#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



----------- .xsession-errors ---------------------
(evolution:2799): camel-WARNING **: Could not find key entry for word 'gem': Multibyte ou caracter largo inválido
CalDAV Eplugin starting up ...
** (evolution:2856): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2856): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:2856): e-data-server-WARNING **: Could not open converter for 'charset=us-ascii' to 'UTF-8' charset
(evolution:2856): camel-WARNING **: Could not find key entry for word 'gem': Multibyte ou caracter largo inválido
(evolution:2856): camel-WARNING **: Could not find key entry for word 'gem': Multibyte ou caracter largo inválido
--------------------------------------------------

Comment 1 Tobias Mueller 2008-02-08 13:56: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 339602 ***