Bug 484599 – 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 484599 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 339602

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
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-10-08 05:41 UTC by victor.kupsamy
Modified:	2007-10-08 20:47 UTC

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

Description victor.kupsamy 2007-10-08 05:41:43 UTC

Version: 2.10

What were you doing when the application crashed?



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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 166813696 vsize: 166813696 resident: 59981824 share: 41046016 rss: 59981824 rss_rlim: 4294967295
CPU usage: start_time: 1191821834 rtime: 1240 utime: 1098 stime: 142 cutime:0 cstime: 0 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 -1208195360 (LWP 2361)]
[New Thread -1319777392 (LWP 2375)]
[New Thread -1305019504 (LWP 2372)]
[New Thread -1247810672 (LWP 2367)]
[New Thread -1224914032 (LWP 2364)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 168682

Thread 3 (Thread -1305019504 (LWP 2372))

#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:2361): camel-WARNING **: Could not find key entry for word 'mtt10jrcpabukhrl3osqiyzh96d7abatpcjp': Success
(evolution:2361): camel-WARNING **: Could not find key entry for word '0mdfy1k8dwvnspsgqminqprvrbqc53lj6ud': Success
(evolution:2361): camel-WARNING **: Could not find key entry for word 'syub0jv6bmhor0f0tr29wjtgdkvwre5a': Success
(evolution:2361): e-data-server-WARNING **: Could not open converter for 'unicode-1-1-utf-7' to 'UTF-8' charset
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x50
--------------------------------------------------

Comment 1 Tobias Mueller 2007-10-08 20:47:32 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 ***