desktop-packages team mailing list archive

[Jamie Strandboge <jamie@xxxxxxxxxx>]

** Description changed:

  From irc:
  08:28 < jdstrand> Laney: question for you-- just otoh, can you think of a reason why dlna wouldn't work on xenial in rhythmbox any more when it has the same upstream version as wily (and the Ubuntu delta didn't have any relevant changes), grilo is the same as wily and grilo-plugins only has one irrelevant change over wily?
  08:29 < jdstrand> (it the dleyna code in grilo that handles this afaik)
  08:30 < jdstrand> Laney: the dlna server just doesn't show up any more (but daap still does)
  08:33 < jdstrand> I have both forked-daapd and minidlna exporting <music>
  08:33 < jdstrand> and rhythmbox used to see both on wily. on xenial, it only sees daap
  
  This may be a bug in grilo or grilo-plugins since, AIUI, it is the
- dleyna code in grilo-plugins that handles this.
+ dleyna code in grilo-plugins that handles this. It appears that grilo
+ relies on dleyna-server and dleyna-server isn't able to find the server
+ any more. I tried on a separate wily into and it wasn't able to find it.
  
- TODO: I'm working on a simple reproducer now
+ 
+ Coming up with a reproducer was more difficult than I thought it would be.
+ 
+ 1. minidlna server setup
+ $ sudo apt-get install minidlna
+ 
+ Adjust /etc/minidlna.conf to have:
+ media_dir=A,/path/to/some/music/files
+ 
+ I believe everything else can be left as defaults.
+ 
+ 2. rhythmbox setup
+ $ sudo apt-get install grilo-plugins-0.2-extra rhythmbox-plugins dleyna-server
+ 
+ stop and start rhythmbox
+ 
+ go into Tools/Plugins and check Grilo media browser
+ 
+ This was all I needed to do initially for it to start working. Now it
+ now longer works. Android devices and 'kodi' from Ubuntu can find and
+ use it fine. Using d-feet and going to 'com.intel.dleyna-server' and
+ into com.intel.dLeynaServer.Manager and looking at 'GetServers' returns
+ nothing. Looking at Rescan() triggers traffic (as seen with tcpcump)
+ with the server (ie, there are responses). Looking at an strace of
+ /usr/lib/dleyna-server/dleyna-server-service shows it got a response
+ from the minidlna server. I guess the problem is in dleyna-server. There
+ is a new upstream version (0.5), but it is newer than what is in Debian.
+ 
+ Apparently minidlna is installed in Netgear devices and other places and
+ is quite popular.

** Also affects: dleyna-server (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: rhythmbox (Ubuntu)
     Assignee: (unassigned) => Iain Lane (laney)

** Description changed:

  From irc:
  08:28 < jdstrand> Laney: question for you-- just otoh, can you think of a reason why dlna wouldn't work on xenial in rhythmbox any more when it has the same upstream version as wily (and the Ubuntu delta didn't have any relevant changes), grilo is the same as wily and grilo-plugins only has one irrelevant change over wily?
  08:29 < jdstrand> (it the dleyna code in grilo that handles this afaik)
  08:30 < jdstrand> Laney: the dlna server just doesn't show up any more (but daap still does)
  08:33 < jdstrand> I have both forked-daapd and minidlna exporting <music>
  08:33 < jdstrand> and rhythmbox used to see both on wily. on xenial, it only sees daap
  
  This may be a bug in grilo or grilo-plugins since, AIUI, it is the
  dleyna code in grilo-plugins that handles this. It appears that grilo
  relies on dleyna-server and dleyna-server isn't able to find the server
- any more. I tried on a separate wily into and it wasn't able to find it.
+ any more. I tried on a separate wily install to see if it would work and
+ it wasn't able to find it.
  
- 
- Coming up with a reproducer was more difficult than I thought it would be.
+ Coming up with a reproducer was more difficult than I thought it would
+ be.
  
  1. minidlna server setup
  $ sudo apt-get install minidlna
  
  Adjust /etc/minidlna.conf to have:
  media_dir=A,/path/to/some/music/files
  
  I believe everything else can be left as defaults.
  
  2. rhythmbox setup
  $ sudo apt-get install grilo-plugins-0.2-extra rhythmbox-plugins dleyna-server
  
  stop and start rhythmbox
  
  go into Tools/Plugins and check Grilo media browser
  
  This was all I needed to do initially for it to start working. Now it
  now longer works. Android devices and 'kodi' from Ubuntu can find and
  use it fine. Using d-feet and going to 'com.intel.dleyna-server' and
  into com.intel.dLeynaServer.Manager and looking at 'GetServers' returns
  nothing. Looking at Rescan() triggers traffic (as seen with tcpcump)
  with the server (ie, there are responses). Looking at an strace of
  /usr/lib/dleyna-server/dleyna-server-service shows it got a response
  from the minidlna server. I guess the problem is in dleyna-server. There
  is a new upstream version (0.5), but it is newer than what is in Debian.
  
  Apparently minidlna is installed in Netgear devices and other places and
  is quite popular.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1536208

Title:
  Can no longer find dlna server after upgrade from 15.10 to 16.04

Status in dleyna-server package in Ubuntu:
  New
Status in grilo-plugins package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  From irc:
  08:28 < jdstrand> Laney: question for you-- just otoh, can you think of a reason why dlna wouldn't work on xenial in rhythmbox any more when it has the same upstream version as wily (and the Ubuntu delta didn't have any relevant changes), grilo is the same as wily and grilo-plugins only has one irrelevant change over wily?
  08:29 < jdstrand> (it the dleyna code in grilo that handles this afaik)
  08:30 < jdstrand> Laney: the dlna server just doesn't show up any more (but daap still does)
  08:33 < jdstrand> I have both forked-daapd and minidlna exporting <music>
  08:33 < jdstrand> and rhythmbox used to see both on wily. on xenial, it only sees daap

  This may be a bug in grilo or grilo-plugins since, AIUI, it is the
  dleyna code in grilo-plugins that handles this. It appears that grilo
  relies on dleyna-server and dleyna-server isn't able to find the
  server any more. I tried on a separate wily install to see if it would
  work and it wasn't able to find it.

  Coming up with a reproducer was more difficult than I thought it would
  be.

  1. minidlna server setup
  $ sudo apt-get install minidlna

  Adjust /etc/minidlna.conf to have:
  media_dir=A,/path/to/some/music/files

  I believe everything else can be left as defaults.

  2. rhythmbox setup
  $ sudo apt-get install grilo-plugins-0.2-extra rhythmbox-plugins dleyna-server

  stop and start rhythmbox

  go into Tools/Plugins and check Grilo media browser

  This was all I needed to do initially for it to start working. Now it
  now longer works. Android devices and 'kodi' from Ubuntu can find and
  use it fine. Using d-feet and going to 'com.intel.dleyna-server' and
  into com.intel.dLeynaServer.Manager and looking at 'GetServers'
  returns nothing. Looking at Rescan() triggers traffic (as seen with
  tcpcump) with the server (ie, there are responses). Looking at an
  strace of /usr/lib/dleyna-server/dleyna-server-service shows it got a
  response from the minidlna server. I guess the problem is in dleyna-
  server. There is a new upstream version (0.5), but it is newer than
  what is in Debian.

  Apparently minidlna is installed in Netgear devices and other places
  and is quite popular.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dleyna-server/+bug/1536208/+subscriptions