Red Hat Bugzilla – Bug 470654
beagle daemon crashes while querying evolution-data-server
Last modified: 2008-12-21 10:46:28 EST
Created attachment 322942 [details]
Description of problem:
If the data source EvolutionDataServer is enabled, beagled crashs within minutes.
Version-Release number of selected component (if applicable):
$ rpm -q beagle evolution-data-server mono-core mono-addins evolution-sharp gnome-desktop-sharp gnome-sharp gtk-sharp2
Steps to Reproduce:
1. Enable the EvolutionDataServer data source in beagle-settings
2. Start the beagle daemon
3. Wait some minutes
beagled crashes with an unhandled exception
Does this still happen with evolution-sharp-0.18.1 (http://koji.fedoraproject.org/koji/buildinfo?buildID=68735) (it should have a fix for this)
OK, seems like gtk-sharp > 2.12.5 is required too
From evolution-sharp's changelog:
"Fix for BG0 #555242. This would need r117424 of gtk-sharp
or gtk-sharp > 2.12.5." (bug in BGO is the same issue)
Xavier, can we have this patch backported to our package?
updated to 2.12.5.
let me know if you get into trouble with this new release.
I have been testing with with evolution-sharp-0.18.1-1 and gtk-sharp2-2.12.5-1 today. The good news are that beagled does not crash anymore. The bad news are that it is throwing an exception. Please take a look at the attached logs.
P.S. gtk-sharp2-2.12.5-1 is only built for F11 yet
Created attachment 322998 [details]
beagle is throwing an exception, log 1
Created attachment 322999 [details]
beagle is throwing an exception, log 2
Never mind the last logs. I think I should have rebooted before restarting beagled.
After a reboot beagled crashes in the same way as without the updated *-sharp packages. Does beagle need a rebuild with the new libs?
Which libs ?
(In reply to comment #8)
> Which libs ?
evolution-sharp-0.18.1-1 and gtk-sharp2-2.12.5-1 ... I guessed those are libs, you may call them bindings or something like that. Whatever.
hmm...beagles should already rebuilt against new gtk-sharp2 libs 2.12.
However, try a rebuild and give your tries.
You can also check that from koji or by doing a repoquery on beagles.
Yes, beagle is already built against the gtk-sharp2 2.12 libs and of course a rebuild did not help...
To sum up: nothing has changed with the evolution-sharp and gtk-sharp2 updates installed. The beagle daemon crashs if the e-d-s data source is enabled.
duplicate of bug 435049 ?
(In reply to comment #12)
> duplicate of bug 435049 ?
I don't think so. I can't reproduce bug 435049 in rawhide and even with the e-d-s backend I don't get that "double free or corruption" error mentioned there. Notice that we have evolution-sharp 0.18 in rawhide where bug 435049 should be already fixed.
(In reply to comment #3)
> updated to 2.12.5.
> let me know if you get into trouble with this new release.
This wont help we need > 2.12.5 (patch got into trunk after the release).
"This would need *r117424* of gtk-sharp or gtk-sharp *>* 2.12.5."
I just built myself an updated gtk-sharp 2.12.6 RPM and it helps. After installing it and rebooting beagled actually does not crash anymore.
=> Xavier, could you please update gtk-sharp2 to version 2.12.6?
=> You should consider getting evolution-sharp-0.18.1 and gtk-sharp2-2.12.6 into dist-f10 as the e-d-s backend is enabled by default and beagle won't really work. I am not sure if the updates have any side effects. But I could not find any problems with tomboy and f-spot so far.
there is no 2.12.16 release yet at mono source repo.
i'll check that patch and add it to release 2.12.5, otherwise if you have any good link where i can find this fresh release outside of mono main website, that would be great.
(In reply to comment #16)
> there is no 2.12.16 release yet at mono source repo.
> i'll check that patch and add it to release 2.12.5, otherwise if you have any
> good link where i can find this fresh release outside of mono main website,
> that would be great.
I downloaded it from
which redirects me to
However, i can't build the release yet due to broken dependency issue.
will try on f10 within an hours.
At least the F10 builds should not make that much trouble. For me it was just taking your 2.12.5 SRPM and a quick and dirty changing of the version and the source tar.bz2. Building with rawhide's current mock and its fedora-rawhide-[x86_64|i386] profiles went without hassle.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Gtk-sharp2 2.12.6 seems to build for dist-f11 now. I tried a scratch build in Koji:
Could you please update the F-10 and devel branches, so that this bug can be closed?
This bug is fixed in https://admin.fedoraproject.org/updates/gtk-sharp2-2.12.7-1.fc10.1