GNOME Bugzilla – Bug 460874
crash in Calendar: 随意点击了一封邮件
Last modified: 2007-07-29 23:08:07 UTC
What were you doing when the application crashed? 随意点击了一封邮件 Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000001 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 191893504 vsize: 191893504 resident: 55021568 share: 26693632 rss: 55021568 rss_rlim: 4294967295 CPU usage: start_time: 1185524145 rtime: 1476 utime: 1339 stime: 137 cutime:39 cstime: 8 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 -1208584480 (LWP 4174)] [New Thread -1252000880 (LWP 5125)] [New Thread -1351279728 (LWP 5124)] [New Thread -1274037360 (LWP 4205)] [New Thread -1344361584 (LWP 4204)] [New Thread -1263547504 (LWP 4197)] (no debugging symbols found) 0x00a82402 in __kernel_vsyscall ()
+ Trace 150895
Thread 1 (Thread -1208584480 (LWP 4174))
----------- .xsession-errors (35 sec old) --------------------- (evolution:4174): camel-WARNING **: Could not find key entry for word '继续整理httpd部分的文档': 成功 (evolution:4174): camel-WARNING **: Could not find key entry for word '0x21800000': 无效或不完整的多字节字符或宽字符 (evolution:4174): camel-WARNING **: Could not find key entry for word '6月份的日常开支': 无效或不完整的多字节字符或宽字符 (evolution:4174): camel-WARNING **: Could not find key entry for word '在下一层合成一个函数': 无效或不完整的多字节字符或宽字符 (evolution:4174): camel-WARNING **: Could not find key entry for word '并且上传到了服务器上': 无效或不完整的多字节字符或宽字符 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 433922 ***