ubuntustudio-bugs team mailing list archive

[Christopher Warner <cwarner@xxxxxxxxxxxxxx>]

So i'm just going to add on here instead of opening a new bug report.
The problem is that in most cases when you're setting the limits, you're
doing so for a process/user that isn't going to login. So the default is
to set it in login, cron, sshd, su etc. Unfortunately, for a process
that isn't going to login via normal methods. Such as a server process
or the like this will be ignored because pam_limits.so will never be
activated.

We need to put pam_limits.so in /etc/pam.d/common-session and /etc/pam.d
/common-session-noninteractive as required by default, or, update the
documentation somewhere that notes that limits.conf will not be
activated by pam_limits.so otherwise. Since everything is already
commented out by limits.conf per default it should be a straight-forward
change.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to jackd2 in Ubuntu.
Matching subscriptions: ubuntustudio-bugs: jackd2
https://bugs.launchpad.net/bugs/1627769

Title:
  limits.conf not applied

Status in jackd2 package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgraded to 16.10 Yakkety, modifications in
  /etc/security/limits.conf are not taken into consideration when
  logging in the graphical interface.

  
  /etc/security/limits.conf:
  @audio   -  rtprio     99
  @audio   -  memlock    unlimited

  I tried the same settings in /etc/security/limits.d/audio.conf, to the
  same results.

  
  After logging in Unity, opening a console, the limits are not set:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory       (kbytes, -l) 64
  real-time priority              (-r) 0

  
  Reloging to my user via bash DOES apply the limits:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory       (kbytes, -l) 64
  real-time priority              (-r) 0
  blablack@ideaon:~$ su blablack
  Password: 
  blablack@ideaon:~$ ulimit -l -r
  max locked memory       (kbytes, -l) unlimited
  real-time priority              (-r) 95

  
  Switching to a console (ctrl+alt+f1) and logging in would apply the limits as well.



  The exact same setup used to work fine on Xenial 16.04 before upgrade.

  
  If you need any more information, please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 26 17:27:10 2016
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1627769/+subscriptions