I' using amarok 2.4.0 with KDE 4.6.0 on opensuse 11.3, amarok does not display my mediatomb server. I have avahi-daemon setup and logs show amarok gets the correct info and tries to connect.
Here is the amarok log showing the daap info. Hoping someone has a suggestion how to fix this. Amarok has the same problem with minidlna server too.
Peter

amarok --debug --nofork 2>&1 | tee log | grep Daap
amarok: BEGIN: virtual void Collections::DaapCollectionFactory::init()
amarok: END__: virtual void Collections::DaapCollectionFactory::init() [Took: 0.006s]
amarok: BEGIN: void Collections::DaapCollectionFactory::foundDaap(DNSSD::RemoteService::Ptr)
amarok: END__: void Collections::DaapCollectionFactory::foundDaap(DNSSD::RemoteService::Ptr) [Took: 0.001s]
amarok: [DaapCollection] "server" "server.local" "local" "_daap._tcp"
amarok: BEGIN: void Collections::DaapCollectionFactory::resolvedServiceIp(QHostInfo)
amarok: [DaapCollection] Host: "server.local" port: 50500
amarok: [DaapReader] Host: "server.local" port: 50500
amarok: BEGIN: void Daap::Reader::loginRequest()
amarok: END__: void Daap::Reader::loginRequest() [Took: 0s]
amarok: END__: void Collections::DaapCollectionFactory::resolvedServiceIp(QHostInfo) [Took: 0.001s]
amarok: BEGIN: void Collections::DaapCollectionFactory::connectToManualServers()
amarok: END__: void Collections::DaapCollectionFactory::connectToManualServers() [Took: 0s]
amarok: BEGIN: void Daap::Reader::loginHeaderReceived(const QHttpResponseHeader&)
amarok: END__: void Daap::Reader::loginHeaderReceived(const QHttpResponseHeader&) [Took: 0s]
amarok: BEGIN: void Daap::Reader::loginFinished(int, bool)
amarok: BEGIN: static Daap::Map Daap::Reader::parse(QDataStream&, uint, bool)
amarok: [WARNING] [DaapReader] <htm does not work
amarok: [WARNING] [DaapReader] ody> does not work
amarok: [WARNING] [DaapReader] 404 does not work
amarok: [WARNING] [DaapReader] Foun does not work
amarok: [WARNING] [DaapReader] 1></ does not work
amarok: [WARNING] [DaapReader] ></h does not work
amarok: END__: static Daap::Map Daap::Reader::parse(QDataStream&, uint, bool) [Took: 0s]
amarok: [DaapReader] list size is 0
amarok: END__: void Daap::Reader::loginFinished(int, bool) [Took: 0s]

Well, apparently you get a 404 error which usually means the server is not found. I don't know much about Daap, but you should check your connection to the server.

DAAP is a protocol created by Apple for sharing between iTunes clients. No idea what the DAAP protocol handler is doing trying to talk to a UPnP AV server though.

Hi,

Is Amarok able to access to dlna (UPnP?) shares ?
Do we need to set it up somewhere ?

On my network, daap shares show up well. I don't like using it as Amarok does not associate album covers when shared with daap. --> This is why I use a samba share instead

Ok, edited avahi-daemon on the server to point to upnp instead of daap, amarok sees the change and tries to use upnp but still mediatomb does show up in amarok. The uuid for Mediaserver:1 is my upnp server.
amarok: BEGIN: virtual void Collections::UpnpCollectionFactory::init()
amarok: [UpnpCollectionFactory] |||| DEVICE "uuid:80329b2d-a9ca-429e-a25a-78ec1f92d0bb" "urn:schemas-upnp-org:device:MediaServer:1"
amarok: [UpnpCollectionFactory] |||| Creating collection "uuid:80329b2d-a9ca-429e-a25a-78ec1f92d0bb"
amarok: [UpnpCollectionFactory] |||| Creating collection "80329b2d-a9ca-429e-a25a-78ec1f92d0bb"
amarok: [UpnpCollectionFactory] |||| DEVICE "uuid:0016-b6cf-695d02001c84" "urn:schemas-upnp-org:device:WANConnectionDevice:1"
amarok: [UpnpCollectionFactory] |||| DEVICE "uuid:0016-b6cf-695d00981c84" "urn:schemas-upnp-org:device:InternetGatewayDevice:1"
amarok: [UpnpCollectionFactory] |||| DEVICE "uuid:0016-b6cf-695d01c01c84" "urn:schemas-upnp-org:device:WANDevice:1"
amarok: END__: virtual void Collections::UpnpCollectionFactory::init() [Took: 0.008s]

Now getting a popup stating:

Unable to create io-slave: Klauncher said unknown protocol upnp-ms:

Good news for the future - We've had a re-work of Collections and Services, which will roll out with 2.4.1. You'll be able to choose all the Collections and Services you want with a simple check mark. It's quite exciting to think about!

I hope someone else has some guidance for the present, until our 2.4.1 release (beta next week, final next month).

That's great, can't wait for 2.4.1