sweet Dude !! -- thanks KTRT- radio 97.5 fm
Dov On Sun, Feb 8, 2009 at 6:59 AM, Yann Papouin <yann.papo...@gmail.com> wrote: > 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 direct subscriber > of the bug. > > Status in Flumotion Streaming Server: New > Status in "flumotion" source package in Ubuntu: New > > Bug description: > Binary package hint: flumotion > > When trying to start the local flumotion service, during flumotion startup, > I get this error dialog: > > " > Could not start manager > > The command that failed was: > /usr/sbin/flumotion -C /tmp/tmp1Uue8r.flumotion/etc -L > /tmp/tmp1Uue8r.flumotion/var/log -R /tmp/tmp1Uue8r.flumotion/var/run start > manager admin > The command exited with an exit code of 1. > " > > This is in Ubuntu Gutsy. The flumotion package version is 0.4.2-2. > -- 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
