GNOME Bugzilla – Bug 496884
crash in Tasks:
Last modified: 2007-11-16 00:26:57 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 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: 128548864 vsize: 128548864 resident: 40148992 share: 31043584 rss: 40148992 rss_rlim: 4294967295 CPU usage: start_time: 1195080269 rtime: 119 utime: 101 stime: 18 cutime:1 cstime: 1 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 -1208584480 (LWP 3876)] [New Thread -1247810672 (LWP 3896)] [New Thread -1225188464 (LWP 3893)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 177754
Thread 1 (Thread -1208584480 (LWP 3876))
----------- .xsession-errors --------------------- error getting update info: Cannot find a valid baseurl for repo: fedora CalDAV Eplugin starting up ... ** (evolution:3832): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3832): DEBUG: mailto URL program: evolution (bug-buddy:3864): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject' (bug-buddy:3864): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:3864): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:3864): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed CalDAV Eplugin starting up ... ** (evolution:3876): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3876): DEBUG: mailto URL program: evolution --------------------------------------------------
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 ***