GNOME Bugzilla – Bug 456508
crash in Tasks: I'm working with email c...
Last modified: 2007-07-17 19:10:31 UTC
Version: 2.10 What were you doing when the application crashed? I'm working with email client on Exchange connectors Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 161914880 vsize: 161914880 resident: 66621440 share: 44716032 rss: 66621440 rss_rlim: 4294967295 CPU usage: start_time: 1184315994 rtime: 1934 utime: 1759 stime: 175 cutime:3 cstime: 7 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 -1208858912 (LWP 3661)] [New Thread -1394041968 (LWP 3939)] [New Thread -1329714288 (LWP 3938)] [New Thread -1255150704 (LWP 3867)] [New Thread -1373062256 (LWP 3814)] [New Thread -1362572400 (LWP 3813)] (no debugging symbols found) 0x00648402 in __kernel_vsyscall ()
+ Trace 147715
Thread 1 (Thread -1208858912 (LWP 3661))
----------- .xsession-errors (78 sec old) --------------------- ** Message: Unsetting for Birthdays & Anniversaries ** Message: Unsetting for Calendario ** Message: Setting for Calendario (evolution:3661): e-dateedit.c-WARNING **: time_text:17:00 (evolution:3661): e-dateedit.c-WARNING **: time_text:17:00 (evolution:3661): e-dateedit.c-WARNING **: time_text:18:00 (evolution:3661): e-dateedit.c-WARNING **: time_text:09:00 (evolution:3661): e-dateedit.c-WARNING **: time_text:18:00 (evolution:3661): e-dateedit.c-WARNING **: time_text:18:00 --------------------------------------------------
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 433922 ***