GNOME Bugzilla – Bug 483161
crash in Tasks:
Last modified: 2007-10-12 13:16: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.7-85.fc7 #1 SMP Fri Sep 21 19:53:05 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 224702464 vsize: 224702464 resident: 96231424 share: 44576768 rss: 96231424 rss_rlim: 4294967295 CPU usage: start_time: 1191437923 rtime: 41817 utime: 29686 stime: 12131 cutime:34 cstime: 39 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 -1208215840 (LWP 1197)] [New Thread -1236464752 (LWP 1291)] [New Thread -1250952304 (LWP 1273)] [New Thread -1259345008 (LWP 1216)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167559
Thread 1 (Thread -1208215840 (LWP 1197))
----------- .xsession-errors --------------------- Done. (evolution:1197): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkPaned' (evolution:1197): Gtk-CRITICAL **: gtk_paned_get_position: assertion `GTK_IS_PANED (paned)' failed (evolution:1197): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkPaned' (evolution:1197): Gtk-CRITICAL **: gtk_paned_set_position: assertion `GTK_IS_PANED (paned)' failed ** Message: Response 1 (evolution:1197): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ETableModel' (evolution:1197): e-table-CRITICAL **: e_table_model_pre_change: assertion `E_IS_TABLE_MODEL (e_table_model)' failed --------------------------------------------------
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 387143 ***