GNOME Bugzilla – Bug 552693
crash in Evolution Mail and Calendar:
Last modified: 2008-09-18 03:45:59 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: 93007872 vsize: 93007872 resident: 30838784 share: 19644416 rss: 30838784 rss_rlim: 4294967295 CPU usage: start_time: 1221685718 rtime: 449 utime: 408 stime: 41 cutime:3 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb6684b80 (LWP 6982)] [New Thread 0xb2fafb90 (LWP 7034)] [New Thread 0xb5b40b90 (LWP 7007)] 0xb7f7b424 in __kernel_vsyscall ()
+ Trace 206909
Thread 1 (Thread 0xb6684b80 (LWP 6982))
----------- .xsession-errors (8 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:6982): DEBUG: mailto URL command: evolution %s ** (evolution:6982): DEBUG: mailto URL program: evolution (evolution:6982): calendar-gui-CRITICAL **: e_cal_model_get_component_at: assertion `row >= 0 && row < priv->objects->len' failed (evolution:6982): 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 ***