2017-07-16 20:22:57 |
linuxball |
bug |
|
|
added bug |
2017-07-16 20:30:05 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
2017-07-17 06:07:34 |
Steve Langasek |
affects |
linux (Ubuntu) |
systemd (Ubuntu) |
|
2017-07-17 06:07:34 |
Steve Langasek |
systemd (Ubuntu): status |
Incomplete |
New |
|
2017-07-17 06:08:25 |
Steve Langasek |
systemd (Ubuntu): importance |
Undecided |
Critical |
|
2017-07-17 06:08:29 |
Steve Langasek |
systemd (Ubuntu): assignee |
|
Dimitri John Ledkov (xnox) |
|
2017-07-17 07:37:20 |
linuxball |
tags |
regression-proposed xenial |
apport-collected package-from-proposed regression-proposed third-party-packages xenial |
|
2017-07-17 07:37:21 |
linuxball |
description |
The systemd version 229-4ubuntu18 from xenial-proposed archive has a bug. The '+' prefix (see https://www.freedesktop.org/software/systemd/man/systemd.service.html) in ExecStart*= and ExecStop*= statements does not work any longer.
File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of this version contains two commands prefixed with '+':
# When resolved is in use, it must be brought up before we consider networking
# available because otherwise there is a window where DNS resolution doesn't
# work.
[Unit]
Before=network-online.target
# tell resolvconf about resolved's builtin DNS server, so that DNS servers
# picked up via networkd are respected when using resolvconf, and that software
# like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
# resolution
[Service]
ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
Those two statements in section [Service] lead to the following two error messages in dmesg:
[ 3.687475] systemd[1]: [/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable path is not absolute, ignoring: +/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
[ 3.687614] systemd[1]: [/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable path is not absolute, ignoring: +/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved' |
The systemd version 229-4ubuntu18 from xenial-proposed archive has a bug. The '+' prefix (see https://www.freedesktop.org/software/systemd/man/systemd.service.html) in ExecStart*= and ExecStop*= statements does not work any longer.
File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of this version contains two commands prefixed with '+':
# When resolved is in use, it must be brought up before we consider networking
# available because otherwise there is a window where DNS resolution doesn't
# work.
[Unit]
Before=network-online.target
# tell resolvconf about resolved's builtin DNS server, so that DNS servers
# picked up via networkd are respected when using resolvconf, and that software
# like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
# resolution
[Service]
ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
Those two statements in section [Service] lead to the following two error messages in dmesg:
[ 3.687475] systemd[1]: [/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable path is not absolute, ignoring: +/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
[ 3.687614] systemd[1]: [/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable path is not absolute, ignoring: +/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
---
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
CurrentDesktop: LXDE
DistroRelease: Ubuntu 16.04
MachineType: LENOVO 42406AG
Package: systemd 229-4ubuntu18
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
Tags: xenial package-from-proposed third-party-packages
Uname: Linux 4.4.0-85-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd lpadmin netdev plugdev saned scanner sudo tape video wireshark
_MarkForUpload: True
dmi.bios.date: 09/20/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 8AET66WW (1.46 )
dmi.board.asset.tag: Not Available
dmi.board.name: 42406AG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 42406AG
dmi.product.version: ThinkPad T520
dmi.sys.vendor: LENOVO
mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992 |
|
2017-07-17 07:37:21 |
linuxball |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916008/+files/CurrentDmesg.txt |
|
2017-07-17 07:37:22 |
linuxball |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916009/+files/Dependencies.txt |
|
2017-07-17 07:37:23 |
linuxball |
attachment added |
|
JournalErrors.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916010/+files/JournalErrors.txt |
|
2017-07-17 07:37:24 |
linuxball |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916011/+files/Lspci.txt |
|
2017-07-17 07:37:25 |
linuxball |
attachment added |
|
Lsusb.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916012/+files/Lsusb.txt |
|
2017-07-17 07:37:26 |
linuxball |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916013/+files/ProcCpuinfo.txt |
|
2017-07-17 07:37:27 |
linuxball |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916014/+files/ProcCpuinfoMinimal.txt |
|
2017-07-17 07:37:29 |
linuxball |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916015/+files/ProcEnviron.txt |
|
2017-07-17 07:37:30 |
linuxball |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916016/+files/ProcInterrupts.txt |
|
2017-07-17 07:37:31 |
linuxball |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916017/+files/ProcModules.txt |
|
2017-07-17 07:37:31 |
linuxball |
attachment added |
|
SystemdDelta.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916018/+files/SystemdDelta.txt |
|
2017-07-17 07:37:32 |
linuxball |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916019/+files/UdevDb.txt |
|
2017-07-17 07:37:33 |
linuxball |
attachment added |
|
modified.conffile..etc.pam.d.systemd-user.txt https://bugs.launchpad.net/bugs/1704677/+attachment/4916020/+files/modified.conffile..etc.pam.d.systemd-user.txt |
|
2017-07-17 11:21:44 |
linuxball |
systemd (Ubuntu): status |
New |
Confirmed |
|
2017-07-17 15:57:06 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Xenial |
|
2017-07-17 15:57:06 |
Dimitri John Ledkov |
bug task added |
|
systemd (Ubuntu Xenial) |
|
2017-07-17 15:57:10 |
Dimitri John Ledkov |
systemd (Ubuntu): status |
Confirmed |
Invalid |
|
2017-07-17 15:57:13 |
Dimitri John Ledkov |
systemd (Ubuntu Xenial): status |
New |
Triaged |
|
2017-07-17 15:57:15 |
Dimitri John Ledkov |
systemd (Ubuntu Xenial): importance |
Undecided |
Critical |
|
2017-07-17 15:57:17 |
Dimitri John Ledkov |
systemd (Ubuntu Xenial): assignee |
|
Dimitri John Ledkov (xnox) |
|
2017-07-17 15:57:20 |
Dimitri John Ledkov |
systemd (Ubuntu Xenial): milestone |
|
ubuntu-16.04.3 |
|
2017-07-17 16:00:33 |
Dimitri John Ledkov |
description |
The systemd version 229-4ubuntu18 from xenial-proposed archive has a bug. The '+' prefix (see https://www.freedesktop.org/software/systemd/man/systemd.service.html) in ExecStart*= and ExecStop*= statements does not work any longer.
File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of this version contains two commands prefixed with '+':
# When resolved is in use, it must be brought up before we consider networking
# available because otherwise there is a window where DNS resolution doesn't
# work.
[Unit]
Before=network-online.target
# tell resolvconf about resolved's builtin DNS server, so that DNS servers
# picked up via networkd are respected when using resolvconf, and that software
# like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
# resolution
[Service]
ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
Those two statements in section [Service] lead to the following two error messages in dmesg:
[ 3.687475] systemd[1]: [/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable path is not absolute, ignoring: +/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
[ 3.687614] systemd[1]: [/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable path is not absolute, ignoring: +/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
---
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
CurrentDesktop: LXDE
DistroRelease: Ubuntu 16.04
MachineType: LENOVO 42406AG
Package: systemd 229-4ubuntu18
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
Tags: xenial package-from-proposed third-party-packages
Uname: Linux 4.4.0-85-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd lpadmin netdev plugdev saned scanner sudo tape video wireshark
_MarkForUpload: True
dmi.bios.date: 09/20/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 8AET66WW (1.46 )
dmi.board.asset.tag: Not Available
dmi.board.name: 42406AG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 42406AG
dmi.product.version: ThinkPad T520
dmi.sys.vendor: LENOVO
mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992 |
[Impact]
229-4ubuntu18 included changes irrelevant for xenial, which whilst harmless generates a lot of scary journal entries.
[Fix]
Drop the cherrypciked ExecStart|StopPost stanzas from the drop in snippet. Integration of the resolved stub resolver with resolvconf on xenial is not required, because resolved in xenial does not have stub resolver. Also xenial's systemd does not support '+' prefix on the Exec* lines.
[Testcase]
Upgrade to te new SRU, make sure testcase from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673860 still passes
Check that there is no extra journal warnings/errors about "Executable path is not absolute" from systemd reading /lib/systemd/system/systemd-resolved.service.d/resolvconf.con
[Original Descrption]
The systemd version 229-4ubuntu18 from xenial-proposed archive has a bug. The '+' prefix (see https://www.freedesktop.org/software/systemd/man/systemd.service.html) in ExecStart*= and ExecStop*= statements does not work any longer.
File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of this version contains two commands prefixed with '+':
# When resolved is in use, it must be brought up before we consider networking
# available because otherwise there is a window where DNS resolution doesn't
# work.
[Unit]
Before=network-online.target
# tell resolvconf about resolved's builtin DNS server, so that DNS servers
# picked up via networkd are respected when using resolvconf, and that software
# like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
# resolution
[Service]
ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
Those two statements in section [Service] lead to the following two error messages in dmesg:
[ 3.687475] systemd[1]: [/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable path is not absolute, ignoring: +/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
[ 3.687614] systemd[1]: [/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable path is not absolute, ignoring: +/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
---
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
CurrentDesktop: LXDE
DistroRelease: Ubuntu 16.04
MachineType: LENOVO 42406AG
Package: systemd 229-4ubuntu18
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
Tags: xenial package-from-proposed third-party-packages
Uname: Linux 4.4.0-85-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd lpadmin netdev plugdev saned scanner sudo tape video wireshark
_MarkForUpload: True
dmi.bios.date: 09/20/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 8AET66WW (1.46 )
dmi.board.asset.tag: Not Available
dmi.board.name: 42406AG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 42406AG
dmi.product.version: ThinkPad T520
dmi.sys.vendor: LENOVO
mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992 |
|
2017-07-17 16:03:36 |
Dimitri John Ledkov |
systemd (Ubuntu Xenial): status |
Triaged |
In Progress |
|
2017-07-17 16:03:41 |
Dimitri John Ledkov |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2017-07-17 16:03:48 |
Dimitri John Ledkov |
bug |
|
|
added subscriber Steve Langasek |
2017-07-17 16:05:23 |
Dimitri John Ledkov |
cve linked |
|
2017-9445 |
|
2017-07-18 23:34:45 |
Adam Conrad |
systemd (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
2017-07-18 23:34:47 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
2017-07-18 23:34:52 |
Adam Conrad |
tags |
apport-collected package-from-proposed regression-proposed third-party-packages xenial |
apport-collected package-from-proposed regression-proposed third-party-packages verification-needed verification-needed-xenial xenial |
|
2017-07-19 13:41:45 |
Dimitri John Ledkov |
tags |
apport-collected package-from-proposed regression-proposed third-party-packages verification-needed verification-needed-xenial xenial |
apport-collected package-from-proposed regression-proposed third-party-packages verification-done verification-done-xenial xenial |
|
2017-07-20 23:43:36 |
Adam Conrad |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
2017-07-20 23:43:25 |
Launchpad Janitor |
systemd (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
2017-09-29 17:25:06 |
Francis Ginther |
tags |
apport-collected package-from-proposed regression-proposed third-party-packages verification-done verification-done-xenial xenial |
apport-collected id-596df10ca7021ce6e7899a19 package-from-proposed regression-proposed third-party-packages verification-done verification-done-xenial xenial |
|