[PlanetCCRMA] permission problems with recent jack update 0.109.2

Fernando Lopez-Lezcano nando at ccrma.Stanford.EDU
Wed Mar 19 12:55:02 2008


On Tue, 2008-03-18 at 19:08 -0400, Hector Centeno wrote:
> Ok, I created the file /etc/security/console.perms.d/51-default.perms
> containing this:
> 
> <firewire1>=/dev/dv1394-0
> <firewire2>=/dev/raw1394
> 
> <console> 0600 <firewire1> 0600 root
> <console> 0600 <firewire2> 0600 root
> 
> And that solved the problem with Jack 109.2. Still I don't understand
> why the previous version didn't need this.

I think I know, the Fedora jack package has that built in. I have to
include that in my jack package as well. Later today.....

-- Fernando


> On Tue, Mar 18, 2008 at 6:41 PM, Hector Centeno <hcengar@gmail.com> wrote:
> > Thanks Fernando,
> >
> >  I'll try that. For now I would like to report that downgrading to the
> >  previous version works and I can get Jack with Freebob running
> >  normally. The strange thing is that right after downgrading I tried to
> >  start Jack and got the same error as with 109.2 but after rebooting it
> >  worked fine! I then reinstalled 109.2 and rebooted but it didn't work,
> >  same error.
> >
> >  Hector
> >
> >  On Tue, Mar 18, 2008 at 6:11 PM, Fernando Lopez-Lezcano
> >  <nando@ccrma.stanford.edu> wrote:
> >  > On Tue, 2008-03-18 at 17:59 -0400, Hector Centeno wrote:
> >  >  > Fernandom
> >  >  >
> >  >  > Thanks for your reply. I found the same suggestion by googling the
> >  >  > problem but setting the permissions this way would have to be redone
> >  >  > after each boot. I tried the solutions suggested at the Freebob FAQ
> >  >  > page ( http://freebob.sourceforge.net/index.php/UdevConfiguration )
> >  >  > but none of them work with Fedora 8. I think I'll be downgrading for
> >  >  > now.
> >  >
> >  >  The permissions can be set permanently by
> >  >  editing /etc/security/console.perms (and/or associated files).
> >  >
> >  >  I don't have handy the files for fc8 to look around. But it involves
> >  >  setting up a new class of devices and defining which permissions to use
> >  >  for both "logged in" and "logged out" conditions.
> >  >
> >  >  > On Tue, Mar 18, 2008 at 5:11 PM, Fernando Lopez-Lezcano
> >  >  > <nando@ccrma.stanford.edu> wrote:
> >  >  > >
> >  >  > > On Tue, 2008-03-18 at 16:08 -0400, Hector Centeno wrote:
> >  >  > >  > Hello,
> >  >  > >  >
> >  >  > >  > I just updated Jack to the recent 0.109.2 and I can't get it to start
> >  >  > >  > using FreeBob. I get this in the messages window:
> >  >  > >  >
> >  >  > >  > Freebob using Firewire port 0, node -1
> >  >  > >  > Ieee1394Service::initialize: Could not get 1394 handle: Permission denied
> >  >  > >  > Is ieee1394 and raw1394 driver loaded?
> >  >  > >  > Fatal (devicemanager.cpp)[68] initialize: Could not initialize
> >  >  > >  > Ieee1349Service object
> >  >  > >  > Fatal (freebob.cpp)[69] freebob_new_handle: Could not initialize device manager
> >  >  > >  > LibFreeBoB ERR: cannot create libfreebob handle
> >  >  > >  > FreeBoB ERR: FREEBOB: Error creating virtual device
> >  >  > >  > cannot load driver module freebob
> >  >  > >  >
> >  >  > >  > Starting Jack using the same command but as root works fine. The
> >  >  > >  > previous version of Jack didn't have this problem.
> >  >  > >
> >  >  > >  Check the permissions of the /dev/*1394* files first... I think that
> >  >  > >  would be the difference between non-root and root based on the messages
> >  >  > >  you posted. But I can't see how the jack upgrade alone would change
> >  >  > >  that...
> >  >  > >
> >  >  > >  -- Fernando
> >  >  > >
> >  >  > >
> >  >  > >