GNOME Bugzilla – Bug 484752
crash in Tasks: setting time preference ...
Last modified: 2007-10-09 15:19:09 UTC
Version: 2.10 What were you doing when the application crashed? setting time preference to 24 hours from 12. 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.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 165363712 vsize: 165363712 resident: 62656512 share: 49504256 rss: 62656512 rss_rlim: 4294967295 CPU usage: start_time: 1191855102 rtime: 325 utime: 296 stime: 29 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208703264 (LWP 13758)] [New Thread -1233945712 (LWP 13795)] [New Thread -1244046448 (LWP 13763)] (no debugging symbols found) 0x00fc8402 in __kernel_vsyscall ()
+ Trace 168793
Thread 1 (Thread -1208703264 (LWP 13758))
----------- .xsession-errors --------------------- (evolution:13758): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:13758): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:13758): e-dateedit.c-WARNING **: time_text: 7:00 PM (evolution:13758): e-dateedit.c-WARNING **: time_text:09:00 AM (evolution:13758): e-dateedit.c-WARNING **: time_text: 7:00 PM (evolution:13758): e-dateedit.c-WARNING **: time_text: 7:00 PM (evolution:13758): e-dateedit.c-WARNING **: time_text:09:00 AM (evolution:13758): e-dateedit.c-WARNING **: time_text:09: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 426807 ***