GNOME Bugzilla – Bug 722943
dlna upnp browsing not working in totem 3.10 with Synology multimedia server
Last modified: 2014-02-22 07:01:38 UTC
Description of problem: Dlna shares are shown in the sidebar. But when I double click in one of the them, I get an error popup window; "Browse Error Action Failed". And I can't browse the share Version: totem-3.10.1-1.fc20.x86_64 grilo-0.2.7-1.fc20.x86_64 grilo-plugins-0.2.9-2.fc20.x86_64 In F19, I can browse and play videos from the share: totem-3.8.2-1.fc19.x86_64 grilo-0.2.6-1.fc19.x86_64 grilo-plugins-0.2.8-2.fc19.x86_64 With grilo-test-ui-0.2, I can browse the share. So it works with grilo-test-ui-0.2 and it doesn't with totem
(In reply to comment #0) > Description of problem: > Dlna shares are shown in the sidebar. But when I double click in one of the > them, I get an error popup window; "Browse Error Action Failed". And I can't > browse the share > > Version: totem-3.10.1-1.fc20.x86_64 grilo-0.2.7-1.fc20.x86_64 > grilo-plugins-0.2.9-2.fc20.x86_64 > > In F19, I can browse and play videos from the share: totem-3.8.2-1.fc19.x86_64 > grilo-0.2.6-1.fc19.x86_64 grilo-plugins-0.2.8-2.fc19.x86_64 > > With grilo-test-ui-0.2, I can browse the share. So it works with > grilo-test-ui-0.2 and it doesn't with totem Did you disable audio and image media in the top-left bar before trying to browse using grilo-test-ui-0.2? That's the main difference between Totem and grilo-test-ui-0.2, and the main trigger for bad UPnP servers.
Related: bug #721303.
(In reply to comment #1) > > Did you disable audio and image media in the top-left bar before trying to > browse using grilo-test-ui-0.2? > That's the main difference between Totem and grilo-test-ui-0.2, and the main > trigger for bad UPnP servers. If I disable audio and image I get an error ** (grilo-test-ui-0.2:4736): CRITICAL **: Error: Action Failed My dlna server is a Synology NAS with DSM 4.3 This server works with the builtin dlna browser of my blue ray device and with totem in F19 and before
Created attachment 267358 [details] Grilo debug output
I have run grilo-tes-ui with debuging options. After unchecking audio and image I get an error. The relevant part in the debug log seems to be (I skip the xml here): > POST /ContentDirectory/control HTTP/1.1 > Soup-Debug-Timestamp: 1390785563 > Soup-Debug: SoupSessionAsync 1 (0x189fc40), SoupMessage 7 (0x199cd50), SoupSocket 7 (0x1a25190) > Host: 192.168.0.200:50001 > SOAPAction: "urn:schemas-upnp-org:service:ContentDirectory:1#Search" > Accept-Encoding: gzip > Content-Type: text/xml; charset="utf-8" > User-Agent: grilo-test-ui-0.2 GUPnP/0.20.9 DLNADOC/1.50 > Connection: Keep-Alive > < HTTP/1.1 500 Internal Server Error < Soup-Debug-Timestamp: 1390785563 < Soup-Debug: SoupMessage 7 (0x199cd50) < Content-Length: 411 < Content-Type: text/xml; charset="utf-8" < DATE: Mon, 27 Jan 2014 01:23:49 GMT < EXT: < SERVER: Linux/2.6.32.12, UPnP/1.0, Portable SDK for UPnP devices/1.6.18 < X-User-Agent: redsonic <
bug #682574 probably is a duplicate of this bug, describing the same issue in rhythmbox when using grilo, and there seem to be other similar bug reports around. When using the grilo plugin with rhythmbox in Ubuntu, this is part of the Query sent by grilo when trying to browse my DLNA share: <SearchCriteria>( ( upnp:class derivedfrom "object.item.audioItem" ) or upnp:class derivedfrom "object.container" ) and @parentID = "0"</SearchCriteria> In my case, that's an issue because minidlna doesn't support the @parentID check apparently, creating SQL like (this almost smells like possibility for SQL injection): > SELECT [..] WHERE [..] and @parentID = "0" [..] even though it should be "PARENT_ID". Looking at the parse_search_criteria function in minidlna, it seems like only @id and @refID are supported. Since minidlna is quite popular, this makes grilo-upnp useless for a lot of DLNA shares. I realize that this is probably not a bug in grilo (I didn't read the ContentDirectory spec completely..), but I'd prefer missing filter support over broken browse feature. Maybe the grilo code could be changed to always use the Browse actions instead of Search for browsing? Or retry using Browse if Search returns 0 results?
(In reply to comment #6) > I realize that this is probably not a bug in grilo (I didn't read the > ContentDirectory spec completely..), but I'd prefer missing filter support over > broken browse feature. Maybe the grilo code could be changed to always use the > Browse actions instead of Search for browsing? Or retry using Browse if Search > returns 0 results? Maybe we can detect the server and try to adjust, or at least add an option to disable the feature. In any case, we are moving to a completely new UPnP module which, I hope, fixes all this problems.
Can you please test with grilo-plugins 0.2.9? I actually have a Synology Diskstation as well, and haven't had problems with browsing for a long while.
(In reply to comment #8) > Can you please test with grilo-plugins 0.2.9? > That's the version of grilo-plugins I had when I wrote the report. So, no, it doesn't work. > I actually have a Synology Diskstation as well, and haven't had problems with > browsing for a long while. Can you play video in totem directly from the dlan share?
(In reply to comment #9) > (In reply to comment #8) > > Can you please test with grilo-plugins 0.2.9? > > > > That's the version of grilo-plugins I had when I wrote the report. So, no, it > doesn't work. > > > I actually have a Synology Diskstation as well, and haven't had problems with > > browsing for a long while. > > Can you play video in totem directly from the dlan share? I can using grilo and grilo-plugins from master, but can't using the stock Fedora 20 grilo (grilo-0.2.7-1.fc20.x86_64, grilo-plugins-0.2.9-2.fc20.x86_64). I think that the problem might be bug 709208, which was fixed in grilo 0.2.8 released about 10 days ago. Can any of test this out and confirm? I'll drop a mail to the GNOME distributor list so that people can upgrade if that's the case.
I have installed grilo-0.2.9-1.fc21.x86_64.rpm from Fedora koji and now I can reproduce videos inside totem directly from the dlna share. Great! Sorry I haven't tested 0.2.8, but for sure 0.2.9 works
Cool, marking as a duplicate. Thanks! *** This bug has been marked as a duplicate of bug 709208 ***