This bug was fixed in the package systemd - 248.3-1ubuntu8.5
---
systemd (248.3-1ubuntu8.5) impish; urgency=medium
* debian/tests/boot-and-services: Ignore failed snap mount units in
test_no_failed (LP: #1967576)
systemd (248.3-1ubuntu8.4) impish; urgency=medium
[ Lukas Märdian
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish-
proposed have been resolved. The regressions were caused either by (1)
network/infrastructure issues and succeeded on retry, or by (2)
unrelated snapd regressions. The systemd 248.3-1ubuntu8.5 upload added
an autopkgtest
Hello Steve, or anyone else affected,
Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I tested systemd 248.3-1ubuntu8.4 from impish-proposed to verify the
fix:
$ systemctl --version
systemd 248 (248.3-1ubuntu8.4)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL
+ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP
-LIBFDISK +PCRE2
Hello Steve, or anyone else affected,
Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package procps - 2:3.3.17-6ubuntu2
---
procps (2:3.3.17-6ubuntu2) jammy; urgency=medium
* Add basic autopkgtest to validate sysctl-defaults (LP: #1962038)
-- Lukas Märdian Fri, 25 Feb 2022 12:57:56 +0100
** Changed in: procps (Ubuntu Jammy)
This bug was fixed in the package systemd - 249.10-0ubuntu2
---
systemd (249.10-0ubuntu2) jammy; urgency=medium
* Fix deadlock between pid1 and dbus-daemon (LP: #1871538)
File:
debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch
oh correction, it does because of the added autopkgtest :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962038
Title:
wrong sysrq value in /usr/lib/sysctl.d/50-default.conf
To manage
dropping the update-excuse tag, since this bug has nothing to do with
why the packages are or aren't migrating out of -proposed AFAIK
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962038
Title:
On Tue, Mar 08, 2022 at 04:11:45PM -, Lukas Märdian wrote:
> >> systemd should drop its setting to defer to the file that we have been
> >> carrying in procps for a very long time.
> > at some point it would be a better idea to drop the procps files and
> > adjust the systemd defaults
>> systemd should drop its setting to defer to the file that we have been
>> carrying in procps for a very long time.
>
> at some point it would be a better idea to drop the procps files and adjust
> the systemd defaults where/if needed. The sysctl configuration hasn't been
> applied by procps
> systemd should drop its setting to defer to the file that we have been
carrying in procps for a very long time.
at some point it would be a better idea to drop the procps files and
adjust the systemd defaults where/if needed. The sysctl configuration
hasn't been applied by procps since upstart;
** Also affects: procps (Ubuntu)
Importance: Undecided
Status: New
** Changed in: procps (Ubuntu Impish)
Status: New => Won't Fix
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
I've just learned that systemd is setting kernel.sysrq to 16 in
/usr/lib/sysctl.d/50-default.conf. This is inconsistent with
/etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176 by
default. systemd should drop its setting to defer to
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962038
Title:
wrong sysrq value in
** Also affects: systemd (Ubuntu Jammy)
Importance: High
Status: Triaged
** Tags removed: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962038
Title:
wrong sysrq value
** Tags added: fr-2083
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962038
Title:
wrong sysrq value in /usr/lib/sysctl.d/50-default.conf
To manage notifications about this bug go to:
I've analyzed the situation on Jammy, Impish and Focal and got the
following result:
Jammy+Impish:
/usr/lib/sysctl.d/50-default.conf:net.ipv4.conf.default.rp_filter = 2
=> shadowed but equal value
/usr/lib/sysctl.d/50-default.conf:net.ipv4.conf.*.rp_filter = 2
=> shadows default.rp_filter &
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962038
Title:
wrong sysrq value in /usr/lib/sysctl.d/50-default.conf
To manage notifications about this bug go to:
we may want to audit /usr/lib/sysctl.d vs /etc/sysctl.d to verify if
there are any other settings that are being shadowed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962038
Title:
wrong sysrq
20 matches
Mail list logo
