evolution crashes when backup

[Pastito]

Binary package hint: evolution

When I try to make the backup into the file "evolution-backup.tar.gz", all goes fine until evolution restart and the crash panel appears and ask me if I want to recover or restart my previous session. I don't know if it is a problem of evolution or only with the recover panel.
This is the backtrace of the crash:
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) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/evolution
[Thread debugging using libthread_db enabled]
[New Thread 0xb6541740 (LWP 11366)]
[New Thread 0xb3f54b90 (LWP 11383)]
[New Thread 0xb3753b90 (LWP 11384)]
[New Thread 0xb2f52b90 (LWP 11385)]
[Thread 0xb2f52b90 (LWP 11385) exited]
[New Thread 0xb2f52b90 (LWP 11386)]
[Thread 0xb3f54b90 (LWP 11383) exited]
[New Thread 0xb3f54b90 (LWP 11387)]
[New Thread 0xb274fb90 (LWP 11388)]
[New Thread 0xb1f4db90 (LWP 11389)]
[Thread 0xb1f4db90 (LWP 11389) exited]
[Thread 0xb3753b90 (LWP 11384) exited]
[New Thread 0xb1f4db90 (LWP 11390)]
[New Thread 0xb3753b90 (LWP 11391)]
[Thread 0xb274fb90 (LWP 11388) exited]
[Thread 0xb1f4db90 (LWP 11390) exited]
[Thread 0xb3753b90 (LWP 11391) exited]
[New Thread 0xb3753b90 (LWP 11395)]
[New Thread 0xb1f4db90 (LWP 11396)]
[New Thread 0xb274fb90 (LWP 11397)]
[New Thread 0xb134db90 (LWP 11398)]
[Thread 0xb274fb90 (LWP 11397) exited]
[New Thread 0xb0b2fb90 (LWP 11399)]
[New Thread 0xb274fb90 (LWP 11400)]
[New Thread 0xb032eb90 (LWP 11401)]
[Thread 0xb0b2fb90 (LWP 11399) exited]
[Thread 0xb032eb90 (LWP 11401) exited]
[Thread 0xb274fb90 (LWP 11400) exited]
[Thread 0xb1f4db90 (LWP 11396) exited]
[Thread 0xb3753b90 (LWP 11395) exited]
[Thread 0xb134db90 (LWP 11398) exited]
[Thread 0xb3f54b90 (LWP 11387) exited]
[New Thread 0xb3f54b90 (LWP 11422)]
[New Thread 0xb134db90 (LWP 11423)]
[New Thread 0xb3753b90 (LWP 11424)]
[New Thread 0xb1f4db90 (LWP 11425)]
[New Thread 0xb0b2fb90 (LWP 11426)]
[Thread 0xb3753b90 (LWP 11424) exited]
[Thread 0xb134db90 (LWP 11423) exited]
[Thread 0xb0b2fb90 (LWP 11426) exited]
[Thread 0xb3f54b90 (LWP 11422) exited]
[New process 11366]
Executing new program: /usr/lib/evolution/2.22/evolution-backup
warning: Cannot initialize thread debugging library: generic error
warning: Cannot initialize thread debugging library: generic error
warning: Cannot initialize thread debugging library: generic error
warning: Cannot initialize thread debugging library: generic error
[New process 11366]
[Thread debugging using libthread_db enabled]
** Message: Backing up to the folder /home/eugenio/.evolution/evolution-backup.tar.gz
** Message: evolution --force-shutdown
Cerrando evolution-exchange-storage (Backend de Calendario de Exchange / Backend de libreta de direcciones de Exchange de Evolution)
Cerrando evolution-data-server-2.22 (Soporte de calendario y webcal de Evolution / Soporte de libretas de direcciones en archivo local de Evolution)
Cerrando evolution-alarm-notify (Servicio de notificación por alerta del Calendario de Evolution)
** Message: gconftool-2 --dump /apps/evolution > $HOME/.evolution/backup-restore-gconf.xml
** Message: cd $HOME && tar cf - .evolution .camel_certs | gzip > /home/eugenio/.evolution/evolution-backup.tar.gz
tar: .evolution/evolution-backup.tar.gz: el fichero cambió mientras se estaba leyendo
tar: .evolution/cache/tmp/spamd-socket-path-eS3INY: el `socket' no se tendrá en cuenta
tar: .camel_certs: No se puede stat: No existe el fichero ó directorio
tar: Salida con error demorada desde errores anteriores
** Message: evolution
RSS Plugin enabled
RSS Plugin enabled
RSS: cleaning all remaining sessions ...done

ProblemType: Bug
Architecture: i386
Date: Sun Apr 27 13:34:29 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/evolution
Package: evolution 2.22.1-0ubuntu3
PackageArchitecture: i386
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
Uname: Linux 2.6.24-16-generic i686

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, there's no stacktrace of the crash. Please follow these instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

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.

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.

[Pastito (pastito)]

Disculpa Pedro, (asumo que eres de habla hispana por el nombre y
apellido) pero en la carpeta que tu me señalas /var/crash hay nada,
ningún reporte ni nada.
Te agradecería mucho que me expliques por que puede ser esto.

Saludos,
    Eugenio.

-----Mensaje original-----
De: Pedro Villavicencio <email address hidden>
Responder a: Bug 223216 <email address hidden>
Para: <email address hidden>
Asunto: [Bug 223216] Re: evolution crashes when backup
Fecha: Mon, 28 Apr 2008 00:53:19 -0000

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, there's no stacktrace of the crash. Please
follow these instuctions to have apport report a new bug about your
crash that can be dealt with by the automatic retracer.

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.

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)
       Status: New => Invalid

--
Carpe Diem / Lo Único Constante en el Universo es el Cambio

[Fernando Luís Santos (flsantos)]

I have the same problem, but there is no crash report and the bug report option send me here.
When I do a backup evolution simply crashed a then give me the message to restart evolution after a crash, but no link to bug report.

[DrC (drcowsley)]

After a couple of Evolution-related Ubuntu updates (Hardy) this problem is still here.

The process outlined above is not totally clear to me. I ask Evolution to restart after the backup - should I run the process before I backup, when I get the option dialogue, when the crash report is showing or afterwards?

Or should I untick the restart box and go through the procedure after the backup or when I restart?

Incidentally, looking now (after using Help-Report a Problem then coming to Help-Submit Bug Report) my /var/crash is empty...

Chris

[Sebastien Bacher (seb128)]

could you try if that's still an issue in jaunty?

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[DrC (drcowsley)]

Apologies - I missed the preceding post.

I have to either build a Jaunty bx or wait until I return to work...

 I should have the answer in a day or two.

[DrC (drcowsley)]

I tried it today at school on Jaunty - no problem seen. NB this is a different single email account.

On my current (LTS) Hardy, if I backup choosing not to restart Evolution after the backup. the backup apparently does not happen, and on restart I get the "Evolution appears to have exited unexpectedly the last time........" with Ignore and Recover options. This is an old copy of my various mail accounts, which I stopped using some time ago.

If this issue with Hardy is not widely reproducible, let me know what I can do to help - but note there is still nothing in /var/crash

For information my live email is on an unsupported Feisty system - which I will probably migrate over the summer to Jaunty.

Chris

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Closing the bug as you stated upstream that the crash issue has been resolved for you. Thanks for your investigations.

[DrC (drcowsley)]

Oops - sorry. Didn't realise I was on both systems. It all seems fine now - thanks for all you guys do.

[DrC (drcowsley)]

Lucid seems good and solid. Have the developers done anything like tidying up that might have cleaned out the bug? If so, I would be comfortable closing it.