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


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 446494

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-06-11 20:17 UTC by Daye Liu
Modified:	2007-06-12 08:23 UTC

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

Description Daye Liu 2007-06-11 20:17:40 UTC

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 164470784 vsize: 164470784 resident: 60653568 share: 32145408 rss: 60653568 rss_rlim: 4294967295
CPU usage: start_time: 1181593046 rtime: 584 utime: 364 stime: 220 cutime:32 cstime: 11 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209088288 (LWP 4767)]
[New Thread -1256989808 (LWP 4806)]
[New Thread -1338221680 (LWP 4803)]
[New Thread -1311130736 (LWP 4797)]
[New Thread -1246499952 (LWP 4787)]
(no debugging symbols found)
0x00c58402 in __kernel_vsyscall ()

+ Trace 140166

Thread 2 (Thread -1256989808 (LWP 4806))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/i686/nosegneg/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/i686/nosegneg/libpthread.so.0
#3 pthread_mutex_lock
from /lib/i686/nosegneg/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/i686/nosegneg/libpthread.so.0
#19 clone
from /lib/i686/nosegneg/libc.so.6



----------- .xsession-errors ---------------------
(evolution:4767): camel-WARNING **: Could not find key entry for word 'kkgpqsutqwvjhkluhglxnuhptqjhuv2vr': Invalid argument
(evolution:4767): camel-WARNING **: Could not find key entry for word 'kkgpqsutqwvjhkluhglxnuhptqjhuv2vs': Invalid argument
(evolution:4767): e-data-server-WARNING **: Could not open converter for 'DEFAULT' to 'UTF-8' charset
(evolution:4767): camel-WARNING **: Could not find key entry for word 'w4rt02f182982b3f87b3d31c026700': Invalid or incomplete multibyte or wide character
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x64
--------------------------------------------------

Comment 1 Mart Raudsepp 2007-06-12 08:23:30 UTC

Thanks for the bug report. 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 446494 ***