[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Hello Mauricio, or anyone else affected, Accepted debian-installer into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu557.1 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: debian-installer (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1807023 Title: installer stock images fail to validate any HTTPS certificates (ca- certificates missing) Status in debian-installer: Unknown Status in ca-certificates package in Ubuntu: Invalid Status in debian-installer package in Ubuntu: Fix Committed Status in ca-certificates source package in Trusty: In Progress Status in debian-installer source package in Trusty: In Progress Status in ca-certificates source package in Xenial: In Progress Status in debian-installer source package in Xenial: In Progress Status in ca-certificates source package in Bionic: Invalid Status in debian-installer source package in Bionic: Fix Committed Status in ca-certificates source package in Cosmic: Invalid Status in debian-installer source package in Cosmic: Fix Committed Status in ca-certificates source package in Disco: Invalid Status in debian-installer source package in Disco: Fix Committed Status in debian-installer package in Debian: Fix Released Bug description: [Impact] * The installer stock images fail to validate any HTTPS certificates because ca-certificates is not available in the installer environment. * This causes wget/download errors for preseed files on HTTPS servers (or HTTP servers that redirect to HTTPS, which are increasingly common nowadays - e.g., GitHub) and theoretically any other files that are downloaded with d-i-utils/fetch-url/wget. * The fix is to ship ca-certificates-udeb in installer stock images. * Debian already ships ca-certificate-udeb in the stock installer images; the fix is applied since Jan 2017. (reference: Debian Bug #842040 / d-i commit 2f00c51a [1]) [Test Case] * In the installer shell: ~ # wget http://github.com # or https://github.com - FAIL if ca-certificates-udeb is missing: "ERROR: cannot verify github.com's certificate, <...>' - PASS if ca-certificates-udeb is available "Saving to: 'index.html'" * Test steps with virt-install and netboot images are provided in the comments, for each release. [Regression Potential] * Low. This just adds the ca-certificates files in /etc/ssl/certs and symlink in /usr/lib/ssl/certs, so only tools looking for that would be affected. * Apparently only wget checks for/uses those files, and the difference in behavior is download errors no longer occur. [Notes] * The ca-certificates-udeb is not currently present in the Ubuntu 'main' component, but in 'universe', despite the normal deb being in 'main'. However, when rebuilding in a PPA it goes into 'main' accordingly, and can be used by default by debian-installer (otherwise, UDEB_COMPONENTS has to be modified to include universe/d-i). * So this fix includes a no-change-rebuild for the ca-certificates package, in order to publish the udeb in the archive (at least in PPA for testing). Hopefully that can be sorted out for this fix to work out. * The ca-certificates and debian-installer builds have been done in a PPA using all architectures, and testing has been done with the amd64 images. * This fix is requested for Bionic, Cosmic, Disco at least. * The fix for Trusty and Xenial needed a little bit more work to build/ship the (new) udeb. (reference: Debian Bug #845456 / ca-certificates
[Touch-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.2.2-0ubuntu1~18.04.1 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-joystick package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in xserver-xorg-video-vesa package in Ubuntu: Invalid Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom source package in Bionic: New Status in xorg source package in Bionic: New Status in xorg-server source package in Bionic: New Status in xserver-xorg-input-evdev source package in Bionic: New Status in xserver-xorg-input-joystick source package in Bionic: New Status in xserver-xorg-input-libinput source package in Bionic: New Status in xserver-xorg-input-synaptics source package in Bionic: New Status in xserver-xorg-video-amdgpu source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: New Status in xserver-xorg-video-fbdev source package in Bionic: New Status in xserver-xorg-video-nouveau source package in Bionic: New Status in xserver-xorg-video-qxl source package in Bionic: New Status in xserver-xorg-video-vesa source package in Bionic: New Status in xserver-xorg-video-vmware source package in Bionic: New Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1789924] Re: Missing Intel GPU pci-id's
Hello Timo, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.2.2-0ubuntu1~18.04.1 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: New Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1757951] Re: backport from cosmic, move libwayland-egl to src:wayland
*** This bug is a duplicate of bug 1798597 *** https://bugs.launchpad.net/bugs/1798597 ** This bug has been marked a duplicate of bug 1798597 Backport packages for 18.04.2 HWE stack -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1757951 Title: backport from cosmic, move libwayland-egl to src:wayland Status in wayland package in Ubuntu: Invalid Status in wayland source package in Bionic: New Bug description: [Impact] libwayland-egl was moved from mesa to wayland in 1.15rc and got dropped from Mesa after 18.0.0. This update was planned as a FFE but it didn't quite make it before bionic release, so here we are. [Test case] [Regression potential] [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1757951/+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 1781440] Please test proposed package
Hello Till, or anyone else affected, Accepted wayland into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wayland/1.16.0-1ubuntu1.1~18.04.1 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1781440 Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 Status in wayland package in Ubuntu: Fix Released Status in wayland source package in Bionic: Fix Committed Status in wayland source package in Cosmic: Fix Committed Bug description: [impact] upgrade from bionic fails if libwayland-dev & libegl1-mesa-dev was installed [test case] install libwayland-dev & libegl1-mesa-dev on bionic, upgrade to cosmic [regression potential] none, the fix only changes the version numbers in Breaks/Replaces -- Occured when upgrading from Bionic to Cosmic. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-dev 1.15.0-2 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Thu Jul 12 18:41:26 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224e] InstallationDate: Installed on 2018-02-07 (155 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207) MachineType: LENOVO 20JDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=150ad8bc-1d20-4de9-a767-b2b0679455f3 ro quiet splash acpi_osi= vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha2 SourcePackage: wayland Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1NET33W(1.20):bd10/26/2017:svnLENOVO:pn20JDCTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 2nd dmi.product.name: 20JDCTO1WW dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to:
[Touch-packages] [Bug 1781440] Re: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1
Hello Till, or anyone else affected, Accepted wayland into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wayland/1.16.0-1ubuntu1.1 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wayland (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: wayland (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1781440 Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 Status in wayland package in Ubuntu: Fix Released Status in wayland source package in Bionic: Fix Committed Status in wayland source package in Cosmic: Fix Committed Bug description: [impact] upgrade from bionic fails if libwayland-dev & libegl1-mesa-dev was installed [test case] install libwayland-dev & libegl1-mesa-dev on bionic, upgrade to cosmic [regression potential] none, the fix only changes the version numbers in Breaks/Replaces -- Occured when upgrading from Bionic to Cosmic. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-dev 1.15.0-2 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Thu Jul 12 18:41:26 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224e] InstallationDate: Installed on 2018-02-07 (155 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207) MachineType: LENOVO 20JDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=150ad8bc-1d20-4de9-a767-b2b0679455f3 ro quiet splash acpi_osi= vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha2 SourcePackage: wayland Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1NET33W(1.20):bd10/26/2017:svnLENOVO:pn20JDCTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 2nd dmi.product.name: 20JDCTO1WW dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
[Touch-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted wayland into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wayland/1.16.0-1ubuntu1.1~18.04.1 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wayland (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-joystick package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in xserver-xorg-video-vesa package in Ubuntu: Invalid Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom source package in Bionic: New Status in xorg source package in Bionic: New Status in xorg-server source package in Bionic: New Status in xserver-xorg-input-evdev source package in Bionic: New Status in xserver-xorg-input-joystick source package in Bionic: New Status in xserver-xorg-input-libinput source package in Bionic: New Status in xserver-xorg-input-synaptics source package in Bionic: New Status in xserver-xorg-video-amdgpu source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: New Status in xserver-xorg-video-fbdev source package in Bionic: New Status in xserver-xorg-video-nouveau source package in Bionic: New Status in xserver-xorg-video-qxl source package in Bionic: New Status in xserver-xorg-video-vesa source package in Bionic: New Status in xserver-xorg-video-vmware source package in Bionic: New Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1798597] Re: Backport packages for 18.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted libclc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20180917-2~ubuntu0.18.04.1 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libclc (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-joystick package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in xserver-xorg-video-vesa package in Ubuntu: Invalid Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom source package in Bionic: New Status in xorg source package in Bionic: New Status in xorg-server source package in Bionic: New Status in xserver-xorg-input-evdev source package in Bionic: New Status in xserver-xorg-input-joystick source package in Bionic: New Status in xserver-xorg-input-libinput source package in Bionic: New Status in xserver-xorg-input-synaptics source package in Bionic: New Status in xserver-xorg-video-amdgpu source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: New Status in xserver-xorg-video-fbdev source package in Bionic: New Status in xserver-xorg-video-nouveau source package in Bionic: New Status in xserver-xorg-video-qxl source package in Bionic: New Status in xserver-xorg-video-vesa source package in Bionic: New Status in xserver-xorg-video-vmware source package in Bionic: New Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1770082] Re: systemd-networkd not renaming devices on boot
Hello Daniel, or anyone else affected,
Accepted netplan.io into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/netplan.io/0.40.2.2
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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Tags removed: verification-done-cosmic
** Tags added: verification-needed verification-needed-cosmic
** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic
--
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/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Status in netplan.io source package in Cosmic:
Fix Committed
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Bring down interface : 'ip link set dev ens3 down'
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
[Touch-packages] [Bug 1770082] Please test proposed package
Hello Daniel, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.40.1~18.04.3 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-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
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/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Status in netplan.io source package in Cosmic:
Fix Committed
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Bring down interface : 'ip link set dev ens3 down'
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
Hello Timo, or anyone else affected, Accepted libdrm into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.95-1~18.04.1 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libdrm (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted libdrm into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.95-1~18.04.1 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Bionic: New Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] [Test case] [Regression potential] libdrm: llvm-7: libclc: mesa: xserver: drivers: [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1798597] Re: Backport packages for 18.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted llvm-toolchain-7 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm- toolchain-7/1:7-3~ubuntu0.18.04.1 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: llvm-toolchain-7 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: libdrm (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Bionic: New Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] [Test case] [Regression potential] libdrm: llvm-7: libclc: mesa: xserver: drivers: [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1799111] Proposed package upload rejected
An upload of qtbase-opensource-src to cosmic-proposed has been rejected from the upload queue for the following reason: "Per our IRC discussion, this should be fixed in the buggy tool, not the package that surfaced the bug.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1799111 Title: lots of Classes missing from docs (e.g. QFileInfo) Status in qtbase-opensource-src package in Ubuntu: New Status in qtbase-opensource-src package in Debian: Unknown Bug description: [Impact] The packaged Qt documentation, which can be viewed in browser (qt*-doc-html packages) or in Qt Assistant (qt*-doc packages) is missing all documentation generated from C++ files. Only the static text is present. Qt is split by many modules (qtbase, qtdeclarative, qtwebengine, etc.). I am now fixing it for qtbase, the largest module, but I may fix it for other modules if someone requests it. [Test Case] 1. Install qtbase5-doc-html package. 2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present. [Regression Potential] The proposed fix only adds a new build-dependency. There is absolutely no regression potential. [Other Info] Description of the fix: qdoc is a tool that parses C++ source files and generates documentation from them. Recently, qdoc began using clang instead of its own C++ parser. Clang needs the C++ standard library to work. qdoc build system uses a build-time macro (CLANG_RESOURCE_DIR) that hard- codes the path to standard library in the executable: https://code.qt.io/cgit/qt/qttools.git/tree/src/qdoc/qdoc.pro?h=5.11#n19. From qttools-opensource-src 5.11.1-5 build log in Cosmic amd64, one can see that qdoc was compiled with -D'CLANG_RESOURCE_DIR="/usr/lib/llvm-6.0/lib/clang/6.0.1/include"'. So this directory needs to be present when qdoc is used. This directory is provided by libclang-common-6.0-dev package. So adding it to build- dependencies makes the documentation build correctly. This is the minimal fix for Cosmic. For Ubuntu 19.04, I will try to use a better solution like moving the clang standard library detection from build time to run time, or making qttools5-dev-tools depend on the needed -dev packages. [Original Description] The Qt offline documentation for cosmic is incomplete. In fact there's virtually no content what so ever. It would be easier I think to list what actually got picked up that what was missed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1799111/+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 1475945] Re: blacklisting i2c_i801 breaks trackpad detection on Acer C710, plus other hardware
*** This bug is a duplicate of bug 1786574 *** https://bugs.launchpad.net/bugs/1786574 ** This bug has been marked a duplicate of bug 1786574 remove i2c-i801 from blacklist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1475945 Title: blacklisting i2c_i801 breaks trackpad detection on Acer C710, plus other hardware Status in kmod package in Ubuntu: Confirmed Bug description: file: /etc/modprobe.d/blacklist.conf contains the text: # causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306) blacklist i2c_i801 note: actually the correct LP id appears to be https://bugs.launchpad.net/bugs/16602 after short discussion at https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 I'm raising this as a bug as well as preventing trackpad detection in the case of Acer C710, there is an older bug open at https://bugs.launchpad.net/bugs/857175. Here this same blacklist entry breaks some functionality for a Thinkpad T41. In turn, that bug includes a reference to another source (http://permalink.gmane.org/gmane.linux.drivers.i2c/9120) where the blacklist entry has required support effort. lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 apt-cache policy kmod kmod: Installed: 18-3ubuntu1 Candidate: 18-3ubuntu1 Version table: *** 18-3ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1475945/+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 1783810] Update Released
The verification of the Stable Release Update for util-linux has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1783810 Title: [SRU] blocks boot on core18 Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Bionic: Fix Released Bug description: The current version of libuuid is using getrandom() without the GRND_NONBLOCK flag. This means that in early boot the boot is blocked until the crng is initialized to "level=1" which on virtual machines may take some time. Upstream fixed this in https://github.com/karelzak/util- linux/commit/a9cf659e0508c1f56813a7d74c64f67bbc962538 and we should just backport the fix. [Impact] * Makes systems that use libuuid in early boot hang [Test Case] * boot a fresh core18 system with kernel 4.15 [Regression Potential] * little, change is very targeted This is uploaded to the bionic-proposed queue now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1783810/+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 1784347] Re: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath
Hello bugproxy, or anyone else affected, Accepted util-linux into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/util- linux/2.31.1-0.4ubuntu3.3 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: util-linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1784347 Title: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath Status in The Ubuntu-power-systems project: Triaged Status in util-linux package in Ubuntu: Triaged Status in util-linux source package in Bionic: Fix Committed Bug description: [Impact] Any user of Ubuntu on multipath, where the default path separator has been changed to something else. This possibly affects other scenarios where the partition separator can be changed. [Test case] 1) Install Ubuntu on multipath system 2) Change /etc/multipath.conf to set "path_separator" to "" or "p". 3) Reboot 4) Run 'sudo fdisk -l /dev/mapper/mpathX', to display a device's partitions where the path separator would be visible. [Regression potential] Minimal. This only affects display. Default separator on Ubuntu remains "-part". If the separator is not one of "", "p", or "-part", then "-part" would be used, as is already the case. == Comment: #0 - Chanh H. Nguyen - 2018-01-09 11:14:07 == We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the Emulex adapter to have the mpath disk. Running the fdisk -l and ls -l showing the conflict name for the mpath. :~# uname -a Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@boslcp4:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Bionic Beaver (development branch)" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic :~# fdisk -l /dev/mapper/mpatha Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 32768 bytes / 32768 bytes Disklabel type: dos Disk identifier: 0xa5be904b Device Boot StartEnd Sectors Size Id Type /dev/mapper/mpatha-part1 2048 419432447 419430400 200G 83 Linux /dev/mapper/mpatha-part2 419432448 838862847 419430400 200G 83 Linux /dev/mapper/mpatha-part3 838862848 1258291199 419428352 200G 83 Linux :~# ls -l /dev/mapper/mpatha* lrwxrwxrwx 1 root root 7 Jan 9 04:04 /dev/mapper/mpatha -> ../dm-0 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha1 -> ../dm-1 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha2 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha3 -> ../dm-3 == Comment: #2 - Chanh H. Nguyen - 2018-01-09 11:35:04 == I just modify the partitions and it is still showing the conflicting name on partitions. :~# ls -l /dev/mapper/mpatha* lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha -> ../dm-0 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha1 -> ../dm-1 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha2 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha3 -> ../dm-3 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha4 -> ../dm-4 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha5 -> ../dm-5 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha6 -> ../dm-6 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha7 -> ../dm-7 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha8 -> ../dm-8 :~# fdisk -l /dev/mapper/mpatha Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes,
[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5
Ubiquity with this fix exists in both cosmic and bionic-updates. ** Changed in: ubiquity (Ubuntu) Status: New => Fix Released ** Changed in: ubiquity (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1788597 Title: ubiquity broken with console-setup 1.178ubuntu2.5 Status in console-setup package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in console-setup source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Fix Released Bug description: [ SRU Justification ] Due to my brain being in the wrong language, a function was exiting the script instead of returning. Derp. [ Regression Potential ] N'much. [ Test Case ] Build a new ubiquity and see if we can haz keyboard again. [ Original Bug ] Since this version of console-setup in bionic ubiquity now skips the Keyboard and Wireless pages. http://launchpadlibrarian.net/382474004/console- setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+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 1797932] Re: Upgrade doesn't respect proprietary driver selection
To be clear, nvidia was never removed, as far as I can tell, but it was installed and then nouveau selected as the default. So, the upgrade upgraded nvidia (which is fine), but then the default became nvidia again. Not sure what should really happen in this case, or if maybe selecting nouveau should tear out all the nvidia bits. ** Summary changed: - Upgrade installs Nvidia + Upgrade doesn't respect proprietary driver selection -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1797932 Title: Upgrade doesn't respect proprietary driver selection Status in software-properties package in Ubuntu: New Bug description: Upgraded Bionic to Cosmic with iso from 13/10. Prior to upgrading was using the nouveau driver. Had previously installed nvidia to test a recent SRU fix. Once I had tested the fix I had gone back to additional drivers to revert to nouveau. Attached 2 screenshots from during the b-c upgrade and post upgrade - I've now got nvidia installed once more. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-common 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Oct 15 17:32:34 2018 InstallationDate: Installed on 2018-08-27 (49 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180824) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to cosmic on 2018-10-14 (1 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-09-21T16:30:23.845026 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797932/+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 1576353] Re: Install openssh-server with disabled password auth by default on servers
** Changed in: ubuntu-cdimage Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1576353 Title: Install openssh-server with disabled password auth by default on servers Status in Ubuntu CD Images: Won't Fix Status in livecd-rootfs package in Ubuntu: Won't Fix Status in openssh package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: we want to remove 'cloud-image' seed and join it with 'server' seed. openssh-server is one of the few (3) packages that are in cloud image and not in 'ubuntu-server'. We'd like to have the server iso install openssh-server by default and prompt the user if they want to enable it or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1576353/+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 1576353] Re: Install openssh-server with disabled password auth by default on servers
See the comment on the linked debian-cd MP from Marc Deslauriers. Note that the goal of removing the cloud-image seed is still entirely reasonable and doable, openssh-server should just move to livecd-rootfs as something always added to cloud images. Done and done. There's no reason that one package needs to be represented in a seed/task any more than custom kernels or cloud agents are. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1576353 Title: Install openssh-server with disabled password auth by default on servers Status in Ubuntu CD Images: In Progress Status in livecd-rootfs package in Ubuntu: New Status in openssh package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: New Bug description: we want to remove 'cloud-image' seed and join it with 'server' seed. openssh-server is one of the few (3) packages that are in cloud image and not in 'ubuntu-server'. We'd like to have the server iso install openssh-server by default and prompt the user if they want to enable it or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1576353/+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 1792189] Re: linux-firmware does not depend on initramfs-tools
This isn't a bug in linux-firmware, it shouldn't depend on initramfs- tools, but initrafms-tools shouldn't fail miserably when called in this fashion either. ** Package changed: linux-firmware (Ubuntu) => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1792189 Title: linux-firmware does not depend on initramfs-tools Status in initramfs-tools package in Ubuntu: New Bug description: In bug #1646197 the linux-firmware.postinst was added to call update- initramfs (provided by initramfs-tools. If the initramfs-tools package is not installed the installation of linux-firmware will fail. Recreate: sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* sudo apt-get install --assume-yes linux-generic Result: Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ... Setting up initramfs-tools-bin (0.130ubuntu3.3) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 2 ... Errors were encountered while processing: linux-firmware linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Impact: Builds of minimized images start with an image that has the linux-kvm kernel but lack initramfs-tools. Derivative builds that require a different kernel, linux-generic for example, will purge the existing kernel and install the correct kernel which could pull in linux-firmware and initramfs-tools. In that case the builds fail unless initramfs-tools is installed prior to kernel installation as a workaround for this missing package dependency. This has been recreated on cosmic and bionic, a fix is desired on each. (I was unable to recreate on Xenial but that package lacks the dependency as well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1792189/+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 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5
** Also affects: console-setup (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: console-setup (Ubuntu) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: console-setup (Ubuntu Bionic) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: console-setup (Ubuntu) Status: Confirmed => In Progress ** Changed in: console-setup (Ubuntu Bionic) Status: New => In Progress ** Changed in: console-setup (Ubuntu) Status: In Progress => Fix Committed ** Description changed: - Since this version of console-setup in bionic ubiquity now skips the - Keyboard and Wireless pages. + [ SRU Justification ] + Due to my brain being in the wrong language, a function was exiting the script instead of returning. Derp. + + [ Regression Potential ] + N'much. + + [ Test Case ] + Build a new ubiquity and see if we can haz keyboard again. + + [ Original Bug ] + Since this version of console-setup in bionic ubiquity now skips the Keyboard and Wireless pages. http://launchpadlibrarian.net/382474004/console- setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1788597 Title: ubiquity broken with console-setup 1.178ubuntu2.5 Status in console-setup package in Ubuntu: Fix Committed Status in console-setup source package in Bionic: In Progress Bug description: [ SRU Justification ] Due to my brain being in the wrong language, a function was exiting the script instead of returning. Derp. [ Regression Potential ] N'much. [ Test Case ] Build a new ubiquity and see if we can haz keyboard again. [ Original Bug ] Since this version of console-setup in bionic ubiquity now skips the Keyboard and Wireless pages. http://launchpadlibrarian.net/382474004/console- setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+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 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5
*sigh*... That exit really wanted to be a return. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1788597 Title: ubiquity broken with console-setup 1.178ubuntu2.5 Status in console-setup package in Ubuntu: Confirmed Bug description: Since this version of console-setup in bionic ubiquity now skips the Keyboard and Wireless pages. http://launchpadlibrarian.net/382474004/console- setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+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 1787460] Re: Unattended upgrades removed linux-image-generic
So, this might partially be a linux-meta/overrides bug. The top-level metas (linux-$flavour) should be in the metapackages section so that if they're removed (for instance, by someone who doesn't want headers, but kinda likes kernels), the manually installed bit is transferred down one level to linux-image-$flavour and linux-headers-$flavour. It might also be valid to say that the neverautoremove apt/kernel magic could/should include the mid-level metas in the list, so they're just considered manual regardless of what state they were accidentally put in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in unattended-upgrades package in Ubuntu: New Bug description: On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux- image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1787460/+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 1787460] Re: Unattended upgrades removed linux-image-generic
It does appear, however, that despite the above comment (which I think highlights ways we can make this foot a smaller target), this definitely began with human error: Start-Date: 2018-08-14 13:37:10 Commandline: apt dist-upgrade Install: linux-headers-4.15.0-32-generic:amd64 (4.15.0-32.35, automatic), linux-headers-4.15.0-32:amd64 (4.15.0-32.35, automatic) Upgrade: linux-headers-generic:amd64 (4.15.0.31.33, 4.15.0.32.34), linux-libc-dev:amd64 (4.15.0-31.33, 4.15.0-32.35) Remove: linux-signed-generic:amd64 (4.15.0.31.33), linux-generic:amd64 (4.15.0.31.33) End-Date: 2018-08-14 13:37:16 That's a manual apt dist-upgrade which would have asked for confirmation on that removal. unattended-upgrades alone would have never gotten into this situation, as it won't remove to force an upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in unattended-upgrades package in Ubuntu: New Bug description: On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux- image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1787460/+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 1772844] Re: snapd didn't initialize all the seeded snaps
Indeed, fixed on 18.04 and broken on 18.10 is intentional, as the 18.04 "fix" was a horrible hack in livecd-rootfs to work around the bug in time for the point release, while I've been assured that 18.10 will get a proper fix in snapd instead. ** Changed in: livecd-rootfs (Ubuntu) Status: New => Won't Fix ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Released ** Changed in: ubuntu-meta (Ubuntu Bionic) Status: New => Fix Released ** Changed in: snapd Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1772844 Title: snapd didn't initialize all the seeded snaps Status in OEM Priority Project: Fix Released Status in snapd: New Status in livecd-rootfs package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in ubuntu-meta source package in Bionic: Fix Released Bug description: snapd didn't initialize all the seeded snaps bionic-desktop-amd64.iso (20180522) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snapd 2.32.9+18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 22 22:59:18 2018 InstallationDate: Installed on 2018-05-23 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772844/+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 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
Note that this bug (and thus, the fix) probably only applies to the HWE variant of d-i with the 4.15 kernel. -- 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/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: In Progress Status in debian-installer package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Committed Status in debian-installer source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ? ? ??? IPR had similar issue reported #164932 and fixed with 4.15.0-20, looks installer need a fix for LSI (mpt3sas) devices too == Comment: #2 - SEETEENA THOUFEEK - 2018-07-03 02:01:47 == 164932 - refers LP1751813 == Comment: #3 - SEETEENA THOUFEEK - 2018-07-03 02:02:51 == Jul 2 08:49:52 anna-install: Installing mdadm-udeb Jul 2 08:49:52 disk-detect: No Intel/DDF RAID disks detected. Jul 2 08:49:52 anna-install: Installing dmraid-udeb Jul 2 08:49:52 disk-detect: No Serial ATA RAID disks detected Jul 2 08:49:53 check-missing-firmware: looking at dmesg again, restarting from \[ 330.659712\] Jul 2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg accordingly Jul 2 08:49:53 check-missing-firmware: saving timestamp for a later use: Jul 2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping Jul 2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not exist,
[Touch-packages] [Bug 1779815] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted debian-installer into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu451.25 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: debian-installer (Ubuntu) Status: Confirmed => Fix Released -- 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/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: In Progress Status in debian-installer package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Committed Status in debian-installer source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ? ?
[Touch-packages] [Bug 1783810] Re: [SRU] blocks boot on core18
Hello Michael, or anyone else affected, Accepted util-linux into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/util- linux/2.31.1-0.4ubuntu3.2 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: util-linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1783810 Title: [SRU] blocks boot on core18 Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Bionic: Fix Committed Bug description: The current version of libuuid is using getrandom() without the GRND_NONBLOCK flag. This means that in early boot the boot is blocked until the crng is initialized to "level=1" which on virtual machines may take some time. Upstream fixed this in https://github.com/karelzak/util- linux/commit/a9cf659e0508c1f56813a7d74c64f67bbc962538 and we should just backport the fix. [Impact] * Makes systems that use libuuid in early boot hang [Test Case] * boot a fresh core18 system with kernel 4.15 [Regression Potential] * little, change is very targeted This is uploaded to the bionic-proposed queue now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1783810/+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 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
Hello bugproxy, or anyone else affected, Accepted debian-installer into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu451.24 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: debian-installer (Ubuntu Xenial) Status: New => Fix Committed -- 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/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: In Progress Status in debian-installer package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Committed Status in debian-installer source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ? ?
[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
** Changed in: console-setup (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: console-setup (Ubuntu) Assignee: Gunnar Hjalmarsson (gunnarhj) => Adam Conrad (adconrad) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Fix Committed Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Confirmed Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Re-opening this bug as we had to revert the fix, because it was causing an installer regression: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1783326 That said, I think the "run it sometimes, but not always" fix was probably naive at best. The only two options that seem to make sense for fixing this properly are: 1) Make GNOME stop writing things to that file that console-setup doesn't understand, or 2) Make console-setup understand the things GNOME writes to that file. The second option is certainly the more appealing of the two, but it's clearly not going to happen before the point release in two days. ** Changed in: console-setup (Ubuntu Bionic) Status: Fix Released => Confirmed ** Changed in: console-setup (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Confirmed Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1779815] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: In Progress Status in debian-installer package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: New Status in systemd source package in Xenial: New Status in debian-installer source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ? ? ??? IPR had similar issue reported #164932 and fixed with 4.15.0-20, looks installer need a fix for LSI (mpt3sas) devices too == Comment: #2 - SEETEENA THOUFEEK - 2018-07-03 02:01:47 == 164932 - refers LP1751813 == Comment: #3 - SEETEENA THOUFEEK - 2018-07-03 02:02:51 == Jul 2 08:49:52 anna-install: Installing mdadm-udeb Jul 2 08:49:52 disk-detect: No Intel/DDF RAID disks detected. Jul 2 08:49:52 anna-install: Installing dmraid-udeb Jul 2 08:49:52 disk-detect: No Serial ATA RAID disks detected Jul 2 08:49:53 check-missing-firmware: looking at dmesg again, restarting from \[ 330.659712\] Jul 2
[Touch-packages] [Bug 1768797] Update Released
The verification of the Stable Release Update for software-properties has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1768797 Title: LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Released Bug description: * Impact When the U1 account credential expire it's not possible to disable livepatch * Test case - install/enable livepatch (from the first login wizard or software-properties) - invalidate your U1 credentials: * open "Password and Keys" * Search for an entry containing "ubuntusso" * Right click and open "Properties" * Show the password entry * Modify the 'macaroon' field (e.g. add a 1 at the beginning of the string so you can easily remote it later) - open software-properties -> the livepatch status should be marked as enable but the control active so it's possible to disable it * Regression potential Check that the software-properties checkbox reflect the correct status when the account are valid and invalid I enabled LivePatch via gnome-initial-setup and added my U1 account to g-o-a. My U1 account gets marked as expired quite often. When it's expired the LP entry in Software & Updates is not ticked to show that LP is running. When my u1 account is re-authenticated then everything shows correctly. This could make it seem that LivePatch does not run if your account expires, which is not the case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1768797/+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 1574351] Update Released
The verification of the Stable Release Update for perl has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1574351 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 Status in perl package in Ubuntu: Confirmed Status in pkgbinarymangler package in Ubuntu: Fix Released Status in perl source package in Bionic: Fix Released Status in pkgbinarymangler source package in Bionic: Fix Released Bug description: [Impact] * Pkgstripfiles generates different stripped documentation for arch:any packages depending on if arch:all packages are built at the same time. In practice it means that amd64 packages may end up different file contents of doc files compared to other architectures making multiarch installation of the affected packages impossible without workarounds. * To fix affected packages by a rebuild the pkgbinarymangler package needs to be backported, too. * The fix in pkgstripfiles is skipping symlinking documentation to dependent packages with identical content when the dependent packages are not built. [Test Case] * To test pkgbinarymangler rebuild perl i386 packages without arch:all packages with the fixed pkgbinarymangler package and observe the following message in the build log: ... Skipping perl-modules-5.26 because it is not to be built ... * Note that PPA builds skip the mangling steps thus the package needs to be built in sbuild/pbuilder/in the official archive with pkgbinarymangler added as an extra package in case of a local build. * The resulting libperl5.2? package can also be analyzed to see changelog.Debian.gz not symlinked to perl-modules-5.2?'s changelog, but to check if the original bug is fixed just install libperl5.26:amd64 and libperl5.26:i386 using multiarch (here we assume the current architecture is amd64): $ sudo dpkg --add-architecture i386 $ sudo apt update $ sudo apt install libperl5.26:i386 [Regression Potential] * The pkgbinarymangler fix may break the pkgstripfiles script causing FTBFS of unrelated packages or could cause building not stripped packages. The former problem would be caught early, while the latter can be avoided by checking the build logs of a few other packages rebuilt with the fixed pkgbinarymangler package. [Original Bug Text] Don't run aplication after upgrade from 14.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 21:08:20 2016 DpkgTerminalLog: Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ... Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 DuplicateSignature: Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 InstallationDate: Installed on 2016-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1574351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1260041] Update Released
The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1260041 Title: Unattended-Upgrades crashes with a dpkg error Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] * Unattended-upgrades fails upgrading packages in the middle of a dpkg/apt call due to a parallel process acquiring apt or dpkg lock while u-u is running, but u-u running apt/dpkg anyway without successfully re-acquiring the lock. * The fix is stopping processing updates when the lock is detected to be lost. [Test Case] * Set up a system with packages (> 30) to be upgraded: $ lxc launch ubuntu:b36ec647e374 uu-lock-bail * Set up two shells to run commands in parallel * In shell "A" run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug * After u-u started installing the updates run the following command in shell "B": $ while sleep 0.1; do python3 -c 'import apt, apt_pkg, time; print(apt_pkg.pkgsystem_lock()); time.sleep(2)' ; done * With not fixed u-u observe the following exception repeated in shell "B", then True being printed when the lock is successfully stolen from u-u: ... Traceback (most recent call last): File "", line 1, in apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? Traceback (most recent call last): File "", line 1, in apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? True Traceback (most recent call last): File "", line 1, in apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? True True True True ... Buggy u-u continues operation even after the lock is stolen. Fixed u-u stops operation with a printout similar to the following when it detects the lock to be stolen: ... Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log /usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure /var/cache/apt/archives/distro-info-data_0.37ubuntu0.1_all.deb /usr/bin/dpkg --status-fd 9 --configure --pending Exception happened during upgrade. Traceback (most recent call last): File "./unattended-upgrade", line 539, in cache_commit res = cache.commit(install_progress=iprogress) File "./unattended-upgrade", line 360, in __exit__ apt_pkg.pkgsystem_lock() apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? Exception happened during upgrade. NoneType: None Installing the upgrades failed! error message: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? dpkg returned a error! See /var/log/unattended-upgrades/unattended-upgrades-dpkg.log for details ... [Regression Potential] * As a consequence of the fix unattended-upgrade stops installing security-updates when an other dpkg frontend's parallel activity is detected. This is intentional to prevent parallel execution of dpkg and potentially leaving the system in an inconsistent state. The full fix will be implemented in LP: #1781169 and changing u-u to use the new locking mechanism, and then u-u will never lose the lock. [Other Info] I believe parallel dpkg calls cause many breakages reported against u-u and other packages listing breaking maintainer scripts. [Original Bug Text] As per https://bugs.launchpad.net/ubuntu/+source/unattended- upgrades/+bug/1052360/comments/17, I am filing a new bug with the specific error I am running into. This has been going on for quite a while now. Also, my log files still show up as I described in https://bugs.launchpad.net/ubuntu/+source/unattended- upgrades/+bug/1052360/comments/14. ProblemType: Bug DistroRelease:
[Touch-packages] [Bug 1762952] Update Released
The verification of the Stable Release Update for console-setup has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Fix Released Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1782835] Update Released
The verification of the Stable Release Update for console-setup has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1782835 Title: d-i step "Configure the keyboard" fails Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Bionic: Fix Released Bug description: Testing a bionic build of d-i w/ proposed results in a failure. From d-i's /var/log/syslog: Jul 20 20:01:04 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:23 main-menu[897]: INFO: Menu item 'console-setup-udeb' selected Jul 20 20:03:25 main-menu[897]: (process:1567): /var/lib/dpkg/info/console-setup-udeb.postinst: line 52: dpkg-query: not found Jul 20 20:03:25 main-menu[897]: WARNING **: Configuring 'console-setup-udeb' failed with error code 127 Jul 20 20:03:25 main-menu[897]: WARNING **: Menu item 'console-setup-udeb' failed. Jul 20 20:03:41 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:46 kernel: [ 224.155631] random: crng init done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1782835/+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 1772844] Re: snapd didn't initialize all the seeded snaps
** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1772844 Title: snapd didn't initialize all the seeded snaps Status in OEM Priority Project: Fix Released Status in snapd: New Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Status in livecd-rootfs source package in Bionic: New Status in ubuntu-meta source package in Bionic: New Bug description: snapd didn't initialize all the seeded snaps bionic-desktop-amd64.iso (20180522) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snapd 2.32.9+18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 22 22:59:18 2018 InstallationDate: Installed on 2018-05-23 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772844/+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 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
Hello bugproxy, or anyone else affected, Accepted debian-installer into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu543.1 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: debian-installer (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- 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/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: New Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: New Status in debian-installer source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ?
[Touch-packages] [Bug 1782835] Re: d-i step "Configure the keyboard" fails
** Package changed: linux (Ubuntu) => console-setup (Ubuntu) ** Changed in: console-setup (Ubuntu) Importance: Critical => Undecided ** Changed in: console-setup (Ubuntu) Status: Incomplete => New ** Changed in: console-setup (Ubuntu) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: console-setup (Ubuntu) Status: New => Fix Committed ** Changed in: console-setup (Ubuntu Bionic) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: console-setup (Ubuntu Bionic) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1782835 Title: d-i step "Configure the keyboard" fails Status in console-setup package in Ubuntu: Fix Committed Status in console-setup source package in Bionic: Fix Committed Bug description: Testing a bionic build of d-i w/ proposed results in a failure. From d-i's /var/log/syslog: Jul 20 20:01:04 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:23 main-menu[897]: INFO: Menu item 'console-setup-udeb' selected Jul 20 20:03:25 main-menu[897]: (process:1567): /var/lib/dpkg/info/console-setup-udeb.postinst: line 52: dpkg-query: not found Jul 20 20:03:25 main-menu[897]: WARNING **: Configuring 'console-setup-udeb' failed with error code 127 Jul 20 20:03:25 main-menu[897]: WARNING **: Menu item 'console-setup-udeb' failed. Jul 20 20:03:41 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:46 kernel: [ 224.155631] random: crng init done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1782835/+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 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
** Changed in: systemd (Ubuntu) Status: New => Fix Committed -- 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/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: New Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: New Status in debian-installer source package in Bionic: New Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ? ? ??? IPR had similar issue reported #164932 and fixed with 4.15.0-20, looks installer need a fix for LSI (mpt3sas) devices too == Comment: #2 - SEETEENA THOUFEEK - 2018-07-03 02:01:47 == 164932 - refers LP1751813 == Comment: #3 - SEETEENA THOUFEEK - 2018-07-03 02:02:51 == Jul 2 08:49:52 anna-install: Installing mdadm-udeb Jul 2 08:49:52 disk-detect: No Intel/DDF RAID disks detected. Jul 2 08:49:52 anna-install: Installing dmraid-udeb Jul 2 08:49:52 disk-detect: No Serial ATA RAID disks detected Jul 2 08:49:53 check-missing-firmware: looking at dmesg again, restarting from \[ 330.659712\] Jul 2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg accordingly Jul 2 08:49:53 check-missing-firmware: saving timestamp for a later use: Jul 2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping Jul 2
[Touch-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
I've uploaded a fixed systemd to cosmic and bionic for this (xenial will follow when I sort out the best way to backport the fix). dannf should be in a position to test this once a new d-i is built using the new udev-udeb. ** Also affects: debian-installer (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: debian-installer (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Adam Conrad (adconrad) -- 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/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in debian-installer source package in Xenial: New Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: New Status in debian-installer source package in Bionic: New Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: New Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB
[Touch-packages] [Bug 1771557] Update Released
The verification of the Stable Release Update for initramfs-tools has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1771557 Title: NVMe boot drives not supported - failing in generating initramfs Status in initramfs-tools: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Bug description: [Impact] When creating the initramfs image, mkinitramfs has multiple options on how to include modules. The default (and most common) one is the "MODULES=most", which includes the majority of filesystem modules and all the block device drivers. One other option is "MODULES=dep", which tries to descend in the sysfs hierarchy and guess modules to add, with the goal of reduce the size of initramfs. For the MODULES=dep case, the initramfs-tools hook-functions script cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing in the sysfs lookup, so it does not build the initram disk. Upstream solution is composed of at least 2 patches (it's a series, but the 2 below are really the needed ones): commit 3cb744c9 Author: Ben Hutchings hook-functions: Rewrite block device sysfs lookup to be generic commit 8ac52dc0 Author: Ben Hutchings hook-functions: Include modules for all components of a multi-disk device Instead of doing the huge backport, we added another sed substitution: currently the script has substitutions for sdX and hdX, in order to convert sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY. It's less intrusive than the full backport, since this is a minimal SRU to Trusty only. [Test Case] 1. Install Trusty with rootfs in a multi-disk(md) array composed of two nvme partitions - in my tests, I've used a RAID1. (lsblk output of my test env: nvme0n1 259:0010G 0 disk └─nvme0n1p1 259:1010G 0 part └─md0 9:0010G 0 raid1 / nvme1n1 259:2010G 0 disk └─nvme1n1p1 259:3010G 0 part └─md0 9:0010G 0 raid1 / ) 2. Once system is booted, modify the "/etc/initramfs- tools/initramfs.conf", replacing "MODULES=most" to "MODULES=dep". 3. Update your initramfs by running something like: "update-initramfs -u -k " The initramfs creating procedure will fail, unless the patch from this LP is present. [Regression Potential] If the sed expression was somewhat broken, we could have an issue generating initiramfs when MODULES is set to "dep", even for generic block devices (like regular HDDs). [Other Info] * This issue is based on Debian bug #785147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147 * Only Trusty is affected, Xenial and late contains the full fix as mentioned above : $ git describe --contains 8ac52dc0 v0.121_rc1~11 $ git describe --contains 3cb744c9 v0.121_rc1~11 $ rmadison initramfs-tools initramfs-tools | 0.103ubuntu4| trusty | source, all ==> initramfs-tools | 0.103ubuntu4.10 | trusty-updates | source, all initramfs-tools | 0.122ubuntu8| xenial | source, all initramfs-tools | 0.122ubuntu8.11 | xenial-updates | source, all initramfs-tools | 0.125ubuntu12 | artful | source, all initramfs-tools | 0.125ubuntu12.1 | artful-updates | source, all initramfs-tools | 0.130ubuntu3| bionic | source, all initramfs-tools | 0.130ubuntu6| cosmic | source, all To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+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 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04
** Changed in: initramfs-tools (Ubuntu Xenial) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1766727 Title: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in s390-tools package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: New Status in s390-tools source package in Xenial: Fix Released Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in initramfs-tools source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Status in s390-tools source package in Bionic: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Bug description: [Impact] Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. [Test Case] Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. [Regression] zipl update on s390x might fail, causing the system to be unbootable. Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). --- Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic Using config file '/etc/zipl.conf' Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or directory run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1 [1mdpkg:[0m error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for dictionaries-common (1.27.2) ... Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. Processing triggers for sgml-base (1.29) ... Processing triggers for resolvconf (1.79ubuntu10) ... Processing triggers for ureadahead (0.100.0-20) ... Errors were encountered while processing: initramfs-tools Log ended: 2018-04-24 13:12:40 --- ApportVersion: 2.20.9-0ubuntu6 Architecture: s390x DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic s390x UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1766727/+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 1766727] Update Released
The verification of the Stable Release Update for s390-tools has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1766727 Title: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in s390-tools package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: New Status in s390-tools source package in Xenial: Fix Released Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in initramfs-tools source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Status in s390-tools source package in Bionic: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Bug description: [Impact] Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. [Test Case] Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. [Regression] zipl update on s390x might fail, causing the system to be unbootable. Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). --- Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic Using config file '/etc/zipl.conf' Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or directory run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1 [1mdpkg:[0m error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for dictionaries-common (1.27.2) ... Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. Processing triggers for sgml-base (1.29) ... Processing triggers for resolvconf (1.79ubuntu10) ... Processing triggers for ureadahead (0.100.0-20) ... Errors were encountered while processing: initramfs-tools Log ended: 2018-04-24 13:12:40 --- ApportVersion: 2.20.9-0ubuntu6 Architecture: s390x DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic s390x UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1766727/+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 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04
** Also affects: s390-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1766727 Title: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). --- Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic Using config file '/etc/zipl.conf' Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or directory run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1 [1mdpkg:[0m error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for dictionaries-common (1.27.2) ... Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. Processing triggers for sgml-base (1.29) ... Processing triggers for resolvconf (1.79ubuntu10) ... Processing triggers for ureadahead (0.100.0-20) ... Errors were encountered while processing: initramfs-tools Log ended: 2018-04-24 13:12:40 --- ApportVersion: 2.20.9-0ubuntu6 Architecture: s390x DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic s390x UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1766727/+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 1761593] Re: Uninstall left nouveau blacklisted
The real answer here is we should rm_conffile those files in /etc and ship them in /lib/modprobe.d instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1761593 Title: Uninstall left nouveau blacklisted Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: Following a successful install and subsequent use of nvidia-340 - uninstallation of nvidia via Additional Drivers led to a reboot to a desktop at 640x480 px. Investigation found an nvidia created file left on the system blacklisting nouveau, deleted file and rebooted to normal desktop. Didn't think about ubuntu-reporting this - can try and replicate and apport-collect if it's of any use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+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 1761593] Re: Uninstall left nouveau blacklisted
This is very much a bug in nvidia-graphics-drivers-340. One can debate if software-properties should or shouldn't purge (though traditionally, the argument was that silent frontends shouldn't purge because the user hasn't explicitly asked for that), but if a removed package's unpurged conffiles cause the system to misbehave, that package needs to be rethought to avoid that situation. ** Package changed: nvidia-settings (Ubuntu) => nvidia-graphics- drivers-340 (Ubuntu) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1761593 Title: Uninstall left nouveau blacklisted Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: Following a successful install and subsequent use of nvidia-340 - uninstallation of nvidia via Additional Drivers led to a reboot to a desktop at 640x480 px. Investigation found an nvidia created file left on the system blacklisting nouveau, deleted file and rebooted to normal desktop. Didn't think about ubuntu-reporting this - can try and replicate and apport-collect if it's of any use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+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 1746807] Re: 18.04 daily installer fails missing kernel
** Also affects: apt (Ubuntu Bionic) Importance: Critical Assignee: Julian Andres Klode (juliank) Status: Fix Released -- 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/1746807 Title: 18.04 daily installer fails missing kernel Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Bug description: "No installable kernel was found in the defined APT sources. You may try to continue without a kernel, and manually install your own kernel later. This is only recommended for experts, otherwise you will likely end up with a machine that doesn't boot. Continue without installing a kernel." Lubuntu Daily 18.04 dated 2018-February 1. note: yesterdays (Jan 31) install works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746807/+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 1753441] Re: [MIR] lame
lame 3.100-2 in bionic: universe/sound -> main lame 3.100-2 in bionic amd64: universe/sound/optional/100% -> main lame 3.100-2 in bionic arm64: universe/sound/optional/100% -> main lame 3.100-2 in bionic armhf: universe/sound/optional/100% -> main lame 3.100-2 in bionic i386: universe/sound/optional/100% -> main lame 3.100-2 in bionic ppc64el: universe/sound/optional/100% -> main lame 3.100-2 in bionic s390x: universe/sound/optional/100% -> main lame-doc 3.100-2 in bionic amd64: universe/doc/optional/100% -> main lame-doc 3.100-2 in bionic arm64: universe/doc/optional/100% -> main lame-doc 3.100-2 in bionic armhf: universe/doc/optional/100% -> main lame-doc 3.100-2 in bionic i386: universe/doc/optional/100% -> main lame-doc 3.100-2 in bionic ppc64el: universe/doc/optional/100% -> main lame-doc 3.100-2 in bionic s390x: universe/doc/optional/100% -> main libmp3lame-dev 3.100-2 in bionic amd64: universe/libdevel/optional/100% -> main libmp3lame-dev 3.100-2 in bionic arm64: universe/libdevel/optional/100% -> main libmp3lame-dev 3.100-2 in bionic armhf: universe/libdevel/optional/100% -> main libmp3lame-dev 3.100-2 in bionic i386: universe/libdevel/optional/100% -> main libmp3lame-dev 3.100-2 in bionic ppc64el: universe/libdevel/optional/100% -> main libmp3lame-dev 3.100-2 in bionic s390x: universe/libdevel/optional/100% -> main libmp3lame0 3.100-2 in bionic amd64: universe/libs/optional/100% -> main libmp3lame0 3.100-2 in bionic arm64: universe/libs/optional/100% -> main libmp3lame0 3.100-2 in bionic armhf: universe/libs/optional/100% -> main libmp3lame0 3.100-2 in bionic i386: universe/libs/optional/100% -> main libmp3lame0 3.100-2 in bionic ppc64el: universe/libs/optional/100% -> main libmp3lame0 3.100-2 in bionic s390x: universe/libs/optional/100% -> main Override [y|N]? y 25 publications overridden. ** Changed in: lame (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: lame (Ubuntu) Assignee: Iain Lane (laney) => Adam Conrad (adconrad) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1753441 Title: [MIR] lame Status in lame package in Ubuntu: Fix Released Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/lame https://people.canonical.com/~ubuntu-security/cve/pkg/lame.html The Ubuntu CVE page lists some 'needed' ones but from looking at those ones in Debian they are duplicates and should be fixed already. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/lame https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=lame I think they are reasonably calm given that this is a well known project. Dependencies We need libmp3lame0 in main, and this depends on libc6 only. Standards compliance 4.1.1 and dh minimal style rules. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1753441/+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 1753450] Re: [MIR] mpg123
mpg123 1.25.8-1 in bionic: universe/sound -> main libmpg123-0 1.25.8-1 in bionic amd64: universe/libs/optional/100% -> main libmpg123-0 1.25.8-1 in bionic arm64: universe/libs/optional/100% -> main libmpg123-0 1.25.8-1 in bionic armhf: universe/libs/optional/100% -> main libmpg123-0 1.25.8-1 in bionic i386: universe/libs/optional/100% -> main libmpg123-0 1.25.8-1 in bionic ppc64el: universe/libs/optional/100% -> main libmpg123-0 1.25.8-1 in bionic s390x: universe/libs/optional/100% -> main libmpg123-dev 1.25.8-1 in bionic amd64: universe/libdevel/optional/100% -> main libmpg123-dev 1.25.8-1 in bionic arm64: universe/libdevel/optional/100% -> main libmpg123-dev 1.25.8-1 in bionic armhf: universe/libdevel/optional/100% -> main libmpg123-dev 1.25.8-1 in bionic i386: universe/libdevel/optional/100% -> main libmpg123-dev 1.25.8-1 in bionic ppc64el: universe/libdevel/optional/100% -> main libmpg123-dev 1.25.8-1 in bionic s390x: universe/libdevel/optional/100% -> main libout123-0 1.25.8-1 in bionic amd64: universe/libs/optional/100% -> main libout123-0 1.25.8-1 in bionic arm64: universe/libs/optional/100% -> main libout123-0 1.25.8-1 in bionic armhf: universe/libs/optional/100% -> main libout123-0 1.25.8-1 in bionic i386: universe/libs/optional/100% -> main libout123-0 1.25.8-1 in bionic ppc64el: universe/libs/optional/100% -> main libout123-0 1.25.8-1 in bionic s390x: universe/libs/optional/100% -> main mpg123 1.25.8-1 in bionic amd64: universe/sound/optional/100% -> main mpg123 1.25.8-1 in bionic arm64: universe/sound/optional/100% -> main mpg123 1.25.8-1 in bionic armhf: universe/sound/optional/100% -> main mpg123 1.25.8-1 in bionic i386: universe/sound/optional/100% -> main mpg123 1.25.8-1 in bionic ppc64el: universe/sound/optional/100% -> main mpg123 1.25.8-1 in bionic s390x: universe/sound/optional/100% -> main Override [y|N]? y 25 publications overridden. ** Changed in: mpg123 (Ubuntu) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: mpg123 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1753450 Title: [MIR] mpg123 Status in mpg123 package in Ubuntu: Fix Released Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/mpg123 https://people.canonical.com/~ubuntu-security/cve/pkg/mpg123.html The Ubuntu CVE page lists a 'needed' one which AFAICS is fixed in 1.25.8-1. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/mpg123 https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=mpg123 Dependencies We need libmpg123-0 in main, and this depends on libc6 only. Standards compliance 4.1.2. debian/rules is slightly complicated because it generates some wrapper scripts for some old binary names. Those binaries don't go in a package that we need in main. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1753450/+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 1749036] Re: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has multiple installed in
e2fsprogs (1.43.9-1ubuntu1) bionic; urgency=medium * Make transitional library packages be Arch: any and Multi-Arch: same so that upgrades actually function correctly when two or more exist. -- Adam Conrad <adcon...@ubuntu.com> Mon, 19 Feb 2018 06:05:49 -0700 ** Changed in: e2fsprogs (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1749036 Title: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has multiple installed instances Status in e2fsprogs package in Ubuntu: Fix Released Bug description: This happened during a partial upgrade of Bionic. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libcomerr2 1.43.8-2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Mon Feb 12 15:51:57 2018 Dependencies: gcc-7-base 7.2.0-18ubuntu2 libc6 2.26-0ubuntu2 libgcc1 1:7.2.0-18ubuntu2 DpkgTerminalLog: Preparing to unpack .../comerr-dev_2.1-1.43.9-1_amd64.deb ... Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ... dpkg: error processing archive /var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack): libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has multiple installed instances DuplicateSignature: package:libcomerr2:1.43.8-2 Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ... dpkg: error processing archive /var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack): libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has multiple installed instances ErrorMessage: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has multiple installed instances InstallationDate: Installed on 2013-01-16 (1853 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: e2fsprogs Title: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has multiple installed instances UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1749036/+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 1687454] Re: [MIR] nghttp2
Override component to main nghttp2 1.28.0-1 in bionic: universe/misc -> main Override [y|N]? y 1 publication overridden. Override component to main libnghttp2-14 1.28.0-1 in bionic amd64: universe/libs/optional/100% -> main libnghttp2-14 1.28.0-1 in bionic arm64: universe/libs/optional/100% -> main libnghttp2-14 1.28.0-1 in bionic armhf: universe/libs/optional/100% -> main libnghttp2-14 1.28.0-1 in bionic i386: universe/libs/optional/100% -> main libnghttp2-14 1.28.0-1 in bionic ppc64el: universe/libs/optional/100% -> main libnghttp2-14 1.28.0-1 in bionic s390x: universe/libs/optional/100% -> main libnghttp2-dev 1.28.0-1 in bionic amd64: universe/libdevel/optional/100% -> main libnghttp2-dev 1.28.0-1 in bionic arm64: universe/libdevel/optional/100% -> main libnghttp2-dev 1.28.0-1 in bionic armhf: universe/libdevel/optional/100% -> main libnghttp2-dev 1.28.0-1 in bionic i386: universe/libdevel/optional/100% -> main libnghttp2-dev 1.28.0-1 in bionic ppc64el: universe/libdevel/optional/100% -> main libnghttp2-dev 1.28.0-1 in bionic s390x: universe/libdevel/optional/100% -> main libnghttp2-doc 1.28.0-1 in bionic amd64: universe/doc/optional/100% -> main libnghttp2-doc 1.28.0-1 in bionic arm64: universe/doc/optional/100% -> main libnghttp2-doc 1.28.0-1 in bionic armhf: universe/doc/optional/100% -> main libnghttp2-doc 1.28.0-1 in bionic i386: universe/doc/optional/100% -> main libnghttp2-doc 1.28.0-1 in bionic ppc64el: universe/doc/optional/100% -> main libnghttp2-doc 1.28.0-1 in bionic s390x: universe/doc/optional/100% -> main Override [y|N]? y ** Changed in: nghttp2 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1687454 Title: [MIR] nghttp2 Status in apache2 package in Ubuntu: Triaged Status in curl package in Ubuntu: Triaged Status in nghttp2 package in Ubuntu: Fix Released Bug description: Availability: src:nghttp2 is in artful/universe and builds binary packages for all available architectures. Rationale: In order to enable apache2's support for HTTP/2, libnghttp2-14 must be in main (libnghttp2-dev is added as a b-d for src:apache2, but it can remain in universe). The other binary packages produced by src:nghttp2 should remain in universe. While upstream Apache still describes mod_http2 as 'experimental' (https://httpd.apache.org/docs/2.4/mod/mod_http2.html), we presumably want to enable it by 18.04. It makes sense to process this MIR now so that we can work through issues with HTTP/2 support during the 17.10 cycle. Rationale update: Upstream Apache has indicated 2.4.26 will 'unmark' mod_http2 has 'experimental': https://httpd.apache.org/docs/2.4/howto/http2.html#comments_section Rationale update v2: The public page referred above already has removed the note and marked http2 as an "extension". Quality assurance: The only package needed at runtime to be in main is libnghttp2-14 (current ABI) itself. As this is only a library, there is no configuration required after installation. No debconf questions are asked by default during the installation of libnghttp2-14. There are no long-term outstanding bugs against libnghttp2. Ubuntu bugs: https://bugs.launchpad.net/ubuntu/+source/nghttp2 - There is one automated (it seems) report of a security issue with the 16.04 version. I have not yet confirmed if it was/is present in the latest versions. + I received a forward offlist between the bug reporter and upstream developer. This particular issue is in example code which documents potential usage, but is not part of the shipped library itself. Debian bugs: https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;src=nghttp2 - Two bugs, neither of which are serious. Upstream issue tracker: https://github.com/nghttp2/nghttp2/issues - There are currently 175 open issues for the upstream project. - It is not yet clear how many of these issues are in the core library vs. the binary tools built by the upstream project. The package seems to be well-maintained in Debian. The package does not interact with exotic hardware (or hardware at all). Based upon the latest build logs, some tests are run, but not all. I will investigate if all tests can be run during the build. The package's debian/watch file is current. UI standards: N/A, as the library is not a user-facing application. Dependencies: The only binary dependency of libngttp2-14 is libc6 which is in main. Standards compliance: The package meets the FHS and Debian Policy standards. Maintenance: I have subscribed Ubuntu Server to the nghttp2 source package as the "owning" team. Background information: There are significant improvements associate with HTTP/2. It was deferred in 16.04 because it was considered 'too new' at the time. While Apache still describes the mod as
[Touch-packages] [Bug 1722564] Please test proposed package
Hello Scott, or anyone else affected, Accepted apport into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.4-0ubuntu4.9 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! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1722564 Title: apport question will not accept multi-character responses Status in Apport: Confirmed Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Committed Status in apport source package in Zesty: Fix Committed Status in apport source package in Artful: Fix Committed Bug description: === Begin SRU Template === [Impact] Packages which provide apport integration with more than 9 options in a choice will not be able to select options numbered >= 10 on the commandline using 'ubuntu-bug ' [Test Case] Overview: 1. Update to proposed versions of cloud-init v. 17.1 and apport v. 2. Run 'ubuntu-bug cloud-init' attempt to report a bug on a cloud choice greater than 9 3. View report and make sure the proper cloud is reported Script: if [ ! -f './lxc-proposed-snapshot' ]; then wget https://raw.githubusercontent.com/cloud-init/ubuntu-sru/master/bin/lxc-proposed-snapshot; chmod 755 lxc-proposed-snapshot; fi for release in xenial artful; do ref=$release-proposed; echo "$release START --"; lxc-proposed-snapshot --proposed --publish $release $ref; lxc init $ref test-$release; lxc start test-$release; lxc exec test-$release -- apt install apport; lxc exec test-$release -- dpkg-query --show apport; lxc exec test-$release -- ubuntu-bug cloud-init; done [Regression Potential] Minimal. This bug only affects packages with >9 bug filing options for a given choice. Worst case, is bugs filed would incorrectly represent option 1 of a selection instead of option 1X. === End SRU Template === === original description === the newly added cloud-init apport support shows a list of cloud providers and asks the user to select one. There are currently 18 options. For any option > 10, apport will just take the '1' that is typed as the answer. It should obviously wait for more than one character or a carriage return. *** Please select the cloud vendor or environment in which this instance is running Choices: 1: Amazon - Ec2 2: AliYun 3: AltCloud 4: Azure 5: Bigstep 6: CloudSigma 7: CloudStack 8: DigitalOcean 9: GCE - Google Compute Engine 10: MAAS 11: NoCloud 12: OpenNebula 13: OpenStack 14: OVF 15: Scaleway 16: SmartOS 17: VMware 18: Other C: Cancel Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 Date: Tue Oct 10 15:21:48 2017 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1722564/+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 1722564] Please test proposed package
Hello Scott, or anyone else affected, Accepted apport into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.7-0ubuntu3.6 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-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. 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! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1722564 Title: apport question will not accept multi-character responses Status in Apport: Confirmed Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Committed Status in apport source package in Zesty: Fix Committed Status in apport source package in Artful: Fix Committed Bug description: === Begin SRU Template === [Impact] Packages which provide apport integration with more than 9 options in a choice will not be able to select options numbered >= 10 on the commandline using 'ubuntu-bug ' [Test Case] Overview: 1. Update to proposed versions of cloud-init v. 17.1 and apport v. 2. Run 'ubuntu-bug cloud-init' attempt to report a bug on a cloud choice greater than 9 3. View report and make sure the proper cloud is reported Script: if [ ! -f './lxc-proposed-snapshot' ]; then wget https://raw.githubusercontent.com/cloud-init/ubuntu-sru/master/bin/lxc-proposed-snapshot; chmod 755 lxc-proposed-snapshot; fi for release in xenial artful; do ref=$release-proposed; echo "$release START --"; lxc-proposed-snapshot --proposed --publish $release $ref; lxc init $ref test-$release; lxc start test-$release; lxc exec test-$release -- apt install apport; lxc exec test-$release -- dpkg-query --show apport; lxc exec test-$release -- ubuntu-bug cloud-init; done [Regression Potential] Minimal. This bug only affects packages with >9 bug filing options for a given choice. Worst case, is bugs filed would incorrectly represent option 1 of a selection instead of option 1X. === End SRU Template === === original description === the newly added cloud-init apport support shows a list of cloud providers and asks the user to select one. There are currently 18 options. For any option > 10, apport will just take the '1' that is typed as the answer. It should obviously wait for more than one character or a carriage return. *** Please select the cloud vendor or environment in which this instance is running Choices: 1: Amazon - Ec2 2: AliYun 3: AltCloud 4: Azure 5: Bigstep 6: CloudSigma 7: CloudStack 8: DigitalOcean 9: GCE - Google Compute Engine 10: MAAS 11: NoCloud 12: OpenNebula 13: OpenStack 14: OVF 15: Scaleway 16: SmartOS 17: VMware 18: Other C: Cancel Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 Date: Tue Oct 10 15:21:48 2017 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1722564/+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 1722564] Re: apport question will not accept multi-character responses
Hello Scott, or anyone else affected, Accepted apport into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.1-0ubuntu2.14 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: apport (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial ** Changed in: apport (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1722564 Title: apport question will not accept multi-character responses Status in Apport: Confirmed Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Committed Status in apport source package in Zesty: Fix Committed Status in apport source package in Artful: Fix Committed Bug description: === Begin SRU Template === [Impact] Packages which provide apport integration with more than 9 options in a choice will not be able to select options numbered >= 10 on the commandline using 'ubuntu-bug ' [Test Case] Overview: 1. Update to proposed versions of cloud-init v. 17.1 and apport v. 2. Run 'ubuntu-bug cloud-init' attempt to report a bug on a cloud choice greater than 9 3. View report and make sure the proper cloud is reported Script: if [ ! -f './lxc-proposed-snapshot' ]; then wget https://raw.githubusercontent.com/cloud-init/ubuntu-sru/master/bin/lxc-proposed-snapshot; chmod 755 lxc-proposed-snapshot; fi for release in xenial artful; do ref=$release-proposed; echo "$release START --"; lxc-proposed-snapshot --proposed --publish $release $ref; lxc init $ref test-$release; lxc start test-$release; lxc exec test-$release -- apt install apport; lxc exec test-$release -- dpkg-query --show apport; lxc exec test-$release -- ubuntu-bug cloud-init; done [Regression Potential] Minimal. This bug only affects packages with >9 bug filing options for a given choice. Worst case, is bugs filed would incorrectly represent option 1 of a selection instead of option 1X. === End SRU Template === === original description === the newly added cloud-init apport support shows a list of cloud providers and asks the user to select one. There are currently 18 options. For any option > 10, apport will just take the '1' that is typed as the answer. It should obviously wait for more than one character or a carriage return. *** Please select the cloud vendor or environment in which this instance is running Choices: 1: Amazon - Ec2 2: AliYun 3: AltCloud 4: Azure 5: Bigstep 6: CloudSigma 7: CloudStack 8: DigitalOcean 9: GCE - Google Compute Engine 10: MAAS 11: NoCloud 12: OpenNebula 13: OpenStack 14: OVF 15: Scaleway 16: SmartOS 17: VMware 18: Other C: Cancel Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 Date: Tue Oct 10 15:21:48 2017 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1722564/+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 1716203] Re: Backport packages for 16.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted xorg-server-hwe-16.04 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-hwe-16.04/2:1.19.5-0ubuntu2~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: xorg-server-hwe-16.04 (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1716203 Title: Backport packages for 16.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-5.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-5.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in wayland-protocols source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.4 *** A minor update, only some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.76 to 2.4.83 - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests - intel: new pci-ids - drm: leak fixes, manpage updates - exynos, etnaviv, freedreno, android: fixes, new stuff wayland-protocols: None, just adds a few protocol definitions (xml files) llvm-toolchain-5.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-5 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for the bugfix release (xenial & artful) is bug 1727390 [Other information] build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault
Hello Lawrence, or anyone else affected, Accepted mesa into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: mesa (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1720890 Title: vulkan-smoketest segfaults steam vulkan games segfault Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: $ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 $ apt-cache policy mesa-vulkan-drivers mesa-vulkan-drivers: Installed: 17.2.1-0ubuntu1 Candidate: 17.2.1-0ubuntu1 Version table: *** 17.2.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install vulkan-utils Open a terminal type vulkan-smoketest instead of a glxgears type window it will segfault. message from kernel.log: Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in libvulkan_radeon.so[7fed619ab000+18b000] syslog: Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in libvulkan_radeon.so[7f627053b000+18b000] What should happen is a glxgears like window will open and render properly instead of segfaulting. It appears that the culprit is an old or broken libvulkan_radeon.so provided by mesa-vulkan-drivers. As a test I renamed the old lib and dropped in a newer version from oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad Max now work properly in Vulkan mode as well instead of segfaulting. This issue is also present on Zesty and fixed in both Oibaf's and Padoka's ppa's since April back when they were rolling 17.2 mesa. I have no idea if libvulkan_intel.so also needs updating no hardware to check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+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 1716203] Re: Backport packages for 16.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted mesa into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: mesa (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1716203 Title: Backport packages for 16.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-5.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-5.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in wayland-protocols source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.4 *** A minor update, only some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.76 to 2.4.83 - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests - intel: new pci-ids - drm: leak fixes, manpage updates - exynos, etnaviv, freedreno, android: fixes, new stuff wayland-protocols: None, just adds a few protocol definitions (xml files) llvm-toolchain-5.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-5 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for the bugfix release (xenial & artful) is bug 1727390 [Other information] build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)
Hello Timo, or anyone else affected, Accepted mesa into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: mesa (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) Status in Mesa: In Progress Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+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 1727390] Re: New bugfix release 17.2.4
Hello Timo, or anyone else affected, Accepted mesa into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: mesa (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727390 Title: New bugfix release 17.2.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] A new upstream bugfix release is available. Release note diff compared to 17.2.2: "Mesa 17.2.3 is now available. In this release we have: The Vulkan drivers ANV and RADV have multiple small fixes. The EGL code has improved handling of the new wl_dmabuf codepath. SWR no longer crashes when checking environment variables. Other gallium drivers have also seen updates - freedreno, nouveau and radeonsi. The gallivm module, used by llvmpipe et al. has gained little endian PPC64 fixes. The VA and VDPAU state-trackers have seems improvements handling interlaced videos. We're using python3 compatible constructs which gives us SCons 3.0 support." "Mesa 17.2.4 is now available. In this release we have: In Mesa Core we have included a change to prevent KOTOR from breaking when in combination with the ATI fragment shader extension. Additionally, NIR has also received a correction. Mesa's state tracker has gotten a patch to avoid leaks in certain situations like when resizing a window. Intel drivers have received several fixes. The compiler has gotten a couple, while anv also received one. i965 got a patch to avoid VA- API, Beignet and other contexts in the system to break when in combination with previous versions of Mesa 17.2.x. AMD's compiler has received a couple of fixes while radv has also received another couple, including one to avoid a hang due to an overflow on huge textures. Broadcom's vc4 has corrected a problem when compiling with Android's clang. clover has also seen fixed a problem compiling after a specific clang revision. Vulkan's WSI has gotten plugged a memory leak for X11." [Test case] Test typical use cases on the most common hw/driver combinations: intel/i965 nvidia/nouveau radeon/radeonsi [Regression potential] These releases are tested against compliance, bugfix releases in particular have minimal risk of regressing anything major at least. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1726608] Re: Alt+Arrow in gnome-shell unexpectedly switches VTs
Oh, derp. It's not the udev rule, it's the console-setup postinst. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1726608 Title: Alt+Arrow in gnome-shell unexpectedly switches VTs Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Trusty: New Status in console-setup source package in Xenial: New Status in console-setup source package in Zesty: New Bug description: I'm experiencing a bug similar to bug 1710637 with Ubuntu 17.10 again. Test Case - schroot -u root -c trusty-amd64 edit /etc/apt/sources.list to xenial apt-get update apt-get install console-setup use alt+tab to bring up the window switcher then use alt+arrow to switch windows I then end up at the gdm login screen or a virtual tty. Installing a different set of packages, via apt-get dist-upgrade, actually ended up killing my desktop session. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 14:30:16 2017 DisplayManager: gdm3 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['sound-output-device-choo...@kgshank.net', 'multi-monitors-add-on@spin83', 'datetime-for...@daniel-khodabakhsh.github.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'terminator.desktop', 'virt-manager.desktop', 'chromium-browser.desktop', 'firefox.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2013-01-16 (1741 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1726608/+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 1726608] Re: Alt+Arrow in gnome-shell unexpectedly switches VTs
The real question here is why a rule in a chroot is being executed by a udev outside the chroot. WTF, udev. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1726608 Title: Alt+Arrow in gnome-shell unexpectedly switches VTs Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Trusty: New Status in console-setup source package in Xenial: New Status in console-setup source package in Zesty: New Bug description: I'm experiencing a bug similar to bug 1710637 with Ubuntu 17.10 again. Test Case - schroot -u root -c trusty-amd64 edit /etc/apt/sources.list to xenial apt-get update apt-get install console-setup use alt+tab to bring up the window switcher then use alt+arrow to switch windows I then end up at the gdm login screen or a virtual tty. Installing a different set of packages, via apt-get dist-upgrade, actually ended up killing my desktop session. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 14:30:16 2017 DisplayManager: gdm3 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['sound-output-device-choo...@kgshank.net', 'multi-monitors-add-on@spin83', 'datetime-for...@daniel-khodabakhsh.github.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'terminator.desktop', 'virt-manager.desktop', 'chromium-browser.desktop', 'firefox.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2013-01-16 (1741 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1726608/+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 1716203] Re: Backport packages for 16.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted wayland-protocols into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wayland- protocols/1.10-1~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: wayland-protocols (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1716203 Title: Backport packages for 16.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-5.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-5.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in wayland-protocols source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.4 *** A minor update, only some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.76 to 2.4.83 - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests - intel: new pci-ids - drm: leak fixes, manpage updates - exynos, etnaviv, freedreno, android: fixes, new stuff wayland-protocols: None, just adds a few protocol definitions (xml files) llvm-toolchain-5.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-5 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for the bugfix release (xenial & artful) is bug 1727390 [Other information] build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1716203] Re: Backport packages for 16.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted llvm-toolchain-5.0 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm- toolchain-5.0/1:5.0-3~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: llvm-toolchain-5.0 (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1716203 Title: Backport packages for 16.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-5.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-5.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in wayland-protocols source package in Xenial: New Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.4 *** A minor update, only some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.76 to 2.4.83 - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests - intel: new pci-ids - drm: leak fixes, manpage updates - exynos, etnaviv, freedreno, android: fixes, new stuff wayland-protocols: None, just adds a few protocol definitions (xml files) llvm-toolchain-5.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-5 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for the bugfix release (xenial & artful) is bug 1727390 [Other information] build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1696298] Update Released
The verification of the Stable Release Update for tzdata has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1696298 Title: leap-seconds.list file expires 28 June 2017 Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Released Status in tzdata source package in Xenial: Fix Released Status in tzdata source package in Zesty: Fix Released Status in tzdata source package in Artful: Fix Released Bug description: The currently published tzdata package for supported distributions contains a leap-seconds.list file that expires on 28 June 2017 and that was based on data available up through IERS Bulletin C52. IERS Bulletin C53 was published on Jan 9 2017 confirming that a June 30 2017 would not be issued. I'm not sure what serves as the upstream data source for this package, but both IEFT and the eggertz tz repo have a leap-seconds.list file that incorporates Bulletin C53. https://www.ietf.org/timezones/data/leap-seconds.list https://github.com/eggert/tz/blob/master/leap-seconds.list Would it be possible to get the package updated to include these more recent files? Some applications make use of the expiration data in this file and will raise exceptions to the user if it has gone stale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1696298/+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 1722162] Please test proposed package
Hello Timo, or anyone else affected, Accepted binutils into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/binutils/2.26.1-1ubuntu1~16.04.6 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1722162 Title: gold: Fix internal error when applying TLSDESC relocations with no TLS segment. Status in binutils: Fix Released Status in binutils package in Ubuntu: Invalid Status in binutils source package in Xenial: Fix Committed Bug description: [Impact] llvm-5.0 fails to build on arm64/xenial because of gold/19353. [Test case] backport the upstream commit, test llvm-5 build ond arm64 [Regression potential] Unknown To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1722162/+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 1722162] Re: gold: Fix internal error when applying TLSDESC relocations with no TLS segment.
I've built this in the ubuntu-security-proposed PPA so it can be copied to -security once it passes SRU verification, to keep the toolchain in sync between pockets. ** Changed in: binutils (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1722162 Title: gold: Fix internal error when applying TLSDESC relocations with no TLS segment. Status in binutils: Fix Released Status in binutils package in Ubuntu: Invalid Status in binutils source package in Xenial: Fix Committed Bug description: [Impact] llvm-5.0 fails to build on arm64/xenial because of gold/19353. [Test case] backport the upstream commit, test llvm-5 build ond arm64 [Regression potential] Unknown To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1722162/+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 1712675] Please test proposed package
Hello Lance, or anyone else affected, Accepted tzdata into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.16.04 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: tzdata (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1712675 Title: tzdata-2017b is not in any new LTS Ubuntu releases Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Zesty: Fix Committed Status in tzdata source package in Artful: Fix Committed Bug description: tzdata-2017b has been released since March 2017. There has been no new tzdata releases on LTS versions. I'm filing this as a bug since time is pretty critical. Requesting to add this package to the next release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1712675/+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 1696298] Please test proposed package
Hello Ryan, or anyone else affected, Accepted tzdata into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.17.10 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-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. 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! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1696298 Title: leap-seconds.list file expires 28 June 2017 Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Zesty: Fix Committed Status in tzdata source package in Artful: Fix Committed Bug description: The currently published tzdata package for supported distributions contains a leap-seconds.list file that expires on 28 June 2017 and that was based on data available up through IERS Bulletin C52. IERS Bulletin C53 was published on Jan 9 2017 confirming that a June 30 2017 would not be issued. I'm not sure what serves as the upstream data source for this package, but both IEFT and the eggertz tz repo have a leap-seconds.list file that incorporates Bulletin C53. https://www.ietf.org/timezones/data/leap-seconds.list https://github.com/eggert/tz/blob/master/leap-seconds.list Would it be possible to get the package updated to include these more recent files? Some applications make use of the expiration data in this file and will raise exceptions to the user if it has gone stale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1696298/+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 1691092] Please test proposed package
Hello Pablo, or anyone else affected, Accepted tzdata into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.16.04 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: tzdata (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1691092 Title: outdated timezone information for Mongolia Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Zesty: Fix Committed Status in tzdata source package in Artful: Fix Committed Bug description: Mongolia stopped following DST this year. The timezone information in Ubuntu 16.04.2 LTS is outdated: $ TZ=Asia/Ulaanbaatar date --date="2017-05-16 12:15 UTC" +%H:%M 21:15 The correct output is '20:15'. This has been updated in version 2017a of tzdata. My Ubuntu 16.04 is using 2016j. I guess the previous LTS versions are also affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1691092/+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 1691092] Please test proposed package
Hello Pablo, or anyone else affected, Accepted tzdata into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.17.10 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-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. 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! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1691092 Title: outdated timezone information for Mongolia Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Zesty: Fix Committed Status in tzdata source package in Artful: Fix Committed Bug description: Mongolia stopped following DST this year. The timezone information in Ubuntu 16.04.2 LTS is outdated: $ TZ=Asia/Ulaanbaatar date --date="2017-05-16 12:15 UTC" +%H:%M 21:15 The correct output is '20:15'. This has been updated in version 2017a of tzdata. My Ubuntu 16.04 is using 2016j. I guess the previous LTS versions are also affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1691092/+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 1712675] Please test proposed package
Hello Lance, or anyone else affected, Accepted tzdata into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.17.04 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: tzdata (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1712675 Title: tzdata-2017b is not in any new LTS Ubuntu releases Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Zesty: Fix Committed Status in tzdata source package in Artful: Fix Committed Bug description: tzdata-2017b has been released since March 2017. There has been no new tzdata releases on LTS versions. I'm filing this as a bug since time is pretty critical. Requesting to add this package to the next release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1712675/+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 1696298] Please test proposed package
Hello Ryan, or anyone else affected, Accepted tzdata into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.17.04 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: tzdata (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1696298 Title: leap-seconds.list file expires 28 June 2017 Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Zesty: Fix Committed Status in tzdata source package in Artful: Fix Committed Bug description: The currently published tzdata package for supported distributions contains a leap-seconds.list file that expires on 28 June 2017 and that was based on data available up through IERS Bulletin C52. IERS Bulletin C53 was published on Jan 9 2017 confirming that a June 30 2017 would not be issued. I'm not sure what serves as the upstream data source for this package, but both IEFT and the eggertz tz repo have a leap-seconds.list file that incorporates Bulletin C53. https://www.ietf.org/timezones/data/leap-seconds.list https://github.com/eggert/tz/blob/master/leap-seconds.list Would it be possible to get the package updated to include these more recent files? Some applications make use of the expiration data in this file and will raise exceptions to the user if it has gone stale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1696298/+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 1696298] Please test proposed package
Hello Ryan, or anyone else affected, Accepted tzdata into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.16.04 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: tzdata (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1696298 Title: leap-seconds.list file expires 28 June 2017 Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Zesty: Fix Committed Status in tzdata source package in Artful: Fix Committed Bug description: The currently published tzdata package for supported distributions contains a leap-seconds.list file that expires on 28 June 2017 and that was based on data available up through IERS Bulletin C52. IERS Bulletin C53 was published on Jan 9 2017 confirming that a June 30 2017 would not be issued. I'm not sure what serves as the upstream data source for this package, but both IEFT and the eggertz tz repo have a leap-seconds.list file that incorporates Bulletin C53. https://www.ietf.org/timezones/data/leap-seconds.list https://github.com/eggert/tz/blob/master/leap-seconds.list Would it be possible to get the package updated to include these more recent files? Some applications make use of the expiration data in this file and will raise exceptions to the user if it has gone stale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1696298/+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 1691092] Re: outdated timezone information for Mongolia
Hello Pablo, or anyone else affected, Accepted tzdata into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.14.04 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-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. 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: tzdata (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-trusty ** Changed in: tzdata (Ubuntu) Status: Confirmed => Fix Released ** Changed in: tzdata (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1691092 Title: outdated timezone information for Mongolia Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Zesty: Fix Committed Status in tzdata source package in Artful: Fix Committed Bug description: Mongolia stopped following DST this year. The timezone information in Ubuntu 16.04.2 LTS is outdated: $ TZ=Asia/Ulaanbaatar date --date="2017-05-16 12:15 UTC" +%H:%M 21:15 The correct output is '20:15'. This has been updated in version 2017a of tzdata. My Ubuntu 16.04 is using 2016j. I guess the previous LTS versions are also affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1691092/+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 1691092] Please test proposed package
Hello Pablo, or anyone else affected, Accepted tzdata into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.17.04 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: tzdata (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1691092 Title: outdated timezone information for Mongolia Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Zesty: Fix Committed Status in tzdata source package in Artful: Fix Committed Bug description: Mongolia stopped following DST this year. The timezone information in Ubuntu 16.04.2 LTS is outdated: $ TZ=Asia/Ulaanbaatar date --date="2017-05-16 12:15 UTC" +%H:%M 21:15 The correct output is '20:15'. This has been updated in version 2017a of tzdata. My Ubuntu 16.04 is using 2016j. I guess the previous LTS versions are also affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1691092/+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 1696298] Re: leap-seconds.list file expires 28 June 2017
Hello Ryan, or anyone else affected, Accepted tzdata into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.14.04 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-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. 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: tzdata (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-trusty ** Changed in: tzdata (Ubuntu) Status: Confirmed => Fix Released ** Changed in: tzdata (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1696298 Title: leap-seconds.list file expires 28 June 2017 Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Zesty: Fix Committed Status in tzdata source package in Artful: Fix Committed Bug description: The currently published tzdata package for supported distributions contains a leap-seconds.list file that expires on 28 June 2017 and that was based on data available up through IERS Bulletin C52. IERS Bulletin C53 was published on Jan 9 2017 confirming that a June 30 2017 would not be issued. I'm not sure what serves as the upstream data source for this package, but both IEFT and the eggertz tz repo have a leap-seconds.list file that incorporates Bulletin C53. https://www.ietf.org/timezones/data/leap-seconds.list https://github.com/eggert/tz/blob/master/leap-seconds.list Would it be possible to get the package updated to include these more recent files? Some applications make use of the expiration data in this file and will raise exceptions to the user if it has gone stale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1696298/+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 1712675] Please test proposed package
Hello Lance, or anyone else affected, Accepted tzdata into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.17.10 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-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. 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! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1712675 Title: tzdata-2017b is not in any new LTS Ubuntu releases Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Zesty: Fix Committed Status in tzdata source package in Artful: Fix Committed Bug description: tzdata-2017b has been released since March 2017. There has been no new tzdata releases on LTS versions. I'm filing this as a bug since time is pretty critical. Requesting to add this package to the next release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1712675/+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 1712675] Re: tzdata-2017b is not in any new LTS Ubuntu releases
Hello Lance, or anyone else affected, Accepted tzdata into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.14.04 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-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. 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: tzdata (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-trusty ** Changed in: tzdata (Ubuntu) Status: New => Fix Released ** Changed in: tzdata (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1712675 Title: tzdata-2017b is not in any new LTS Ubuntu releases Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Zesty: Fix Committed Status in tzdata source package in Artful: Fix Committed Bug description: tzdata-2017b has been released since March 2017. There has been no new tzdata releases on LTS versions. I'm filing this as a bug since time is pretty critical. Requesting to add this package to the next release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1712675/+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 1676117] Re: tzdata-java 2017a package required
Hello hurelhuyag, or anyone else affected, Accepted tzdata into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2017c- 0ubuntu0.14.04 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-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. 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: tzdata (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1676117 Title: tzdata-java 2017a package required Status in tzdata package in Ubuntu: Invalid Status in tzdata source package in Trusty: Fix Committed Bug description: Mongolia no longer observes DST. I can't find tzdata-java_2017a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1676117/+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 1676117] Re: tzdata-java 2017a package required
** Also affects: tzdata (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: tzdata (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1676117 Title: tzdata-java 2017a package required Status in tzdata package in Ubuntu: Invalid Status in tzdata source package in Trusty: New Bug description: Mongolia no longer observes DST. I can't find tzdata-java_2017a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1676117/+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 1657473] Re: date format incorrect for a number of Timezones
Date formats are a function of your locale, not your timezone. When using a GB locale, the output is, indeed, what you expect it to be: (base)adconrad@nosferatu:~$ LANG=fr_FR.UTF-8 TZ=Europe/London date jeudi 9 novembre 2017, 23:08:00 (UTC+) (base)adconrad@nosferatu:~$ LANG=en_US.UTF-8 TZ=Europe/London date Thu Nov 9 23:08:03 GMT 2017 (base)adconrad@nosferatu:~$ LANG=en_GB.UTF-8 TZ=Europe/London date Thu 9 Nov 23:08:06 GMT 2017 ** Changed in: tzdata (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1657473 Title: date format incorrect for a number of Timezones Status in tzdata package in Ubuntu: Invalid Bug description: Body: For a number of locales, for example, TZ=Europe/London, the default format of the date command is wrong. At least one other timezone is affected: TZ=Africa/Johannesburg has the same bug. $(TZ=Europe/London;date) Wed Jan 18 13:59:33 GMT 2017 This format is wrong. It should be: $(TZ=Europe/London;date) Wed 18 Jan 13:59:33 GMT 2017 In other words, the date format should be: date +%a\ %d\ %b\ %H:%M:%S\ %Z\ %Y Not, as it currently is: date +%a\ %b\ %d\ %H:%M:%S\ %Z\ %Y affects ubuntu status new -- Peter Brooks Mobile: +27 82 717 6404 Direct: +27 21 447 9752 Skype: Fustbariclation Twitter: Fustbariclation Google+: Fustbariclation Author Page: amazon.com/author/peter_brooks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1657473/+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 1730647] Re: on s390x one should alway be able to manipulate z devices
** Changed in: ubuntu-meta (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1730647 Title: on s390x one should alway be able to manipulate z devices Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Zesty: Fix Committed Status in ubuntu-meta source package in Artful: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Released Bug description: [Impact] * Currently s390-tools is not installed as part of the server seed, which leads to inconsistencies between manually installed systems with d-i and systems originating from cloud images - containers, cloud images, maas. d-i installs s390-tools, whilst the rest do not. However, s390-tools ship tooling to inspect, list, operate on z specific devices and should always be available across all of ubuntu, including containers, maas, etc. Hence seeding it to server seed. [Test Case] * s390x containers have s390-tools package installed * s390x cloud images have s390-tools package installed * s390x maas images have s390-tools package installed [Regression Potential] * This is calling ubuntu-meta update script only * The only other changes are those that have been introduced in other srus. * s390-tools is in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1730647/+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 1726093] Re: ubuntu-desktop: Install gir1.2-gmenu-3.0 by default
Hello Jeremy, or anyone else affected, Accepted ubuntu-meta into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.404.1 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-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. 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! ** Also affects: ubuntu-meta (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1726093 Title: ubuntu-desktop: Install gir1.2-gmenu-3.0 by default Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Artful: Fix Committed Bug description: Impact == Ubuntu doesn't install particular files ( gir1.2-gmenu-3.0 ) that are needed by several popular GNOME Shell extensions. Test Case = Install the update to Ubuntu 17.10. Open the Ubuntu Software app. Search for Arc Menu Install it. There should be an A menu in the top left of the screen. Other Info == Debian-based distros are somewhat unique in that they split gir files into separate packages. This is normally not a problem since .deb packages should simply depend on the packages they need. It is a bit of a problem for GNOME Shell extensions distributed through extensions.gnome.org since they can't depend on system packages except as a comment in the extension description that may or may be read even if it is mentioned. Specifically, there are several extensions that add a traditional applications menu to GNOME Shell. These usually need gir1.2-gmenu-3.0. This wasn't noticed much before because both Debian GNOME and Ubuntu GNOME installed the gnome-shell-extensions package by default which depends on gir1.2-gmenu-3.0. Now though, it just feels to users like Ubuntu is broken. I've read comments that think that Ubuntu is intentionally trying to make it difficult to use these app menu extensions. Approved at the Ubuntu Desktop meeting (discussion continues until 15:09) https://irclogs.ubuntu.com/2017/10/24/%23ubuntu-desktop.html#t14:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726093/+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 1730647] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted ubuntu-meta into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-meta/1.379.1 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: ubuntu-meta (Ubuntu Artful) Status: In Progress => Fix Committed ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1730647 Title: on s390x one should alway be able to manipulate z devices Status in ubuntu-meta package in Ubuntu: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Zesty: Fix Committed Status in ubuntu-meta source package in Artful: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Committed Bug description: [Impact] * Currently s390-tools is not installed as part of the server seed, which leads to inconsistencies between manually installed systems with d-i and systems originating from cloud images - containers, cloud images, maas. d-i installs s390-tools, whilst the rest do not. However, s390-tools ship tooling to inspect, list, operate on z specific devices and should always be available across all of ubuntu, including containers, maas, etc. Hence seeding it to server seed. [Test Case] * s390x containers have s390-tools package installed * s390x cloud images have s390-tools package installed * s390x maas images have s390-tools package installed [Regression Potential] * This is calling ubuntu-meta update script only * The only other changes are those that have been introduced in other srus. * s390-tools is in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1730647/+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 1730647] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted ubuntu-meta into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.404.1 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-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. 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! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1730647 Title: on s390x one should alway be able to manipulate z devices Status in ubuntu-meta package in Ubuntu: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Zesty: Fix Committed Status in ubuntu-meta source package in Artful: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Committed Bug description: [Impact] * Currently s390-tools is not installed as part of the server seed, which leads to inconsistencies between manually installed systems with d-i and systems originating from cloud images - containers, cloud images, maas. d-i installs s390-tools, whilst the rest do not. However, s390-tools ship tooling to inspect, list, operate on z specific devices and should always be available across all of ubuntu, including containers, maas, etc. Hence seeding it to server seed. [Test Case] * s390x containers have s390-tools package installed * s390x cloud images have s390-tools package installed * s390x maas images have s390-tools package installed [Regression Potential] * This is calling ubuntu-meta update script only * The only other changes are those that have been introduced in other srus. * s390-tools is in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1730647/+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 1730647] Re: on s390x one should alway be able to manipulate z devices
Hello Dimitri, or anyone else affected, Accepted ubuntu-meta into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.361.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: ubuntu-meta (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial ** Changed in: ubuntu-meta (Ubuntu Zesty) Status: In Progress => Fix Committed ** Tags added: verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1730647 Title: on s390x one should alway be able to manipulate z devices Status in ubuntu-meta package in Ubuntu: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Zesty: Fix Committed Status in ubuntu-meta source package in Artful: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Committed Bug description: [Impact] * Currently s390-tools is not installed as part of the server seed, which leads to inconsistencies between manually installed systems with d-i and systems originating from cloud images - containers, cloud images, maas. d-i installs s390-tools, whilst the rest do not. However, s390-tools ship tooling to inspect, list, operate on z specific devices and should always be available across all of ubuntu, including containers, maas, etc. Hence seeding it to server seed. [Test Case] * s390x containers have s390-tools package installed * s390x cloud images have s390-tools package installed * s390x maas images have s390-tools package installed [Regression Potential] * This is calling ubuntu-meta update script only * The only other changes are those that have been introduced in other srus. * s390-tools is in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1730647/+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 1682102] Re: libseccomp should support GA and HWE kernels
I built this package in the ubuntu-security-proposed PPA so it can be released to both -updates and -security (which seems like probably a sane thing to do) once it's passed the SRU process. ** Changed in: libseccomp (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1682102 Title: libseccomp should support GA and HWE kernels Status in libseccomp package in Ubuntu: Invalid Status in libseccomp source package in Xenial: Fix Committed Bug description: [Impact] out of date libseccomp w.r.t. custom and hwe kernels provides sub-par userspace protection, which is otherwise available on the running kernel and hardware combination. This results in subpar security of systems running new architectures (s390x & ppc64el) and newer hwe/custom kernels. * Version 2.3.1 - April 20, 2016 - Fixed a problem with 32-bit x86 socket syscalls on some systems - Fixed problems with ipc syscalls on 32-bit x86 - Fixed problems with socket and ipc syscalls on s390 and s390x * Version 2.3.0 - February 29, 2016 - Added support for the s390 and s390x architectures - Added support for the ppc, ppc64, and ppc64le architectures - Update the internal syscall tables to match the Linux 4.5-rcX releases - Filter generation for both multiplexed and direct socket syscalls on x86 - Support for the musl libc implementation - Additions to the API to enable runtime version checking of the library - Enable the use of seccomp() instead of prctl() on supported systems - Added additional tests to the regression test suite There is no ABI/API break There are no packaging changes, apart from dropping patches included in this upstream release and updating new symbols. Doing wholesome update is safer and carries less risk, than individually cherrypicking effectively all of the above. This is a backport to an LTS release under the banner of safe introduction of new features and new hardware support. It is expected that container technologies will take advantage of the newly available libseccomp. This may need to be uploaded as a security update. Currently, s390x support in xenial libssecomp is incomplete. And there are v4.5+ syscall tables missing as used by hwe kernels and some custom kernels. [Testcase] Validate that all main contianer technologies are operational and do not regress, e.g.: - lxc - lxd - docker - snapd [Regression Potential] Userspace components may detect at runtime newly available libseccomp, and thus restrict user-space processes more than previously done. This may lead to a change of restrictions applied on the user sapce processes, and result in previously unexpected denials / errors returned. [Proposed Update available in bileto PPA] https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2981 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1682102/+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 1682102] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted libseccomp into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libseccomp/2.3.1-2.1ubuntu2~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: libseccomp (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1682102 Title: libseccomp should support GA and HWE kernels Status in libseccomp package in Ubuntu: Invalid Status in libseccomp source package in Xenial: Fix Committed Bug description: [Impact] out of date libseccomp w.r.t. custom and hwe kernels provides sub-par userspace protection, which is otherwise available on the running kernel and hardware combination. This results in subpar security of systems running new architectures (s390x & ppc64el) and newer hwe/custom kernels. * Version 2.3.1 - April 20, 2016 - Fixed a problem with 32-bit x86 socket syscalls on some systems - Fixed problems with ipc syscalls on 32-bit x86 - Fixed problems with socket and ipc syscalls on s390 and s390x * Version 2.3.0 - February 29, 2016 - Added support for the s390 and s390x architectures - Added support for the ppc, ppc64, and ppc64le architectures - Update the internal syscall tables to match the Linux 4.5-rcX releases - Filter generation for both multiplexed and direct socket syscalls on x86 - Support for the musl libc implementation - Additions to the API to enable runtime version checking of the library - Enable the use of seccomp() instead of prctl() on supported systems - Added additional tests to the regression test suite There is no ABI/API break There are no packaging changes, apart from dropping patches included in this upstream release and updating new symbols. Doing wholesome update is safer and carries less risk, than individually cherrypicking effectively all of the above. This is a backport to an LTS release under the banner of safe introduction of new features and new hardware support. It is expected that container technologies will take advantage of the newly available libseccomp. This may need to be uploaded as a security update. Currently, s390x support in xenial libssecomp is incomplete. And there are v4.5+ syscall tables missing as used by hwe kernels and some custom kernels. [Testcase] Validate that all main contianer technologies are operational and do not regress, e.g.: - lxc - lxd - docker - snapd [Regression Potential] Userspace components may detect at runtime newly available libseccomp, and thus restrict user-space processes more than previously done. This may lead to a change of restrictions applied on the user sapce processes, and result in previously unexpected denials / errors returned. [Proposed Update available in bileto PPA] https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2981 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1682102/+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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies
Removing packages from bionic: lubuntu-software-center 0.0.10-0ubuntu2 in bionic lubuntu-software-center 0.0.10-0ubuntu2 in bionic amd64 lubuntu-software-center 0.0.10-0ubuntu2 in bionic arm64 lubuntu-software-center 0.0.10-0ubuntu2 in bionic armhf lubuntu-software-center 0.0.10-0ubuntu2 in bionic i386 lubuntu-software-center 0.0.10-0ubuntu2 in bionic ppc64el lubuntu-software-center 0.0.10-0ubuntu2 in bionic s390x Comment: Obsolete and unused; LP: #1673258 Remove [y|N]? y 1 package successfully removed. ** Changed in: lubuntu-software-center (Ubuntu) Status: New => Fix Released ** Changed in: lubuntu-software-center (Ubuntu) Assignee: (unassigned) => Adam Conrad (adconrad) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1673258 Title: Remove aptdaemon and drop or port its reverse-dependencies Status in aptdaemon package in Ubuntu: New Status in apturl package in Ubuntu: New Status in dell-recovery package in Ubuntu: Fix Committed Status in gnome-software package in Ubuntu: Fix Committed Status in language-selector package in Ubuntu: New Status in lubuntu-software-center package in Ubuntu: Fix Released Status in mythbuntu-control-centre package in Ubuntu: New Status in sessioninstaller package in Ubuntu: New Status in software-properties package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-mate-welcome package in Ubuntu: New Status in update-manager package in Ubuntu: New Status in update-notifier package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: Fix Released Bug description: aptdaemon is abandoned and unmaintained. It has already been dropped from Debian, but there are several reverse dependencies keeping it in Ubuntu. I will add bug tasks for each of those dependencies, which should be ported or dropped themselves. Then we can get rid of aptdaemon too. See this mailing list thread for more details: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port- from-aptdaemon-to-packagekit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 1706471] Re: please demote exiv2 to universe
Unsubscribing ~ubuntu-archive, this is up to the desktop team to choose to remove from their seeds and, if they do, our magic reports will tell us to demote, we don't need a bug for that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1706471 Title: please demote exiv2 to universe Status in gexiv2: Confirmed Status in exiv2 package in Ubuntu: Triaged Bug description: Hello, Please consider demoting exiv2 to universe. http://dev.exiv2.org/issues/1248 The upstream author appears overwhelmed with the task of hardening exiv2 for use against untrusted inputs and thus far (~nine months) no users have provided the project with patches against known issues. $ reverse-depends -c main -r artful src:exiv2 Reverse-Depends === * libgexiv2-2 (for libexiv2-14) * libgexiv2-dev (for libexiv2-dev) Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/gexiv2/+bug/1706471/+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 1728188] Re: Don't build pulseaudio with trust-store support
@vanvugt It doesn't sound like that to me at all. seb128 was just pointing out that the snappy patches depend on the trust-store changes to a degree. If those dependencies can be isolated, moved to the snappy changeset, and the trust-store dep dropped, then everyone wins. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1728188 Title: Don't build pulseaudio with trust-store support Status in pulseaudio package in Ubuntu: Triaged Bug description: Please check whether we still need to build pulseaudio with trust- store support or if we can drop it and remove trust-store from Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1728188/+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 1718022] Re: RM: obsolete product
Removing packages from bionic: telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic amd64 telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic arm64 telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic armhf telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic i386 telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic ppc64el telepathy-ofono 0.2+17.04.20161109-0ubuntu1 in bionic s390x telepathy-ofono-ril-mc-plugin 0.2+17.04.20161109-0ubuntu1 in bionic amd64 telepathy-ofono-ril-mc-plugin 0.2+17.04.20161109-0ubuntu1 in bionic arm64 telepathy-ofono-ril-mc-plugin 0.2+17.04.20161109-0ubuntu1 in bionic armhf telepathy-ofono-ril-mc-plugin 0.2+17.04.20161109-0ubuntu1 in bionic i386 Comment: Obsolete; LP: #1718022 Remove [y|N]? y 1 package successfully removed. ** Changed in: telepathy-ofono (Ubuntu) Assignee: Will Cooke (willcooke) => Adam Conrad (adconrad) ** Changed in: telepathy-ofono (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1718022 Title: RM: obsolete product Status in telepathy-ofono package in Ubuntu: Fix Released Bug description: telepathy-ofono was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:telepathy-ofono No reverse dependencies found $ reverse-depends -b src:telepathy-ofono No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1718022/+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 1718027] Re: RM: obsolete product
Removing packages from bionic: libusermetrics 1.1.1+17.04.20161208.1-0ubuntu1 in bionic libusermetrics-doc 1.1.1+17.04.20161208.1-0ubuntu1 in bionic amd64 libusermetrics-doc 1.1.1+17.04.20161208.1-0ubuntu1 in bionic arm64 libusermetrics-doc 1.1.1+17.04.20161208.1-0ubuntu1 in bionic armhf libusermetrics-doc 1.1.1+17.04.20161208.1-0ubuntu1 in bionic i386 libusermetrics-doc 1.1.1+17.04.20161208.1-0ubuntu1 in bionic ppc64el libusermetrics-doc 1.1.1+17.04.20161208.1-0ubuntu1 in bionic s390x libusermetrics-tools 1.1.1+17.04.20161208.1-0ubuntu1 in bionic amd64 libusermetrics-tools 1.1.1+17.04.20161208.1-0ubuntu1 in bionic arm64 libusermetrics-tools 1.1.1+17.04.20161208.1-0ubuntu1 in bionic armhf libusermetrics-tools 1.1.1+17.04.20161208.1-0ubuntu1 in bionic i386 libusermetrics-tools 1.1.1+17.04.20161208.1-0ubuntu1 in bionic ppc64el libusermetrics-tools 1.1.1+17.04.20161208.1-0ubuntu1 in bionic s390x libusermetricsinput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic amd64 libusermetricsinput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic arm64 libusermetricsinput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic armhf libusermetricsinput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic i386 libusermetricsinput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic ppc64el libusermetricsinput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic s390x libusermetricsinput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in bionic amd64 libusermetricsinput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in bionic arm64 libusermetricsinput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in bionic armhf libusermetricsinput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in bionic i386 libusermetricsinput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in bionic ppc64el libusermetricsinput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in bionic s390x libusermetricsoutput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic amd64 libusermetricsoutput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic arm64 libusermetricsoutput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic armhf libusermetricsoutput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic i386 libusermetricsoutput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic ppc64el libusermetricsoutput1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic s390x libusermetricsoutput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in bionic amd64 libusermetricsoutput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in bionic arm64 libusermetricsoutput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in bionic armhf libusermetricsoutput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in bionic i386 libusermetricsoutput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in bionic ppc64el libusermetricsoutput1-dev 1.1.1+17.04.20161208.1-0ubuntu1 in bionic s390x qtdeclarative5-usermetrics0.1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic amd64 qtdeclarative5-usermetrics0.1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic arm64 qtdeclarative5-usermetrics0.1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic armhf qtdeclarative5-usermetrics0.1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic i386 qtdeclarative5-usermetrics0.1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic ppc64el qtdeclarative5-usermetrics0.1 1.1.1+17.04.20161208.1-0ubuntu1 in bionic s390x usermetricsservice 1.1.1+17.04.20161208.1-0ubuntu1 in bionic amd64 usermetricsservice 1.1.1+17.04.20161208.1-0ubuntu1 in bionic arm64 usermetricsservice 1.1.1+17.04.20161208.1-0ubuntu1 in bionic armhf usermetricsservice 1.1.1+17.04.20161208.1-0ubuntu1 in bionic i386 usermetricsservice 1.1.1+17.04.20161208.1-0ubuntu1 in bionic ppc64el usermetricsservice 1.1.1+17.04.20161208.1-0ubuntu1 in bionic s390x Comment: Obsolete; LP: #1718027 Remove [y|N]? y 1 package successfully removed. ** Changed in: libusermetrics (Ubuntu) Assignee: Will Cooke (willcooke) => Adam Conrad (adconrad) ** Changed in: libusermetrics (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1718027 Title: RM: obsolete product Status in libusermetrics package in Ubuntu: Fix Released Bug description: libusermetrics was a component of Ubuntu Phone which is no longer developed. Please remove this packag
[Touch-packages] [Bug 1702429] Re: Please remove system-image from Ubuntu Artful
*** This bug is a duplicate of bug 1713262 *** https://bugs.launchpad.net/bugs/1713262 ** Changed in: ubuntu-download-manager (Ubuntu) Status: New => Fix Released ** Changed in: system-image (Ubuntu) Status: New => Fix Released ** This bug has been marked a duplicate of bug 1713262 remove system-image, ubuntu-download-manager, ubuntu-core-upgrader: Ubuntu Touch / Ubuntu Core 15 components, no longer used -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1702429 Title: Please remove system-image from Ubuntu Artful Status in system-image package in Ubuntu: Fix Released Status in ubuntu-download-manager package in Ubuntu: Fix Released Bug description: I would like to request the removal of source and binaries of the system-image in artful. The rationale is that the package no longer has any active maintainer and doesn't have any consumers since vivid. With the incoming Python 3.6 transition, system-image will just cause unneeded delays. There are no reverse dependencies in artful: sil2100@ideamatsu:~$ reverse-depends system-image-cli No reverse dependencies found sil2100@ideamatsu:~$ reverse-depends system-image-dbus No reverse dependencies found sil2100@ideamatsu:~$ reverse-depends -b system-image-dev No reverse dependencies found Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1702429/+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 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.
** Changed in: cups (Ubuntu) Assignee: uklas (uklasius) => (unassigned) ** Changed in: glibc (Ubuntu) Assignee: uklas (uklasius) => Adam Conrad (adconrad) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1719004 Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Status in CUPS: Fix Released Status in cups package in Ubuntu: Invalid Status in glibc package in Ubuntu: Confirmed Bug description: 1. Error: Package/cups-daemon2.2.4-7 (mutilated) 2. compiz-core/tmp/apport_core_q_vnqis (corrupted) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-daemon 2.2.4-7 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Date: Fri Sep 22 22:16:18 2017 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2017-05-27 (118 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Papersize: a4 ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcEnviron: LANG=el_GR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: H110M-K D3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1719004/+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 1728616] Re: using 'devel' in sources.list causes apt-get update to fail
The whole 'devel' thing has been half-broken in one way or another since it was introduced. My advice is just to not use it. And I honestly think we should remove all remnants of it from launchpad and the Ubuntu/PPA archives as well. Trying to treat "the latest at any given point" as the same thing as a "rolling" distribution may have been fun to score some political points, but it doesn't actually do useful things. -- 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/1728616 Title: using 'devel' in sources.list causes apt-get update to fail Status in apt package in Ubuntu: Opinion Bug description: Our /etc/apt/sources.list looks like this: $ cat /etc/apt/sources.list | deb http://archive.ubuntu.com//ubuntu devel main restricted universe multiverse | deb http://archive.ubuntu.com//ubuntu devel-updates main restricted universe multiverse | deb http://archive.ubuntu.com//ubuntu devel-security main restricted universe multiverse | deb http://archive.ubuntu.com//ubuntu devel-backports main restricted universe multiverse I noticed today that 'apt-get update' started failing. Likely that started on Thursday or Friday when bionic opened. This seems less than desireable, but even if the failure is expected, what is the solution to "accept" this change? It does mention 'apt-secure(8)' but nothing there obviously points to the solution. $ sudo apt-get update Hit:2 http://ppa.launchpad.net/uvtool-dev/master/ubuntu devel InRelease Get:1 http://archive.ubuntu.com//ubuntu devel InRelease [235 kB] Get:3 http://archive.ubuntu.com//ubuntu devel-updates InRelease [65.4 kB] Get:4 http://archive.ubuntu.com//ubuntu devel-security InRelease [65.4 kB] Get:5 http://archive.ubuntu.com//ubuntu devel-backports InRelease [65.5 kB] Reading package lists... Done W: Conflicting distribution: http://ppa.launchpad.net/uvtool-dev/master/ubuntu devel InRelease (expected devel but got zesty) W: Conflicting distribution: http://archive.ubuntu.com//ubuntu devel InRelease (expected devel but got bionic) N: Repository 'http://archive.ubuntu.com//ubuntu devel InRelease' changed its 'Version' value from '17.10' to '18.04' E: Repository 'http://archive.ubuntu.com//ubuntu devel InRelease' changed its 'Suite' value from 'artful' to 'bionic' E: Repository 'http://archive.ubuntu.com//ubuntu devel InRelease' changed its 'Codename' value from 'artful' to 'bionic' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. W: Conflicting distribution: http://archive.ubuntu.com//ubuntu devel-updates InRelease (expected devel-updates but got bionic) N: Repository 'http://archive.ubuntu.com//ubuntu devel-updates InRelease' changed its 'Version' value from '17.10' to '18.04' E: Repository 'http://archive.ubuntu.com//ubuntu devel-updates InRelease' changed its 'Suite' value from 'artful-updates' to 'bionic-updates' E: Repository 'http://archive.ubuntu.com//ubuntu devel-updates InRelease' changed its 'Codename' value from 'artful' to 'bionic' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. W: Conflicting distribution: http://archive.ubuntu.com//ubuntu devel-security InRelease (expected devel-security but got bionic) N: Repository 'http://archive.ubuntu.com//ubuntu devel-security InRelease' changed its 'Version' value from '17.10' to '18.04' E: Repository 'http://archive.ubuntu.com//ubuntu devel-security InRelease' changed its 'Suite' value from 'artful-security' to 'bionic-security' E: Repository 'http://archive.ubuntu.com//ubuntu devel-security InRelease' changed its 'Codename' value from 'artful' to 'bionic' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. W: Conflicting distribution: http://archive.ubuntu.com//ubuntu devel-backports InRelease (expected devel-backports but got bionic) N: Repository 'http://archive.ubuntu.com//ubuntu devel-backports InRelease' changed its 'Version' value from '17.10' to '18.04' E: Repository 'http://archive.ubuntu.com//ubuntu devel-backports InRelease' changed its 'Suite' value from 'artful-backports' to 'bionic-backports' E: Repository 'http://archive.ubuntu.com//ubuntu devel-backports InRelease' changed its 'Codename' value from 'artful' to 'bionic' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apt 1.5 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3
