GNOME Bugzilla – Bug 514770
crash in Tasks:
Last modified: 2008-02-08 04:24:52 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.23.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 128401408 vsize: 128401408 resident: 46657536 share: 35512320 rss: 46657536 rss_rlim: 4294967295 CPU usage: start_time: 1202306358 rtime: 630 utime: 589 stime: 41 cutime:0 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 -1208568096 (LWP 20038)] [New Thread -1250956400 (LWP 21111)] [New Thread -1272329328 (LWP 20442)] [New Thread -1228694640 (LWP 20423)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188298
Thread 2 (Thread -1250956400 (LWP 21111))
----------- .xsession-errors (971 sec old) --------------------- (evolution:20038): libglade-WARNING **: unknown property `width_chars' for class `GtkImage' (evolution:20038): libglade-WARNING **: unknown property `single_line_mode' for class `GtkImage' (evolution:20038): libglade-WARNING **: unknown property `angle' for class `GtkImage' (evolution:20038): e-dateedit.c-WARNING **: time_text:03:35 PM (evolution:20038): e-dateedit.c-WARNING **: time_text:03:35 PM (evolution:20038): e-dateedit.c-WARNING **: time_text:11:30 AM (evolution:20038): e-dateedit.c-WARNING **: time_text:12:00 PM (evolution:20038): e-dateedit.c-WARNING **: time_text:11:30 AM --------------------------------------------------
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 445309 ***