GNOME Bugzilla – Bug 471205
crash in Tasks: trying to configure for ...
Last modified: 2007-09-21 18:52:35 UTC
Version: 2.10 What were you doing when the application crashed? trying to configure for connecting to exchange server 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 126910464 vsize: 126910464 resident: 45158400 share: 33251328 rss: 45158400 rss_rlim: 4294967295 CPU usage: start_time: 1188318633 rtime: 617 utime: 558 stime: 59 cutime:2 cstime: 8 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 2969)] [New Thread -1274147952 (LWP 3003)] [New Thread -1242104944 (LWP 2999)] [New Thread -1221424240 (LWP 2998)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 158591
Thread 1 (Thread -1208834336 (LWP 2969))
----------- .xsession-errors (11 sec old) --------------------- (evolution:2969): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__lgarz;auth_Basic@webmail.pdclab.com_' in group 'Passwords-Exchange' (evolution:2969): e-dateedit.c-WARNING **: time_text:09:00 AM (evolution:2969): e-dateedit.c-WARNING **: time_text:09:00 AM (evolution:2969): e-dateedit.c-WARNING **: time_text: 7:00 AM (evolution:2969): e-dateedit.c-WARNING **: time_text: 7:00 AM (evolution:2969): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:2969): e-dateedit.c-WARNING **: time_text: 7:00 AM (evolution:2969): 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 349913 ***