evolution crashed with SIGSEGV in camel_folder_sync()

[Stefan Foerster]

Binary package hint: evolution

I use a mail server (dovecot) in my home network (running on my Linksys NSLU2). I use 'evolution' as mail client on all of my machines. The mailbox is IMAP format.

On one of my notebooks I have recently upgraded from hardy heron to intrepid ibex, i.e. evolution version 2.24.1.1.

Whenever I select "Datei/Müll leeren" (file/empty trash), evolution instantly crashes without any messages. The e-mails in the trash folder don't get deleted, they survive this operation. In my preferences I have the option "delete trash on exit" checked. This also doesn't work - today I have realised that in total 1,599 e-mails had not been deleted after the upgrade to intrepid ibex.

On my wife's notebook, running hardy heron and evolution 2.22.3.1, deleting e-mails from the trash works as expected. The e-mails are in fact gone after this operation, even when I open the trash folder on my notebook with the 2.24.1.1 version of evolution.

This bug is reproducible. It was introduced in version 2.24.

Stefan Förster

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/evolution
Package: evolution 2.24.1.1-0ubuntu1
ProcCmdline: evolution --component=mail
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 camel_folder_sync ()
 ?? () from /usr/lib/libcamel-provider-1.2.so.14
Title: evolution crashed with SIGSEGV in camel_folder_sync()
Uname: Linux 2.6.27.4-20081026-686 i686
UserGroups: adm audio cdrom crontab debian-tor dhcp dialout dip everyone fax floppy fuse gdm lpadmin messagebus netdev ntp plugdev powerdev scanner ssh tape users video

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? ()
?? ()
camel_folder_refresh_info ()
?? () from /usr/lib/libcamel-provider-1.2.so.14

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.