[Touch-packages] [Bug 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=
I tested the proposed package (systemd 229-4ubuntu19) in my xenial system (see above apport info) and I can confirm that the committed fix works. -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: Fix Committed Bug description: [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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=
** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: Confirmed 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] SystemdDelta.txt
apport information ** Attachment added: "SystemdDelta.txt" https://bugs.launchpad.net/bugs/1704677/+attachment/4916018/+files/SystemdDelta.txt -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1704677/+attachment/4916015/+files/ProcEnviron.txt -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1704677/+attachment/4916016/+files/ProcInterrupts.txt -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] modified.conffile..etc.pam.d.systemd-user.txt
apport information ** 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 -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1704677/+attachment/4916019/+files/UdevDb.txt -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1704677/+attachment/4916010/+files/JournalErrors.txt -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1704677/+attachment/4916013/+files/ProcCpuinfo.txt -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1704677/+attachment/4916014/+files/ProcCpuinfoMinimal.txt -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1704677/+attachment/4916017/+files/ProcModules.txt -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1704677/+attachment/4916012/+files/Lsusb.txt -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1704677/+attachment/4916009/+files/Dependencies.txt -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1704677/+attachment/4916011/+files/Lspci.txt -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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' --- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+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
[Touch-packages] [Bug 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=
apport information ** Tags added: apport-collected package-from-proposed third-party- packages ** Description changed: 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 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1704677/+attachment/4916008/+files/CurrentDmesg.txt -- 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/1704677 Title: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*= Status in systemd package in Ubuntu: New 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]
[Touch-packages] [Bug 1373598] Re: apt-get update fails, hash sum mismatches (trusty)
The bug hits me from time to time, too. Right now it shows up, again: W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/i18n/Translation-en Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1373598 Title: apt-get update fails, hash sum mismatches (trusty) Status in apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: 1. Release: Description: Ubuntu 14.04.1 LTS Release: 14.04 2. not a package. The whole distro is broken. 3. I always expect apt-get update to work, at least with Ubuntu's own repositories. 4. apt-get update failed, and later apt-get dist upgrade It started with this when doing a normal apt-get update W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/source/Sources Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/binary-amd64/Packages Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/universe/binary-i386/Packages Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. When doing a dist-upgrade, I then got this: E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025. No apport report written because the error message indicates its a followup error from a previous failure. dpkg: error processing package linux-image-extra-3.13.0-36-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-extra-3.13.0-36-generic; however: Package linux-image-extra-3.13.0-36-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured Setting up linux-headers-3.13.0-36 (3.13.0-36.63) ... Setting up linux-headers-3.13.0-36-generic (3.13.0-36.63) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-36-generic /boot/vmlinuz-3.13.0-36-generic Setting up linux-headers-generic (3.13.0.36.43) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 3.13.0.36.43); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured And later this at the end: Processing triggers for libc-bin (2.19-0ubuntu6.3) ... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.5 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Sep 24 21:57:55 2014 InstallationDate: Installed on 2013-05-09 (503 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2014-05-04 (142 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1373598/+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
[Touch-packages] [Bug 1273201] Re: bridge_ignore_without_connections.patch breaks NM created bridge at boot
Me too. Mathieu, please leave a comment here as soon as the new NM package can be downloaded or is in proposed. I'd like to test it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1273201 Title: bridge_ignore_without_connections.patch breaks NM created bridge at boot Status in “network-manager” package in Ubuntu: Confirmed Bug description: I've created a bridge with network-manager-gnome, the bridge slave physical device is eth0. After a reboot the bridge is brought up, but eth0 isn't attached. First test-case: Created a bridge with network-manager-gnome with the bridge slave physical device is eth0 and remove all other connections. After a reboot the bridge is brought up, but eth0 isn't attached. When I open /etc/NetworkManager/NetworkManager.conf and save it without any modification, eth0 is instantly added to my bridge. Strange! Second test-case: Created a bridge with network-manager-gnome with the bridge slave physical device is eth0. Disable the autoconnect of the default wired network. After a reboot the bridge is brought up, but eth0 isn't attached. Instead eth0 is brought up and full configured. After compiling and testing different upstream versions, i could track the problem down to bridge_ignore_without_connections.patch. A network-manager package without this specific patch, brings my bridge up at boot and adds eth0 to the bridge in both test-cases. I've checked the behaviour on my ubuntu 13.10 box with network-manager (0.9.8.0-0ubuntu22) and the trusty version network-manager (0.9.8.8-0ubuntu1) . Till now i couldn't encounter any sideeffects of removing this patch with the bridge created by libvirt. Regards Mathias Kresin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+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
[Touch-packages] [Bug 1273201] Re: bridge_ignore_without_connections.patch breaks NM created bridge at boot
Bug confirmed for my system, too: $ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 $ apt-cache policy network-manager network-manager: Installed: 0.9.8.8-0ubuntu7 Candidate: 0.9.8.8-0ubuntu7 Version table: *** 0.9.8.8-0ubuntu7 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Regards, Wolfgang -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1273201 Title: bridge_ignore_without_connections.patch breaks NM created bridge at boot Status in “network-manager” package in Ubuntu: Confirmed Bug description: I've created a bridge with network-manager-gnome, the bridge slave physical device is eth0. After a reboot the bridge is brought up, but eth0 isn't attached. First test-case: Created a bridge with network-manager-gnome with the bridge slave physical device is eth0 and remove all other connections. After a reboot the bridge is brought up, but eth0 isn't attached. When I open /etc/NetworkManager/NetworkManager.conf and save it without any modification, eth0 is instantly added to my bridge. Strange! Second test-case: Created a bridge with network-manager-gnome with the bridge slave physical device is eth0. Disable the autoconnect of the default wired network. After a reboot the bridge is brought up, but eth0 isn't attached. Instead eth0 is brought up and full configured. After compiling and testing different upstream versions, i could track the problem down to bridge_ignore_without_connections.patch. A network-manager package without this specific patch, brings my bridge up at boot and adds eth0 to the bridge in both test-cases. I've checked the behaviour on my ubuntu 13.10 box with network-manager (0.9.8.0-0ubuntu22) and the trusty version network-manager (0.9.8.8-0ubuntu1) . Till now i couldn't encounter any sideeffects of removing this patch with the bridge created by libvirt. Regards Mathias Kresin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+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
[Touch-packages] [Bug 1319047] Re: udev rule file naming requirements changed breaking compatibility to Ubuntu 12.04
I investigated this issue again and it is more tricky than I initially thought. The rules (see attachment) are supposed to create a symbolic link in /etc/X11/ (it worked ALWAYS perfectly in Ubuntu 12.04 on the same hardware). The problem seems to be due to a race condition (and not due to naming. I initially assumed it is due to naming because the symlink was succesfully created when I renamed the file from graphics- xorg.config.rules to graphics-xorg-config.rules and started the system. Then I deleted the symlink renamed it back to graphics-xorg.config.rules and the symlink was not created after the next boot). After much more tries it turns out that the symlink in /etc/X11/ is sometimes created after booting and sometimes not. I assume that the symlink is created (not created) when the udev event for my rule is triggered after (before) the root files system is mounted. In the meantime I hit a similar issue with another udev rule for an USB sound device. This rule's action also requires root to be mounted for its successful execution. When the USB device is cold plugged the action is sometimes executed successfully and sometimes not. When the device is hot plugged the action is always executed successfully. So the subject of the bug should be rephrased to udev events for cold plug devices are often triggered before root fs is mounted breaking compatibility to Ubuntu 12.04 ** Attachment added: Rules file in /etc/udev/rules.d/ https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1319047/+attachment/4201557/+files/graphics-xorg-config.rules -- 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/1319047 Title: udev rule file naming requirements changed breaking compatibility to Ubuntu 12.04 Status in “systemd” package in Ubuntu: Incomplete Bug description: Binary package: udev: Installed: 204-5ubuntu20 Candidate: 204-5ubuntu20 Version table: *** 204-5ubuntu20 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Source package: systemd Ubuntu release: Description:Ubuntu 14.04 LTS Release:14.04 Expected behavior: All rule files in /etc/udev/rules.d/ having the extension '.rules' [see udev(7)] should be honored by udevd (as it has been in Ubuntu 12.04 and as it is still by udevadm test syspath). Actual behavior: If udev rule file has an additional '.' (dot) in its name (e.g. graphics-xorg.conf.rules) it will be silently ignored by udevd. But such a file will not be ignored by udevadm test syspath, which even adds to the confusion about why the rule is not working. Also the man page udev(7) does not mention any additional/new naming requirements. How to reproduce: Create or rename a rule file in /etc/udev/rules.d/ so that its name contains an additional '.' (dot) (beside the one in '.rules', e.g. 'graphics-xorg.conf.rules') and run udevadm control --reload. From now on the udev rules in that file will be ignored silently by udevd (but not by 'udevadm test syspath'!). How to solve this issue: (1) Revert to the old behavior and make udevd honor rule file names as in Ubuntu 12.04 (preferred alternative) __OR__ (2) If this change has been introduced intentionally then (2a) Announce it (e.g. in a changelog and/or upgrade guide so that users/admins know about it and can rename their rule files not matching the changed needs) (2b) Change the code of udevadm test (and possibly other tools) to behave consistently so that users have a chance to narrow down the naming issue (2c) Add the changed naming requirement to man page udev(7), info files, tutorials... Urgency/Importance: Normal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1319047/+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
