Please re-open if this is still an issue in newer releases.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bug
Did absolutely everything...
/etc/sysctl.conf
/proc/sys/fs/file-max
/etc/security/limits.conf
/etc/pam.d/common-session-noninteractive
/etc/pam.d/common-session
/etc/systemd/user.conf
Only setting this worked:
sudo vim /etc/systemd/system.conf
DefaultLimitNOFILE=64000
Let me tell you that t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.ne
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: jackd2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net
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 goi
OK - I was finally able to get this working in 17.04 after more
experimentation, which revealed the following caveats:
- Ubuntu will respect limits you put in /etc/security/limits.conf (or
/etc/security/limits.d/audio.conf), but **only after a reboot**.
Logging out and back in are not sufficient t
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: jackd2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
htt
Artful (17.10) has systemd 233. I just ran the Artful daily build in
VirtualBox and tried this there. I see the same problem in Artful:
neither a change to /etc/security/limits.conf nor /etc/systemd/user.conf
affects the limits I see when I run 'prlimit' in a terminal window.
--
You received th
On 17.04, even the workaround that Ewan posted in #5 above doesn't work
for me. If I add DefaultLimitNOFILE=4 to /etc/systemd/user.conf and
log out and log in again, prlimit still shows this:
adam:~$ prlimit
RESOURCE DESCRIPTION SOFT HARD UNITS
...
NOFILE
Apparently Fedora has wrestled with this too:
https://bugzilla.redhat.com/show_bug.cgi?id=1364332
The last comment there
(https://bugzilla.redhat.com/show_bug.cgi?id=1364332) seems to indicate
that this has been fixed in Fedora 26, which has systemd 233.
I'm running Ubuntu 17.04 Zesty with syste
I've found that editting /etc/systemd/user.conf and inserting lines such
as
DefaultLimitNOFILE=4
changes the ulimit for the graphical user sessions
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https
Still seems to be an issue for me, logging into the terminal I have the
modified ulimit values, but not in a lightdm session
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/16
Issue seems to be fixed for me in the latest updates (1st of October).
Could someone confirm it as well?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1627769
Title:
limi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.n
14 matches
Mail list logo
