On Mon, 2019-09-09 at 11:10 +0200, Ricardo Wurmus wrote: > Jesse Gibbons writes: > > > On Sat, 2019-08-31 at 14:17 +0200, Ricardo Wurmus wrote: > > > Hi Jesse, > > > > > > > under certain conditions; see the file COPYING for details > > > > JACK is running in realtime mode, but you are not allowed to > > > > use > > > > realtime scheduling. > > > > grep: /etc/security/limits.conf: No such file or directory > > > > Please check your /etc/security/limits.conf for the following > > > > line > > > > and correct/add it if necessary: > > > > @audio - rtprio 99 > > > > > > Why doesn’t /etc/security/limits.conf ekxist? Have you > > > reconfigured > > > your > > > system with the limits service that is suggested in the manual? > > > > > > > I added the pam-limits-service, reconfigured, and restarted but the > > issue persists. > > This is very strange and I can’t reproduce the problem :-/ > > Your configuration looks okay. > The attached system definition replicates this behavior in a VM. jackd works (jack -R -dalsa, or started by qjackctl) when I am root, but not when I am an unprivileged user.