GNOME Bugzilla – Bug 492253
crash in Calendar: 双击鼠标左键打开邮件附件图片
Last modified: 2007-11-02 02:38:28 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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 191471616 vsize: 191471616 resident: 69038080 share: 43569152 rss: 69038080 rss_rlim: 4294967295 CPU usage: start_time: 1193879253 rtime: 3003 utime: 2727 stime: 276 cutime:83 cstime: 4 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 -1208236320 (LWP 3188)] [New Thread -1293530224 (LWP 4842)] [New Thread -1231541360 (LWP 3518)] [New Thread -1315320944 (LWP 3348)] [New Thread -1242031216 (LWP 3331)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 174280
Thread 1 (Thread -1208236320 (LWP 3188))
----------- .xsession-errors (1059 sec old) --------------------- new dimensions = (48,48) initial setting of an image. no scaling scale = 1 new dimensions = (48,48) we need to scale up scale = 1 DEBUG: Inbox/wks (mbox:/home/allan/.evolution/mail/local#Inbox/wks) DEBUG: Inbox/wks/nick (mbox:/home/allan/.evolution/mail/local#Inbox/wks/nick) DEBUG: Inbox/wks/gavin (mbox:/home/allan/.evolution/mail/local#Inbox/wks/gavin) (evolution:3188): camel-WARNING **: Could not find key entry for word 'irir1150pbf30poppopoppoѩr': 没有那个文件或目录 (evolution:3188): camel-WARNING **: Could not find key entry for word 'irirfr9024npbf100stephenritaʿ': 没有那个文件或目录 --------------------------------------------------
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 467763 ***