PipeWire and security limits warning


I have a system I’m testing PipeWire on, I am a member of the audio and pipewire groups and I have a conf file for PipeWire in /etc/security/limits.d and also the usual /etc/security/limits.conf. When I launch Ardour with pipewire-jack I’m still getting this:

How do I exorcize the demon?

Could you post the content of those configuration files, please?

# This file was installed by PipeWire project for its libpipewire-module-rt.so

# It's believed to be acceptable to have match rules that will never be true
# i.e. a group that does not exist.
@pipewire   - rtprio  95
@pipewire   - nice    -19
@pipewire   - memlock 4194304
# /etc/security/limits.conf
#Each line describes a limit for a user in the form:
#<domain>        <type>  <item>  <value>
#<domain> can be:
#        - a user name
#        - a group name, with @group syntax
#        - the wildcard *, for default entry
#        - the wildcard %, can be also used with %group syntax,
#                 for maxlogin limit
#        - NOTE: group and wildcard limits are not applied to root.
#          To apply a limit to the root user, <domain> must be
#          the literal username root.
#<type> can have the two values:
#        - "soft" for enforcing the soft limits
#        - "hard" for enforcing hard limits
#<item> can be one of the following:
#        - core - limits the core file size (KB)
#        - data - max data size (KB)
#        - fsize - maximum filesize (KB)
#        - memlock - max locked-in-memory address space (KB)
#        - nofile - max number of open file descriptors
#        - rss - max resident set size (KB)
#        - stack - max stack size (KB)
#        - cpu - max CPU time (MIN)
#        - nproc - max number of processes
#        - as - address space limit (KB)
#        - maxlogins - max number of logins for this user
#        - maxsyslogins - max number of logins on the system
#        - priority - the priority to run user process with
#        - locks - max number of file locks the user can hold
#        - sigpending - max number of pending signals
#        - msgqueue - max memory used by POSIX message queues (bytes)
#        - nice - max nice priority allowed to raise to values: [-20, 19]
#        - rtprio - max realtime priority
#        - chroot - change root to directory (Debian-specific)
#<domain>      <type>  <item>         <value>

#*               soft    core            0
#root            hard    core            100000
#*               hard    rss             10000
#@student        hard    nproc           20
#@faculty        soft    nproc           20
#@faculty        hard    nproc           50
#ftp             hard    nproc           0
#ftp             -       chroot          /ftp
#@student        -       maxlogins       4

@audio - rtprio 90       # maximum realtime priority
@audio - memlock unlimited  # maximum locked-in-memory address space (KB)

# End of file

Does the top pipewire one need to explicitly say “memlock unlimited”?

1 Like

Seems likely the warning is picking up on the pipewire group memory limit.

Try setting

@pipewire   - memlock unlimited

and see if it helps.

1 Like

Yeah, limits are ‘lowest-wins’.

On a side note, happy to see you checking out Pipewire, Glen :slight_smile:

1 Like

Changing it to ‘memlock unlimited’ did work, thanks! Once I saw the conf files side by side it seemed obvious, not sure why I didn’t see it before… :man_facepalming:

1 Like

Hi @runiq

Yes, I’ve been testing it for a month and working through various obstacles, I have to think in terms of making it work for me and then distributing a working setup to others and PipeWire as installed from a Repository is not really Pro Audio ready without some help…

Secondly thanks and kudos to you for helping on LinuxMusicians with PipeWire mis-identifying my Presonus AR-8 as a ‘surround’ device. That was also a pretty big red flag for me on my own machine… At this point in time if I see PipeWire 1.0.0.get into the main MX Linux 23 Repos (I use the MX buildchain tools to build AV Linux ISO’s) then the next AVL will use PipeWire 1.0.0 with some extra custom tools to help Pro Audio Users…


Pipewire 1.0 can use jackdbus as a backend device, so you could use that in exactly the same way that jackd as the backend for PulseAudio is used today.

1 Like

My feeling is If I’m going PipeWire, I’m going PipeWire… No jackd, jackdbus or PulseAudio and less glue and duct tape and bridging this and that, I’ve been testing on a system with neither JACK or PulseAudio (aside from libpulse) simply ALSA and PipeWire, it if has to be some kludgy hybrid then I’ll VERY happily stick with JACK/Pulse/pajackconnect which hasn’t lost any of it’s reliability and functionality simply because PipeWire happened to come along… :grinning:


I know it’s offtopic, but just as a clarification for myself: You’re talking about this module, right?

Yes, I believe that is correct.

1 Like

I’ve been working exclusively with PipeWire for about a year and a half. It’s an ambitious project, and not the most stable one, if you know what I mean. But when one’s on a stable version, life is very good. The amount of flexibility one gets is second to none, and its performance is awesome.
With that being said, when it fails, one’s stuck. Luckily, that’s happened to me only twice or thrice, and never for more than a week. Additionally, I think those episodes are rarer now than they were two or three months ago.
Of course, I know better than asking for advice or support relate to Ardour here, while I’m using PipeWire.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.