GNOME Bugzilla – Bug 519812
crash in Tasks: switching months from Ma...
Last modified: 2008-03-06 13:12:23 UTC
Version: 2.10 What were you doing when the application crashed? switching months from March to April 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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 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: 109936640 vsize: 109936640 resident: 42213376 share: 30089216 rss: 42213376 rss_rlim: 4294967295 CPU usage: start_time: 1204408877 rtime: 1583 utime: 1502 stime: 81 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 -1208834336 (LWP 15021)] [New Thread -1219683440 (LWP 15076)] [New Thread -1252537456 (LWP 15036)] [New Thread -1240663152 (LWP 15034)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 190994
Thread 1 (Thread -1208834336 (LWP 15021))
----------- .xsession-errors (35 sec old) --------------------- (evolution:15021): e-dateedit.c-WARNING **: time_text:11:00 AM (evolution:15021): e-dateedit.c-WARNING **: time_text:11:00 AM (evolution:15021): e-dateedit.c-WARNING **: time_text:11:00 AM (evolution:15021): e-dateedit.c-WARNING **: time_text:02:00 PM (evolution:15021): e-dateedit.c-WARNING **: time_text:11:00 AM (evolution:15021): e-dateedit.c-WARNING **: time_text:02:00 PM (evolution:15021): e-dateedit.c-WARNING **: time_text:11:00 AM (evolution:15021): e-dateedit.c-WARNING **: time_text:02:00 PM --------------------------------------------------
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 ***