GNOME Bugzilla – Bug 446493
crash in Tasks:
Last modified: 2007-06-15 15:55:34 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: 163872768 vsize: 163872768 resident: 60203008 share: 32133120 rss: 60203008 rss_rlim: 4294967295 CPU usage: start_time: 1181592992 rtime: 529 utime: 334 stime: 195 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 -1208330528 (LWP 4646)] [New Thread -1256232048 (LWP 4685)] [New Thread -1296868464 (LWP 4682)] [New Thread -1310844016 (LWP 4675)] [New Thread -1245742192 (LWP 4665)] (no debugging symbols found) 0x003c2402 in __kernel_vsyscall ()
+ Trace 140164
Thread 2 (Thread -1256232048 (LWP 4685))
----------- .xsession-errors --------------------- (evolution:4646): camel-WARNING **: Could not find key entry for word 'kkgpqsutqwvjhkluhglxnuhptqjhuv2vs': Invalid argument (evolution:4646): e-data-server-WARNING **: Could not open converter for 'DEFAULT' to 'UTF-8' charset (evolution:4646): e-data-server-WARNING **: Could not open converter for '{THEBAT_ENG_CHARSET}' to 'UTF-8' charset (evolution:4646): e-data-server-WARNING **: Could not open converter for '{THEBAT_ENG_CHARSET}' to 'UTF-8' charset (evolution:4646): e-data-server-WARNING **: Could not open converter for '{THEBAT_ENG_CHARSET}' to 'UTF-8' charset X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x64 --------------------------------------------------
*** Bug 446494 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
same crash as bug 447044 which has a better stacktrace
*** This bug has been marked as a duplicate of 447044 ***