Hello WoJ, or anyone else affected, Accepted systemd into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Zesty) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-zesty -- 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/1710410 Title: Must run systemd-resolve --status before DNS resolving is operative Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Committed Status in systemd source package in Artful: Fix Released Bug description: [Impact] systemd-resolved is not enabled by default, therefore relies on dbus activation to become active and operatable and update resolvconf with resolved stub resolver [Fix] Enable systemd-resolved in the src:systemd package by default, even when libnss-resolve is not installed [Regression Potential] Minimal, simply the service is now started earlier in the boot, as part of the multi-user.targer, rather than awaiting for dbus activation from command line tool or the nss-resolved module. [Testcase] Debootstrap minimal zesty, without libnss-resolve package installed, boot and check that 127.0.0.53 is present in /etc/resolv.conf and that systemd-resolved.service is running Context: fresh install of zesty via debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1 http://fr.archive.ubuntu.com/ubuntu ran via asystemd-nspawn with a static IP 1. Upon first connexion, a ping fails: root@zesty1:~# ping google.com ping: google.com: Temporary failure in name resolution 2. The content of /etc/resolv.conf: root@zesty1:~# cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. 3. When running systemd-resolve --status: root@zesty1:~# systemd-resolve --status Global DNS Servers: 8.8.8.8 8.8.4.4 2001:4860:4860::8888 2001:4860:4860::8844 DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa (...) 4. After running this command the resolution is miraculously restored: root@zesty1:~# ping google.com PING google.com (172.217.22.142) 56(84) bytes of data. 64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms 64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710410/+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
