This bug was fixed in the package systemd - 246.6-1ubuntu1
---------------
systemd (246.6-1ubuntu1) groovy; urgency=medium
[ Dan Streetman ]
* Fix resolved.conf Cache= default to match default (LP: #1895418)
Files:
- debian/patches/lp1895418.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=dd4d93d94ebe2cf416f6b5a5eb59a16432cbc47b
[ Balint Reczey ]
* Bugfix-only upload
* Merge from Debian unstable
- core: propagate unit start limit hit state to triggering path unit (LP:
#1891657)
* Skip test_rsyslog in s390x containers.
The test is failing almost all the time. (LP: #1895576)
File: debian/tests/boot-and-services
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ff8d286de52daa8b0856213ae52e66b81474fb57
* debian/tests/tests-in-lxd: Don't create the lxd test image twice
File: debian/tests/tests-in-lxd
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e858e7c41b84bc4c34e8af79d6e4b6114fe23952
systemd (246.6-1) unstable; urgency=medium
* New upstream version 246.6
* Rebase patches
-- Balint Reczey <[email protected]> Thu, 24 Sep 2020 21:27:11 +0200
** Changed in: systemd (Ubuntu Groovy)
Status: In Progress => 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/1891657
Title:
systemd 100% cpu usage apport-autoreport.service: Failed with result
'start-limit-hit'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
