hey,
I installed F12 beta in a virtual machine and as a long time banshee use of course installed and tried banshee. It always crashed some seconds after startup with an error which seems to be connected to a bug in glibc. See https://bugzilla.redhat.com/show_bug.cgi?id=526132#c6
I noticed there's a new mono-zeroconf release out which contains a Avahi DBus backend. Maybe we can use this to workaround the bug? The updated package can be found here: http://palango.fedorapeople.org/zeroconf/ koji build is here: http://koji.fedoraproject.org/koji/taskinfo?taskID=1762918
What do you think?
best regards, Paul
Hi Paul,
Paul Lange wrote:
I installed F12 beta in a virtual machine and as a long time banshee use of course installed and tried banshee. It always crashed some seconds after startup with an error which seems to be connected to a bug in glibc. See https://bugzilla.redhat.com/show_bug.cgi?id=526132#c6
I noticed there's a new mono-zeroconf release out which contains a Avahi DBus backend. Maybe we can use this to workaround the bug? The updated package can be found here: http://palango.fedorapeople.org/zeroconf/ koji build is here: http://koji.fedoraproject.org/koji/taskinfo?taskID=1762918
What do you think?
Yeah, this could work!
Most likely we can get an intermediate fix faster than waiting for an glibc update. ;-)
I've tried you package I got it working after some changes:
The AvahiDBus provider of mono-zeroconf works good. I got the complete setup with mt-daapd running on a different server working!
However, unfortunately mono-zeroconf's internal DefaultProvider is Bonjour (they just search some directories for the providers and for whatever reason Bonjour is the first in their final provider list).
Unfortunately, the Bonjour support doesn't work, because the mapping of the library in /usr/lib/mono-zeroconf/Mono.Zeroconf.Providers.Bonjour.dll.config seems to be incorrect - I couldn't find "libnss_mdns-2.so" in F12. I've tried to use "libnss_mdns.so.2" as a substitute, but the Bonjour Plugin didn't work so far...
So we have two options: - get the bonjour support working in mono-zeroconf [1] or - remove the bonjour support so that solely the AvahiDBus provider is in the mono-zeroconf package
Somehow I tend to the 2nd option since it has less dependencies. ;-)
Best regards, Christian
p.s.: [1] It is always a little bit surprising for the user, if a mono library requires a *.so file. In general, the *.so links are intended for development of the libraries and so they are located in the -devel package. I suggest we do the following: - map to the SONAME of the library (usually lib*.so.x) in *.config - require the package which provides the library in the respective mono-package
On Thu, Oct 22, 2009 at 2:43 PM, Christian Krause chkr@fedoraproject.org wrote:
So we have two options:
- get the bonjour support working in mono-zeroconf [1]
or
- remove the bonjour support so that solely the AvahiDBus provider is in
the mono-zeroconf package
Somehow I tend to the 2nd option since it has less dependencies. ;-)
Considering our Bonjour is actually Avahi's compatibility interface anyway, and not the real thing, I'd say that solely using avahi (once it's fixed) and AvahiDBus would be much safer.
Regards,
On Thu, Oct 22, 2009 at 6:33 PM, Michel Alexandre Salim michael.silvanus@gmail.com wrote:
On Thu, Oct 22, 2009 at 2:43 PM, Christian Krause chkr@fedoraproject.org wrote:
So we have two options:
- get the bonjour support working in mono-zeroconf [1]
or
- remove the bonjour support so that solely the AvahiDBus provider is in
the mono-zeroconf package
Somehow I tend to the 2nd option since it has less dependencies. ;-)
Considering our Bonjour is actually Avahi's compatibility interface anyway, and not the real thing, I'd say that solely using avahi (once it's fixed) and AvahiDBus would be much safer.
OK, an update: - mono-zeroconf's AvahiDBus provider uses a bundled copy of ndesk-dbus, that Aaron Brockover patched a few months after the latest stable release - there has been no ndesk-dbus release since (and SUSE actually ships an older version than we do!) - I've backported Aaron's changes, and they seem to be safe (F-spot still works).
I'm currently chain-building an ndesk-dbus/zeroconf/banshee update for Rawhide (F-13); if nothing breaks I'll build them for F-12 and try and get them manually pushed. A bit annoying as we are dealing with three packages here...
Hi Michel,
Michel Alexandre Salim wrote:
OK, an update:
- mono-zeroconf's AvahiDBus provider uses a bundled copy of ndesk-dbus, that Aaron Brockover patched a few months after the latest stable release
- there has been no ndesk-dbus release since (and SUSE actually ships an older version than we do!)
- I've backported Aaron's changes, and they seem to be safe (F-spot
still works).
I'm currently chain-building an ndesk-dbus/zeroconf/banshee update for Rawhide (F-13); if nothing breaks I'll build them for F-12 and try and get them manually pushed. A bit annoying as we are dealing with three packages here...
I've tried your packages in a fully updated F12 (still rawhide) system and they work so far without any problems.
Since more and more bug reports about the banshee crash are coming in it would be good to get the new builds into F12.
ndesk-dbus and mono-zeroconf are used by some more applications:
notify-sharp gnome-keyring-sharp tomboy podsleuth ipod-sharp f-spot
(These are just the ones I've installed - I don't know how I can search for all packages in the complete repository which needs a specific package...)
Once the builds of ndesk-dbus and zeroconf are done for F12, we should make sure that we test also the mentioned dependencies before asking rel-eng for inclusion... But I'm sure that's manageable and so I still vote for inclusion in F12. ;-) Just give me a hint once they are built and I'll help testing...
Best regards, Christian
mono@lists.stg.fedoraproject.org
-
Christian Krause -
Michel Alexandre Salim -
Paul Lange