GNOME Bugzilla – Bug 555822
Evolution Mail and Calendar: Evolution crashes and ex...
Last modified: 2008-10-19 17:01:19 UTC
Evolution crashes and exits abruptly upon changing status, priority, due date, or % complete of a task. To reproduce, simply change the status of a task. In my case, to reproduce, change the status from "not started" to "in progress" while in the main tasks page. Message from terminal: username@localhost:~$ evolution evolution-shell-Message: Killing old version of evolution-data-server... (evolution:30949): calendar-gui-CRITICAL **: e_cal_model_get_component_at: assertion `row >= 0 && row < priv->objects->len' failed (evolution:30949): calendar-gui-CRITICAL **: e_cal_model_copy_component_data: assertion `comp_data != NULL' failed Segmentation fault Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.3 2008-07-09 (Ubuntu) BugBuddy Version: 2.22.0
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Here's the stack trace, or at least what I hope to be the "stack trace": username@localhost:~$ gdb evolution GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread 0xb6546740 (LWP 22218)] evolution-shell-Message: Killing old version of evolution-data-server... [New Thread 0xafaf9b90 (LWP 22246)] [New Thread 0xaf0ffb90 (LWP 22247)] [New Thread 0xae8feb90 (LWP 22248)] [New Thread 0xae0fdb90 (LWP 22249)] [Thread 0xae0fdb90 (LWP 22249) exited] [Thread 0xaf0ffb90 (LWP 22247) exited] [New Thread 0xaf0ffb90 (LWP 22250)] [New Thread 0xad748b90 (LWP 22254)] [New Thread 0xae0fdb90 (LWP 22256)] [New Thread 0xad707b90 (LWP 22257)] [Thread 0xad707b90 (LWP 22257) exited] [Thread 0xae8feb90 (LWP 22248) exited] [Thread 0xae0fdb90 (LWP 22256) exited] [New Thread 0xae0fdb90 (LWP 22277)] [New Thread 0xae8feb90 (LWP 22282)] [New Thread 0xad707b90 (LWP 22286)] [New Thread 0xacd7bb90 (LWP 22291)] [Thread 0xacd7bb90 (LWP 22291) exited] [Thread 0xae0fdb90 (LWP 22277) exited] [Thread 0xad707b90 (LWP 22286) exited] [New Thread 0xad707b90 (LWP 22301)] [Thread 0xae8feb90 (LWP 22282) exited] [New Thread 0xae8feb90 (LWP 22306)] [Thread 0xafaf9b90 (LWP 22246) exited] [Thread 0xad707b90 (LWP 22301) exited] [Thread 0xae8feb90 (LWP 22306) exited] [New Thread 0xae8feb90 (LWP 22309)] [Thread 0xae8feb90 (LWP 22309) exited] [New Thread 0xae8feb90 (LWP 22313)] (evolution:22218): calendar-gui-CRITICAL **: e_cal_model_get_component_at: assertion `row >= 0 && row < priv->objects->len' failed (evolution:22218): calendar-gui-CRITICAL **: e_cal_model_copy_component_data: assertion `comp_data != NULL' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb6546740 (LWP 22218)] e_cal_menu_target_new_select (eabp=0x8465800, model=0x8401580, events=0x85f0230) at e-cal-menu.c:144 144 e-cal-menu.c: No such file or directory. in e-cal-menu.c (gdb)
can you please provide full traces. I mean start evolution in gdb and do 'thread a a bt' when it crashes.
It seems to be working just fine now... maybe within the recent updates? I dunno, but we can close this now. Thanks for your help Akhil and Andre.
Created attachment 120869 [details] The Trace of Evolution seg fault I closed this bug thinking it was fixed somehow. It's not. Here's the full trace.
Ah. That is bug 544187 and has been fixed in version 2.24.0. *** This bug has been marked as a duplicate of 544187 ***