GNOME Bugzilla – Bug 485122
crash in Tasks: Viewing email
Last modified: 2007-10-09 18:04:16 UTC
Version: 2.10 What were you doing when the application crashed? Viewing email 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Fedora Memory status: size: 141950976 vsize: 141950976 resident: 49795072 share: 37154816 rss: 49795072 rss_rlim: 4294967295 CPU usage: start_time: 1191949686 rtime: 482 utime: 438 stime: 44 cutime:37 cstime: 12 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 -1208363296 (LWP 4116)] [New Thread -1278768240 (LWP 4204)] [New Thread -1332290672 (LWP 4203)] [New Thread -1299747952 (LWP 4147)] [New Thread -1233400944 (LWP 4123)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 169068
Thread 1 (Thread -1208363296 (LWP 4116))
----------- .xsession-errors (66 sec old) --------------------- (evolution:4116): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:4116): e-dateedit.c-WARNING **: time_text: 6:00 AM (evolution:4116): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:4116): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:4116): e-dateedit.c-WARNING **: time_text: 6:00 PM (evolution:4116): e-dateedit.c-WARNING **: time_text: 6:00 AM (evolution:4116): e-dateedit.c-WARNING **: time_text: 6:00 PM (evolution:4116): e-dateedit.c-WARNING **: time_text: 6: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 444866 ***