First I open evolution to a date on which I already have an appointment scheduled. Either via the Clock (calendar) applet on my toolbar, or the command that invokes, "evolution calendar:///?startdate=20100923T040000Z", or other appointment days I've opened where it eventually crashes as well.
Then I copy from within the appointment. I can select all and copy, or highlight one letter and copy, or whatever. It doesn't matter what field - summary, location, both will eventually crash it.
So then I close the appointment out, then close evolution out.
Boom! Segmentation fault.
When I do it in gdb, I get the same stacktrace as is attached here.
I can reproduce this at will.
First I open evolution to a date on which I already have an appointment scheduled. Either via the Clock (calendar) applet on my toolbar, or the command that invokes, "evolution calendar: ///?startdate= 20100923T040000 Z", or other appointment days I've opened where it eventually crashes as well.
Then I copy from within the appointment. I can select all and copy, or highlight one letter and copy, or whatever. It doesn't matter what field - summary, location, both will eventually crash it.
So then I close the appointment out, then close evolution out.
Boom! Segmentation fault.
When I do it in gdb, I get the same stacktrace as is attached here.