GNOME Bugzilla – Bug 443544
crash in Email:
Last modified: 2007-06-03 16:06:49 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: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 95006720 vsize: 95006720 resident: 23580672 share: 15142912 rss: 23580672 rss_rlim: 4294967295 CPU usage: start_time: 1180877112 rtime: 69 utime: 62 stime: 7 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 -1208269088 (LWP 3032)] (no debugging symbols found) 0x00b1a402 in __kernel_vsyscall ()
+ Trace 137797
Thread 1 (Thread -1208269088 (LWP 3032))
----------- .xsession-errors --------------------- Loading "installonlyn" plugin compiz: No stencil buffer. Clipping of transformed windows is not going to be correct when screen is transformed. compiz: pixmap 0x3603e44 can't be bound to texture compiz: pixmap 0x360a563 can't be bound to texture CalDAV Eplugin starting up ... (evolution:3003): e-data-server-DEBUG: Loaded default categories (bug-buddy:3014): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject' (bug-buddy:3014): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:3014): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:3014): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed CalDAV Eplugin starting up ... --------------------------------------------------
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 ***