Hi James,
thanks for taking care of Gerbera and mediatomb's bug reports.
Unfortunately, I do not have a UPnP setup anymore, so I can't test it.
However, with /etc/default being removed, I can't see how this bug could still
occur, so even without testing, I am very positive, that the bug is
Dear Héctor,
sorry for the delay until I found the time to answer.
So this is definitely inconsistent (using the port number from
/etc/default/mediatomb in systemd and using the port number from
/etc/mediatomb/config.xml in the init script) and completely
non-transparent to the user.
Hola,
Find inlined comments below.
2014-12-09 14:35 GMT+01:00 Patrick Häcker pa...@web.de:
Even if it started, it wouldn't work, as it does not read the
configuration file /etc/mediatomb/config.xml
Additionally, it does not seem to make sense to have
/etc/default/mediatomb, as nearly
Hello,
thanks for answering this bug report and sorry for reporting back this late.
Even if it started, it wouldn't work, as it does not read the
configuration file /etc/mediatomb/config.xml
Additionally, it does not seem to make sense to have
/etc/default/mediatomb, as nearly all
I'm a first time poster here and a complete Linux noob. I, too, am having a
hard time with this version of Mediatomb. Earlier this year Jessie's mediatomb
worked fine until mid October. Things broke so bad so I reloaded with Debian
7.7 and things worked again. My setup is a dummy headless
severity 769325 important
thanks
Hello,
On Wed, Nov 12, 2014 at 09:43:21PM +0100, Patrick Häcker wrote:
version 0.12.1-7 does not start when using systemd without a useable error
message:
Process: 2788 ExecStart=/usr/bin/mediatomb -d -u $MT_USER -g $MT_GROUP -P
/run/mediatomb.pid -l
Package: mediatomb
Version: 0.12.1-7
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
version 0.12.1-7 does not start when using systemd without a useable error
message:
Process: 2788 ExecStart=/usr/bin/mediatomb -d -u $MT_USER -g $MT_GROUP -P
7 matches
Mail list logo
