I'll start with this here.
Consitent crash when I switch to the calendar component in Evolution. EDS
crashes completely. Backtrace and output from EDS attached. I tried removing
my weather calendar after seeing this crash and still got the same thing, so it
seems to be something else.
Let me know if you want me to push this upstream.
Created attachment 122494 [details]
Backtrace and Output during crash
Oh yeah, FYI, saw this is 2.5.2 and now seeing it in 2.5.3.
Created attachment 122495 [details]
More Backtrace, after removing weather calendar
Looks like this one was a little better. Seems like maybe it has something to
do with remote calendars.
Created attachment 122497 [details]
Last One, another crash with just one webcal
I removed all my remote calendars (webcal/weather cal) and all worked fine.
Couled NOT add a weather calendar or remote calendar through evolution. Went
to the web and let evolution-webcal add a remote webcal and then restarted and
got this crash immediately. Something seems to be broken with webcals. Not
sure if its the Red Hat compile or if its Evolution in general. I un-checked
and checked the plugins and that didn't seem to help. Is Fedora up to the
correct libsoup version? Maybe that's the problem??
Thanks for this bug report, and the great debug information.
Looks like a g_free of a bogus pointer inside e_cal_backend_http_get_object (
possibly the comp string?)
I'm seeing a similar problem in bug 176370, though that's with a free of a comp
string in a different place (weather backend)
We probably should push this upstream...
I did try reproduce this on latest evolution 2.11.2 and evolution-data-server
1.11.2 and could not reproduce with one public webcal
I also saw couple of bugs upstream about crash in webcal, (search term "webcal
crash"), unfortunately many of them were closed because could not been reproduced.
Ryan, could you try to reproduce this bug on latest version of evolution,
please? And if it will be still there and your webcal is not private, could you
send here a link on it so we could try to fix it? Thanks.
As this is from about 3 versions of evolution ago, I woudl just close this :)
Closing per reporter's recommendation and inability to reproduce the problem
with the latest releases.