This bug was fixed in the package systemd - 234-2ubuntu12.3
---------------
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
* systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
* netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
* resolved.service: set DefaultDependencies=no (LP: #1734167)
* systemd.postinst: enable persistent journal. (LP: #1618188)
* core: add support for non-writable unified cgroup hierarchy for container
support.
Rebase and de-fuzz. (LP: #1734410)
* Prevent MemoryDenyWriteExecution policy bypass, by disallowing
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
* networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)
[ Kleber Sacilotto de Souza ]
* systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)
-- Dimitri John Ledkov <x...@ubuntu.com> Tue, 20 Feb 2018 16:11:58
+0000
** Changed in: systemd (Ubuntu Artful)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908
--
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/1736955
Title:
dep8 test systemd-fsckd fails on s390
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Zesty:
Won't Fix
Status in systemd source package in Artful:
Fix Released
Bug description:
The systemd-fsckd test has a constraint of isolation-machine, among
others. Until recently, that actually prevented it from running on
s390 because we were using containers for it.
About 3 weeks ago, apparently we started using VMs for s390 dep8
tests, so that constraint was finally satisfied and systemd-fsckd
started to run. And to fail consistently, as can be see in
http://autopkgtest.ubuntu.com/packages/s/systemd/artful/s390x:
Traceback (most recent call last):
File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd",
line 267, in <module>
boot_with_systemd_distro()
File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd",
line 243, in boot_with_systemd_distro
enable_plymouth()
File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd",
line 224, in enable_plymouth
plymouth_enabled = 'splash' in open('/boot/grub/grub.cfg').read()
FileNotFoundError: [Errno 2] No such file or directory: '/boot/grub/grub.cfg'
There is no grub for s390, so this test must be adjusted or skipped in
that architecture.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1736955/+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
