I understand that Jamu can only be run on the backend, and that it is
unrelated to the hanging. But:
a) why does does it try to start on a machine that has never been installed as
a backend?
b) why does it show up during start of MCC, and complains about an -M option
that I have not even added i
Thanks for the very fast reaction.
another error this time:
Traceback (most recent call last):
File "/usr/bin/mythbuntu-control-centre", line 264, in summaryApply
plugin.user_scripted_changes(self.reconfigure_user[item])
File "/usr/share/mythbuntu/plugins/python/mysql_configuration.py", l
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/647367/+attachment/1634032/+files/Dependencies.txt
--
MCC hangs with Jamu-related error on frontend (new install)
https://bugs.launchpad.net/bugs/647367
You received this bug notification because you are a member of Ubun
Public bug reported:
Binary package hint: mythbuntu-control-centre
I have done a clean install of Mythbuntu 10.04 on an Acer Revo, and have
selected frontend-only during install.
When I launch MCC I get errors related to Jamu and backend:
t...@myth-front:~$ mythbuntu-control-centre
WARNING: Wit
