mythbuntu-bugs team mailing list archive

[Thomas Mashos <590741@xxxxxxxxxxxxxxxxxx>]

Thank you for your bug report. Are you still experiencing this issue on
your slave backend? I haven't seen this issue crop up elsewhere.

As for the comment on the mythtv logs. What is so private about the
logs? Is there something better we can do to resolve that issue for you?


** Changed in: mythbuntu
   Importance: Undecided => Medium

** Changed in: mythbuntu
       Status: New => Incomplete

-- 
/etc/mythtv/config.xml invalid on slave backend
https://bugs.launchpad.net/bugs/590741
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.

Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Incomplete

Bug description:
On my slave backend (0.23.0+fixes24879-0ubuntu0+mythbuntu2) /etc/mythtv/config.xml is completely invalid:

<Configuration>
  <UPnP>
    <MythFrontend>
      <DefaultBackend>
        <DBHostName>localhost</DBHostName>
        <DBUserName>mythtv</DBUserName>
        <DBPassword>nosxjyig</DBPassword>
        <DBName>mythconverg</DBName>
        <DBPort>0</DBPort>
      </DefaultBackend>
    </MythFrontend>
  </UPnP>
</Configuration>

Of course there is no mysql server on this slave backend and therefor the DBHostName is wrong, as is the password.

I'm really not sure how this file gets set up, but it was created/modified recently (not by me, directly):

-rw-rw---- 1 mythtv mythtv 327 2010-05-27 08:01 /etc/mythtv/config.xml

BTW: I would have used ubuntu-bug to report this but I find it totally unacceptable that it sends both my complete front and back end logs.  That is too much of a breach of my privacy, thanx.