Evolution segfaults when creating a new Task or Memo on Karmic RC

[Steve Mottram]

Binary package hint: evolution

When creating a new Task or Memo in Evolution on Karmic RC, as soon as the Task or memo is saved, Evolution segfaults. For some reason I'm not able to catch the crash in Apport, but the Syslog reports:

ct 27 11:10:26 stvwolx056 kernel: [ 8035.575572] evolution[3639]: segfault at 4 ip 008f0797 sp bfb3311c error 4 in libical.so.0.43.0[8b4000+4f000]

If I restart Evolution, the saved Task or Memo is present, so the crash appears to be triggered by some action that Evolution performs immediately after saving.

This has been happening repeatably for me since updates on 26th October.

In case it is useful, I have attached the contents of an apport log created using "apport-cli -f -p evolution", which doesn't include the crash details, but at least shows environment and library information.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Steve Mottram (steve-d-mottram)]

Hi,

I have re-enabled apport as recommended and generated a .crash file. However
apport is unable to submit the file and automatically open a new bug because
it can't get through the authenticating web proxy at our site. I don't have
any control over the proxy and cannot bypass it. Can I manually attach the
.crash file to this bug?

Steve

2009/10/27 Pedro Villavicencio <email address hidden>

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. However, your crash report is either missing or
> challenging to deal with as a ".crash" file. Please follow these
> instructions to have apport report a new bug about your crash that can
> be dealt with by the automatic retracer.
>
> If you are running the Ubuntu Stable Release you might need to enable
> apport in /etc/default/apport and restart.
>
> If you are using Ubuntu with the Gnome desktop environment - launch
> nautilus and navigate to your /var/crash directory and double click on the
> crash report you wish to submit.
> If you are using Kubuntu or Xubuntu you can file the crash using
> /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash
> in a terminal - where _my_crash_report.crash is the crash you would like to
> report.
>
> I'm closing this bug report since the process outlined above will
> automatically open a new bug report which can then dealt with more
> efficiently. Thanks in advance for your cooperation and understanding.
>
> ** Changed in: evolution (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: evolution (Ubuntu)
> Status: New => Invalid
>
> --
> Evolution segfaults when creating a new Task or Memo on Karmic RC
> https://bugs.launchpad.net/bugs/461843
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Richard Senior (sanhozay)]

Hi,

I've got the same problem as Steve. I've been able to submit the crash report using apport as requested.

I note that the problem only occurs if tasks and notes are added directly in the list view in Evolution. If the "New" button is used, tasks and notes don't cause a crash.

[Richard Senior (sanhozay)]

I've just run an update using karmic-proposed updates and the problem has been fixed. That was quick. Well done! ;)