This bug was fixed in the package systemd - 237-3ubuntu10.44
---------------
systemd (237-3ubuntu10.44) bionic; urgency=medium
* d/extra/dhclient-enter-resolved-hook:
suppress output of cmp command in dhclient hook (LP: #1878955)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c5a2db69aafc7a3ab4e71bae44fd7ad9dd955c97
*
d/p/lp1905044/0001-capability-add-a-way-to-get-a-uint64_t-with-all-caps.patch,
d/p/lp1905044/0002-test-use-cap_last_cap-for-max-supported-cap-number-n.patch:
test: use cap_last_cap() instead of capability_list_length()
(LP: #1905044)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=34ebc6e28e63881d40c91c5839597acc2fdab546
* d/p/lp1905245/0001-basic-cap-list-parse-print-numerical-capabilities.patch:
print number of unknown capabilities instead of failing
(LP: #1905245)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5ab225b7f731c6cf6b4655cb27c3a842150c4c1a
*
d/p/lp1907306/0001-sd-dhcp-client-don-t-log-timeouts-if-already-expired.patch,
d/p/lp1907306/0002-sd-dhcp-client-track-dhcp4-t1-t2-expire-times.patch,
d/p/lp1907306/0003-sd-dhcp-client-add-RFC2131-retransmission-details.patch,
d/p/lp1907306/0004-sd-dhcp-client-simplify-dhcp4-t1-t2-parsing.patch,
d/p/lp1907306/0005-sd-dhcp-client-correct-dhcpv4-renew-rebind-retransmi.patch,
d/p/lp1907306/0008-sd-dhcp-client-fix-renew-rebind-timeout-calculation-.patch:
Send correct number of dhcpv4 renew and rebind requests
(LP: #1907306)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=036230cac8232bf4f970e565c355ee1a82fc2ee6
* d/t/root-unittests:
Remove any corrupt journal files (LP: #1881947)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b284b93e40b6cb834bb40dd3db94850853ab5bb8
-- Dan Streetman <ddstr...@canonical.com> Wed, 06 Jan 2021 16:04:25
-0500
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1905245
Title:
"Failed to parse bus message: Invalid argument" with Linux 5.8
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
newer kernels introduced a new capability, and existing systemd
doesn't have the name mapping for the new cap (since the mapping table
is generated at systemd compile time), so it fails when trying to map
the capability to a user-facing name, which causes failure when
running commands like 'systemctl show'
[test case]
install a focal system, and install the 5.8 (or newer) kernel, e.g.
from linux-generic-hwe-20.04-edge, and reboot into the new kernel.
Find any service that does not specify its CapabilityBoundingSet; e.g.
'apparmor', and run systemctl show on it:
ubuntu@lp1905245-f:~$ systemctl show -p CapabilityBoundingSet apparmor
Failed to parse bus message: Invalid argument
the command should correctly show the value, e.g.:
$ systemctl show -p CapabilityBoundingSet apparmor
CapabilityBoundingSet=cap_chown cap_dac_override ...etc...
[regression potential]
a regression would likely occur while systemd is parsing or printing
or otherwise handling kernel capabilities. A regression could happen
when running systemd commands, such as systemctl, or when pid1 is
managing services.
[scope]
this is needed only in focal and bionic.
This is fixed upstream by PR 16424:
https://github.com/systemd/systemd/pull/16424
which was first included in v246, so this is already fixed in groovy and
later.
This was introduced upstream in systemd by commit
52610b020c077ee769c6923249f7e6c4e99d2980 which was first included in
v235, so this bug does not exist in Xenial.
This bug will reproduce on any system running under the 5.8 kernel,
with the new capability, if the systemd binary was compiled with
kernel headers that do not include the new capability. This means this
is reproducable on bare-metal/vm instances running 5.8, as well as
containers on hosts running 5.8. Therefore, while bionic may not ever
receive a new kernel with added capability, it still needs to be
patched to avoid the bug on a bionic container running on a host with
the 5.8 kernel.
[other info]
there is a testcase-only related bug 1905044
[original description]
When I run `systemctl show myservice.service`, I get the following
error message:
Failed to parse bus message: Invalid argument
systemd version: 245.4-4ubuntu3.3
linux version: 5.8.0-29-generic #31~20.04.1-Ubuntu (From
linux-generic-hwe-20.04-edge)
This is a bug that has been fixed in Debian. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964926
Please can we port the fix to the ubuntu 20.04 version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905245/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
