GNOME Bugzilla – Bug 445817
crash in Email:
Last modified: 2007-06-12 00:56:46 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:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 547794944 vsize: 547794944 resident: 25624576 share: 15196160 rss: 25624576 rss_rlim: 18446744073709551615 CPU usage: start_time: 1181410968 rtime: 61 utime: 54 stime: 7 cutime:1 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496385632 (LWP 3980)] [New Thread 1094719824 (LWP 4003)] [New Thread 1084229968 (LWP 4002)] (no debugging symbols found) 0x00000034eda0d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 139618
Thread 1 (Thread 46912496385632 (LWP 3980))
----------- .xsession-errors --------------------- Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". CalDAV Eplugin starting up ... (evolution:3980): camel-WARNING **: Cannot load summary file: `/home/punk/.evolution/mail/local/Outbox.ev-summary': Нет такого файла или каталога Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". --------------------------------------------------
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 425129 ***