Package Details: upmpdcli 1.4.10-2

Git Clone URL: https://aur.archlinux.org/upmpdcli.git (read-only, click to copy)
Package Base: upmpdcli
Description: A UPnP Media Renderer front-end for the Music Player Daemon (MPD)
Upstream URL: http://www.lesbonscomptes.com/upmpdcli/
Licenses: GPL2
Submitter: oxplot
Maintainer: FabioLolix (blackhole, ElVirolo)
Last Packager: blackhole
Votes: 16
Popularity: 0.78
First Submitted: 2015-11-24 03:17
Last Updated: 2020-05-23 12:44

Dependencies (28)

Required by (0)

Sources (2)

Latest Comments

1 2 3 4 5 Next › Last »

fvdb06 commented on 2020-05-07 09:49

The problem is solved..... Different upmpdcli configurations and one router caused the dissappearing effect. After resetting the router the problem was solved.

fvdb06 commented on 2020-05-05 07:27

This is exact the way I compiled & installed, first libnpupnp, followed by libupnpp, en last upmpdcli. All packages with theit own PKGBUILD. Do you also have installed recoll and python-mutagen?

skunark commented on 2020-05-05 00:42

It seems that libnpupnp needs to be compiled first followed by a recompile of libupnpp and then upmpdcli. Maybe the upmpdcli needs to have an uprev requirement of libupnpp and a requirement of the libnpupnp version too.

I just upgraded my config, seems okay, if there isn’t a libnpupnp PKGBUILD available, I can binpaste a link to it.

fvdb06 commented on 2020-05-04 18:25

yes, I recompiled everything: situation still the same Next step I did: removed python, installed everything again: situation still the same

What software component is responsible for publishing the upnp/dlna server on the network?

skunark commented on 2020-05-04 16:48

I assumed you recompiled everything after the recoll and mutagen updates?

fvdb06 commented on 2020-05-04 16:41

I just removed python-mutagen and recoll and did the installation of upmpdcli again on the same system. Unfortenately the situation stays the same. If I install upmpdcli on a fresh installed arch system, there are no problems. As soon I install recoll and python-mutagen additional to this new system, the "friendly name" issue appears. At the moment I stucked with 2 incorrect linux systems and one correct one.

blackhole commented on 2020-05-04 14:56

You can remove python-mutagen and recoll, if you want... unless you need them

keithspg commented on 2020-05-04 14:46

I do not have python-mutagen nor recoll installed.

fvdb06 commented on 2020-05-04 14:00

I also start upmpdcli from the cli

[root@archlabs archlabs]# /usr/bin/upmpdcli -c /etc/upmpdcli.conf -q 1 -d /var/log/upmpdcli.log -l 2 writing RSA key

No errors and log file is also empty

I tried 4 scenarios: root/No root and upmpdcli.service/upmpdcli from the cli

All 4 the scenario's with the same results

First, I have to open the control app on my iPhone (mconnect or C5), then start of upmpdcli => friendly name appears If I first start upmpdcli, then open the control app => No friendly appears

I also totally did re-install libnpupnp, libupnpp and upmpdcli (both 4.7 and 4.8), but the situation stays the same. For me it is a dependancy problemm, but what???

Before I installed recoll and python-mutagen all functioned with no problem. Do you also have installed recoll and python-mutagen?

keithspg commented on 2020-05-04 12:58

I have not experienced this problem of the vanishing friendly name. I also use the .service file. I have noticed a few permissions things with systemd and permissions on the logging folder or other folders (/run ?) which may be causing what you are seeing. 1.4.7 and 1.4.8 seem to be fine for me here. Look at the settings in /etc/upmpdcli.conf. I would recommend shutting down the service and running upmpdcli from the cli by the same command as in the ExecStart line of the *.service file. Mine is this: ExecStart=/usr/bin/upmpdcli -c /etc/upmpdcli.conf -q 1 -d /var/log/runeaudio/upmpdcli.log -l 2

Run whatever yours is from the command line and see if it shows you any errors. I have seen inability to write to the log file and inability to create a pid file and problems writing the RSA token. Usually after it has a successful start and you resolve any permissions problems, it 'just works'.