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.
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
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
Hi,
I do not know if it is related, but here vlc sometimes (4 out of 10 times)
segfaults when opening a directory from the command line, i.e. vlc ..
Valgrind complains about an Unrecognised instruction, so it does not help
so much.
This is the gdb output:
(gdb) run
Starting program:
I managed to reproduce the segfaults and I believe I just fixed this
in the version available in the git repository.
It's always a pleasure if the open source community shines like this:
I can confirm, that the bug is fixed in the git repository. Thanks for
solving the problem so quickly and
I could narrow the reason of the segfault down.
The segfault occurs only if virtual-layout is set to js in
/etc/mediatomb/config.xml. It does not occur if it is set to disabled or
builtin.
If virtual-layout is set to js the segfault in my setup occurs if and only
if the copyObject function is