GNOME Bugzilla – Bug 443046
crash in Email: I clicked on send buttom...
Last modified: 2007-06-02 01:07:11 UTC
What were you doing when the application crashed? I clicked on send buttom on the image in firefox 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: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 106790912 vsize: 106790912 resident: 23474176 share: 15015936 rss: 23474176 rss_rlim: 4294967295 CPU usage: start_time: 1180733285 rtime: 137 utime: 116 stime: 21 cutime:0 cstime: 0 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 -1208617248 (LWP 22121)] (no debugging symbols found) 0x00675402 in __kernel_vsyscall ()
+ Trace 137362
Thread 1 (Thread -1208617248 (LWP 22121))
----------- .xsession-errors (164 sec old) --------------------- (file-roller:17136): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:17136): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:17136): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:17136): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:17136): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:17136): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:17136): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (nautilus:2724): libgnomevfs-WARNING **: gnome-vfs-monitor.c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It is --------------------------------------------------
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 ***