GNOME Bugzilla – Bug 498898
crash in Tasks:
Last modified: 2007-11-23 04:52:20 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 203468800 vsize: 203468800 resident: 74002432 share: 44363776 rss: 74002432 rss_rlim: 4294967295 CPU usage: start_time: 1195698714 rtime: 11958 utime: 10695 stime: 1263 cutime:43 cstime: 80 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208379680 (LWP 3357)] [New Thread -1259906160 (LWP 3555)] [New Thread -1299784816 (LWP 3411)] [New Thread -1238529136 (LWP 3381)] (no debugging symbols found) 0x00cc8402 in __kernel_vsyscall ()
+ Trace 179202
Thread 1 (Thread -1208379680 (LWP 3357))
----------- .xsession-errors (23 sec old) --------------------- (evolution:3357): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2b2930(0xa4c5450) (evolution:3357): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2b2930(0xa4c5450) (evolution:3357): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2b2930(0xa4c5450) GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized (evolution:3357): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2b2930(0x9ab8428) GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 458322 ***