Bug 5617

Summary:	Ardour cannot be started with a vague error message
Product:	Mageia	Reporter:	Jehan Hysseo <jehan.marmottard>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	ardour 2.8.12 revision 1.mga2	CVE:
Status comment:
Attachments:	Ardour error window. Terminal output when running ardour2 Terminal output in English when running ardour2

Description Jehan Hysseo 2012-04-26 07:34:50 CEST

Description of problem
-----------------------

If I start ardour, I get an error message telling me that Jack could not be started with 2 hints which basically won't help anyone. See screenshot.

Version-Release number of selected component (if applicable):
Ardour 2.8.12 - 64 bits last version from package manager.

How reproducible
-----------------

Reproduced every time in my configuration, where I simply installed ardour from package manager.

Steps to Reproduce
-------------------

1. Install ardour.
2. Start it.
3. You get a "Session Control" window. Click "Start Audio Engine". 
4. Get the error message.

Expected result: ardour should run normally out of the box.

More
----

ardour.txt has the output when I start from terminal to get more details.

Comment 1 Jehan Hysseo 2012-04-26 07:35:57 CEST

Created attachment 2111 [details]
Ardour error window.

Comment 2 Jehan Hysseo 2012-04-26 07:36:49 CEST

Created attachment 2112 [details]
Terminal output when running ardour2

Comment 3 Jehan Hysseo 2012-04-26 07:39:12 CEST

Created attachment 2113 [details]
Terminal output in English when running ardour2

Attachment 2112 is obsolete: 0 => 1

Comment 4 Manuel Hiebel 2012-04-26 11:10:24 CEST

Well this is not a bug only a wrong conf, after this error message you can choose pulseaudio for the sound. But ardour works better with jackit. qjackctl is a wonderful interface for that.

Comment 5 Jehan Hysseo 2012-04-26 14:02:16 CEST

Hi,

I was considering this indeed as a configuration issue, which is therefore a distribution bug. But that's just terminology.
In any case, I found the reason. The user needed to be in the audio group to be allowed to run jack. Group management is definitely something which should be improved. :-/

Anyway I'll close this ticket.

Status: NEW => RESOLVED
Resolution: (none) => INVALID