Bug 1377844

Summary:	SELinux is overriding locked memory limit setting in 95-jack.conf
Product:	[Fedora] Fedora	Reporter:	Benjamin Xiao <ben.r.xiao>
Component:	jack-audio-connection-kit	Assignee:	Brendan Jones <brendan.jones.it>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	24	CC:	ben.r.xiao, brendan.jones.it, nphilipp, oget.fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-22 03:06:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Benjamin Xiao 2016-09-20 18:24:27 UTC

Description of problem:
I have Jack and Ardour installed on Fedora 24. Installing Jack automatically puts a file called /etc/security/limits.d/95-jack.conf which specifies:

@jackuser - memlock 4194304

which is supposed to increase my locked memory limit so I can get real time audio scheduling. However, when SELinux is in enforcing mode ulimit -l returns 64 instead of 4194304. When SELinux is in permissive mode, everything works correctly.

Now a value of 64 will allow JACK itself to run in real time mode, but not additional apps like alsa_in and alsa_out, which I need to attach my USB mics. I'd like to be able to use JACK without disabling SELinux.

Version-Release number of selected component (if applicable):
jack-audio-connection-kit 1.9.10-5.fc24

How reproducible:
Everytime.

Steps to Reproduce:
1. Install jack-audio-connection-kit
2. Add user to jackuser group
3. Set selinux to be permissive on boot by editing /etc/sysconfig/selinux
4. Reboot. Notice that ulimit -l correctly returns 4194304.
5. Reset selinux to be enforcing on boot
6. Reboot. Notice that ulimit -l now returns 64, which is not enough locked memory for JACK and alsa_in

Actual results:
ulimit -l returns 64, showing that the setting in 95-jack.conf isn't taking into effect

Expected results:
ulimit -l returns 4194304

Additional info:

Comment 1 Orcan Ogetbil 2016-09-20 22:52:46 UTC

I'm not sure if this is a jack bug.

Which terminal are you using for the command "ulimit -l"? Also could you try a different tty (like ctrl+alt+f2) to run "ulimit -l"?

Comment 2 Benjamin Xiao 2016-09-21 08:00:25 UTC

I am using Gnome Terminal to run ulimit -l. If I run in a different tty I get the correct value of 4194304 oddly enough.


If I set SELinux to be permissive, then ulimit -l is 4194304 even in Gnome Terminal. Ideally I'd like to be able to run alsa_in in Gnome Terminal instead of another tty.

Comment 3 Orcan Ogetbil 2016-09-22 03:06:17 UTC

I see. This is a known problem with Gnome Terminal. I am merging this bug with an existing one. Thank you for the report!

*** This bug has been marked as a duplicate of bug 1364332 ***

Comment 4 Benjamin Xiao 2016-09-22 05:34:53 UTC

Thanks Orcan!