can't start JACK with real-time scheduling even when in audio group

Bug #1693024 reported by Adam Dingle
This bug report is a duplicate of:  Bug #1627769: limits.conf not applied. Edit Remove
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
jackd2 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I'm running Ubuntu 17.04. I've installed jack2 and have added myself to the 'audio' group as suggested at

  http://jackaudio.org/faq/linux_rt_config.html

But when I start JACK it reports

Tue May 23 16:10:24 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: Operation not permitted)
Tue May 23 16:10:24 2017: ERROR: AcquireSelfRealTime error

I am in the 'audio' group in /etc/group:

adam:~$ grep audio /etc/group
audio:x:29:pulse,adam
adam:~$

(I restarted the machine after adding myself to this group.)

'ulimit' isn't showing real-time priority privileges for me:

adam:~$ ulimit -a | grep real
real-time priority (-r) 0
adam:~$

The file /etc/security/limits.d/audio.conf looks like this:

===

# Provided by the jackd package.
#
# Changes to this file will be preserved.
#
# If you want to enable/disable realtime permissions, run
#
# dpkg-reconfigure -p high jackd

@audio - rtprio 95
@audio - memlock unlimited
#@audio - nice -19

===

Adam Dingle (adam-yorba)
summary: - can't start JACK with real-time schedule even when in audio group
+ can't start JACK with real-time scheduling even when in audio group
Revision history for this message
Adam Dingle (adam-yorba) wrote :

I believe this problem may have to with Ubuntu's recent transition to systemd. Apparently systemd completely ignores /etc/security/limits*.

description: updated
Revision history for this message
Adam Dingle (adam-yorba) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in jackd2 (Ubuntu):
status: New → Confirmed
Revision history for this message
Amir reza Irani ali poor (amir1376irani) wrote :

exactly same problem
ubuntu 18.04.03

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.