GNOME Bugzilla – Bug 482070
crash in Tasks:
Last modified: 2007-10-01 13:50:53 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 146989056 vsize: 146989056 resident: 46948352 share: 31088640 rss: 46948352 rss_rlim: 4294967295 CPU usage: start_time: 1191220841 rtime: 400 utime: 365 stime: 35 cutime:0 cstime: 2 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 -1208379680 (LWP 30785)] [New Thread -1247806576 (LWP 30806)] [New Thread -1235854448 (LWP 30805)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 166762
Thread 1 (Thread -1208379680 (LWP 30785))
----------- .xsession-errors --------------------- (bug-buddy:30764): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject' (bug-buddy:30764): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:30764): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:30764): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed CalDAV Eplugin starting up ... ** (evolution:30785): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:30785): DEBUG: mailto URL program: evolution (evolution:30785): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:30785): camel-WARNING **: camel_exception_get_id called with NULL parameter. --------------------------------------------------
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 364700 ***