Evolution crashed after sending an email with a link (https)

We noticed that some of the sentences in this bug report are not in English. If they were translated in English they would be more understandable to triagers. Could you please translate them?

Oh, sorry.

Evolution crashed entirely after sending an email with a link (https) of Launchpad. My email server is Gmail. I had to kill the process of this application.

Thank you for taking the time to report this bug (and to translate it, hopefully I got it correct for the bug title) and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

I could not make the Evolution crash again, even sending emails with links randomly. Even so, I will report the details of backtrace (but do not know if I did correctly).

----------------------------------------------------------------------------------------------------------------------------------------------------------

GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2
Copyright (C) 2010 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 "i686-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Lendo símbolos de /usr/bin/evolution...Lendo símbolos de /usr/lib/debug/usr/bin/evolution...concluído.
concluído.
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) handle SIG33 pass nostop noprintset pagination 0
(gdb) run
Starting program: /usr/bin/evolution
[Thread debugging using libthread_db enabled]
[New Thread 0xb7caab70 (LWP 2577)]
[New Thread 0xb495cb70 (LWP 2578)]
[New Thread 0xb415bb70 (LWP 2579)]
[New Thread 0xb3954b70 (LWP 2580)]
[New Thread 0xb2fffb70 (LWP 2581)]
[New Thread 0xb27feb70 (LWP 2582)]
[New Thread 0xb1ffdb70 (LWP 2583)]

(evolution:2574): GLib-GObject-CRITICAL **: Object class EMFolderTree doesn't implement property 'paste-target-list' from interface 'ESelectable'

(evolution:2574): GLib-GObject-CRITICAL **: Object class EMFolderTree doesn't implement property 'copy-target-list' from interface 'ESelectable'
[Thread 0xb1ffdb70 (LWP 2583) exited]
[New Thread 0xb1ffdb70 (LWP 2585)]
[New Thread 0xad699b70 (LWP 2586)]
[New Thread 0xace98b70 (LWP 2587)]
[Thread 0xace98b70 (LWP 2587) exited]
[New Thread 0xace98b70 (LWP 2588)]
[Thread 0xb3954b70 (LWP 2580) exited]
[New Thread 0xb3954b70 (LWP 2592)]
[New Thread 0xac696b70 (LWP 2593)]
[New Thread 0xabe95b70 (LWP 2594)]
[Thread 0xabe95b70 (LWP 2594) exited]
[New Thread 0xabe95b70 (LWP 2596)]
[Thread 0xabe95b70 (LWP 2596) exited]
[New Thread 0xabe95b70 (LWP 2597)]
[Thread 0xabe95b70 (LWP 2597) exited]
[New Thread 0xabe95b70 (LWP 2598)]
[Thread 0xb3954b70 (LWP 2592) exited]
[Thread 0xad699b70 (LWP 2586) exited]
[Thread 0xac696b70 (LWP 2593) exited]
[Thread 0xabe95b70 (LWP 2598) exited]
[New Thread 0xabe95b70 (LWP 2599)]
[Thread 0xace98b70 (LWP 2588) exited]
[Thread 0xabe95b70 (LWP 2599) exited]
[New Thread 0xabe95b70 (LWP 2606)]
[New Thread 0xace98b70 (LWP 2607)]
[Thread 0xace98b70 (LWP 2607) exited]
[New Thread 0xace98b70 (LWP 2608)]
[Thread 0xabe95b70 (LWP 2606) exited]
[New Thread 0xabe95b70 (LWP 2609)]
[New Thread 0xac696b70 (LWP 2610)]
[Thread 0xac696b70 (LWP 2610) exited]
[New Thread 0xac696b70 (LWP 2611)]
[Thread 0xac696b70 (LWP 2611) exited]
[New Thread 0xac696b70 (LWP 2612)]
[Thread 0xac696b70 (LWP 2612) exited]
[New Thread 0xac696b70 (LWP 2613)]
[Thread 0xac696...

Thank you for your backtrace, unfortuately it is not very usefull when the application did not crash.
So I guess we'll have to wait for another crash.

To help you get the backtrace properly you could enable apport. For more information see https://wiki.kubuntu.org/Apport#How to enable apport
As your crash it not reproducable, it might be convient to keep apport enabled until the crash occurred again (instead of enabling it once), so editing /etc/default/apport seems your best option at the moment.

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.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

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.