[Group.of.nepali.translators] [Bug 1804018] Re: Autogenerated interface name prevents creating a bridge over a VLAN
** Changed in: juju Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1804018 Title: Autogenerated interface name prevents creating a bridge over a VLAN Status in juju: Fix Released Status in juju 2.4 series: Fix Released Status in vlan package in Ubuntu: In Progress Status in vlan source package in Trusty: Won't Fix Status in vlan source package in Xenial: Won't Fix Status in vlan source package in Bionic: Won't Fix Status in vlan source package in Cosmic: Won't Fix Status in vlan source package in Disco: Won't Fix Bug description: Hi, First of all, thanks for all your work on creating and maintaining Juju and the charms ecosystem! I believe I have stumbled onto a bug in autogenerating the name for the bridge interface when one needs to be created to grant a container access to a host's network interface. This bug is currently blocking a MAAS/Juju/OpenStack deployment where traffic is separated into VLANs. I have successfully reproduced it on 2.4.6 and 2.5-beta1 installations, although I believe that it has been present ever since at least 2.2.0, if not maybe earlier. Currently the name of the bridge interface is, if possible, generated by prepending "br-" to the host interface name; however, this is problematic with VLAN interfaces. If the host interface is called e.g. "enp3s0f0.503", this would create a bridge named "br- enp3s0f0.503"; however, if there is *also* a bridge on the "enp3s0f0" interface (without the VLAN ID), this would cause the Debian/Ubuntu ifupdown scripts to consider "br-enp3s0f0.503" to be VLAN 503 on the "br-enp3s0f0" interface and, consequently, fail to bring it up correctly the next time the node is rebooted. Steps to reproduce: 1. Define a node with an Ethernet interface (let's call it "enp3s0f0") and a network space (let's call it "mgmt") 2. Define a VLAN over that interface (let's call it "enp3s0f0.503") and a network space for the VLAN (let's call it "storage") 3. Deploy a charm on that node so that Juju knows about the enp3s0f0 interface in the mgmt space and the enp3s0f0.503 interface in the storage space 4. Deploy a charm in a container, specitying `--constraints spaces=storage`; this will lead to Juju autogenerating a bridge interface and calling it "br-enp3s0f0.503" 5. Deploy a charm in a container, specifynig `--constraints spaces=mgmt`; this will lead to Juju autogenerating another bridge interface and calling it "br-enp3s0f0" 6. Reboot the server, then log into it The br-enp3s0f0 bridge may be brought up correctly, but the br- enp3s0f0.503 interface, although it will exist, will have been created as a VLAN interface, not a bridge interface, and so any attempts to add any interfacesd to it will have failed; consequently, the container will also have failed to start up. A naive fix for newly-bootstrapped environments would be to replace any dots with e.g. dashes in the `BridgeNameForDevice()` function in the `network/containerizer/bridgepolicy.go` file - this will lead to creating the new interface with a name that will not be interpreted as a VLAN over an existing interface. However, I think that a proper fix would have to include some sort of migration path for existing deployments, e.g. generating both the old and new names and possibly migrating network interfaces from the old bridge to the new one. Please let me know if there is any more information that I can provide for a hopefully speedy resolution of this problem. Thanks in advance for your consideration, and keep up the great work! Best regards, Peter To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1804018/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1784926] Re: ipmi-locate fails to detect BMCs described by ACPI
** Also affects: freeipmi (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: freeipmi (Ubuntu Xenial) Status: New => In Progress ** Changed in: freeipmi (Ubuntu Xenial) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: freeipmi (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1784926 Title: ipmi-locate fails to detect BMCs described by ACPI Status in freeipmi package in Ubuntu: Fix Released Status in freeipmi source package in Xenial: In Progress Status in freeipmi source package in Bionic: Fix Released Bug description: [Impact] ipmi-locate will not detect and report BMCs in systems where the firmware describes them only in an ACPI SPMI table. I surveyed several IPMI-capable systems, and all but 1 describe their BMCs in SMBIOS, with a subset of those also describing their BMC in ACPI as well. ipmi-locate works fine on those systems because it successfully parses the SMBIOS (dmidecode) info. But, one system - the HiSilicon D06 - only describes the BMC in ACPI. For this system, ipmi-locate fails to find a BMC. One way this surfaces to the user is with MAAS. MAAS uses ipmi-locate to look for a BMC to determine which version of the IPMI protocol it supports. The way the query works is that it checks for >= 2.0 support and, if that fails, it assumes 1.5 support. Since ipmi-locate fails to find *any* support, the fallback to 1.5 is triggered and MAAS tries to talk to the system w/ IPMI LAN 1.5 protocol. This system actually supports IPMI LAN 2.0 protocol, which is incompatible with 1.5 LAN protocol, so MAAS is unable to power control the system. Even if you manually enlist the node and tell it the node is IPMI 2.0, commissioning will attempt to re-detect the BMC and reset it to 1.5. [Test Case] On a system where /sys/firmware/acpi/tables/SPMI* exists: $ sudo ipmi-locate At least one of the "[Probing KCS|SMIC|BT|SSIF] device using ACPI" tests should not report "FAILED". [Fix] The following patch series from upstream git fixes the problem: 40ba578f8 Correct order of bytes in specification_revision field of ACPI SPMI table d92888128 Allow sysfs SPMI parsing on ARM platforms 158a901d7 Add support for parsing SPMI tables exposed via sysfs 184c74649 Split RSDT/XSDT parsing into new function 3c6fa7054 Don't try to separate the header from the ACPI table data d8673cf67 Fix acpi spmi searching corner case [Regression Risk] While neither myself nor upstream are aware of a system where the existing freeipmi ACPI/SPMI parsing code works - and works *correctly* - it is possible that there is such a system. From my experimentation and reading of the code - even if the existing code to extract an SPMI table from /dev/mem were to work, the parsing of that table would be buggy and would not report correct information (see commits 3c6fa7054 and 40ba578f8 for details). However - an earlier version of this code did apparently work at some point on some system - so it's possible that my parsing fixes would now break said system. Note that for this to be an issue for the MAAS use-case, that system would also need to *not* also describe the IPMI device in SMBIOS, which my survey of 4 systems shows to be nearly always the case (except for the 1 case that triggered this whole thing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1784926/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1748983] Re: Generate per-machine MOK for dkms signing
This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.6 --- dkms (2.2.0.3-2ubuntu11.6) xenial; urgency=medium * debian/patches/shim_secureboot_support.patch: - Move to signing just after module build to ensure it correctly applies at kernel update times. (LP: #1772950) - Generate a new MOK if there isn't one yet, and use that so sign newly-built kernel modules. (LP: #1748983) -- Mathieu Trudel-Lapierre Mon, 28 Jan 2019 10:21:09 -0500 ** Changed in: dkms (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1748983 Title: Generate per-machine MOK for dkms signing Status in dkms package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in dkms source package in Trusty: Fix Released Status in shim-signed source package in Trusty: Fix Released Status in dkms source package in Xenial: Fix Released Status in shim-signed source package in Xenial: Fix Released Bug description: [SRU Justification] Move to using self-signed keys for signing DKMS modules, along with the wizard / guide to make this work properly, to let third-party modules be signed and loaded by enforcing kernels, rather than disabling Secure Boot altogether. [Test case] 1) Install Ubuntu in UEFI mode. 2) Install bbswitch-dkms (or another -dkms package if useful on your system). 3) Follow the steps in the debconf prompts (enter a password, remember the password for next boot). 4) Reboot; follow the steps in MokManagerL 4a) Pick Enroll MOK: add the new key, enter the password when prompted to do so. 4b) If a dkms package was previously installed on the system (so Secure Boot is currently disabled in shim), pick "Change Secure Boot state". Follow the prompts to enter password characters. The option will only show up if Secure Boot validation was found to be disabled. 5) Pick "Reboot". 6) Log in and verify that the dkms module is loaded, using "lsmod | grep ". 7) Run 'modprobe ' to validate that the module can be loaded explicilty. 8) Validate that there are no errors from modprobe or errors in dmesg concerning signing keys. [Regression potential] If anything currently relies on Secure Boot validation being disabled in order to correctly run with an enforcing kernel, or grub is used in enforcing mode, custom / third-party kernels and modules may fail to load. --- shim-signed's update-secureboot-policy should allow creating a machine-owner key, and using this for signing kernel modules built via DKMS. Key generation and enrolling should be made as easy as possible for users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1772950] Re: dkms key enrolled in mok, but dkms module fails to load
This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.6 --- dkms (2.2.0.3-2ubuntu11.6) xenial; urgency=medium * debian/patches/shim_secureboot_support.patch: - Move to signing just after module build to ensure it correctly applies at kernel update times. (LP: #1772950) - Generate a new MOK if there isn't one yet, and use that so sign newly-built kernel modules. (LP: #1748983) -- Mathieu Trudel-Lapierre Mon, 28 Jan 2019 10:21:09 -0500 ** Changed in: dkms (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1772950 Title: dkms key enrolled in mok, but dkms module fails to load Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Trusty: Fix Released Status in dkms source package in Xenial: Fix Released Status in dkms source package in Bionic: Fix Released Bug description: [Impact] All Ubuntu users for whom Secure Boot is enabled. [Test cases] 1) install dkms module (use virtualbox-dkms for example) 2) Upgrade kernel (for example, install 4.15.0-22-generic on top of 4.15.0-20-generic). 3) Verify that the generated module for the new kernel (4.15.0-22-generic in this example) is built and signed by verifying that the file in /lib/modules/$kernel/updates/dkms/$module.ko ends in ~Module signature appended~: $ hexdump -Cv /lib/modules/4.15.0-22-generic/updates/dkms/vboxdrv.ko | tail -n 100 [...] ~Module signature appended~ 4) Reboot 5) modprobe -v the module. It should not respond "Required key not available", and should return with no error. 6) Verify that dkms does not contain PKCS#7 errors. [Regression potential] Possible regressions involve failure to sign and/or be able to load modules after updates: failure to sign leading to a module being built but unsigned after a new kernel is installed or after a new DKMS module is installed, failure to load modules after reboot (usually caused by module being unsigned); failure to sign due to missing keys, signature key not being automatically slated for enrollment. All these potential regression scenarios present as failure to load a DKMS module after a reboot when it should be loaded successfully. --- At my last reboot, I was prompted to enable SecureBoot, so I did. When I booted, however, I noticed that the virtualbox service failed to start because it couldn't load its kernel module. If I attempt the same thing, I see that there's an issue with keys: $ sudo modprobe vboxdrv modprobe: ERROR: could not insert 'vboxdrv': Required key not available I do have keys enrolled; `mokutil --list-enrolled` produces http://paste.ubuntu.com/p/rntTQr5XJV/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1772950/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/plDdBsnS/749-pc-kernel-440-143169-188 ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814647 Title: linux: 4.4.0-143.169 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial) derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 (linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 14. February 2019 16:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814647/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1814657] Re: linux-snapdragon: 4.4.0-1108.113 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/FoTUyj8f/751-dragonboard- kernel-440-1108113-81 ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814657 Title: linux-snapdragon: 4.4.0-1108.113 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814647 phase: Testing phase-changed: Thursday, 14. February 2019 17:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814657/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1814655] Re: linux-raspi2: 4.4.0-1104.112 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/rY5iUjvX/750-pi2-kernel-440-1104112-83 ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814655 Title: linux-raspi2: 4.4.0-1104.112 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814647 phase: Testing phase-changed: Thursday, 14. February 2019 17:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814655/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1814657] Re: linux-snapdragon: 4.4.0-1108.113 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814647 - phase: Promote to Proposed - phase-changed: Tuesday, 12. February 2019 15:35 UTC + phase: Testing + phase-changed: Thursday, 14. February 2019 17:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: Pending -- snap not in beta channel - snap-release-to-edge: Pending -- snap not in edge channel + snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814657 Title: linux-snapdragon: 4.4.0-1108.113 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814647 phase: Testing phase-changed: Thursday, 14. February 2019 17:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814657/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1814655] Re: linux-raspi2: 4.4.0-1104.112 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814647 - phase: Promote to Proposed - phase-changed: Friday, 08. February 2019 21:34 UTC + phase: Testing + phase-changed: Thursday, 14. February 2019 17:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: Pending -- snap not in beta channel - snap-release-to-edge: Pending -- snap not in edge channel + snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814655 Title: linux-raspi2: 4.4.0-1104.112 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814647 phase: Testing phase-changed: Thursday, 14. February 2019 17:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814655/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1814742] Re: linux-aws-hwe: 4.15.0-1033.35~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814726 - phase: Packaging - phase-changed: Wednesday, 06. February 2019 10:07 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 14. February 2019 17:00 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814742 Title: linux-aws-hwe: 4.15.0-1033.35~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws-hwe package in Ubuntu: Invalid Status in linux-aws-hwe source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814726 phase: Holding before Promote to Proposed phase-changed: Thursday, 14. February 2019 17:00 UTC reason: promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814742/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1748983] Re: Generate per-machine MOK for dkms signing
This bug was fixed in the package shim-signed - 1.33.1~14.04.4 --- shim-signed (1.33.1~14.04.4) trusty; urgency=medium * update-secureboot-policy: (LP: #1748983) - Backport update-secureboot-policy changes to generate a MOK and guide users through re-enabling validation and automatically signing DKMS modules. * debian/shim-signed.postinst: - When triggered, explicitly try to enroll the available MOK. * debian/shim-signed.install, openssl.cnf: Install some default configuration for creating our self-signed key. * debian/shim-signed.dirs: make sure we have a directory where to put a MOK. * debian/templates: update templates for update-secureboot-policy changes. * debian/control: Breaks dkms (<< 2.2.0.3-1.1ubuntu5.14.04.10~) since we're changing the behavior of update-secureboot-policy. -- Mathieu Trudel-Lapierre Mon, 28 Jan 2019 11:02:00 -0500 ** Changed in: shim-signed (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: dkms (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1748983 Title: Generate per-machine MOK for dkms signing Status in dkms package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in dkms source package in Trusty: Fix Released Status in shim-signed source package in Trusty: Fix Released Status in dkms source package in Xenial: Fix Committed Status in shim-signed source package in Xenial: Fix Released Bug description: [SRU Justification] Move to using self-signed keys for signing DKMS modules, along with the wizard / guide to make this work properly, to let third-party modules be signed and loaded by enforcing kernels, rather than disabling Secure Boot altogether. [Test case] 1) Install Ubuntu in UEFI mode. 2) Install bbswitch-dkms (or another -dkms package if useful on your system). 3) Follow the steps in the debconf prompts (enter a password, remember the password for next boot). 4) Reboot; follow the steps in MokManagerL 4a) Pick Enroll MOK: add the new key, enter the password when prompted to do so. 4b) If a dkms package was previously installed on the system (so Secure Boot is currently disabled in shim), pick "Change Secure Boot state". Follow the prompts to enter password characters. The option will only show up if Secure Boot validation was found to be disabled. 5) Pick "Reboot". 6) Log in and verify that the dkms module is loaded, using "lsmod | grep ". 7) Run 'modprobe ' to validate that the module can be loaded explicilty. 8) Validate that there are no errors from modprobe or errors in dmesg concerning signing keys. [Regression potential] If anything currently relies on Secure Boot validation being disabled in order to correctly run with an enforcing kernel, or grub is used in enforcing mode, custom / third-party kernels and modules may fail to load. --- shim-signed's update-secureboot-policy should allow creating a machine-owner key, and using this for signing kernel modules built via DKMS. Key generation and enrolling should be made as easy as possible for users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1803973] Re: Update gce-compute-image-packages to 20181206
*** This bug is a duplicate of bug 1813246 *** https://bugs.launchpad.net/bugs/1813246 This bug was fixed in the package gce-compute-image-packages - 20190124+dfsg1-0ubuntu1~14.04.0 --- gce-compute-image-packages (20190124+dfsg1-0ubuntu1~14.04.0) trusty; urgency=medium * Rebuild for Trusty gce-compute-image-packages (20190124+dfsg1-0ubuntu1) disco; urgency=medium * New upstream version 20190124 (LP: #1813246) - Update script retrieval to support Python 3 gce-compute-image-packages (20181206+dfsg1-0ubuntu1~14.04.0) trusty; urgency=medium * Backport to Trusty with the following remaining changes: - Revert ordering shutdown scripts after snapd.service. - Revert adding /snap/bin to PATH for startup/shutdown scripts - Revert to using dh-systemd because Trusty does not have the debhelper - Build-depend on libboost-regex-dev for regex support version making dh-systemd obsolete - Link with boost for regex support - Free tests from C++11 constructs to let them being compiled without C++11 support - debian/rules: Handle all upstart services in override_dh_installinit - Clean up obsoleted services for upstart, too - Manage upstart scripts in postinst/preinst/prerm * Restore switch to using NOOP as the default scheduler that was lost in 20180905+dfsg1-0ubuntu1~14.04.0 * Simply add -lboost_regex to LIBS instead of fixing Makefile and passing it from debian/rules. Setting -Wl,-z,defs broke the prior solution and upstreaming the Makefile fix did not go smooth anyway. gce-compute-image-packages (20181206+dfsg1-0ubuntu1) disco; urgency=medium [ Brian Murray ] * Add 0001-set-LDFLAGS-to-prevent-undefs.patch [ Balint Reczey ] * Keep Debian patch unapplied * New upstream version 20181206 (LP: #1803973) - Support enabling OS Login two factor authentication * Refresh patches * Update Lintian overrides for renamed commands * Update shared library symlinks -- Balint Reczey Fri, 25 Jan 2019 14:46:10 +0700 ** Changed in: gce-compute-image-packages (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1803973 Title: Update gce-compute-image-packages to 20181206 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Bionic: Fix Released Status in gce-compute-image-packages source package in Cosmic: Fix Released Bug description: [Impact] compute-image-packages is provided by Google for installation within guests that run on Google Compute Engine. It is a collection of tools and daemons, packaged as gce-compute-image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating gce-compute-image-packages to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. With this release we also add a new binary package to the suite - google-compute-engine-oslogin which is for a future feature of using OS Login on GCE VM instances. [Test Case] When a new version of gce-compute-image-packages is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates [Original Bug Text] GCE team has released some versions of its guest agents (https://github.com/GoogleCloudPlatform/compute-image- packages/releases) since you published your latest package version. So there are some new features and bug fixes that
[Group.of.nepali.translators] [Bug 1772950] Re: dkms key enrolled in mok, but dkms module fails to load
This bug was fixed in the package dkms - 2.2.0.3-1.1ubuntu5.14.04.10 --- dkms (2.2.0.3-1.1ubuntu5.14.04.10) trusty; urgency=medium * debian/patches/shim_secureboot_support.patch: - Move to signing just after module build to ensure it correctly applies at kernel update times. (LP: #1772950) - Generate a new MOK if there isn't one yet, and use that so sign newly-built kernel modules. (LP: #1748983) * debian/control: Breaks: shim-signed (<< 1.33.1~14.04.4) to ensure both are updated in lock-step since the changes above require a new version of update-secureboot-policy to correctly generate the new MOK and enroll it in firmware. -- Mathieu Trudel-Lapierre Mon, 28 Jan 2019 11:05:49 -0500 ** Changed in: dkms (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1772950 Title: dkms key enrolled in mok, but dkms module fails to load Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Trusty: Fix Released Status in dkms source package in Xenial: Fix Committed Status in dkms source package in Bionic: Fix Released Bug description: [Impact] All Ubuntu users for whom Secure Boot is enabled. [Test cases] 1) install dkms module (use virtualbox-dkms for example) 2) Upgrade kernel (for example, install 4.15.0-22-generic on top of 4.15.0-20-generic). 3) Verify that the generated module for the new kernel (4.15.0-22-generic in this example) is built and signed by verifying that the file in /lib/modules/$kernel/updates/dkms/$module.ko ends in ~Module signature appended~: $ hexdump -Cv /lib/modules/4.15.0-22-generic/updates/dkms/vboxdrv.ko | tail -n 100 [...] ~Module signature appended~ 4) Reboot 5) modprobe -v the module. It should not respond "Required key not available", and should return with no error. 6) Verify that dkms does not contain PKCS#7 errors. [Regression potential] Possible regressions involve failure to sign and/or be able to load modules after updates: failure to sign leading to a module being built but unsigned after a new kernel is installed or after a new DKMS module is installed, failure to load modules after reboot (usually caused by module being unsigned); failure to sign due to missing keys, signature key not being automatically slated for enrollment. All these potential regression scenarios present as failure to load a DKMS module after a reboot when it should be loaded successfully. --- At my last reboot, I was prompted to enable SecureBoot, so I did. When I booted, however, I noticed that the virtualbox service failed to start because it couldn't load its kernel module. If I attempt the same thing, I see that there's an issue with keys: $ sudo modprobe vboxdrv modprobe: ERROR: could not insert 'vboxdrv': Required key not available I do have keys enrolled; `mokutil --list-enrolled` produces http://paste.ubuntu.com/p/rntTQr5XJV/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1772950/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1813246] Re: Update gce-compute-image-packages to 20190124
This bug was fixed in the package gce-compute-image-packages - 20190124+dfsg1-0ubuntu1~14.04.0 --- gce-compute-image-packages (20190124+dfsg1-0ubuntu1~14.04.0) trusty; urgency=medium * Rebuild for Trusty gce-compute-image-packages (20190124+dfsg1-0ubuntu1) disco; urgency=medium * New upstream version 20190124 (LP: #1813246) - Update script retrieval to support Python 3 gce-compute-image-packages (20181206+dfsg1-0ubuntu1~14.04.0) trusty; urgency=medium * Backport to Trusty with the following remaining changes: - Revert ordering shutdown scripts after snapd.service. - Revert adding /snap/bin to PATH for startup/shutdown scripts - Revert to using dh-systemd because Trusty does not have the debhelper - Build-depend on libboost-regex-dev for regex support version making dh-systemd obsolete - Link with boost for regex support - Free tests from C++11 constructs to let them being compiled without C++11 support - debian/rules: Handle all upstart services in override_dh_installinit - Clean up obsoleted services for upstart, too - Manage upstart scripts in postinst/preinst/prerm * Restore switch to using NOOP as the default scheduler that was lost in 20180905+dfsg1-0ubuntu1~14.04.0 * Simply add -lboost_regex to LIBS instead of fixing Makefile and passing it from debian/rules. Setting -Wl,-z,defs broke the prior solution and upstreaming the Makefile fix did not go smooth anyway. gce-compute-image-packages (20181206+dfsg1-0ubuntu1) disco; urgency=medium [ Brian Murray ] * Add 0001-set-LDFLAGS-to-prevent-undefs.patch [ Balint Reczey ] * Keep Debian patch unapplied * New upstream version 20181206 (LP: #1803973) - Support enabling OS Login two factor authentication * Refresh patches * Update Lintian overrides for renamed commands * Update shared library symlinks -- Balint Reczey Fri, 25 Jan 2019 14:46:10 +0700 ** Changed in: gce-compute-image-packages (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1813246 Title: Update gce-compute-image-packages to 20190124 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Bionic: Fix Released Status in gce-compute-image-packages source package in Cosmic: Fix Released Bug description: [Impact] compute-image-packages is provided by Google for installation within guests that run on Google Compute Engine. It is a collection of tools and daemons, packaged as gce-compute-image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating gce-compute-image-packages to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. With this release we also add a new binary package to the suite - google-compute-engine-oslogin which is for a future feature of using OS Login on GCE VM instances. [Test Case] When a new version of gce-compute-image-packages is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates [Original Bug Text] GCE team has released some versions of its guest agents (https://github.com/GoogleCloudPlatform/compute-image- packages/releases) since you published your latest package version. So there are some new features and bug fixes that would be great to have in all Ubuntu releases. The current latest upstream version is
[Group.of.nepali.translators] [Bug 1748983] Re: Generate per-machine MOK for dkms signing
This bug was fixed in the package shim-signed - 1.33.1~16.04.4 --- shim-signed (1.33.1~16.04.4) xenial; urgency=medium * update-secureboot-policy: (LP: #1748983) - Backport update-secureboot-policy changes to generate a MOK and guide users through re-enabling validation and automatically signing DKMS modules. * debian/shim-signed.postinst: - When triggered, explicitly try to enroll the available MOK. * debian/shim-signed.install, openssl.cnf: Install some default configuration for creating our self-signed key. * debian/shim-signed.dirs: make sure we have a directory where to put a MOK. * debian/templates: update templates for update-secureboot-policy changes. * debian/control: Breaks dkms (<< 2.2.0.3-2ubuntu11.5~) since we're changing the behavior of update-secureboot-policy. -- Mathieu Trudel-Lapierre Mon, 28 Jan 2019 10:22:31 -0500 ** Changed in: shim-signed (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1748983 Title: Generate per-machine MOK for dkms signing Status in dkms package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in dkms source package in Trusty: Fix Released Status in shim-signed source package in Trusty: Fix Released Status in dkms source package in Xenial: Fix Committed Status in shim-signed source package in Xenial: Fix Released Bug description: [SRU Justification] Move to using self-signed keys for signing DKMS modules, along with the wizard / guide to make this work properly, to let third-party modules be signed and loaded by enforcing kernels, rather than disabling Secure Boot altogether. [Test case] 1) Install Ubuntu in UEFI mode. 2) Install bbswitch-dkms (or another -dkms package if useful on your system). 3) Follow the steps in the debconf prompts (enter a password, remember the password for next boot). 4) Reboot; follow the steps in MokManagerL 4a) Pick Enroll MOK: add the new key, enter the password when prompted to do so. 4b) If a dkms package was previously installed on the system (so Secure Boot is currently disabled in shim), pick "Change Secure Boot state". Follow the prompts to enter password characters. The option will only show up if Secure Boot validation was found to be disabled. 5) Pick "Reboot". 6) Log in and verify that the dkms module is loaded, using "lsmod | grep ". 7) Run 'modprobe ' to validate that the module can be loaded explicilty. 8) Validate that there are no errors from modprobe or errors in dmesg concerning signing keys. [Regression potential] If anything currently relies on Secure Boot validation being disabled in order to correctly run with an enforcing kernel, or grub is used in enforcing mode, custom / third-party kernels and modules may fail to load. --- shim-signed's update-secureboot-policy should allow creating a machine-owner key, and using this for signing kernel modules built via DKMS. Key generation and enrolling should be made as easy as possible for users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1803973] Re: Update gce-compute-image-packages to 20181206
*** This bug is a duplicate of bug 1813246 *** https://bugs.launchpad.net/bugs/1813246 This bug was fixed in the package gce-compute-image-packages - 20190124+dfsg1-0ubuntu1~16.04.0 --- gce-compute-image-packages (20190124+dfsg1-0ubuntu1~16.04.0) xenial; urgency=medium * Rebuild for Xenial gce-compute-image-packages (20190124+dfsg1-0ubuntu1) disco; urgency=medium * New upstream version 20190124 (LP: #1813246) - Update script retrieval to support Python 3 gce-compute-image-packages (20181206+dfsg1-0ubuntu1~16.04.0) xenial; urgency=medium * Backport to Xenial with the following remaining changes: - Revert ordering shutdown scripts after snapd.service. - Revert adding /snap/bin to PATH for startup/shutdown scripts - Revert to using dh-systemd because Xenial does not have the debhelper - Build-depend on libboost-regex-dev for regex support version making dh-systemd obsolete - Link with boost for regex support - Free tests from C++11 constructs to let them being compiled without C++11 support * Simply add -lboost_regex to LIBS instead of fixing Makefile and passing it from debian/rules. Setting -Wl,-z,defs broke the prior solution and upstreaming the Makefile fix did not go smooth anyway. gce-compute-image-packages (20181206+dfsg1-0ubuntu1) disco; urgency=medium [ Brian Murray ] * Add 0001-set-LDFLAGS-to-prevent-undefs.patch [ Balint Reczey ] * Keep Debian patch unapplied * New upstream version 20181206 (LP: #1803973) - Support enabling OS Login two factor authentication * Refresh patches * Update Lintian overrides for renamed commands * Update shared library symlinks -- Balint Reczey Fri, 25 Jan 2019 14:38:44 +0700 ** Changed in: gce-compute-image-packages (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1803973 Title: Update gce-compute-image-packages to 20181206 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Bionic: Fix Released Status in gce-compute-image-packages source package in Cosmic: Fix Released Bug description: [Impact] compute-image-packages is provided by Google for installation within guests that run on Google Compute Engine. It is a collection of tools and daemons, packaged as gce-compute-image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating gce-compute-image-packages to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. With this release we also add a new binary package to the suite - google-compute-engine-oslogin which is for a future feature of using OS Login on GCE VM instances. [Test Case] When a new version of gce-compute-image-packages is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates [Original Bug Text] GCE team has released some versions of its guest agents (https://github.com/GoogleCloudPlatform/compute-image- packages/releases) since you published your latest package version. So there are some new features and bug fixes that would be great to have in all Ubuntu releases. The current latest upstream version is 20181023. This update also might help us doing some QA on Ubuntu GCE images, as you can see here: https://k8s-testgrid.appspot.com/google-gce-compute- image-tools#linux-image-tests&width=20 T
[Group.of.nepali.translators] [Bug 1813246] Re: Update gce-compute-image-packages to 20190124
This bug was fixed in the package gce-compute-image-packages - 20190124+dfsg1-0ubuntu1~16.04.0 --- gce-compute-image-packages (20190124+dfsg1-0ubuntu1~16.04.0) xenial; urgency=medium * Rebuild for Xenial gce-compute-image-packages (20190124+dfsg1-0ubuntu1) disco; urgency=medium * New upstream version 20190124 (LP: #1813246) - Update script retrieval to support Python 3 gce-compute-image-packages (20181206+dfsg1-0ubuntu1~16.04.0) xenial; urgency=medium * Backport to Xenial with the following remaining changes: - Revert ordering shutdown scripts after snapd.service. - Revert adding /snap/bin to PATH for startup/shutdown scripts - Revert to using dh-systemd because Xenial does not have the debhelper - Build-depend on libboost-regex-dev for regex support version making dh-systemd obsolete - Link with boost for regex support - Free tests from C++11 constructs to let them being compiled without C++11 support * Simply add -lboost_regex to LIBS instead of fixing Makefile and passing it from debian/rules. Setting -Wl,-z,defs broke the prior solution and upstreaming the Makefile fix did not go smooth anyway. gce-compute-image-packages (20181206+dfsg1-0ubuntu1) disco; urgency=medium [ Brian Murray ] * Add 0001-set-LDFLAGS-to-prevent-undefs.patch [ Balint Reczey ] * Keep Debian patch unapplied * New upstream version 20181206 (LP: #1803973) - Support enabling OS Login two factor authentication * Refresh patches * Update Lintian overrides for renamed commands * Update shared library symlinks -- Balint Reczey Fri, 25 Jan 2019 14:38:44 +0700 ** Changed in: gce-compute-image-packages (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1813246 Title: Update gce-compute-image-packages to 20190124 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Bionic: Fix Released Status in gce-compute-image-packages source package in Cosmic: Fix Released Bug description: [Impact] compute-image-packages is provided by Google for installation within guests that run on Google Compute Engine. It is a collection of tools and daemons, packaged as gce-compute-image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating gce-compute-image-packages to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. With this release we also add a new binary package to the suite - google-compute-engine-oslogin which is for a future feature of using OS Login on GCE VM instances. [Test Case] When a new version of gce-compute-image-packages is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates [Original Bug Text] GCE team has released some versions of its guest agents (https://github.com/GoogleCloudPlatform/compute-image- packages/releases) since you published your latest package version. So there are some new features and bug fixes that would be great to have in all Ubuntu releases. The current latest upstream version is 20181023. This update also might help us doing some QA on Ubuntu GCE images, as you can see here: https://k8s-testgrid.appspot.com/google-gce-compute- image-tools#linux-image-tests&width=20 This is a test suite that is executed against all Linux distros images, and since the beg
[Group.of.nepali.translators] [Bug 1815201] Re: mdadm checkraid cronjob runs at the same time
** Also affects: mdadm (Ubuntu Disco) Importance: High Status: Triaged ** Tags removed: rls-dd-incoming -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1815201 Title: mdadm checkraid cronjob runs at the same time Status in mdadm package in Ubuntu: Triaged Status in mdadm source package in Xenial: New Status in mdadm source package in Bionic: New Status in mdadm source package in Cosmic: New Status in mdadm source package in Disco: Triaged Bug description: Currently the mdadm package will install a checkraid crontab, that is the same on all installations. This is fine for a single installation, but in bigger (distributed) environments this hurts performance. E.g. having mysql clusters on softRaid all having their arrays checked at the same moment, causes problems with availability. An solution would / could be to add an option that will allow the date-time to be randomized. Then this option / question can be used where appropriate, while still retaining the option to have the static configuration as a default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1815201/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial) derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 (linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Promote to Proposed - phase-changed: Monday, 11. February 2019 15:40 UTC + phase: Testing + phase-changed: Thursday, 14. February 2019 16:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: Pending -- snap not in beta channel - snap-release-to-edge: Pending -- snap not in edge channel + snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814647 Title: linux: 4.4.0-143.169 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial) derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 (linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 14. February 2019 16:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814647/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1803973] Re: Update gce-compute-image-packages to 20181206
*** This bug is a duplicate of bug 1813246 *** https://bugs.launchpad.net/bugs/1813246 This bug was fixed in the package gce-compute-image-packages - 20190124+dfsg1-0ubuntu1~18.10.0 --- gce-compute-image-packages (20190124+dfsg1-0ubuntu1~18.10.0) cosmic; urgency=medium * Rebuild for Cosmic gce-compute-image-packages (20190124+dfsg1-0ubuntu1) disco; urgency=medium * New upstream version 20190124 (LP: #1813246) - Update script retrieval to support Python 3 gce-compute-image-packages (20181206+dfsg1-0ubuntu1~18.10.0) cosmic; urgency=medium * Rebuild for Cosmic gce-compute-image-packages (20181206+dfsg1-0ubuntu1) disco; urgency=medium [ Brian Murray ] * Add 0001-set-LDFLAGS-to-prevent-undefs.patch [ Balint Reczey ] * Keep Debian patch unapplied * New upstream version 20181206 (LP: #1803973) - Support enabling OS Login two factor authentication * Refresh patches * Update Lintian overrides for renamed commands * Update shared library symlinks -- Balint Reczey Fri, 25 Jan 2019 12:47:54 +0700 ** Changed in: gce-compute-image-packages (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Changed in: gce-compute-image-packages (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1803973 Title: Update gce-compute-image-packages to 20181206 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Committed Status in gce-compute-image-packages source package in Xenial: Fix Committed Status in gce-compute-image-packages source package in Bionic: Fix Released Status in gce-compute-image-packages source package in Cosmic: Fix Released Bug description: [Impact] compute-image-packages is provided by Google for installation within guests that run on Google Compute Engine. It is a collection of tools and daemons, packaged as gce-compute-image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating gce-compute-image-packages to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. With this release we also add a new binary package to the suite - google-compute-engine-oslogin which is for a future feature of using OS Login on GCE VM instances. [Test Case] When a new version of gce-compute-image-packages is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates [Original Bug Text] GCE team has released some versions of its guest agents (https://github.com/GoogleCloudPlatform/compute-image- packages/releases) since you published your latest package version. So there are some new features and bug fixes that would be great to have in all Ubuntu releases. The current latest upstream version is 20181023. This update also might help us doing some QA on Ubuntu GCE images, as you can see here: https://k8s-testgrid.appspot.com/google-gce-compute- image-tools#linux-image-tests&width=20 This is a test suite that is executed against all Linux distros images, and since the beginning of this month Ubuntu has been tested too. This test suite has been improved in order to support Ubuntu. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1803973/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.ne
[Group.of.nepali.translators] [Bug 1813246] Re: Update gce-compute-image-packages to 20190124
This bug was fixed in the package gce-compute-image-packages - 20190124+dfsg1-0ubuntu1~18.10.0 --- gce-compute-image-packages (20190124+dfsg1-0ubuntu1~18.10.0) cosmic; urgency=medium * Rebuild for Cosmic gce-compute-image-packages (20190124+dfsg1-0ubuntu1) disco; urgency=medium * New upstream version 20190124 (LP: #1813246) - Update script retrieval to support Python 3 gce-compute-image-packages (20181206+dfsg1-0ubuntu1~18.10.0) cosmic; urgency=medium * Rebuild for Cosmic gce-compute-image-packages (20181206+dfsg1-0ubuntu1) disco; urgency=medium [ Brian Murray ] * Add 0001-set-LDFLAGS-to-prevent-undefs.patch [ Balint Reczey ] * Keep Debian patch unapplied * New upstream version 20181206 (LP: #1803973) - Support enabling OS Login two factor authentication * Refresh patches * Update Lintian overrides for renamed commands * Update shared library symlinks -- Balint Reczey Fri, 25 Jan 2019 12:47:54 +0700 ** Changed in: gce-compute-image-packages (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Changed in: gce-compute-image-packages (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1813246 Title: Update gce-compute-image-packages to 20190124 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Committed Status in gce-compute-image-packages source package in Xenial: Fix Committed Status in gce-compute-image-packages source package in Bionic: Fix Released Status in gce-compute-image-packages source package in Cosmic: Fix Released Bug description: [Impact] compute-image-packages is provided by Google for installation within guests that run on Google Compute Engine. It is a collection of tools and daemons, packaged as gce-compute-image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating gce-compute-image-packages to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. With this release we also add a new binary package to the suite - google-compute-engine-oslogin which is for a future feature of using OS Login on GCE VM instances. [Test Case] When a new version of gce-compute-image-packages is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates [Original Bug Text] GCE team has released some versions of its guest agents (https://github.com/GoogleCloudPlatform/compute-image- packages/releases) since you published your latest package version. So there are some new features and bug fixes that would be great to have in all Ubuntu releases. The current latest upstream version is 20181023. This update also might help us doing some QA on Ubuntu GCE images, as you can see here: https://k8s-testgrid.appspot.com/google-gce-compute- image-tools#linux-image-tests&width=20 This is a test suite that is executed against all Linux distros images, and since the beginning of this month Ubuntu has been tested too. This test suite has been improved in order to support Ubuntu. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1813246/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1814742] Re: linux-aws-hwe: 4.15.0-1033.35~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/upload-to-ppa-dnu Status: New => Invalid ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814726 phase: Packaging phase-changed: Wednesday, 06. February 2019 10:07 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814742 Title: linux-aws-hwe: 4.15.0-1033.35~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws-hwe package in Ubuntu: Invalid Status in linux-aws-hwe source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814726 phase: Packaging phase-changed: Wednesday, 06. February 2019 10:07 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814742/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1806818] Re: Fix Intel I210 doesn't work when ethernet cable gets plugged
This bug was fixed in the package linux-oem - 4.15.0-1033.38
---
linux-oem (4.15.0-1033.38) bionic; urgency=medium
* linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
[ Ubuntu: 4.15.0-45.48 ]
* linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
* External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
* kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in
ext4_check_descriptors()
linux-oem (4.15.0-1032.37) bionic; urgency=medium
* linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)
* Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"
* Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad
* Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47
[ Ubuntu: 4.15.0-44.47 ]
* linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
* To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't
support
1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion
detection
- memstick: Prevent memstick host from getting runtime suspended during card
detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
* Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
* ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
* Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
* Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling
roce
callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of
notifying
roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make m
[Group.of.nepali.translators] [Bug 1772919] Re: pam-gnome-keyring.so reveals user’s password credential as a plaintext form
** Also affects: gnome-keyring (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-keyring (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: gnome-keyring (Ubuntu) Status: New => Fix Released ** Changed in: gnome-keyring (Ubuntu Trusty) Status: New => Confirmed ** Changed in: gnome-keyring (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1772919 Title: pam-gnome-keyring.so reveals user’s password credential as a plaintext form Status in gnome-keyring package in Ubuntu: Fix Released Status in gnome-keyring source package in Trusty: Confirmed Status in gnome-keyring source package in Xenial: Confirmed Bug description: When I perform memory dump of session-child process, user’s login credential, including user accounts and their password, is revealed as a plaintext form. In ‘pam_sm_authenticate’ function, user’s password is stored in the heap memory of ‘pam_handle->data” to perform unlock the keyring in later. After unlocking the keyring, the pam module does not free/overwrite the memory area though the password is no longer used. We thus could find user’s login credentials. This raises concerns over the credential being misused for illegal behavior, such as acquiring user’s session key. It would be better to clean the heap memory. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 23 22:53:12 2018 InstallationDate: Installed on 2018-04-20 (32 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) upstart.gnome-keyring-ssh.log: grep: /home/sungjungk/.config/autostart/gnome-keyring-ssh.desktop: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1772919/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1806818] Re: Fix Intel I210 doesn't work when ethernet cable gets plugged
This bug was fixed in the package linux-oem - 4.15.0-1033.38
---
linux-oem (4.15.0-1033.38) bionic; urgency=medium
* linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
[ Ubuntu: 4.15.0-45.48 ]
* linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
* External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
* kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in
ext4_check_descriptors()
linux-oem (4.15.0-1032.37) bionic; urgency=medium
* linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)
* Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"
* Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad
* Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47
[ Ubuntu: 4.15.0-44.47 ]
* linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
* To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't
support
1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion
detection
- memstick: Prevent memstick host from getting runtime suspended during card
detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
* Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
* ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
* Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
* Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling
roce
callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of
notifying
roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make m
[Group.of.nepali.translators] [Bug 1814652] Re: linux-euclid: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa-dnu Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-euclid (Ubuntu Xenial) Status: Confirmed => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814652 Title: linux-euclid: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-euclid package in Ubuntu: Invalid Status in linux-euclid source package in Xenial: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814647 phase: Packaging phase-changed: Thursday, 07. February 2019 08:05 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814652/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1814651] Re: linux-aws: 4.4.0-1076.86 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814647 - phase: Packaging - phase-changed: Thursday, 07. February 2019 08:05 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 14. February 2019 11:31 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814651 Title: linux-aws: 4.4.0-1076.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814647 phase: Holding before Promote to Proposed phase-changed: Thursday, 14. February 2019 11:31 UTC reason: promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814651/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
