From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.3)
Description of problem:
When attempting to paste from the clipboard into a new email being
typed in - evolution crashes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start kde
2. Start evolution
3. Start a new message
4. Start kterm
5. run ls and mark some text
6. In the new message window of evolution click the middle mouse button
Actual Results: Evolution crashes
Expected Results: Should paste test text
I am running evolution under KDE not Gaim
Further investigation shows that it doesn't happen with all clipboard
I am yet to find a pattern, maybe you need to do a code review to see
if that comes up with something.
It may be that it crashes if the pasted text includes HTML.
Please can you attach a backtrace to this bug; for more information on
how to do this, see this link:
(please install the evolution-debuginfo and the gtkhtml3-debuginfo
Created attachment 107612 [details]
Thanks. Did you get as far as step 6 above before gdb stopped
evolution? Please can you try doing this again, but type the
following into gdb before you type "run":
(gdb) handle SIG33 nostop
Created attachment 107649 [details]
Stack trace 2
I fired up as you said and double clicked on the link to bring up this page so
that I could reply. As I did that, evolution died again. I hope this trace
helps - notuce the intersting assertion failures against mime-type - though
those may be red herrings.
Same problem with SIGINT this time:
Program received signal SIGINT, Interrupt.
The stack trace still isn't usable.
Closing per lack of response to previous request for information.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.