Red Hat Bugzilla – Bug 269301
Poor KDE integration
Last modified: 2007-11-30 17:12:14 EST
Description of problem:
I want to use JACK as the audio device
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start Control Centre
2. Select Sound/Multimedia/Hardware/Select Audio Device/Jack Audio Connection Kit
I got a message box stating:
Sound server informational message:
Error while initializing the sound driver:
Couldn't connect to jackd
The sound server will continue, using the null output device.
I should be enjoying real time audio.
From the documentation it appears that the JACK daemon (jackd) should be started
somewhere - KDE startup maybe?
My investigations show the jack could be used as kde sound engine only after
starting it in other way. In other words, you should to start jack via
initscripts or profile environment, or via QJackCtl (just install it by yum and
start under X session). After jack is started you may choose the Jack as middle-
end sound service.
P.S. If you have some information with another description of the KDE and jack
integration, you are welcome to reopen this bug. Also do not forget to add
yourself into jackuser group to gain realtime priority.
You can call me picky in this regard!
It just seems to me that the functionality that QJackCtl provides should be
available as a KDE kcontrol page with a build-in ability to manage jackd just
Now that would be good KDE integration.