[Group.of.nepali.translators] [Bug 1829823] Re: libvirt-bin: during shutdown libvirt-bin is stopped before libvirt-guests causing hang
** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: libvirt (Ubuntu Xenial) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: cloud-archive Assignee: (unassigned) => Matthew Ruffell (mruffell) -- 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/1829823 Title: libvirt-bin: during shutdown libvirt-bin is stopped before libvirt- guests causing hang Status in Ubuntu Cloud Archive: New Status in libvirt package in Ubuntu: New Status in libvirt source package in Xenial: New Bug description: [Impact] * libvirt-bin, in: libvirt-1.3.1-1ubuntu10.24~cloud0 in trusty mitaka uca and the parent package in xenial, libvirt-1.3.1-1ubuntu10.24 are effected. * When you shutdown a system in trusty which is running some kvm virtual machines, the libvirt-bin service is stopped before libvirt-guests. libvirt-guests tries to connect to the libvirt socket to send shutdown commands to the running vms, which cannot happen since libvirtd is not running. * On some machines, the qemu processes behind the virtual machines are not killed and are left behind as defunct processes, which can cause the system to hang on them not being terminated. * The bug is caused by the libvirt-bin upstart script [1] calling a non-existant script, /usr/lib/libvirt/libvirt-stop-guests [2]. This script used to exist in the upstart script itself in version 1.2.2-0ubuntu13.1.27 [3], the version in the trusty archives. In liberty UCA, version 1.2.16-2ubuntu11.15.10.4~cloud0 [4], the script was seperated out into /usr/lib/libvirt/libvirt-stop-guests [2]. In the mitaka release, the libvirt-stop-guests script was removed and rewritten as /etc/init.d/libvirt-guests [5], but the script in [1] was never updated to point to it. [1] http://paste.ubuntu.com/p/GxxBczkCmk [2] http://paste.ubuntu.com/p/fKCDQh46vh [3] http://paste.ubuntu.com/p/QrKXqK2Bvz [4] http://paste.ubuntu.com/p/W8DgQwpYv3 [5] http://paste.ubuntu.com/p/Z28Sp2fPd6 * Since the upstart script was never updated to point to it, libvirt-bin stops without stopping libvirt-guests first. When libvirt-guests is stopped later, it cannot access the libvirt socket, cannot shut down the machines, causing the bug. * The fix is to change the upstart script to point to the new libvirt-guests script. [Test Case] * You can reproduce this in trusty with the mitaka UCA enabled. 1) Enable mitaka UCA and install libvirt0 and libvirt-bin $ sudo add-apt-repository cloud-archive:mitaka $ sudo apt update $ sudo apt install libvirt0 libvirt-bin 2) Install a virtual machine, either by using virt-install or virt-manager. I used a bionic VM. 3) Enable debugging on libvirt-guests so you can see what is going on Modify /etc/init.d/libvirt-guests and add "-x" to the end of "!/bin/sh" 4) With the vm running, shut down the system $ sudo shutdown -h now 5) Check /var/log/upstart/libvirt-bin.log, on reboot. It will say "No such file or directory: /usr/lib/libvirt/libvirt-stop-guests" 6) During that shutdown, you will see messages like: error: failed to connect to the hypervisor error: no valid connection error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory What should happen: If you follow the same steps with the fixed package, when you look at /var/log/upstart/libvirt-bin.log, you will see output of libvirt-guests connecting to and shutting down the virtual machines which lookes a little like this: https://paste.ubuntu.com/p/s4jyJX2y9F/ [Regression Potential] * There is only one file modified, the upstart script for libvirt-bin. Currently this upstart file references a file which doesn't exist, so fixing it will restore the behaviour in a way which aligns with excactly what took place in previous versions. * In xenial, there is no concern of stopping an already stopped service in the event that the upstart script pre-stop section is called by systemd. * This change only effects systems during shutdown while they still have virtual machines running, and do not effect starting and stopping services while the machine is running normally. * I believe the regression potential is low. [Other Info] * Xenial is not effected by this bug even though it ships the exact same packages. This is because xenial uses insserv to generate service dependency files ".depend.boot" ".depend.start" ".depend.stop" which pars
[Group.of.nepali.translators] [Bug 1829823] Re: libvirt-bin: during shutdown libvirt-bin is stopped before libvirt-guests causing hang
Please do -NOT- make a Xenial SRU for that. As we discussed on IRC and you pointed out in the report yourself - it is not affected due to systemd doing it right. This should only be an Upstart related change that goes on top of the Cloud-Archive-Mitaka Delta. ** Changed in: libvirt (Ubuntu) Status: In Progress => Invalid ** Changed in: libvirt (Ubuntu Xenial) Status: In Progress => Invalid ** Changed in: libvirt (Ubuntu) Assignee: Matthew Ruffell (mruffell) => (unassigned) ** Changed in: libvirt (Ubuntu Xenial) Assignee: Matthew Ruffell (mruffell) => (unassigned) -- 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/1829823 Title: libvirt-bin: during shutdown libvirt-bin is stopped before libvirt- guests causing hang Status in Ubuntu Cloud Archive: In Progress Status in libvirt package in Ubuntu: Invalid Status in libvirt source package in Xenial: Invalid Bug description: [Impact] * libvirt-bin, in: libvirt-1.3.1-1ubuntu10.24~cloud0 in trusty mitaka uca and the parent package in xenial, libvirt-1.3.1-1ubuntu10.24 are effected. * When you shutdown a system in trusty which is running some kvm virtual machines, the libvirt-bin service is stopped before libvirt-guests. libvirt-guests tries to connect to the libvirt socket to send shutdown commands to the running vms, which cannot happen since libvirtd is not running. * On some machines, the qemu processes behind the virtual machines are not killed and are left behind as defunct processes, which can cause the system to hang on them not being terminated. * The bug is caused by the libvirt-bin upstart script [1] calling a non-existant script, /usr/lib/libvirt/libvirt-stop-guests [2]. This script used to exist in the upstart script itself in version 1.2.2-0ubuntu13.1.27 [3], the version in the trusty archives. In liberty UCA, version 1.2.16-2ubuntu11.15.10.4~cloud0 [4], the script was seperated out into /usr/lib/libvirt/libvirt-stop-guests [2]. In the mitaka release, the libvirt-stop-guests script was removed and rewritten as /etc/init.d/libvirt-guests [5], but the script in [1] was never updated to point to it. [1] http://paste.ubuntu.com/p/GxxBczkCmk [2] http://paste.ubuntu.com/p/fKCDQh46vh [3] http://paste.ubuntu.com/p/QrKXqK2Bvz [4] http://paste.ubuntu.com/p/W8DgQwpYv3 [5] http://paste.ubuntu.com/p/Z28Sp2fPd6 * Since the upstart script was never updated to point to it, libvirt-bin stops without stopping libvirt-guests first. When libvirt-guests is stopped later, it cannot access the libvirt socket, cannot shut down the machines, causing the bug. * The fix is to change the upstart script to point to the new libvirt-guests script. [Test Case] * You can reproduce this in trusty with the mitaka UCA enabled. 1) Enable mitaka UCA and install libvirt0 and libvirt-bin $ sudo add-apt-repository cloud-archive:mitaka $ sudo apt update $ sudo apt install libvirt0 libvirt-bin 2) Install a virtual machine, either by using virt-install or virt-manager. I used a bionic VM. 3) Enable debugging on libvirt-guests so you can see what is going on Modify /etc/init.d/libvirt-guests and add "-x" to the end of "!/bin/sh" 4) With the vm running, shut down the system $ sudo shutdown -h now 5) Check /var/log/upstart/libvirt-bin.log, on reboot. It will say "No such file or directory: /usr/lib/libvirt/libvirt-stop-guests" 6) During that shutdown, you will see messages like: error: failed to connect to the hypervisor error: no valid connection error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory What should happen: If you follow the same steps with the fixed package, when you look at /var/log/upstart/libvirt-bin.log, you will see output of libvirt-guests connecting to and shutting down the virtual machines which looks a little like this: https://paste.ubuntu.com/p/s4jyJX2y9F/ [Regression Potential] * There is only one file modified, the upstart script for libvirt-bin. Currently this upstart file references a file which doesn't exist, so fixing it will restore the behaviour in a way which aligns with exactly what took place in previous versions. * In xenial, there is no concern of stopping an already stopped service in the event that the upstart script pre-stop section is called by systemd. * This change only effects systems during shutdown while they still have virtual machines running, and do not effect starting and stopping services while the machine is running normally. * I believe the regression potential is low. [Other Info] * Xenial is not effected by this bug even thou
[Group.of.nepali.translators] [Bug 1829214] Re: linux-azure: 4.15.0-1046.50 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829213 (trusty/linux-azure) derivatives: bug 1829212 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Testing phase-changed: Monday, 20. May 2019 15:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected channel(s): - arch=amd64:channel=latest/candidate:rev=59' stakeholder-signoff: Pending -- waiting for signoff 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/1829214 Title: linux-azure: 4.15.0-1046.50 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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 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-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829213 (trusty/linux-azure) derivatives: bug 1829212 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Testing phase-changed: Monday, 20. May 2019 15:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829214/+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 1829196] Re: linux-gcp: 4.15.0-1033.35~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829200 phase: Testing phase-changed: Monday, 20. May 2019 18:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress promote-to-updates: Pending -- Nvidia object not found -- current-driver-4.15.0-1033-gcp-amd64 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap gcp-kernel not in expected channel(s): arch=amd64:channel=latest/beta' - snap-release-to-edge: 'Pending -- snap gcp-kernel not in expected channel(s): arch=amd64:channel=latest/edge' + snap-release-to-candidate: 'Pending -- snap gcp-kernel not in expected channel(s): + arch=amd64:channel=latest/candidate:rev=62' 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/1829196 Title: linux-gcp: 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: In Progress 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 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-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829200 phase: Testing phase-changed: Monday, 20. May 2019 18:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress promote-to-updates: Pending -- Nvidia object not found -- current-driver-4.15.0-1033-gcp-amd64 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap gcp-kernel not in expected channel(s): arch=amd64:channel=latest/candidate:rev=62' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829196/+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 1829196] Re: linux-gcp: 4.15.0-1033.35~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1829847 (linux-gcp) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829200 phase: Testing phase-changed: Monday, 20. May 2019 18:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress promote-to-updates: Pending -- Nvidia object not found -- current-driver-4.15.0-1033-gcp-amd64 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: 'Pending -- snap gcp-kernel not in expected channel(s): - arch=amd64:channel=latest/candidate:rev=62' 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/1829196 Title: linux-gcp: 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: In Progress 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 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-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1829847 (linux-gcp) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829200 phase: Testing phase-changed: Monday, 20. May 2019 18:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress promote-to-updates: Pending -- Nvidia object not found -- current-driver-4.15.0-1033-gcp-amd64 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829196/+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 1824016] Re: Built-Using incorrect
This bug was fixed in the package linux-signed - 5.0.0-15.16 --- linux-signed (5.0.0-15.16) disco; urgency=medium * Master version: 5.0.0-15.16 linux-signed (5.0.0-14.15) disco; urgency=medium * Master version: 5.0.0-14.15 * Built-Using incorrect (LP: #1824016) - Rename "VERSION" template string to more precise "UNSIGNED_SRC_VERSION" - Use the correct source package name in Built-Using field -- Stefan Bader Mon, 06 May 2019 19:11:54 +0200 ** Changed in: linux-signed (Ubuntu) Status: In Progress => 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/1824016 Title: Built-Using incorrect Status in linux-signed package in Ubuntu: Fix Released Status in linux-signed-hwe package in Ubuntu: Invalid Status in linux-signed-hwe-edge package in Ubuntu: Invalid Status in linux-signed source package in Xenial: Fix Committed Status in linux-signed-hwe source package in Xenial: Fix Committed Status in linux-signed-hwe-edge source package in Xenial: Invalid Status in linux-signed source package in Bionic: Fix Committed Status in linux-signed-hwe source package in Bionic: Fix Committed Status in linux-signed-hwe-edge source package in Bionic: Fix Committed Status in linux-signed source package in Cosmic: Fix Committed Status in linux-signed-hwe source package in Cosmic: Invalid Status in linux-signed-hwe-edge source package in Cosmic: Invalid Status in linux-signed source package in Disco: Fix Released Status in linux-signed-hwe source package in Disco: Invalid Status in linux-signed-hwe-edge source package in Disco: Invalid Bug description: [Impact] The Build-Using control file field is incorrect for linux-signed-hwe & linux-signed-hwe-edge. They claim they were built against the "linux" package, but should be linux-hwe/linux-hwe-edge respectively. [Test Case] Look at the Packages file. [Fix] Detect and insert the correct package name at build time. [Regression Risk] Hm.. maybe if something gets added using the PACKAGE keyword in control.stub that isn't intended to be replaced gets accidentally replaced, screwing up some other control field? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1824016/+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 1818490] Re: Intel I210 Ethernet card not working after hotplug [8086:1533]
This bug was fixed in the package linux - 5.0.0-15.16 --- linux (5.0.0-15.16) disco; urgency=medium * CVE-2019-11683 - udp: fix GRO reception in case of length mismatch - udp: fix GRO packet of death * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130 - x86/msr-index: Cleanup bit defines - x86/speculation: Consolidate CPU whitelists - x86/speculation/mds: Add basic bug infrastructure for MDS - x86/speculation/mds: Add BUG_MSBDS_ONLY - x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests - x86/speculation/mds: Add mds_clear_cpu_buffers() - x86/speculation/mds: Clear CPU buffers on exit to user - x86/kvm/vmx: Add MDS protection when L1D Flush is not active - x86/speculation/mds: Conditionally clear CPU buffers on idle entry - x86/speculation/mds: Add mitigation control for MDS - x86/speculation/mds: Add sysfs reporting for MDS - x86/speculation/mds: Add mitigation mode VMWERV - Documentation: Move L1TF to separate directory - Documentation: Add MDS vulnerability documentation - x86/speculation/mds: Add mds=full,nosmt cmdline option - x86/speculation: Move arch_smt_update() call to after mitigation decisions - x86/speculation/mds: Add SMT warning message - x86/speculation/mds: Fix comment - x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off - x86/speculation/mds: Add 'mitigations=' support for MDS * CVE-2017-5715 // CVE-2017-5753 - s390/speculation: Support 'mitigations=' cmdline option * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639 - powerpc/speculation: Support 'mitigations=' cmdline option * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 // CVE-2018-3646 - cpu/speculation: Add 'mitigations=' cmdline option - x86/speculation: Support 'mitigations=' cmdline option * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log linux (5.0.0-14.15) disco; urgency=medium * linux: 5.0.0-14.15 -proposed tracker (LP: #1826150) * [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update (LP: #1825210) - vbox-update: updates for renamed makefiles - ubuntu: vbox -- update to 6.0.6-dfsg-1 * Intel I210 Ethernet card not working after hotplug [8086:1533] (LP: #1818490) - igb: Fix WARN_ONCE on runtime suspend * [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade (LP: #1821663) - ALSA: hda - Add two more machines to the power_save_blacklist * CVE-2019-9500 - brcmfmac: assure SSID length from firmware is limited * CVE-2019-9503 - brcmfmac: add subtype check for event handling in data path * CVE-2019-3882 - vfio/type1: Limit DMA mappings per container * autofs kernel module missing (LP: #1824333) - [Config] Update autofs4 path in inclusion list * The Realtek card reader does not enter PCIe 1.1/1.2 (LP: #1825487) - misc: rtsx: Enable OCP for rts522a rts524a rts525a rts5260 - SAUCE: misc: rtsx: Fixed rts5260 power saving parameter and sd glitch * headset-mic doesn't work on two Dell laptops. (LP: #1825272) - ALSA: hda/realtek - add two more pin configuration sets to quirk table * CVE-2019-3887 - KVM: x86: nVMX: close leak of L0's x2APIC MSRs (CVE-2019-3887) - KVM: x86: nVMX: fix x2APIC VTPR read intercept * CVE-2019-3874 - sctp: implement memory accounting on tx path - sctp: implement memory accounting on rx path * CVE-2019-1999 - binder: fix race between munmap() and direct reclaim * apparmor does not start in Disco LXD containers (LP: #1824812) - SAUCE: shiftfs: use separate llseek method for directories -- Stefan Bader Mon, 06 May 2019 17:33:15 +0200 ** Changed in: linux (Ubuntu) Status: In Progress => 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/1818490 Title: Intel I210 Ethernet card not working after hotplug [8086:1533] Status in HWE Next: Confirmed Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: Summary: Intel I210 Ethernet card not working after hotplug Steps to reproduce: 1. Power on system with ethernet cable on Intel I210 2. Check ethernet is workable 3. Unplug then plug the ethernet cable Expected result: Intel I210 Ethernet card is working, e.g. IP address acquired automatically if configured as DHCP. Actual result: Intel I210 Ethernet card not working after hotplug. dmesg has following erro
[Group.of.nepali.translators] [Bug 1829196] Re: linux-gcp: 4.15.0-1033.35~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1829847 (linux-gcp) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829200 phase: Testing phase-changed: Monday, 20. May 2019 18:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress promote-to-updates: Pending -- Nvidia object not found -- current-driver-4.15.0-1033-gcp-amd64 - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff 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/1829196 Title: linux-gcp: 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: In Progress 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 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1829847 (linux-gcp) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829200 phase: Testing phase-changed: Monday, 20. May 2019 18:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress promote-to-updates: Pending -- Nvidia object not found -- current-driver-4.15.0-1033-gcp-amd64 security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829196/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
Oops; picked the wrong openjdk... FWIW; according to the email by Mitsuya Shibata, openjdk 8 and 11 at least are affected (so, everything prior to disco if updates are not applied. Openjdk-8 updates appear to already be at 8u212, which should include Reiwa support. Marking as Fix Released so we can see at a glance that it's already been covered. ** Also affects: openjdk-13 (Ubuntu) Importance: Undecided Status: New ** Also affects: icu (Ubuntu) Importance: Undecided Status: New ** Also affects: unicode-data (Ubuntu) Importance: Undecided Status: New ** Also affects: poppler-data (Ubuntu) Importance: Undecided Status: New ** Description changed: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和) This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. == Typing / input methods == 1) Type in 'heisei' 2) Verify that the input method in use gives you an option "平成", and optionally also the square era glyph. 3) Type in 'reiwa' 4) Verify that the input method in use gives you an option that includes "令和", and possibly also the square era glyph (if supported for Heisei) 5) Type in the following strings, and verify that the options are provided in the input method: - * "れいわ"(reiwa) => "令和" - * "れいわ"(reiwa) => "㋿" - * "2018ねん"(2018nenn) => "平成三十年" - * "2018ねん"(2018nenn) => "平成三十年" - * "2019ねん"(2019nenn) => "平成三十一年" - * "2019ねん"(2019nenn) => "令和元年" - * "2020ねん"(2020nenn) => "令和二年" + * "れいわ"(reiwa) => "令和" + * "れいわ"(reiwa) => "㋿" + * "2018ねん"(2018nenn) => "平成三十年" + * "2019ねん"(2019nenn) => "平成三十一年" + * "2019ねん"(2019nenn) => "令和元年" + * "2020ねん"(2020nenn) => "令和二年" /!\ Some fonts, like fonts-noto-cjk, currently have no glyph for U+32FF. [Regression potential] This is a potentially large change as it impacts font display, character sets as well as date conversions. As such, extreme care should be taken to ensure that regressions are avoided, such that dates previous to May 1, 2019 continue to display as before, and dates onward are displayed with the new era symbols. The included test cases account for verifying the continued behavior or previous dates. ** No longer affects: openjdk-13 (Ubuntu) ** Also affects: openjdk-8 (Ubuntu) Importance: Undecided Status: New ** Changed in: openjdk-8 (Ubuntu) Status: New => Fix Released ** Also affects: gucharmap (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: icu (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: unicode-data (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: poppler-data (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: mozc (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: libreoffice (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: libreoffice-l10n (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: openjdk-8 (Ubuntu Disco) Importance: Undecided Status: New ** A
[Group.of.nepali.translators] [Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
unicode-data in eoan does include Reiwa. Reverse-depends probably still need to be rebuilt (I'm testing gucharmap which seemed easy enough to patch to work). ** Changed in: unicode-data (Ubuntu) Status: New => 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/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in fonts-noto-cjk package in Ubuntu: New Status in gnome-characters package in Ubuntu: New Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in fonts-noto-cjk source package in Xenial: New Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: New Status in libreoffice-l10n source package in Xenial: New Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: New Status in gnome-characters source package in Bionic: New Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: New Status in libreoffice-l10n source package in Bionic: New Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in fonts-noto-cjk source package in Cosmic: New Status in gnome-characters source package in Cosmic: New Status in gucharmap source package in Cosmic: New Status in icu source package in Cosmic: New Status in libreoffice source package in Cosmic: New Status in libreoffice-l10n source package in Cosmic: New Status in mozc source package in Cosmic: Fix Released Status in openjdk-8 source package in Cosmic: New Status in poppler-data source package in Cosmic: New Status in unicode-data source package in Cosmic: New Status in fonts-noto-cjk source package in Disco: New Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: New Status in libreoffice-l10n source package in Disco: New Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和) This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty
[Group.of.nepali.translators] [Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
mozc appears to be all done (LP: #1823444) ** Changed in: mozc (Ubuntu Xenial) Status: New => Fix Released ** Changed in: mozc (Ubuntu Bionic) Status: New => Fix Released ** Changed in: mozc (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: mozc (Ubuntu Disco) Status: New => 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/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in fonts-noto-cjk package in Ubuntu: New Status in gnome-characters package in Ubuntu: New Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in fonts-noto-cjk source package in Xenial: New Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: New Status in libreoffice-l10n source package in Xenial: New Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: New Status in gnome-characters source package in Bionic: New Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: New Status in libreoffice-l10n source package in Bionic: New Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in fonts-noto-cjk source package in Cosmic: New Status in gnome-characters source package in Cosmic: New Status in gucharmap source package in Cosmic: New Status in icu source package in Cosmic: New Status in libreoffice source package in Cosmic: New Status in libreoffice-l10n source package in Cosmic: New Status in mozc source package in Cosmic: Fix Released Status in openjdk-8 source package in Cosmic: New Status in poppler-data source package in Cosmic: New Status in unicode-data source package in Cosmic: New Status in fonts-noto-cjk source package in Disco: New Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: New Status in libreoffice-l10n source package in Disco: New Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和) This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a s
[Group.of.nepali.translators] [Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
** Changed in: libreoffice (Ubuntu Disco) Status: New => Fix Released ** Changed in: libreoffice-l10n (Ubuntu Disco) Status: New => 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/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in fonts-noto-cjk package in Ubuntu: New Status in gnome-characters package in Ubuntu: New Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in fonts-noto-cjk source package in Xenial: New Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: New Status in libreoffice-l10n source package in Xenial: New Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: New Status in gnome-characters source package in Bionic: New Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: New Status in libreoffice-l10n source package in Bionic: New Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in fonts-noto-cjk source package in Cosmic: New Status in gnome-characters source package in Cosmic: New Status in gucharmap source package in Cosmic: New Status in icu source package in Cosmic: New Status in libreoffice source package in Cosmic: New Status in libreoffice-l10n source package in Cosmic: New Status in mozc source package in Cosmic: Fix Released Status in openjdk-8 source package in Cosmic: New Status in poppler-data source package in Cosmic: New Status in unicode-data source package in Cosmic: New Status in fonts-noto-cjk source package in Disco: New Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和) This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is t
[Group.of.nepali.translators] [Bug 1829193] Re: linux-aws: 4.4.0-1084.94 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829209 - phase: Promote to Proposed - phase-changed: Tuesday, 21. May 2019 13:06 UTC + phase: Testing + phase-changed: Tuesday, 21. May 2019 15:06 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: 'Pending -- snap aws-kernel not in expected channel(s): arch=amd64:channel=latest/beta' + snap-release-to-edge: 'Pending -- snap aws-kernel not in expected channel(s): arch=amd64:channel=latest/edge' + 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/1829193 Title: linux-aws: 4.4.0-1084.94 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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: 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-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829209 phase: Testing phase-changed: Tuesday, 21. May 2019 15:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap aws-kernel not in expected channel(s): arch=amd64:channel=latest/beta' snap-release-to-edge: 'Pending -- snap aws-kernel not in expected channel(s): arch=amd64:channel=latest/edge' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829193/+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 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system
This bug was fixed in the package apt - 1.8.1 --- apt (1.8.1) unstable; urgency=medium * Add test case for local-only packages pinned to never * Prevent shutdown while running dpkg (LP: #1820886) * Add linux-{buildinfo,image-unsigned,source} versioned kernel pkgs (LP: #1821640) -- Julian Andres Klode Mon, 06 May 2019 10:41:52 +0200 ** Changed in: apt (Ubuntu Disco) 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/1821640 Title: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: In Progress Status in apt source package in Cosmic: In Progress Status in apt source package in Disco: Fix Released Status in apt source package in Eoan: Fix Released Bug description: [Impact] Unattended-upgrades keeps versioned kernel packages because they don't match known kernel package patterns: ... Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it would also remove the following packages which should be kept in this step: linux-image-unsigned-4.18.0-14-generic ... For reproduction see LP: #1795696, but running u-u with --verbose. And APT does not apply proper kernel-version based protection to it. [Test case] linux-image-unsigned should popup in the same list in 01autoremove-kernels as linux-signed-image, and should be autoremovable iff it's signed counterpart is autoremovable. [Regression potential] Not really any, it's just an additional string in the entry. The only difference really possible therefore is that the set of autoremovable packages changes and unattended-upgrades and friends might autoremove different sets of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress
This bug was fixed in the package apt - 1.8.1 --- apt (1.8.1) unstable; urgency=medium * Add test case for local-only packages pinned to never * Prevent shutdown while running dpkg (LP: #1820886) * Add linux-{buildinfo,image-unsigned,source} versioned kernel pkgs (LP: #1821640) -- Julian Andres Klode Mon, 06 May 2019 10:41:52 +0200 ** Changed in: apt (Ubuntu Disco) 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/1820886 Title: Potential inconsistency due to system halt/reboot being allowed when package installation in progress Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: In Progress Status in apt source package in Cosmic: In Progress Status in apt source package in Disco: Fix Released Bug description: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] 1. User1 at Ubuntu box issues "sudo apt-get upgrade"; 2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI; 3. System reboots and potentially turns into an inconsistent state. [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
Dropping the fonts-noto-cjk Xenial task, since Noto is not default font for Japanese in Xenial. (Takao is.) ** No longer affects: fonts-noto-cjk (Ubuntu Xenial) -- 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/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in fonts-noto-cjk package in Ubuntu: New Status in gnome-characters package in Ubuntu: New Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: New Status in libreoffice-l10n source package in Xenial: New Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: New Status in gnome-characters source package in Bionic: New Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: New Status in libreoffice-l10n source package in Bionic: New Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in fonts-noto-cjk source package in Cosmic: New Status in gnome-characters source package in Cosmic: New Status in gucharmap source package in Cosmic: New Status in icu source package in Cosmic: New Status in libreoffice source package in Cosmic: New Status in libreoffice-l10n source package in Cosmic: New Status in mozc source package in Cosmic: Fix Released Status in openjdk-8 source package in Cosmic: New Status in poppler-data source package in Cosmic: New Status in unicode-data source package in Cosmic: New Status in fonts-noto-cjk source package in Disco: New Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和) This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character,
[Group.of.nepali.translators] [Bug 1829203] Re: linux-fips: 4.4.0-1011.14 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829209 - phase: Promote to Proposed - phase-changed: Tuesday, 21. May 2019 13:37 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 21. May 2019 16:08 UTC reason: - promote-signing-to-proposed: Holding -- builds not complete in Signing - promote-to-proposed: Ongoing -- packages copied but not yet published to Signing + promote-signing-to-proposed: Pending -- ready for review -- 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/1829203 Title: linux-fips: 4.4.0-1011.14 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829209 phase: Ready for Promote to Proposed phase-changed: Tuesday, 21. May 2019 16:08 UTC reason: promote-signing-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829203/+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 1829198] Re: linux-raspi2: 4.4.0-1110.118 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829209 - phase: Promote to Proposed - phase-changed: Tuesday, 21. May 2019 15:07 UTC + phase: Testing + phase-changed: Tuesday, 21. May 2019 16:38 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: 'Pending -- snap pi2-kernel not in expected channel(s): arch=armhf:channel=latest/beta' + snap-release-to-edge: 'Pending -- snap pi2-kernel not in expected channel(s): arch=armhf:channel=latest/edge' + 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/1829198 Title: linux-raspi2: 4.4.0-1110.118 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829209 phase: Testing phase-changed: Tuesday, 21. May 2019 16:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap pi2-kernel not in expected channel(s): arch=armhf:channel=latest/beta' snap-release-to-edge: 'Pending -- snap pi2-kernel not in expected channel(s): arch=armhf:channel=latest/edge' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829198/+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 1829208] Re: linux-oracle: 4.15.0-1014.16~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829210 - phase: Promote to Proposed - phase-changed: Tuesday, 21. May 2019 14:14 UTC + phase: Testing + phase-changed: Tuesday, 21. May 2019 17:45 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + 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/1829208 Title: linux-oracle: 4.15.0-1014.16~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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 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 verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829210 phase: Testing phase-changed: Tuesday, 21. May 2019 17:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829208/+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 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
I reported this upstream here: https://github.com/hughsie/lvfs- website/issues/335 It looks like it's related to the metadata being too big. ** No longer affects: appstream-glib (Ubuntu) ** Bug watch added: github.com/hughsie/lvfs-website/issues #335 https://github.com/hughsie/lvfs-website/issues/335 ** Changed in: fwupd (Ubuntu) Status: New => Triaged ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu) Status: Triaged => Fix Released ** Changed in: fwupd (Ubuntu Xenial) Status: New => Triaged ** Changed in: fwupd (Ubuntu Xenial) Importance: Undecided => Critical -- 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/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Triaged Bug description: Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in a fully updated Ubuntu 16.04 desktop, To reproduce on any Ubuntu 16.04 classic (Xenial): #apt install fwupd #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML The core snap `uefi-fw-tools` used in Ubuntu Core 16 also affected with same issue. This is worked in Ubuntu 18.04 (bionic) #fwupdmgr refresh Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz Downloading… [***] Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc The `fwupd` classic confined snap also works. === Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial ii fwupd 0.8.3-0ubuntu4 #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+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 1829198] Re: linux-raspi2: 4.4.0-1110.118 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829209 - phase: Testing - phase-changed: Tuesday, 21. May 2019 16:38 UTC + phase: Signoff + phase-changed: Tuesday, 21. May 2019 21:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap pi2-kernel not in expected channel(s): arch=armhf:channel=latest/beta' snap-release-to-edge: 'Pending -- snap pi2-kernel not in expected channel(s): arch=armhf:channel=latest/edge' 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/1829198 Title: linux-raspi2: 4.4.0-1110.118 -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: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829209 phase: Signoff phase-changed: Tuesday, 21. May 2019 21: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 pi2-kernel not in expected channel(s): arch=armhf:channel=latest/beta' snap-release-to-edge: 'Pending -- snap pi2-kernel not in expected channel(s): arch=armhf:channel=latest/edge' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829198/+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 1829208] Re: linux-oracle: 4.15.0-1014.16~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829210 - phase: Testing - phase-changed: Tuesday, 21. May 2019 17:45 UTC + phase: Signoff + phase-changed: Tuesday, 21. May 2019 21:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff 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/1829208 Title: linux-oracle: 4.15.0-1014.16~16.04.1 -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: 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 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 verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829210 phase: Signoff phase-changed: Tuesday, 21. May 2019 21:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829208/+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 1829203] Re: linux-fips: 4.4.0-1011.14 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829209 - phase: Promote to Proposed - phase-changed: Tuesday, 21. May 2019 20:38 UTC + phase: Ready for Testing + phase-changed: Tuesday, 21. May 2019 22:08 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror - sync + automated-testing: Ongoing -- testing in progress + regression-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/1829203 Title: linux-fips: 4.4.0-1011.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1829209 phase: Ready for Testing phase-changed: Tuesday, 21. May 2019 22:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-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/1829203/+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 1829214] Re: linux-azure: 4.15.0-1046.50 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829213 (trusty/linux-azure) derivatives: bug 1829212 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 - phase: Testing - phase-changed: Monday, 20. May 2019 15:10 UTC + phase: Signoff + phase-changed: Tuesday, 21. May 2019 22:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff 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/1829214 Title: linux-azure: 4.15.0-1046.50 -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: 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 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-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829213 (trusty/linux-azure) derivatives: bug 1829212 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Signoff phase-changed: Tuesday, 21. May 2019 22:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829214/+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