On 07/13/2012 01:33 AM, Brendan Jones wrote:
On 07/13/2012 10:17 AM, Jørn Lomax wrote:
On 07/13/2012 05:09 AM, Brian Monroe wrote:
Bug off the 7/12 iso:
I think liveuser was added to the jackuser and audio groups but the user
I created after install definately wasn't.
We should fix this, as nothing will be more frustrating to folks to have
them say "It was working fine until I installed it."
I added my user to the appropriate groups but I kept getting errors
trying to run qjackctl:
09:45:16.223 Patchbay deactivated.
09:45:16.224 Statistics reset.
09:45:16.227 Could not open ALSA sequencer as a client. ALSA MIDI
patchbay will be not available.
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed:
Permission denied
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
I checked and running it on the live spin doesn't give an error, but I
can start Jack fine after I acknowledge the error in qjackctl and press
the start button in the GUI. O.o weird.
There is no way for us to set the default user when the spin is
installed afik. This is set by anaconda at install, and we have no way
of knowing what the username is when someone installs the spin. We might
be able to cat the passwd file and get all usernames with a uuid > 1000,
but i would have to check with the spins team about what order things
are done in so that it's done at the first config, not install (which is
where the %post section in the kickstart is performed). I'll look into
it and see what i find out.
Not sure if this the approved way but you could put this in your %post
section:
for i in `users`; do usermod --groups audio,jackuser $i ; done;
Maybe this would work but any users created after the initial install
would not work properly either - with the resulting support problems.
In my Planet CCRMA installs I give access to rt scheduling to all users
but that would not be a solution that would be approved by Fedora
(security issues) - it should only be interactive users.
I think the only way in which this can be fixed once and for all is to
tie the rt permissions and memory locking to systemd so that only
interactive seats are assigned those privileges while the person has
control of the hardware (they would be dropped if, for example, we
switch users). Looks to me like the right tool but I have not tried to
design something that could be useful.
Maybe it would also be possible to use pam_script for this, and maybe it
is a better solution. I had to use it to do some clean up right before a
user logs in and right after it logs out and it works just fine for that
(pam_scripts is in review last time I checked, I built a local version
based on that spec file). I don't know what would be involved to modify
the pam setup as part of the install...
-- Fernando
_______________________________________________
music mailing list
music@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/music
