GNOME Bugzilla – Bug 552787
crash in Evolution Mail and Calendar:
Last modified: 2008-09-19 10:37:48 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Thu Aug 28 12:00:54 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 93085696 vsize: 93085696 resident: 31817728 share: 20869120 rss: 31817728 rss_rlim: 4294967295 CPU usage: start_time: 1221750672 rtime: 836 utime: 769 stime: 67 cutime:4 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb6620b80 (LWP 4961)] [New Thread 0xb3904b90 (LWP 5024)] [New Thread 0xb5adcb90 (LWP 4990)] 0xb7f17424 in __kernel_vsyscall ()
+ Trace 206942
Thread 1 (Thread 0xb6620b80 (LWP 4961))
----------- .xsession-errors (13 sec old) --------------------- (epiphany-browser:3849): GLib-GObject-WARNING **: value "((GaProtocol) 2)" of type `GaProtocol' is invalid or out of range for property `flags' of type `GaProtocol' CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:4282): DEBUG: mailto URL command: evolution %s ** (evolution:4282): DEBUG: mailto URL program: evolution (firefox-bin:3174): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:4961): DEBUG: mailto URL command: evolution %s ** (evolution:4961): DEBUG: mailto URL program: evolution (evolution:4961): calendar-gui-CRITICAL **: e_cal_model_get_component_at: assertion `row >= 0 && row < priv->objects->len' failed (evolution:4961): calendar-gui-CRITICAL **: e_cal_model_copy_component_data: assertion `comp_data != 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 544187 ***