Oh and also openvswitch, bug 1906280
To summarize, here are all the applications (found so far) that thought
they needed to lock all their current and future memory:
slick-greeter (bug 1902879)
lightdm-gtk-greeter (bug 1890394)
corosync (bug 1911904)
openvswitch (bug 1906280)
--
You received
found another 'special' application that thinks it needs all its memory
locked: corosync.
opened bug 1911904
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock setting in systemd
Both the slick-greeter and lightdm-gtk-greeter packages have been now
released into -updates. I think it should be now safe-ish to proceed
with the systemd update once again. Let's think about it in the nearest
time.
** Tags removed: block-proposed-bionic
--
You received this bug notification
To clarify, the regression appears to be the same problem that the
rlimit increase is fixing, but the applications failing now are simply
bigger. In general, any application that calls mlockall() with
MCL_FUTURE, but doesn't adjust its rlimit (or change its systemd service
file to adjust
** Tags added: block-proposed-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock setting in systemd (pid 1) too low for containers (bionic)
To manage notifications about
I have backed out the published version in bionic-updates to the
previously published version in the pocket: 237-3ubuntu10.42.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock
The libghtdm-gtk-greeter is having the same issue which is breaking
xubuntu, see bug #1902871. Could we revert that SRU to proposed instead
of updates to avoid bricking more user systems until we have a better
handle on the problem and at least have those greeter fixes out?
--
You received this
Thank you Łukasz, I filed it in LP: #1902879.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock setting in systemd (pid 1) too low for containers (bionic)
To manage
Hey Alkis! Can you please fill in a new bug report with all the detailed
information and tag it wit 'regression-update'? Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
What torel proposed in https://bugs.launchpad.net/ubuntu/+source/unity-
greeter/+bug/1662244/comments/14 avoids the segfault:
* soft memlock 262144
* hard memlock 262144
Should all lightdm users manually put that in limits.conf, or should we
expect some update?
--
You received this bug
Hi, this update makes slick-greeter segfault, so Ubuntu MATE 18.04 users
doing normal updates now get a black screen with a flicking cursor.
A temporary workaround is to enable autologin in
/etc/lightdm/lightdm.conf:
[Seat:*]
autologin-guest=false
autologin-user=administrator
This bug was fixed in the package systemd - 237-3ubuntu10.43
---
systemd (237-3ubuntu10.43) bionic; urgency=medium
[ Guilherme G. Piccoli ]
* d/p/lp1830746-bump-mlock-ulimit-to-64Mb.patch:
- Bump the memlock limit to match Focal and newer releases (LP: #1830746)
I was able to verify this bug with systemd from bionic-proposed (version
237-3ubuntu10.43) by following the procedure in the test case; it's
working as expected, I can see 64M in the memlock limit.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done
Hello Kees, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.43 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags added: sts sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock setting in systemd (pid 1) too low for containers (bionic)
To manage notifications
** Patch added: "This is the (tested) debdiff with the proposed SRU, for Bionic
only."
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+attachment/5409870/+files/bionic_systemd_lp1830746.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
- See also https://discuss.linuxcontainers.org/t/limits-kernel-memlock-
- cannot-exceed-16777216/4856/5
+ [Impact]
+ * Since systemd commit fb3ae275cb ("main: bump RLIMIT_NOFILE for the root
user substantially") [https://github.com/systemd/systemd/commit/fb3ae275cb],
Hi Sebastian, thanks for offering help. And thanks of course Kees for reporting
the issue!
Recently we faced a build breakage of cryptsetup package narrowed to this
issue: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1891473
I intend to bump this limit to 64M to match recent
Unfortunately I have not experience or knowledge of Ubuntu packaging or
bug fixing processes, but is there anything I can do to help get this
fixed in bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830746
** Changed in: systemd (Ubuntu Disco)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock setting in systemd (pid 1) too low for containers (bionic)
OLder systemds, (234-240, I think) have a different erroneous clamp on
RLIMIT_MEMLOCK. See #1840435.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock setting in systemd (pid 1)
Hmm, sorry, brainfart. At least 240. Not sure how far back it went.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock setting in systemd (pid 1) too low for containers (bionic)
This has landed in Eoan in at least version 242 of systemd.
** Changed in: systemd (Ubuntu Eoan)
Status: New => Fix Released
** Tags added: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Eoan)
The attachment "fix-memlock-bump.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
** Patch added: "fix-memlock-bump.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+attachment/5267179/+files/fix-memlock-bump.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
28 matches
Mail list logo
