Coherence and Rhythmbox UPNP not seeing media server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Coherence |
New
|
Unknown
|
|||
coherence (Debian) |
Fix Released
|
Unknown
|
|||
coherence (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Ubuntu 10.04 fully patched.
UPNP/AV server on 192.168.1.1 - which is also my ISP-provided router.
VLC: sees it perfectly - if the server is active when VLC starts, VLC displays it. If it deactivates while VLC is running VLC delists it, if it restarts while VLC is running, VLC lists it again. All media is browsable and playable - perfect behavior.
Coherence uPNP inspector: If the media server is up when the inspector starts, the inspector lists it. If it deactivates while the inspector is running, the inspector delists it. BUT if the media server is then brought back UP, the inspector DOES NOT RE-LIST IT (even when "rediscover devices" in the file menu is selected). However if the media server is down when the inspector is started and then is started, the inspector DOES add it correctly. When the server is seen by the inspector, the inspector can correctly browse its contents.
Rhythmbox just plain never sees the media server at all (and I checked in the device addition signal handler - it never receives notification that a device is there under any circumstances), although it CAN see a mediatomb server on another PC in the home network.
I conclude that there is a small bug in coherence itself, or the inspector - whereby a server that deactivates and then reactivates is not being successfully re-added. And there is a more significant bug in the Rhythmbox plugin whereby it is never being notified of the existence of a server on 192.168.1.1. Of course Rhythmbox has its own issues concerning the listing of tracks from UPNP media servers such as mediatomb - but that is dealt with in another bug report.
Related branches
summary: |
- Coherence and Rhytmn box UPNP not seeing media server + Coherence and Rhythmbox UPNP not seeing media server |
tags: | added: patch |
affects: | ubuntu → coherence (Ubuntu) |
tags: | added: patch-forwarded-upstream |
Changed in coherence (Ubuntu): | |
importance: | Undecided → Medium |
Changed in coherence: | |
status: | Unknown → New |
tags: |
added: patch-forwarded-debian removed: patch |
tags: |
added: patch-accepted-debian removed: patch-forwarded-debian |
Changed in coherence (Debian): | |
status: | Unknown → Fix Released |
djmount also successfully sees the server if it is up when djmount starts, or if it starts after djmount starts, but djmount reacts badly to the server being brought down while djmount is up. When it sees the server, nautilus can quite happily browse the server content and play it.
The point is that, despite this latter bug in djmount, it SEES the server perfectly well - so whatever is happening with Rhythmbox, it is not the server that is the problem, nor is it an issue with routing tables or firewall configurations or the such.