Bug 17883 - Ardour not configuring realtime JACK during installation.
Summary: Ardour not configuring realtime JACK during installation.
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: http://jackaudio.org/faq/linux_rt_con...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-05 15:02 CET by Krzysztof Setlak
Modified: 2016-03-06 23:25 CET (History)
1 user (show)

See Also:
Source RPM: ardour-4.7.0-2.mga6.i586.rpm
CVE:
Status comment:


Attachments

Description Krzysztof Setlak 2016-03-05 15:02:43 CET
Description of problem:
I think the package should configure the realtime JACK operation when it's installed. Normally it's not possible to start a session in Ardour. This issue is described here: http://jackaudio.org/faq/linux_rt_config.html

Errors/Messages:
ERROR: JACK: Cannot use real-time scheduling (RR/5)(1: Operation not permitted)
ERROR: JACK: JackClient::AcquireSelfRealTime error
ERROR: LADSPA: cannot load module "/usr/lib/ladspa/gsm_1215.so" (/usr/lib/ladspa/gsm_1215.so: undefined symbol: gsm_destroy)
ERROR: LADSPA: cannot load module "/usr/lib/ladspa/gsm_1215.so" (/usr/lib/ladspa/gsm_1215.so: undefined symbol: gsm_destroy)
WARNING: Video-monitor 'xjadeo' was not found. Please install http://xjadeo.sf.net/ (a custom path to xjadeo can be specified by setting the XJREMOTE environment variable. It should point to an application compatible with xjadeo's remote-control interface 'xjremote').

see also http://manual.ardour.org/video-timeline/setup/
INFO: Loaded mixer bindings from /etc/ardour4/mixer.bindings
INFO: Loading bindings from /etc/ardour4/mnemonic-us.bindings
Loading menus from /etc/ardour4/ardour.menus
ERROR: JACK: Cannot create thread res = 1


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


How reproducible: easily on any hardware


Steps to Reproduce:
1. Install Ardour from official repo.
2. Run it from a terminal emulator.
3. Try to start a new project and when a message saying something like "Could not create session in "/home/username/Ardour Projects/asd" " comes up, investigate terminal for error messages pasted above.
Comment 1 Barry Jackson 2016-03-05 15:20:34 CET
Did you read and follow the README.urpmi during install?
If not look at the following now on your machine:
/usr/share/doc/ardour/README.Mageia
Please report back if this solves your issue.
Also please do not try to use the MCC method to add yourself to the groups, as this is currently broken in Cauldron - use the terminal instead.

CC: (none) => zen25000

Comment 2 Krzysztof Setlak 2016-03-06 14:59:27 CET
I understand, it's not a big difficulty, this problem is solvable in 5 minutes with Google. My point is that I think it should happen automatically, so that a layman can just install it and run the program without additional steps to perform.
I personally use Mageia only since not long ago, so it never crossed my mind to look at any documentation and I don't even know where README.urpmi can be found, sorry :P
Comment 3 Barry Jackson 2016-03-06 23:25:54 CET
(In reply to Krzysztof Setlak from comment #2)
> I understand, it's not a big difficulty, this problem is solvable in 5
> minutes with Google. My point is that I think it should happen
> automatically, so that a layman can just install it and run the program
> without additional steps to perform.

Yes I agree, but it's not that simple.
You may wish to read this:
https://bugs.mageia.org/show_bug.cgi?id=14426

> I personally use Mageia only since not long ago, so it never crossed my mind
> to look at any documentation and I don't even know where README.urpmi can be
> found, sorry :P

README.urpme is displayed during installation of ardour irrespective of the method of installation, so you must have accepted it without reading.
README.mageia is a copy of it which will normally open in a text editor when clicked, otherwise it is the same.

OK - since there is not actually a bug here I am closing as wontfix.

Feel free to reopen if you can offer a better workable solution.

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


Note You need to log in before you can comment on or make changes to this bug.