Bug#1013447: gupnp-tools: gupnp-av-cp fails to detect upnp av serveur that kodi or vlc detects correctly

[Andreas Henriksson]

Control: severity -1 normal
Control: tags -1 moreinfo

Hello Eric Valette,

On Thu, Jun 23, 2022 at 10:54:10PM +0200, Eric Valette wrote:
> Package: gupnp-tools
> Version: 0.10.3-1
> Severity: grave
> Justification: renders package unusable
> 

The gupnp-tools package consists of multiple tools. You're stating
the bug you report are making the package unusable, thus all tools are
supposedly completely unusable. Since you only actually briefly mention
gupnp-av-cp I'm going to downgrade severity right off the bat.

> starting gupnp-av-cp does not detect any DLNA (minidlnad, smartv TV,
> ...) content server on local network. 

Could you please give details on how these devices exposes themselves
on the network?

The gupnp-av-cp tool will only list Media Renderer and Media Servers.
That is devices exposing themselves as Type
urn:schemas-upnp-org:device:MediaRenderer:1 or
urn:schemas-upnp-org:device:MediaServer:1

See:
https://sources.debian.org/src/gupnp-tools/0.10.3-1/src/av-cp/main.c/#L112-L113
https://sources.debian.org/src/gupnp-tools/0.10.3-1/src/av-cp/main.c/#L40-L41

My Smart TV's for example exposes themselves as Type
urn:dial-multiscreen-org:device:dial:1
according to gupnp-universal-cp (also part of gupnp-tools package!).
They will thus be filtered out from being displayed in gupnp-av-cp.

If you want to test something which will expose itself as something that
will show up in gupnp-av-cp that could for example be gmediarender.

Things seems to work as expected to me, although DLNA/UPnP-AV itself and
proprietary vendors implementations of it are indeed quite confusing.

> 
> VLC and Kodi do detect them.

Regards,
Andreas Henriksson