GNOME Bugzilla – Bug 480398
crash in Tasks:
Last modified: 2007-09-26 17:42:08 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:21:43 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 644186112 vsize: 644186112 resident: 43421696 share: 31854592 rss: 43421696 rss_rlim: 18446744073709551615 CPU usage: start_time: 1190761769 rtime: 52 utime: 47 stime: 5 cutime:1 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496402576 (LWP 6641)] [New Thread 1126189392 (LWP 6703)] [New Thread 1136679248 (LWP 6699)] [New Thread 1105209680 (LWP 6678)] (no debugging symbols found) 0x000000340820d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 165489
Thread 1 (Thread 46912496402576 (LWP 6641))
----------- .xsession-errors (88949 sec old) --------------------- (evolution:11605): e-dateedit.c-WARNING **: time_text: (evolution:11605): e-dateedit.c-WARNING **: time_text: (evolution:11605): e-dateedit.c-WARNING **: time_text: (evolution:11605): GLib-GObject-WARNING **: IA__g_object_set_valist: property `width' of object class `GtkTreeViewColumn' is not writable (evolution:11605): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_changed' is invalid for instance `0x14bd400' ***MEMORY-ERROR***: evolution[11605]: GSlice: assertion failed: sinfo->n_allocated > 0 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ...Too much output, ignoring rest... --------------------------------------------------
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 431459 ***