Description of problem: Whenever I start up Beagle it will idle for a bit then bomb out with a logged message that: 20070624 23:54:04.2711 32131 Beagle ERROR EX: System.MissingMethodException: Method not found: 'Evolution.CalUtil.FreeGlueCompGLibSList'. Version-Release number of selected component (if applicable): beagle-0.2.17-1.fc8 How reproducible: 100% Steps to Reproduce: 1. Start beagle 2. wait Actual results: exception thrown Expected results: indexing joy Additional info:
Created attachment 157725 [details] Beagle log
Created attachment 157726 [details] Beagle Exception log
I see that this bug is reported for 64bit platform, so does beagle work ok in 32bit rawhide? ps. how do I continue using rawhide. I had rawhide installed (Fedora 7 test 4) but once Fedora 7 came out it switched it self to official fedora 7 repositories. What do I need to do in order to get "rawhide" version of Fedora and test these bugs under 32bit?
I think this was reported upstream too. This appears to be an evolution-sharp problem -- they removed API without bumping up the interface number. It can be worked around (for now) by patching out the call to "CalUtil.FreeGlueCompGLibSList (IntPtr.Zero)" in beagled/EvolutionDataServerQueryable.cs:ConnectToEDS(). Now to give the evo-sharp maintainer a tongue lashing about APIs and interface numbers...
Upstream bug is http://bugzilla.gnome.org/show_bug.cgi?id=452494
I have updated Fedora test 4 to latest rawhide and beagle works just fine. Check out the screenshot. I do get an strange output from beagle-info but it works just fine. $ beagle-info --daemon-version ***MEMORY-WARNING***: /usr/lib/beagle/Info.exe[3290]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon... Daemon version: 0.2.17
Created attachment 158477 [details] screenshot of beagle on Fedora rawhide desktop running ok. screenshot of beagle on Fedora rawhide desktop running ok.
Our good friend, the wonderful beer-worthy Joe Shaw provided a patch to workaround this API.. refinement. Could we please apply this to an upcoming build of Beagle so we might start testing it again in the hopes of avoiding another last minute disabling. http://bugzilla.gnome.org/attachment.cgi?id=93599&action=view
beagle-0.2.18-1.fc8 fixes this, closing