GNOME Bugzilla – Bug 466899
crash in Tasks: calendar and alarm prefe...
Last modified: 2007-09-21 13:19:57 UTC
Version: 2.10 What were you doing when the application crashed? calendar and alarm preferences 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:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Phlat-BlueDubbed Icon Theme: Gion Memory status: size: 306200576 vsize: 306200576 resident: 99803136 share: 76279808 rss: 99803136 rss_rlim: 4294967295 CPU usage: start_time: 1187168733 rtime: 3428 utime: 3006 stime: 422 cutime:92 cstime: 153 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 -1208825104 (LWP 2975)] [New Thread -1284011120 (LWP 3392)] [New Thread -1304990832 (LWP 3029)] [New Thread -1294500976 (LWP 3002)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 155352
Thread 1 (Thread -1208825104 (LWP 2975))
----------- .xsession-errors (63 sec old) --------------------- (evolution:2975): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:2975): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:2975): e-dateedit.c-WARNING **: time_text: 7:00 AM (evolution:2975): e-dateedit.c-WARNING **: time_text:09:00 AM (evolution:2975): e-dateedit.c-WARNING **: time_text: 7:00 AM (evolution:2975): e-dateedit.c-WARNING **: time_text:06:00 AM (evolution:2975): e-dateedit.c-WARNING **: time_text: 7:00 AM (evolution:2975): e-dateedit.c-WARNING **: time_text: 7:00 AM --------------------------------------------------
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 436128 ***