GNOME Bugzilla – Bug 564135
crash in Evolution Mail and Calendar:
Last modified: 2008-12-12 11:43:42 UTC
What were you doing when the application crashed? 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: 143392768 vsize: 143392768 resident: 39931904 share: 22609920 rss: 39931904 rss_rlim: 18446744073709551615 CPU usage: start_time: 1229012206 rtime: 372 utime: 344 stime: 28 cutime:3 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 0xb808f980 (LWP 4084)] [New Thread 0xb4fd6b90 (LWP 4176)] [New Thread 0xb7d8db90 (LWP 4109)] 0x00110416 in __kernel_vsyscall ()
+ Trace 210705
Thread 1 (Thread 0xb808f980 (LWP 4084))
----------- .xsession-errors (14 sec old) --------------------- (evolution:4084): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4084): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4084): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4084): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4084): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4084): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4084): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:4084): 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 ***