GNOME Bugzilla – Bug 324102
Evolution crashes on start if http free/busy publishing is set
Last modified: 2008-02-29 20:33:10 UTC
Version details: 2.4.2.1 Distribution/Version: Mandriva Cooker 1. Set up http publishing for free/busy information. 2. Publish Free/Busy (works) 3. Exit evolution 4. Restart (crashes) The crash dialog normally reports that evolution crashes, occasionally it mentions e-d-s. Using gconf-editor to unset /apps/evolution/calendar/publish/uri will allow evolution to run successfully again. Following the steps above is completely reproducible. I'll attach a back trace and the publish/%gconf.xml evolution-data-server-1.4.2.1-2mdk evolution-pilot-2.4.2.1-1mdk libsoup-2.2_8-2.2.7-1mdk libevolution-data-server6-1.4.2.1-2mdk evolution-2.4.2.1-1mdk libsoup-2.2_7-2.2.3-2mdk evolution-webcal-2.4.1-1mdk evolution-debug-2.4.2.1-1mdk libglib2.0_0-2.8.4-1mdk glib2.0-debug-2.8.4-1mdk
Created attachment 55995 [details] Compressed back trace
Created attachment 55996 [details] .gconf/apps/evolution/calendar/publish/%gconf.xml
confirming, same problem here under Gentoo same evolution version 2.4.2.1
Could this bug be verified in evolution 2.6 or anything beyond evolution 2.6. I have tested this feature in evolution 2.6.0 and did not observe this crash.
so, can anyone reproduce this with evo 2.6.x or 2.8.x?
yes I set up calendar publishing after restarting evolution whenever I want to edit the publishing properties, evolution crash GLib-ERROR **: gmem.c:135: failed to allocate 1399830849 bytes aborting... ================================================================= Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= Stacktrace: Native stacktrace: /usr/lib/libmono.so.0(mono_handle_native_sigsegv+0x104) [0xb79f0514] /usr/lib/libmono.so.0 [0xb79aa487] [0xffffe440] /lib/libc.so.6(abort+0x100) [0x4a00ac80] /usr/lib/libglib-2.0.so.0(g_log+0) [0x4a27dbd0] Aborted
hmm, that stacktrace is not useful :-/
sorry I don't have a stracktrace but here's the steps to reproduce the crash 1. go to calendar publishing option 2. add new location 3. choose calendar sources 4. on publishing location choose custom location (I put http://icalx.com/public/maxima/) 5. click ok 6. now edit the entry we've just created 7. click ok (notice the location uri now is changed) 8. click edit again 9. evolution crash
This bug is not reproducible in evolution 2.6.3 and 2.8.x
I've just upgraded my evolution 2.8.1 and I am not able to reproduce the crash anymore. However I still cannot make evolution to publish to icalx.com.
Hi Arif, please file a new bug if this is still an issue for you. Closing as OBSOLETE due to comment #10.