Ok, so the solution should be : 1. Automatically add the super user (the one who used to do sudo apt-get install) to the flumotion group during flumotion installation. 2. Add the "computer need to be restarted" notification as the current running session will not be directly in the flumotion group. 3. Fix invalid file permission of the /etc/flumotion/* files where a flumotion group member cannot "read only" these files.
And for the upstream bug, why not adding: 1. A simple test to check if the config file is available with a GUI feedback. 2. Adding a copy/paste solution fo the command line that failed in the GUI -- flumotion can't start flumotion service https://bugs.launchpad.net/bugs/199637 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
