Bug 1178246 - Jackd unable to start with realtime scheduling, causing ardour et al to fail
Summary: Jackd unable to start with realtime scheduling, causing ardour et al to fail
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: jack-audio-connection-kit
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brendan Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-03 03:11 UTC by Lars Kellogg-Stedman
Modified: 2015-12-02 16:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 06:47:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lars Kellogg-Stedman 2015-01-03 03:11:46 UTC
Description of problem:

Attempting to start jackd with realtime scheduling (the '-R' flag) results in the follow errors:

Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
[...]
Cannot use real-time scheduling (RR/20)(1: Operation not permitted)
AcquireSelfRealTime error

This prevents applications that rely on jack, such as "ardour", to fail.

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

jack-audio-connection-kit-1.9.10-1.fc21.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Run 'jackd -R -d alsa'
2. Sadness

Additional info:

I have read through /usr/share/doc/jack-audio-connection-kit/README.Fedora.  My user is a member of the "jackuser" and "audio" groups:

$ groups
lars wheel audio mock virt jackuser docker

There are limits set in /etc/security/limits.d/95-jack.conf:

@jackuser - rtprio 99
@jackuser - memlock 4194304

And they are active:

$ ulimit -r
99
$ ulimit -l
4194304

Comment 1 Chris Ward 2015-03-17 10:05:16 UTC
Any progress here? Workarounds?

Comment 2 Lars Kellogg-Stedman 2015-03-17 12:57:58 UTC
Nope, not a peep.  A colleague suggested asking the folks behind the "Fedora Jam" audio spin (https://fedoraproject.org/wiki/Fedora_Jam_Audio_Spin), but I haven't pursued that yet myself.

Comment 3 Fedora End Of Life 2015-11-04 13:08:37 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-12-02 06:47:23 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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