This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1704677

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1704677

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in linux package in Ubuntu:
  Incomplete

Bug 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'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704677/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to