GNOME Bugzilla – Bug 516394
crash in Tasks: Pressed the 'Today' butt...
Last modified: 2008-03-06 13:11:38 UTC
Version: 2.10 What were you doing when the application crashed? Pressed the 'Today' button in calendar 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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 363999232 vsize: 363999232 resident: 167526400 share: 88662016 rss: 167526400 rss_rlim: 4294967295 CPU usage: start_time: 1202981410 rtime: 4040 utime: 3382 stime: 658 cutime:0 cstime: 0 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 -1209157920 (LWP 2728)] [New Thread -1372972144 (LWP 2996)] [New Thread -1308623984 (LWP 2739)] [New Thread -1274803312 (LWP 2733)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 189156
Thread 1 (Thread -1209157920 (LWP 2728))
----------- .xsession-errors (29 sec old) --------------------- (evolution:2728): libglade-WARNING **: unknown property `width_chars' for class `GtkImage' (evolution:2728): libglade-WARNING **: unknown property `single_line_mode' for class `GtkImage' (evolution:2728): libglade-WARNING **: unknown property `angle' for class `GtkImage' (evolution:2728): e-dateedit.c-WARNING **: time_text:10:47 (evolution:2728): e-dateedit.c-WARNING **: time_text:10:47 (evolution:2728): e-dateedit.c-WARNING **: time_text:19:30 (evolution:2728): e-dateedit.c-WARNING **: time_text:21:30 (evolution:2728): e-dateedit.c-WARNING **: time_text:19:30 --------------------------------------------------
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 451144 ***