[Touch-packages] [Bug 1536208] Re: Can no longer find dlna server after upgrade from 15.10 to 16.04

2016-02-23 Thread Jamie Strandboge 
I can confirm this is fixed on up to date xenial. Thanks! :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gssdp 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 grilo-plugins package in Ubuntu:
  Invalid
Status in gssdp package in Ubuntu:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Invalid
Status in grilo-plugins source package in Xenial:
  Invalid
Status in gssdp source package in Xenial:
  Fix Released
Status in rhythmbox source package in Xenial:
  Invalid

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 
  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 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/grilo-plugins/+bug/1536208/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536208] Re: Can no longer find dlna server after upgrade from 15.10 to 16.04

2016-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package gssdp - 0.14.14-1ubuntu1

---
gssdp (0.14.14-1ubuntu1) xenial; urgency=medium

  * Resynchronize on Debian, remaining change
- multiarchify the library packages
includes fix for dlna servers (lp: #1536208)

 -- Sebastien Bacher   Tue, 23 Feb 2016 10:53:18
+0100

** Changed in: gssdp (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gssdp 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 grilo-plugins package in Ubuntu:
  Invalid
Status in gssdp package in Ubuntu:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Invalid
Status in grilo-plugins source package in Xenial:
  Invalid
Status in gssdp source package in Xenial:
  Fix Released
Status in rhythmbox source package in Xenial:
  Invalid

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 
  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 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/grilo-plugins/+bug/1536208/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536208] Re: Can no longer find dlna server after upgrade from 15.10 to 16.04

2016-02-23 Thread Sebastien Bacher 
the issue was with gssdp and the difference in guest was probably just
random timing one

** Package changed: dleyna-server (Ubuntu Xenial) => gssdp (Ubuntu
Xenial)

** Changed in: gssdp (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: gssdp (Ubuntu Xenial)
   Status: New => Fix Committed

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

** Changed in: grilo-plugins (Ubuntu Xenial)
 Assignee: Iain Lane (laney) => (unassigned)

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

** Changed in: grilo-plugins (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: grilo-plugins (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: rhythmbox (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: rhythmbox (Ubuntu Xenial)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gssdp 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 grilo-plugins package in Ubuntu:
  Invalid
Status in gssdp package in Ubuntu:
  Fix Committed
Status in rhythmbox package in Ubuntu:
  Invalid
Status in grilo-plugins source package in Xenial:
  Invalid
Status in gssdp source package in Xenial:
  Fix Committed
Status in rhythmbox source package in Xenial:
  Invalid

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 
  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 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/grilo-plugins/+bug/1536208/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536208] Re: Can no longer find dlna server after upgrade from 15.10 to 16.04

2016-02-22 Thread Sebastien Bacher 
gupnp-av-cp has the same issue (and works as well in a guest session)
... unsure what's going on there

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins 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
Status in dleyna-server source package in Xenial:
  New
Status in grilo-plugins source package in Xenial:
  New
Status in rhythmbox source package in Xenial:
  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 
  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 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536208] Re: Can no longer find dlna server after upgrade from 15.10 to 16.04

2016-02-22 Thread Sebastien Bacher 
I looked a bit at the issue today, some data points

- it works in a guest session

- it doesn't work with a existing/new user(?)

- it's not an issue with rhythmbox, rhythmbox doesn't list the share
either, nor does the grilo-test-ui utility (need to rebuild grilo to try
this one)

- the dleyna 0.5 update doesn't fix it


I'm unsure why it works in a guest session, maybe some features get turned off 
due to the restricted permissions and the remaining ones are working...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins 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
Status in dleyna-server source package in Xenial:
  New
Status in grilo-plugins source package in Xenial:
  New
Status in rhythmbox source package in Xenial:
  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 
  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 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536208] Re: Can no longer find dlna server after upgrade from 15.10 to 16.04

2016-02-15 Thread Will Cooke 
** Also affects: rhythmbox (Ubuntu Xenial)
   Importance: Undecided
 Assignee: Iain Lane (laney)
   Status: New

** Also affects: grilo-plugins (Ubuntu Xenial)
   Importance: Undecided
 Assignee: Iain Lane (laney)
   Status: New

** Also affects: dleyna-server (Ubuntu Xenial)
   Importance: Undecided
 Assignee: Iain Lane (laney)
   Status: New

** Tags removed: rls-x-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins 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
Status in dleyna-server source package in Xenial:
  New
Status in grilo-plugins source package in Xenial:
  New
Status in rhythmbox source package in Xenial:
  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 
  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 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536208] Re: Can no longer find dlna server after upgrade from 15.10 to 16.04

2016-02-10 Thread Sebastien Bacher 
** Tags added: rls-x-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins 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 
  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 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536208] Re: Can no longer find dlna server after upgrade from 15.10 to 16.04

2016-01-27 Thread Jamie Strandboge 
** 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 
  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.
+ any more. I tried on a separate wily install 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.

** Changed in: grilo-plugins (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: dleyna-server (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins 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 
  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 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

[Touch-packages] [Bug 1536208] Re: Can no longer find dlna server after upgrade from 15.10 to 16.04

2016-01-20 Thread Jamie Strandboge 
** 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 
  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 
  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 Ubuntu
Touch seeded packages, which is

[Touch-packages] [Bug 1536208] Re: Can no longer find dlna server after upgrade from 15.10 to 16.04

2016-01-20 Thread Jamie Strandboge 
** Summary changed:

- Can no longer fine dlna server after upgrade from 15.10 to 16.04
+ Can no longer find dlna server after upgrade from 15.10 to 16.04

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins 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 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 
  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.

  TODO: I'm working on a simple reproducer now

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp