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

Eric Valette

unread,

Jun 23, 2022, 5:00:04 PM6/23/22

to

Package: gupnp-tools
Version: 0.10.3-1
Severity: grave
Justification: renders package unusable

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

VLC and Kodi do detect them.

-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.121 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages gupnp-tools depends on:
ii libc6 2.34-0experimental4
ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1
ii libglib2.0-0 2.72.2-2
ii libgssdp-1.2-0 1.4.0.1-2
ii libgtk-3-0 3.24.34-1
ii libgtksourceview-4-0 4.8.3-1
ii libgupnp-1.2-1 1.4.3-1
ii libgupnp-av-1.0-3 0.14.1-1
ii libsoup2.4-1 2.74.2-3
ii libxml2 2.9.14+dfsg-1

gupnp-tools recommends no packages.

gupnp-tools suggests no packages.

-- no debconf information

Andreas Henriksson

unread,

Jul 25, 2022, 11:30:03 AM7/25/22

to

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

Eric Valette

unread,

Jul 25, 2022, 1:40:03 PM7/25/22

to

On 25/07/2022 17:17, Andreas Henriksson wrote:
> Control: severity -1 normal
> Control: tags -1 moreinfo

>> VLC and Kodi do detect them.

As kodi and VLC detect them on the same network at the same time and use
also upnp-av serveur types (rendered, file serveur).

Anyway, the bug has vanished and way due to the upnp stack has other
using other upnp stack did work.

--eric