This bug was fixed in the package procps - 2:4.0.6-3ubuntu1
---------------
procps (2:4.0.6-3ubuntu1) stonking; urgency=medium
* Merge from Debian unstable (LP: #2153347). Remaining changes:
- debian/sysctl.d:
+ 55-console-messages.conf: stop low-level kernel messages on console.
+ 55-kernel-hardening.conf: add the kptr_restrict setting
+ 55-ipv6-privacy.conf: add a file to sysctl.d to apply the defaults
for IPv6 privacy extensions for interfaces. (LP #176125, #841353)
+ 55-magic-sysrq.conf: Disable most magic sysrq by default, allowing
critical sync, remount, reboot functions. (LP #194676, #1025467)
+ 55-network-security.conf: enable rp_filter.
+ 55-ptrace.conf: describe new PTRACE setting.
+ 55-zeropage.conf: safe mmap_min_addr value for graceful fall-back
for armhf and arm64.
+ 55-qemu.conf.s390x for qemu.
+ 55-bufferbloat.conf: set default qdisc to fq_codel
+ 55-map-count.conf: Increase vm.max_map_count to 1048576
- d/t/stack-limit: add basic autopkgtest to validate limits
- d/tests: Add basic autopkgtest to validate sysctl-defaults (LP #1962038)
- d/t/stack-limit: call 'pgrep systemd' instead of 'pgrep bash'
The autopkgtest currently fails because there is no bash session, and
pgrep returns non-zero. Use systemd because that will match for pid1.
- d/tests: make sysctl-defaults test comprehensive
- d/t/test_sysctl_defaults.py: skip test if sysctl key invalid
- d/t/control: show all sysctl.d configs before test
- d/t/control: make sysctl-defaults test Restrictions: isolation-machine
(LP #2115346)
* Dropped changes (applied upstream):
- d/p/ignore_eaccess.patch: ignore EACCES when opening sysctl file (LP
#1903351)
- d/p/ignore_erofs.patch: ignore EROFS when opening sysctl file (LP
#1419554)
- d/p/0010-testsuite-ps-etime-ELAPSED-doesn-t-match-full-format.patch:
Fix test failure (FTBFS) in testsuite/ps.test/ps_output.exp due to
invalid regex match inside LXD containers.
- d/p/lp2120904-openat.patch: utilize file descriptors and openat (LP
#2120904)
- d/p/lp2120904-nullpointer.patch: fix a race when 'status' is unavailable
in /proc/<pid> resulting in NULL pointer (LP #2120904)
-- Carter Hawthorne <[email protected]> Thu, 13 Aug 2026
15:27:14 -0700
** Changed in: procps (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2153347
Title:
Merge procps from Debian for stonking cycle
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2153347/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
