[Slackbuilds-users] Jack-rack make failure

B Watson yalhcru at gmail.com
Wed Mar 14 22:08:18 UTC 2018

On 3/14/18, x80 <x80 at telus.net> wrote:

> Jack2 is the optional dependency for qjackctl. Maybe I'll remove jack2
> and reinstall jack1.

In theory, at least, you should be able to install jack1, compile stuff
against it, then replace jack1 with jack2 without recompiling anything
else. It's supposed to be an API-compatible drop-in replacement. Not
sure how well this works in practice though.

> I see alsa is routed to pulseaudio in /etc/asound.conf. That scares me.
> I was content with only alsa.

If you configure jackd to use the hardware (device names beginning with
hw:), it won't get routed to pulse. However jackd will refuse to start
if pulse is already using the device...

My solution to the pulseaudio thing is to log in as root and:

mv /etc/asound.conf /etc/asound.conf.orig
chmod -x /usr/bin/pulseaudio
killall pulseaudio

...and kill/restart any already-running applications that might be
using pulse (which would include KDE, if you run that). This will get
you 14.1-like behaviour. However I'm not sure whether the latest firefox
versions will be able to make sound without pulseaudio (I'm running an
old 'insecure' version, with javascript disabled on 99.9% of the web,
and no flash plugin installed, and it works fine).

Anyway you can restore the default 14.2 behaviour:

mv /etc/asound.conf.orig /etc/asound.conf
chmod a+x /usr/bin/pulseaudio

...I highly recommend *not* running anything else when you're using jack,
anyway. Even better would be to use a dedicated machine for jack stuff
and nothing else (where you can leave pulse disabled always).

I've considered adding this info to the jack-audio-connection-kit README,
but I suspect I'd encounter resistance from the "use a clean Slackware
install" crowd...

More information about the SlackBuilds-users mailing list