[PlanetCCRMA] Troubles with Jack on Fedora 25

Fernando Lopez-Lezcano nando at ccrma.Stanford.EDU
Thu Jan 26 09:25:27 PST 2017

On 01/26/2017 06:58 AM, Yoann LE BARS wrote:
> Hello everybody out there!


> 	I have recently upgraded my workstation from Fedora 24 to Fedora 25.
> Unfortunately, I cannot use Jack with it: when launching Jack with
> QJackCtl, it indicates that Jack is running,

Meaning that you can actually see the input and output ports of the 
soundcard in the connections window?

>but I cannot load the
> modules “jack-sink” and “jack-out” for Pulseaudio. Also, when I try to
> run Qsynth, it indicates it cannot connect to Jack.

This would suggest that jack is not actually running.

> 	Well, first I need to diagnose what the trouble is, but I do not really
> have an idea on how to do this. Can someone help me?
> 	Anyway, here are the packages related to jack that are installed on my
> workstation:
> $ rpm -qa | grep jack
> jack-audio-connection-kit-1.9.10-5.fc24.i686
> pulseaudio-module-jack-10.0-2.fc25.x86_64
> jack-rack-1.4.7-19.fc24.x86_64
> jack-audio-connection-kit-1.9.10-5.fc24.x86_64
> vlc-plugin-jack-3.0.0-16.20170103git8d997bc.fc25.x86_64
> ardour5-audiobackend-jack-5.4.0-4.fc25.x86_64
> jack-audio-connection-kit-dbus-1.9.10-5.fc24.x86_64
> zynjacku-6-13.fc25.x86_64
> mpg123-plugins-jack-1.23.8-2.fc25.x86_64
> alsa-plugins-jack-1.1.1-1.fc25.x86_64
> jack-audio-connection-kit-example-clients-1.9.10-5.fc24.x86_64
> jack_capture-0.9.69-1.fc25.x86_64
> qjackctl-0.4.4-1.fc25.x86_64
> bio2jack-0.9-15.fc24.x86_64
> 	Well, you can notice there are some inconsistencies, as
> “jack-audio-connection-kit”, “jack-rack”,
> “jack-audio-connection-kit-dbus” and “bio2jack” are for Fedora 24, while
> the others packages are for Fedora 25. I do not know how to solve this.

I would start by removing (if you were not using it) the old version of 
jack-audio-connection-kit-dbus. Or try to upgrade it explicitly and see 
why it was not updated.

As to how to diagnose,

- is the soundcard there?
   "cat /proc/asound/cards" should tell you.

- start jackd from a terminal with minimal arguments and see what happens:
   jackd -d alsa -d hw:xxx
   (replace xxx with the ordinal number of the card or its short name as 
printed by cat /proc/asound/cards).

See what happens and what error messages are printed (and/or post them 
to the list). How to proceed depends on what jackd prints...

-- Fernando

More information about the PlanetCCRMA mailing list