default.pen permissions issue

[Murray Cumming]

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.

[Murray Cumming (murrayc)]

The problem still exists on Hardy. Starting from the command line shows that the problem is a missing default.pem file:

murrayc@murrayc-laptop:~$ /usr/sbin/flumotion -C /tmp/tmp3DGe09.flumotion/etc -L /tmp/tmp3DGe09.flumotion/var/log -R /tmp/tmp3DGe09.flumotion/var/run start manager admin
DEBUG [13188] manager May 08 13:52:23 Setting name to admin based on path (flumotion/manager/main.py:240)
DEBUG [13188] setup May 08 13:52:23 registry paths: /usr/lib/flumotion/python (flumotion/common/setup.py:49)
DEBUG [13188] setup May 08 13:52:23 registering package path: /usr/lib/flumotion/python (flumotion/common/setup.py:51)
INFO [13188] manager May 08 13:52:24 Starting manager 'admin' (flumotion/manager/main.py:255)
DEBUG [13188] manager May 08 13:52:24 Running Flumotion version 0.4.2 (flumotion/manager/main.py:258)
DEBUG [13188] manager May 08 13:52:24 Running against Twisted version 2.5.0 (flumotion/manager/main.py:261)
DEBUG [13188] registry May 08 13:52:24 instantiating registry (flumotion/common/registry.py:1329)
INFO [13188] registry May 08 13:52:24 Parsing registry: /home/murrayc/.flumotion/registry.xml (flumotion/common/registry.py:1017)
DEBUG [13188] default May 08 13:52:24 Parsing XML from '/home/murrayc/.flumotion/registry.xml' (flumotion/common/fxml.py:84)
DEBUG [13188] registry May 08 13:52:24 previously scanned registry paths: /usr/lib/flumotion/python (flumotion/common/registry.py:1233)
DEBUG [13188] registry May 08 13:52:24 registry paths are still the same (flumotion/common/registry.py:1244)
DEBUG [13188] registry May 08 13:52:24 /usr/lib/flumotion/python not changed since last registry parse (flumotion/common/registry.py:1258)
DEBUG [13188] registry May 08 13:52:24 Adding bundle colorbalance-effect (flumotion/common/registry.py:1119)
DEBUG [13188] registry May 08 13:52:24 Adding bundle http-server-admin-gtk (flumotion/common/registry.py:1119)
DEBUG [13188] registry May 08 13:52:24 Adding bundle htpasswdcrypt-component (flumotion/common/registry.py:1119)
DEBUG [13188] registry May 08 13:52:24 Adding bundle muxers (flumotion/common/registry.py:1119)
DEBUG [13188] registry May 08 13:52:24 Adding bundle bttv-admin-gtk (flumotion/common/registry.py:1119)
DEBUG [13188] registry May 08 13:52:24 Adding bundle base-plugs-lifecycle (flumotion/common/registry.py:1119)
DEBUG [13188] ...

[Murray Cumming (murrayc)]

Or that the /etc/flumotion/default.pem is there with the wrong permissions.

[dov (dashford)]

hoy is this fixed?? i am using ubuntu 8.04 and have flumotion intstalled from apt sources ,I need to make a streamer for ktrt radio and I would like to use flumotion for this if i can fix or figure out the error ===

"The command that failed was:
/usr/local/sbin/flumotion -C /tmp/tmpBWEhMD.flumotion/etc -L /tmp/tmpBWEhMD.flumotion/var/log -R /tmp/tmpBWEhMD.flumotion/var/run start manager admin
The command exited with an exit code of 1." from the GUI

please help me :)

[dov (dashford)]

how is it fixed I mean

[Thomas Vander Stichele (thomasvs)]

dov,

you're not running it from a package, but from a tarball you built yourself by hand.

I can see this because you pasted a line that got executed where flumotion is in /usr/local/sbin instead of /usr/sbin

[dov (dashford)]

that must be where APT put it i guess ? any ideas i was doind the install
from the web site for 8.04 -I added the APT repositorys as the page says

the PATH = /usr/local/sbin in ubuntu 8.04
that is where it will search also for binarys
PS

i have not compiled it from source though i just let APT do its thing
On Sun, Nov 9, 2008 at 7:16 AM, Thomas Vander Stichele <<email address hidden>
> wrote:

> dov,
>
> you're not running it from a package, but from a tarball you built
> yourself by hand.
>
> I can see this because you pasted a line that got executed where
> flumotion is in /usr/local/sbin instead of /usr/sbin
>
> --
> 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.
>

[Yann Papouin (yann-papouin)]

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

[dov (dashford)]

sweet Dude !! -- thanks

KTRT- radio 97.5 fm

Dov

On Sun, Feb 8, 2009 at 6:59 AM, Yann Papouin <email address hidden> 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.
>

[Thomas Vander Stichele (thomasvs)]

Yann,

why do you need 1. and 2. exactly ?

As for 3, yes, in the rpm packaging we changed it to be 0640/0750 flumotion:flumotion

[Yann Papouin (yann-papouin)]

I'm thinking these steps as a "Desktop user".

I chose to install a streaming service. In the flumotion documentation, after installation it says to start :
Application → Sound & Video → Flumotion Streaming Server Administration

Currently this is not possible to start a new manager and connect to it because the user has no permission to access /etc/flumotion.
The flumotion folder owner is : USER : flumotion GROUP : flumotion.

So, as only flumotion GROUP and USER can read these configuration files, I'm adding the desktop user to this group (step 1) and restarting (step 2) my computer (only restarting the gnome session is Ok but there is no dialog for this whereas there is already the "Restart computer" one with the update-manager process).

and the step 3 is just a fix.

That's what I have done for my server.

[Thomas Vander Stichele (thomasvs)]

Ah, know I get it.

I think a better fix is to upgrade - when we realized this use case had a problem we changed it so that the wizard creates a separate .pem file.

If you add all this machinery and force users to reboot now just for this bug, it sounds like a huge effort in a direction that's not going to be needed after upgrading.

[dread (dreadlokeur)]

Hello all.
I want install Flumotion but i have a problem when install the paquet...
(I use jaunty 9.4)

dread@Dread-Pc:~$ sudo apt-get install flumotion
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les NOUVEAUX paquets suivants seront installés :
  flumotion
0 mis à jour, 1 nouvellement installés, 0 à enlever et 4 non mis à jour.
Il est nécessaire de prendre 0o/599ko dans les archives.
Après cette opération, 3961ko d'espace disque supplémentaires seront utilisés.
Sélection du paquet flumotion précédemment désélectionné.
(Lecture de la base de données... 164543 fichiers et répertoires déjà installés.)
Dépaquetage de flumotion (à partir de .../flumotion_0.4.2-3.1ubuntu1_amd64.deb) ...
Traitement des actions différées (« triggers ») pour « man-db »...
Paramétrage de flumotion (0.4.2-3.1ubuntu1) ...
I: Saving backup of default manager configuration...
`/etc/flumotion/managers/default/planet.xml' -> `/etc/flumotion/managers/default/planet.pre-0.4.1-backup.xml'
I: Upgrading configuration...
`/etc/flumotion/managers/default/planet.xml' -> `/tmp/flumotion.postinst.gUeiFCJmTS/planet.post-0.4.1.xml'
`/tmp/flumotion.postinst.gUeiFCJmTS/planet.post-0.4.1.xml' -> `/etc/flumotion/managers/default/planet.xml'
détruire le répertoire: `/tmp/flumotion.postinst.gUeiFCJmTS'
 * Restarting Flumotion Streaming Server flumotion [fail]

dread@Dread-Pc:~$

When flumotion finish install, it want Restarting server but FAIL...

I launch flumotion streaming server administration (applications/son et vidéo/flumotion streaming...) But don't work....

I have add my user (dread) to flumotion group: sudo adduser dread flumotion and a i have modify permission to /etc/flumotion:
dread@Dread-Pc:~$ cd /etc/
dread@Dread-Pc:/etc$ sudo chmod -R 777 flumotion

and a test start flumotion with:
dread@Dread-Pc:/etc$ sudo flumotion start

BUT:

Traceback (most recent call last):
  File "/usr/bin/flumotion-manager", line 45, in <module>
    boot.boot(PROGRAM_PATH, gst=False)
  File "/usr/lib/flumotion/python/flumotion/common/boot.py", line 189, in boot
    main = reflect.namedAny(path)
  File "/usr/lib/flumotion/python/flumotion/twisted/reflect.py", line 49, in namedAny
    topLevelPackage = __import__(trialname)
  File "/usr/lib/python2.6/ihooks.py", line 407, in import_module
    m = self.load_tail(q, tail)
  File "/usr/lib/python2.6/ihooks.py", line 458, in load_tail
    m = self.import_it(head, mname, m)
  File "/usr/lib/python2.6/ihooks.py", line 497, in import_it
    m = self.loader.load_module(fqname, stuff)
  File "/usr/lib/python2.6/ihooks.py", line 272, in load_module
    m = self.hooks.load_source(name, filename, file)
  File "/usr/lib/python2.6/ihooks.py", line 170, in load_source
    return imp.load_source(name, filename, file)
  File "/usr/lib/flumotion/python/flumotion/manager/main.py", line 33, in <module>
    from flumotion.manager import manager
  File "/usr/lib/python2.6/ihooks.py", line 411, in import_module
    self.ensure_fromlist(m, fromlist)
  File "/usr/lib/python2.6/ihooks.py", line 476, in ensure_fromlist
    submod = self.import_it(sub, subname, m)
  File "...

[Thomas Vander Stichele (thomasvs)]

dread: this bug is the wrong place to post your bug. Please post a separate bug for your issue.

Your issue is resolved in upstream svn in commit 7960 on the flumotion-0.4 branch:
https://code.fluendo.com/flumotion/trac/changeset/7960

It is recommended that the package maintainer include that specific patch into the package until a new release is made.

[dov (dashford)]

Dov Ashford looked for you on MyLife(TM) but you weren't there.
Please confirm you know Dov so we can connect you.

Do You Know Dov?

YES - Connect with Dov, and see who's searching for you
http://smtp26.mail.reunion.com:80/track?type=click&mailingid=172333&messageid=14100&databaseid=1238061976&serial=1228211825&<email address hidden>&userid=185910&extra=&&&2002&&&http://www.mylife.com/showInviteRegistration.do?uid=375793750&<email address hidden>

NO - I don't know Dov http://smtp26.mail.reunion.com:80/track?type=click&mailingid=172333&messageid=14100&databaseid=1238061976&serial=1228211825&<email address hidden>&userid=185910&extra=&&&2000&&&http://www.mylife.com/showInviteRegistration.do?unsub=true&<email address hidden>&uid=375793750

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

MyLife - Find everyone. All in one place.(TM)

You received this email because a MyLife member sent an invitation to
this email address. If you do not know this member or do not want to receive
future invitations from them, click the "NO" link above.

For assistance, please refer to our FAQ or Contact Us:
http://smtp26.mail.reunion.com:80/track?type=click&mailingid=172333&messageid=14100&databaseid=1238061976&serial=1228211825&<email address hidden>&userid=185910&extra=&&&2001&&&http://help.mylife.com/

Our Address: 2118 Wilshire Blvd., Box 1008, Santa Monica, CA 90403-5784

Copyright (c) 2009 MyLife.com, Inc. All Rights Reserved.

[Jan Urbański (wulczer)]

There are two issues mentioned here, one is Python 2.6 compatibility and the other is usage of bash-specific constructs that fail is the system shell is not bash (Ubuntu uses dash for instance).

Both are now fixed and a prerelase is available, see https://bugs.launchpad.net/ubuntu/+source/flumotion/+bug/319204 for details.

[dov (dashford)]

                                                                                                                                    From: Dov Avatar: Guest_dovnix To: Bug Hey Bug,Dov has added you as a friend on IMVU. Is Dov your friend? Yes &nbsp; No Please respond or Dov may think you said no :) IMVU is the world's greatest 3D chat! Dress up your Avatar with 3D clothes. Chat with your friends &amp; meet new ones. Decorate your own 3D Room with furnitur
 e. FREE to download &amp; use! http://www.imvu.com Copyright &copy; 2009 IMVU, Inc. 411 High Street, Palo Alto, CA 94301. This email was sent via IMVU by Dov (<email address hidden>) to <email address hidden>. If you want to prevent any future emails from IMVU, you can remove yourself by pointing your web browser to http://www.imvu.com/catalog/web_nonregisteredoptout.php?code=8d203e&<email address hidden>. Your unsubscribe confirmation code is 8d203e

[Loïc Minier (lool)]

I did an install of flumotion and upgraded to 0.6.1-1 which will soon be available in lucid, and didn't see any permission issue:
# ls -la /etc/flumotion
drwxr-x--- 4 flumotion flumotion 4096 2009-12-21 12:23 .
drwxr-xr-x 56 root root 4096 2009-12-21 16:48 ..
lrwxrwxrwx 1 flumotion flumotion 11 2009-12-21 12:23 9f129ada -> default.pem
-rw------- 1 flumotion flumotion 1514 2009-12-21 12:23 default.pem
drwxr-xr-x 3 flumotion flumotion 4096 2009-12-21 12:22 managers
drwxr-xr-x 2 flumotion flumotion 4096 2009-12-22 13:24 workers

Could you please try 0.6.1-1 when it appears and confirm that this issue is still present for you?

[Loïc Minier (lool)]

NB: .deb packaging also sets up flumotion user/group and permissions of /etc; not sure why it went wrong here.

0.6.1-1 will also fix the python2.6 support issue reported here