GNOME Bugzilla – Bug 564140
crash in Evolution Mail and Calendar: Changing my configuratio...
Last modified: 2009-01-14 14:48:35 UTC
What were you doing when the application crashed? Changing my configuration, Distribution: Fedora release 10 (Cambridge) Gnome Release: 2.24.2 2008-11-25 (Red Hat, Inc) BugBuddy Version: 2.24.2 System: Linux 2.6.27.7-134.fc10.i686 #1 SMP Mon Dec 1 22:42:50 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 143503360 vsize: 143503360 resident: 40235008 share: 22757376 rss: 40235008 rss_rlim: 18446744073709551615 CPU usage: start_time: 1229012296 rtime: 588 utime: 535 stime: 53 cutime:2 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb7ed3980 (LWP 4198)] [New Thread 0xb39feb90 (LWP 4378)] [New Thread 0xb4fa7b90 (LWP 4376)] [New Thread 0xb7bd1b90 (LWP 4224)] 0x00110416 in __kernel_vsyscall ()
+ Trace 210706
Thread 1 (Thread 0xb7ed3980 (LWP 4198))
----------- .xsession-errors --------------------- (evolution:4198): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4198): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4198): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4198): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4198): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4198): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4198): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4198): e-data-server-CRITICAL **: e_account_set_string: assertion `ea != NULL' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 552583 ***
*** Bug 567726 has been marked as a duplicate of this bug. ***