mythbuntu-bugs team mailing list archive

[MarcRandolph <mrand@xxxxxxxxx>]

Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket.  If I understand correctly, you're saying that operating MCC on
a slave backend doesn't change the functions operating on the master
backend - is that correct?

If so, that is the expected behavior.  To my knowledge, MCC does not
currently does not have the ability to communicate between, or even
knowledge of, any machine other than the one it is presently running on.
Perhaps it could be argued that since the role of this machine that of
something other than a master-frontend, most options (such as this one)
should be disabled.  The MCC developers will have to comment on that as
it is a feature request.

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

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

-- 
Mythbuntu Control Centre Error Popup in Mirobrige on Secondary Backend
https://bugs.launchpad.net/bugs/574744
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:
Mythbuntu 10.04
Master Backend
Secondary Backend/Frontend

Mirobridge is configured on Master Backend

- Open Mythbuntu Control Center on Secondary backend
- Click on Mirobridge tab
- Popup appears indicating the Mirobridge plugin will be disabled

It doesn't actually disable the plugin as it still runs correctly on the Master Backend server.