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 in the command? Is there somewhere a default option defined for MCC? -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
