Bug 914907

I don't think this is connected to /etc/mediatomb.conf; specifying the port on the command line (-p option) is also ignored.

Update 23 broke mediatomb from serving content to my Samsung DLNA TVs.  It looks like the update broke some of the parsing of the /etc/mediatomb/config.xml. Mediatomb was reachable by the network DLNA devices, but they couldn't play any of the content (incomplete load of config.xml?).  

I configure a TCP port of 50500 in /etc/mediatomb.conf which used by update 23 (minor issue).  The bigger problem is that the custom HTTP headers are not included from /etc/mediatomb/config.xml.  I also suspect that the media mimetype mappings are not being parsed as well.  

Update 23 startup log messages: 

2013-02-22 08:30:22    INFO: Loading configuration from: /etc/mediatomb/config.xml
2013-02-22 08:30:22    INFO: Checking configuration...
2013-02-22 08:30:22    INFO: Setting filesystem import charset to UTF-8
2013-02-22 08:30:22    INFO: Setting metadata import charset to UTF-8
2013-02-22 08:30:22    INFO: Setting playlist charset to UTF-8
2013-02-22 08:30:22 WARNING: You enabled the YouTube feature, which allows you
                             to watch YouTube videos on your UPnP device!
                             Please check http://www.youtube.com/t/terms
                             By using this feature you may be violating YouTube
                             service terms and conditions!

2013-02-22 08:30:22    INFO: Configuration check succeeded.
2013-02-22 08:30:22    INFO: Initialized port: 49152
2013-02-22 08:30:22    INFO: Server bound to: 192.168.1.4
2013-02-22 08:30:22    INFO: MediaTomb Web UI can be reached by following this link:
2013-02-22 08:30:22    INFO: http://192.168.1.4:49152/

Working update 21:

2013-02-24 12:37:59    INFO: Loading configuration from: /etc/mediatomb/config.xml
2013-02-24 12:37:59    INFO: Checking configuration...
2013-02-24 12:37:59    INFO: Setting filesystem import charset to UTF-8
2013-02-24 12:37:59    INFO: Setting metadata import charset to UTF-8
2013-02-24 12:37:59    INFO: Setting playlist charset to UTF-8
2013-02-24 12:37:59 WARNING: You enabled the YouTube feature, which allows you
                             to watch YouTube videos on your UPnP device!
                             Please check http://www.youtube.com/t/terms
                             By using this feature you may be violating YouTube
                             service terms and conditions!

2013-02-24 12:37:59    INFO: Configuration check succeeded.
2013-02-24 12:37:59    INFO: Initialized port: 50500
2013-02-24 12:37:59    INFO: Server bound to: 192.168.1.4
2013-02-24 12:37:59    INFO: Adding HTTP header "transferMode.dlna.org: Streaming"
2013-02-24 12:37:59    INFO: Adding HTTP header "contentFeatures.dlna.org: DLNA.ORG_OP=01;DLNA.ORG_CI=0;DLNA.ORG_FLAGS=025000 00000000000000000000000000"
2013-02-24 12:38:00    INFO: MediaTomb Web UI can be reached by following this link:
2013-02-24 12:38:00    INFO: http://192.168.1.4:50500/

Yeah I downgraded to mediatomb-0.12.1-16.fc17.x86_64 as well - fixes ignoring port (from both commandline option and config file) - and it also makes my samsung TV work.

(I did keep the newer /usr/lib/systemd/system/mediatomb.service file though since it actually picks up on /etc/mediatomb.conf interface setting.

I also upgraded to mediatomb-0.12.1-22.fc17.x86_64 from koji and that version appears to work fine.

it indeed behaves strangely, only some bits get ignored?

<ui enabled="no" show-tooltips="yes" poll-when-idle="no" poll-interval="2">
      <accounts enabled="no" session-timeout="60">
        <account user="mediatomb" password="mediatomb"/>
      </accounts>

mediatomb enforces authentication no matter what in the config file
fedora 17
mediatomb-0.12.1-23.fc17.x86_64

Currently awaiting bunding exception for libupnp from FPC.

mediatomb-0.12.1-25.fc19.20120403gitb66dc1 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/mediatomb-0.12.1-25.fc19.20120403gitb66dc1

mediatomb-0.12.1-25.fc18.20120403gitb66dc1 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mediatomb-0.12.1-25.fc18.20120403gitb66dc1

mediatomb-0.12.1-25.fc17.20120403gitb66dc1 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/mediatomb-0.12.1-25.fc17.20120403gitb66dc1

Update mediatomb-0.12.1-25.fc18.20120403gitb66dc1 works for me!

Package mediatomb-0.12.1-25.fc19.20120403gitb66dc1:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mediatomb-0.12.1-25.fc19.20120403gitb66dc1'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-4901/mediatomb-0.12.1-25.fc19.20120403gitb66dc1
then log in and leave karma (feedback).

mediatomb-0.12.1-25.fc18.20120403gitb66dc1 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

mediatomb-0.12.1-25.fc17.20120403gitb66dc1 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

mediatomb-0.12.1-25.fc19.20120403gitb66dc1 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.