On 14 June 2012 15:56:31 Brendan Jones wrote:
The autostart questions arise from me considering having a DBUS enabled qjackctl launch on login, configured to autostart jack (this requires modifying the users qjackctl settings in $HOME). Pulseaudio shold release the device and bridging should just work with the module-jackdbus-detect, although I'm finding it a bit flaky here. Of course none of this addresses selecting the default audio device etc etc.
It's touch-and-go for me too. I can do it on my laptop, but not my desktop. Either way, poorly functioning software isn't really our concern. This is Fedora, where we release things before they're 100% stable, so our users can help with testing and reporting bugs.
One thing that has been clouding the issue is that F17 is currently shipping a buggy Jack Control API due to a GCC 4.7 bug. This results in somewhat unintended behaviour for Jack, and has been known to cause Jackdbus to segfault. Whilst an update is imminent, I encourage anyone who's wants to play around with this to stuff now download the jack source RPM and compile it with -O0.
I've since been running this recompiled Jack from login with pulse-bridging using default pulse config for well on 16 hours now with no Xruns/messages, although I must admit have not done any hardcore audio work in that time.
Is your laptop F16 perchance?
Both my machines are. I think my issue on the desktop is either in SELinux or PAM, but I haven't had time to sort through it. I like to run my regular user accounts in the user_u context, which rarely works by default (although it's been getting better). As a huge generalization, it seems like the more an application is developed commercially, the less well it cooperates with SELinux.
Does anybody have advice on JACK + user_u in SELinux?
What's even worse is GCC bugs... because *everything* is involved.
Christopher.