Bug 269301

Summary:	Poor KDE integration
Product:	[Fedora] Fedora	Reporter:	Philip Ashmore <contact>
Component:	jack-audio-connection-kit	Assignee:	Andy Shevchenko <andy>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-09-03 15:26:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Philip Ashmore 2007-08-30 20:59:14 UTC

Description of problem:
I want to use JACK as the audio device

Version-Release number of selected component (if applicable):


How reproducible:
very

Steps to Reproduce:
1. Start Control Centre
2. Select Sound/Multimedia/Hardware/Select Audio Device/Jack Audio Connection Kit
3.
  
Actual results:
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.

Expected results:
I should be enjoying real time audio.

Additional info:
From the documentation it appears that the JACK daemon (jackd) should be started
somewhere - KDE startup maybe?

Comment 1 Andy Shevchenko 2007-09-03 15:26:24 UTC

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.

Comment 2 Philip Ashmore 2007-09-03 17:52:08 UTC

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
like artsd.

Now that would be good KDE integration.