Device.list_children() crashes minidlna on Ubuntu 14.04 #148
Comments
Update: turns out |
Problem seems related to the
|
It's not just more appropriate: helping fix the bug in minidlna is the best way to get dleyna compatible. At that point it would be clear what exactly triggers the problem and working around becomes possible. Currently it's basically a game of guessing. Alternatively you could try some things blindly:
Spec for the container API is here if you're wondering: https://wiki.gnome.org/Projects/Rygel/MediaServer2Spec#org.gnome.UPnP.MediaContainer2 |
@jku: Thanks, using "*" as a filter actually seems to work! |
Great, sometimes debug by guesswork is all it takes... Sorry, I don't have the time to work with minidlnad now and I'm not actively involved with dleyna at the moment. In any case what you have looks quite useful already. If you want to be really useful, find out what the upnp message that dleyna sends that crashes minidlnad looks like -- if you kill dleyna-server-service and start it by hand with "GUPNP_DEBUG=1 /path/to/dleyna-server-service" that should print out the HTTP traffic, if I still remember things correctly. That should be more than enough for minidlnad guys to reproduce -- and to also show whether dleyna sends something strange... |
Okay, so let's hope dLeyna is still actively supported and somebody with more knowledge about this stuff than me will take care of this issue. For now, I'd like to focus on my initial goals, i.e. actually start using dLeyna ;-) But once more, thanks for your support! |
For starters, this is the output of
As I said before, I'm no expert on these subjects, but the empty |
That looks fishy. I don't remember what the specs say but ... there should probably be a value there. Now minidlna shouldn't crash of course but that Filter could still be a bug in dleyna. |
Actually,
|
@jku: I was just kind of learning/experimenting with the dLeyna API, and I just wanted to list the paths to reduce screen clutter. So I guessed passing "Path" as filter would just do that. Also wanted to use filters straight away to reduce bandwidth in my final application, but I guess that was just premature optimization. So, no real reason, just toying around with the API. |
BTW, this works as expected using BubbleUPnP as a media server, otherwise I would have spent more time debugging my own code. |
I want to make sure I understand the BubbleUPnP data point. Are you using dLeyna as the client and BubbleUPnP as DMS on server side or are use using BubbleUPnP Client APIs with BubbleUPnP DMS? The crash occurs when you are using Rygel as the DMS along with dLeyna? I have an Ubuntu 14.04 that I can setup to reproduce the issue. Please provide with the DMS (?Rygel version) and GUPnP package version you are using? Provide with all packages you installed and all the steps. |
|
So if you are using using dLeyna with BubbleUPnP as the DMS and it is not crashing and using dLeyna with minidlna as DMS and it is crashing. Sounds like an issue need minidnla to be filed but we should still look at it to see if there corner case that dLeyna is doing that BubbleUPnP handles better than miniDNLA. We want to make sure we don't have any compatibility issues with other DMS. |
Exactly. I could have filed a bug report with minidlna myself, but I'm new to this whole DLNA stuff, and I think it would be more efficient if dLeyna developers explain to minidlna developers what is wrong. |
Using
test/dbus/mediaconsole.py
fromdleyna-server
master branch on GitHub (v0.5.0), this crashesminidlna
version 1.1.2, as provided with Ubuntu 14.04:Syslog reports this:
I'm well aware that it would probably be more appropriate to file an issue with minidlna (or ReadyMedia as it now seems to be called), but since minidlna is widely deployed and is also shipped with a variety of NETGEAR routers, and various other DLNA clients seem to work fine with it, I guess this should at least be reviewed by the dLeyna developers. If I can contribute in any way to find the cause (or even better, a workaround) for this, just let me know.
The text was updated successfully, but these errors were encountered: