Created attachment 846137 [details] Grilo sees Diskstation Description of problem: Rhythmbox does not show media from two uPNP servers. 1. Synology Diskstation: uPNP server is detected but no media shows up . Search box does not appear 2. miniDLNA: uPNP server is detected, no media to browse, but media is discovered using search box 3. Both uPNP servers and media are discovered by vlc and Grilo Test UI. Version-Release number of selected component (if applicable): rhythmbox-3.0.1-3.fc20 grilo-0.2.7-1.fc20 How reproducible: Always Steps to Reproduce: 1. Prepare two uPNP servers for testing: miniDLNA, Synology NAS 2. Ensure uPNP servers are discovered by Grilo Test UI (disable firewall between servers and renderer) 3. Enable grilo plugin in rhythmbox 4. Start rhythmbox Actual results: Both media servers appear under Shared. No media appears in Browse pane. a. For Synology Diskstation uPNP: empty browse pane, no search box (rhythmbox:27096): GLib-GObject-WARNING **: invalid (NULL) pointer instance b. For miniDLNA: no media in browse pane. search box can discover media Expected results: Media appears in Browse pane. Additional info: vlc, Grilo Test UI discovers both media servers.
Created attachment 846138 [details] Grilo see MiniDLNA
Created attachment 846139 [details] Rhythmbox to Diskstation 1. No media to browse 2. No search box
Created attachment 846140 [details] Rhythmbox to MiniDLNA 1. No media to browse 2. Search works: media will appear in media window if some text is entered into the Search box. 3. The media in the Search results are playable.
Created attachment 846142 [details] vlc finds both uPnP servers vlc finds both media servers. Media is browseable and playable.
Both media servers appear in Totem 3.10.1. Neither is browseable. 1. MiniDLNA - no media to browse; nothing happens when clicked 2. Synology DiskStation NAS - no media to browse; error dialog: "Browse Error Action Failed"
Same here with Twonky and Logitech Media Server on QNAP. Totem tells me "Unsupported or invalid search criteria" when clicking LMS.
Same problem with F20. rhythmbox-3.0.1-3.fc20.x86_64 grilo-0.2.7-1.fc20.x86_64 grilo-plugins-0.2.9-2.fc20.x86_64 DLNA server is visible in rhythmbox, but the shares are not browsable (and obviously not playable) DLNA server is working. (miniDLNA on CentOS) shares are browsable from same F20 client with upnp-inspector (iptables disabled) shares work on other DLNA clients on network.
Running with minidlna 1.1.1 on the localhost works is working better. I can browse and play back media.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.