[Group.of.nepali.translators] [Bug 1822542] [NEW] All 12 tests in kvm-unit-test failed (timeouted) on X s390x KVM
Public bug reported: I think this bug is just a place holder, as the nested KVM is out-of- scope especially on s390x TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./s390x/run s390x/selftest.elf -smp 1 -append 'test 123' FAIL selftest-setup (timeout; duration=90s) TESTNAME=intercept TIMEOUT=90s ACCEL= ./s390x/run s390x/intercept.elf -smp 1 FAIL intercept (timeout; duration=90s) TESTNAME=emulator TIMEOUT=90s ACCEL= ./s390x/run s390x/emulator.elf -smp 1 FAIL emulator (timeout; duration=90s) TESTNAME=sieve TIMEOUT=600 ACCEL= ./s390x/run s390x/sieve.elf -smp 1 FAIL sieve (timeout; duration=600) TESTNAME=sthyi TIMEOUT=90s ACCEL= ./s390x/run s390x/sthyi.elf -smp 1 FAIL sthyi (timeout; duration=90s) TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1 FAIL skey (timeout; duration=90s) TESTNAME=diag10 TIMEOUT=90s ACCEL= ./s390x/run s390x/diag10.elf -smp 1 FAIL diag10 (timeout; duration=90s) TESTNAME=pfmf TIMEOUT=90s ACCEL= ./s390x/run s390x/pfmf.elf -smp 1 FAIL pfmf (timeout; duration=90s) TESTNAME=cmm TIMEOUT=90s ACCEL= ./s390x/run s390x/cmm.elf -smp 1 FAIL cmm (timeout; duration=90s) TESTNAME=vector TIMEOUT=90s ACCEL= ./s390x/run s390x/vector.elf -smp 1 FAIL vector (timeout; duration=90s) TESTNAME=gs TIMEOUT=90s ACCEL= ./s390x/run s390x/gs.elf -smp 1 FAIL gs (timeout; duration=90s) TESTNAME=iep TIMEOUT=90s ACCEL= ./s390x/run s390x/iep.elf -smp 1 FAIL iep (timeout; duration=90s) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-145-generic 4.4.0-145.171 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Mon Apr 1 03:04:02 2019 HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.4.0-145-generic N/A linux-backports-modules-4.4.0-145-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: apport-bug package-from-proposed s390x third-party-packages xenial ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- 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/1822542 Title: All 12 tests in kvm-unit-test failed (timeouted) on X s390x KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: I think this bug is just a place holder, as the nested KVM is out-of- scope especially on s390x TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./s390x/run s390x/selftest.elf -smp 1 -append 'test 123' FAIL selftest-setup (timeout; duration=90s) TESTNAME=intercept TIMEOUT=90s ACCEL= ./s390x/run s390x/intercept.elf -smp 1 FAIL intercept (timeout; duration=90s) TESTNAME=emulator TIMEOUT=90s ACCEL= ./s390x/run s390x/emulator.elf -smp 1 FAIL emulator (timeout; duration=90s) TESTNAME=sieve TIMEOUT=600 ACCEL= ./s390x/run s390x/sieve.elf -smp 1 FAIL sieve (timeout; duration=600) TESTNAME=sthyi TIMEOUT=90s ACCEL= ./s390x/run s390x/sthyi.elf -smp 1 FAIL sthyi (timeout; duration=90s) TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1 FAIL skey (timeout; duration=90s) TESTNAME=diag10 TIMEOUT=90s ACCEL= ./s390x/run s390x/diag10.elf -smp 1 FAIL diag10 (timeout; duration=90s) TESTNAME=pfmf TIMEOUT=90s ACCEL= ./s390x/run s390x/pfmf.elf -smp 1 FAIL pfmf (timeout; duration=90s) TESTNAME=cmm TIMEOUT=90s ACCEL= ./s390x/run s390x/cmm.elf -smp 1 FAIL cmm (timeout; duration=90s) TESTNAME=vector TIMEOUT=90s ACCEL= ./s390x/run s390x/vector.elf -smp 1 FAIL vector (timeout; duration=90s)
[Group.of.nepali.translators] [Bug 1819713] Re: linux-azure: 4.15.0-1041.45 -proposed tracker
** Changed in: kernel-sru-workflow/verification-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 backports: bug 1819711 (trusty/linux-azure) derivatives: bug 1819710 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Testing phase-changed: Wednesday, 20. March 2019 20:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified 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/1819713 Title: linux-azure: 4.15.0-1041.45 -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: 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 stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released 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 1819711 (trusty/linux-azure) derivatives: bug 1819710 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Testing phase-changed: Wednesday, 20. March 2019 20:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819713/+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 1819715] Re: linux-hwe: 4.15.0-47.50~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-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 1819714 (linux-hwe-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Testing phase-changed: Monday, 18. March 2019 20:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified 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/1819715 Title: linux-hwe: 4.15.0-47.50~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: Fix Released 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 verification-testing series: Fix Released Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe 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 1819714 (linux-hwe-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Testing phase-changed: Monday, 18. March 2019 20:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819715/+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 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1821724 Title: linux: 4.4.0-145.171 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed 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 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 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/1821724/+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 1822560] [NEW] e755f780865221252ef3321215c9796b78e7b1c5 in ubuntu_btrfs_kernel_fixes failed on 4.4 i386
Public bug reported: This test can pass if you run it independently. Even with aa9ddcd4b5557102fa25695c11904f249b4dec49 (just like bug 1821913) Invoking test e755f780865221252ef3321215c9796b78e7b1c5 fix e755f780865221252ef3321215c9796b78e7b1c5 btrfs: fix null pointer dereference in clone_fs_devices when name is null when one of the device path is missing btrfs_device name is null. So this patch will check for that. mount: /dev/loop0 is write-protected, mounting read-only Performing full device TRIM (2.00GiB) ... mount failed, kernel bug: [ 8680.949850] BTRFS: device fsid 197ab202-8eef-4a3d-bca6-98f07f73a2e6 devid 1 transid 3 /dev/loop0 [ 8680.953724] BTRFS: device fsid 197ab202-8eef-4a3d-bca6-98f07f73a2e6 devid 2 transid 3 /dev/loop2 [ 8681.335859] = [ 8681.335879] BUG btrfs_extent_map (Tainted: G B ): Objects remaining in btrfs_extent_map on kmem_cache_close() [ 8681.335899] - [ 8681.335917] INFO: Slab 0xf7360ac8 objects=34 used=1 fp=0xe8e45c30 flags=0x2800080 [ 8681.335962] CPU: 3 PID: 29896 Comm: modprobe Tainted: G B 4.4.0-145-generic #171-Ubuntu [ 8681.335964] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.8.2 08/17/2011 [ 8681.335965] c1b0f967 1c177eb0 0286 e0dcdddc c13c089f f7360ac8 e0dcddfc e0dcde70 [ 8681.335969] c11cce82 c1a17524 f7360ac8 0022 0001 e8e45c30 02800080 656a624f [ 8681.335973] 20737463 616d6572 6e696e69 6e692067 72746220 655f7366 6e657478 616d5f74 [ 8681.335976] Call Trace: [ 8681.335984] [] dump_stack+0x58/0x79 [ 8681.335987] [] slab_err+0x82/0xa0 [ 8681.335989] [] ? __kmalloc+0x22d/0x240 [ 8681.335993] [] ? smp_call_function_many+0x1ad/0x220 [ 8681.335995] [] ? free_partial+0xa9/0x1b0 [ 8681.335996] [] ? free_partial+0xa9/0x1b0 [ 8681.335998] [] free_partial+0xce/0x1b0 [ 8681.336001] [] ? __flush_cpu_slab+0x40/0x40 [ 8681.336003] [] __kmem_cache_shutdown+0x42/0x80 [ 8681.336006] [] kmem_cache_destroy+0x162/0x1e0 [ 8681.336028] [] extent_map_exit+0x16/0x20 [btrfs] [ 8681.336042] [] exit_btrfs_fs+0x26/0xfc [btrfs] [ 8681.336044] [] SyS_delete_module+0x1af/0x200 [ 8681.336047] [] ? fput+0xd/0x10 [ 8681.336050] [] ? task_work_run+0x8f/0xa0 [ 8681.336052] [] ? exit_to_usermode_loop+0xb6/0xe0 [ 8681.336054] [] do_fast_syscall_32+0x9f/0x160 [ 8681.336057] [] sysenter_past_esp+0x3d/0x61 [ 8681.336060] INFO: Object 0xe8e450f0 @offset=240 [ 8681.336085] kmem_cache_destroy btrfs_extent_map: Slab cache still has objects [ 8681.336114] CPU: 3 PID: 29896 Comm: modprobe Tainted: G B 4.4.0-145-generic #171-Ubuntu [ 8681.336115] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.8.2 08/17/2011 [ 8681.336116] c1b0f967 1c177eb0 0286 e0dcded4 c13c089f f55b0cc0 f55b0d34 e0dcdf0c [ 8681.336120] c119e880 c1a15d8c ec0edb20 e0dcdf04 000d986b e0dcdeec e0dcdeec e0dcdef4 [ 8681.336124] e0dcdef4 1c177eb0 007b5f34 f8dd0880 e0dcc000 e0dcdf14 f8d48f86 e0dcdf1c [ 8681.336127] Call Trace: [ 8681.336129] [] dump_stack+0x58/0x79 [ 8681.336131] [] kmem_cache_destroy+0x1b0/0x1e0 [ 8681.336146] [] extent_map_exit+0x16/0x20 [btrfs] [ 8681.336160] [] exit_btrfs_fs+0x26/0xfc [btrfs] [ 8681.336162] [] SyS_delete_module+0x1af/0x200 [ 8681.336164] [] ? fput+0xd/0x10 [ 8681.336166] [] ? task_work_run+0x8f/0xa0 [ 8681.336168] [] ? exit_to_usermode_loop+0xb6/0xe0 [ 8681.336170] [] do_fast_syscall_32+0x9f/0x160 [ 8681.336172] [] sysenter_past_esp+0x3d/0x61 [ 8681.455355] Btrfs loaded [ 8681.483803] BTRFS: device fsid 197ab202-8eef-4a3d-bca6-98f07f73a2e6 devid 1 transid 6 /dev/loop0 [ 8681.539920] BTRFS info (device loop0): allowing degraded mounts [ 8681.539929] BTRFS info (device loop0): disk space caching is enabled [ 8681.539930] BTRFS: has skinny extents [ 8681.539932] BTRFS: flagging fs with big metadata feature [ 8681.540722] BTRFS warning (device loop0): devid 2 uuid 5af56aa2-70cd-446c-9c91-e42ce244669e is missing [ 8681.705354] BTRFS info (device loop0): relocating block group 676855808 flags 2 [ 8681.821174] BTRFS info (device loop0): relocating block group 20971520 flags 18 [ 8681.969227] BTRFS info (device loop0): disk added /dev/loop3 umount: /tmp/mnt-e755f780865221252ef3321215c9796b78e7b1c5: not mounted losetup: /dev/loop0: detach failed: No such device or address losetup: /dev/loop2: detach failed: No such device or address losetup: /dev/loop3: detach failed: No such device or address Found kernel issue: [ 8680.949850] BTRFS: device fsid 197ab202-8eef-4a3d-bca6-98f07f73a2e6 devid 1 transid 3 /dev/loop0 [ 8680.953724] BTRFS: device fsid 197ab202-8eef-4a3d-bca6-98f07f73a2e6 devid 2 transid 3 /dev/loop2 [ 8681.335859] = [ 8681.335879] BUG btrfs_extent_map (Tainted: G B ): Objects remaining in btrfs_extent_map on kmem_cache_close() [ 8681.335899] - [
[Group.of.nepali.translators] [Bug 1819714] Re: linux-hwe-edge: 4.15.0-47.50~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819715 phase: Testing phase-changed: Wednesday, 20. March 2019 18:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified 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/1819714 Title: linux-hwe-edge: 4.15.0-47.50~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: 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 verification-testing series: Fix Released Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge 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: 1819715 phase: Testing phase-changed: Wednesday, 20. March 2019 18:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819714/+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 1821726] Re: linux-aws: 4.4.0-1079.89 -proposed tracker
** Changed in: kernel-sru-workflow/verification-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified 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/1821726 Title: linux-aws: 4.4.0-1079.89 -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 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: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821726/+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 1821723] Re: linux-snapdragon: 4.4.0-1110.115 -proposed tracker
** Changed in: kernel-sru-workflow/verification-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 12:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified 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/1821723 Title: linux-snapdragon: 4.4.0-1110.115 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 12:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821723/+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 1821713] Re: linux-raspi2: 4.4.0-1106.114 -proposed tracker
** Changed in: kernel-sru-workflow/verification-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified 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/1821713 Title: linux-raspi2: 4.4.0-1106.114 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821713/+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 1821712] Re: linux-kvm: 4.4.0-1043.49 -proposed tracker
** Changed in: kernel-sru-workflow/verification-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 13:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified 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/1821712 Title: linux-kvm: 4.4.0-1043.49 -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 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 verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 13:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821712/+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 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/verification-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Thursday, 28. March 2019 12:32 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 -- 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/1820326 Title: linux-fips: 4.4.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: 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 verification-testing series: Fix Released 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: 1821724 phase: Testing phase-changed: Thursday, 28. March 2019 12:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820326/+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 1819703] Re: linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819704 phase: Testing phase-changed: Monday, 25. March 2019 14:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified 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/1819703 Title: linux-oracle: 4.15.0-1010.12~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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1819704 phase: Testing phase-changed: Monday, 25. March 2019 14:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819703/+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 1819710] Re: linux-azure-edge: 4.15.0-1041.45 -proposed tracker
** Changed in: kernel-sru-workflow/verification-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819713 phase: Testing phase-changed: Wednesday, 20. March 2019 20:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- stakeholder signoff not verified 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/1819710 Title: linux-azure-edge: 4.15.0-1041.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: 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 stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure-edge package in Ubuntu: Invalid Status in linux-azure-edge 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: 1819713 phase: Testing phase-changed: Wednesday, 20. March 2019 20:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- stakeholder signoff not verified security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819710/+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 1819693] Re: linux-aws-hwe: 4.15.0-1035.37~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819694 phase: Testing phase-changed: Thursday, 21. March 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified 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/1819693 Title: linux-aws-hwe: 4.15.0-1035.37~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 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 verification-testing series: Fix Released Status in linux-aws-hwe package in Ubuntu: Invalid Status in linux-aws-hwe 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: 1819694 phase: Testing phase-changed: Thursday, 21. March 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819693/+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 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819698 phase: Testing phase-changed: Monday, 25. March 2019 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified 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/1819695 Title: linux-gcp: 4.15.0-1029.31~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: 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: Fix Released 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: 1819698 phase: Testing phase-changed: Monday, 25. March 2019 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819695/+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 1656999] Re: [Dell Inspiron 7537/7737] Wireless key does not work on this system
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1656999 Title: [Dell Inspiron 7537/7737] Wireless key does not work on this system Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: CID: 201306-13867 Dell Insprion 7537 The wireless key does not work on this system. This issue was once reported in bug 1339456, and fixed by an ACPI quirk. But now it's not working. Keycode 240 can be detected from showkey -k Nothing can be detected from showkey -s ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1532 F pulseaudio /dev/snd/controlC1: ubuntu 1532 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 16 22:58:40 2017 HibernationDevice: RESUME=UUID=9e1a096f-d8ef-429f-b388-03b62ca17735 InstallationDate: Installed on 2017-01-16 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=7ebd45a5-39be-47e6-a84a-0121cf8445f9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd10/04/2016:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656999/+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 1818673] Re: [SRU] Please accept wslu to supported releases
This bug was fixed in the package wslu - 2.0.0-0ubuntu2~18.10.0 --- wslu (2.0.0-0ubuntu2~18.10.0) cosmic; urgency=medium * Rebuild for Cosmic (LP: #1818673) wslu (2.0.0-0ubuntu2) disco; urgency=medium * Only Suggest imagemagick and print error message when convert is missing wslu (2.0.0-0ubuntu1) disco; urgency=medium * New upstream release * Include src/etc/wsl.ico again in original source. The problematic image was replaced by upstream with one with DFSG-free license. * debian/gbp.conf: Set upstream tag format * debian/copyright: Update copyright info * Stop shipping mime info for wslview. Also drop fixing executable bits of runHidden.vbs * Fix running tests * Skip interop check in scripts * Run full test suite in WSL environments and only a subset on Linux * Makefile: Honor DESTDIR * debian/dirs: Create install dirs * Keep installing the Ubuntu logo as the default for shortcuts Using the logo of the distribution makes it visible which WSL installation will run the command executed by the shortcut. * Stop build-depending on dh-exec, it is not needed anymore * Fix one test failing on Windows wslu (1.9+dfsg1-0ubuntu1) disco; urgency=medium * Initial release -- Balint Reczey Tue, 19 Mar 2019 11:04:18 +0100 ** Changed in: wslu (Ubuntu Cosmic) 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/1818673 Title: [SRU] Please accept wslu to supported releases Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: Fix Committed Status in wslu source package in Bionic: Fix Committed Status in wslu source package in Cosmic: Fix Released Bug description: [Impact] The package is new to the releases and contains integration utilities for Ubuntu when Ubuntu is run in WSL. [Test Case] * Install the package in Ubuntu on WSL and observe the shipped commands working: wslfetch wslupath wslview [Regression Potential] Since the package is new it may not cause regressions by being broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1818673/+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 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
This bug was fixed in the package resolvconf - 1.79ubuntu10.18.10.3 --- resolvconf (1.79ubuntu10.18.10.3) cosmic; urgency=medium * d/resolvconf.resolvconf-pull-resolved.service Hack out the 'edns0' option that systemd-resolved has recently added to its stub-resolv.conf. (LP: #1817903) -- Dan Streetman Thu, 14 Mar 2019 17:33:24 -0400 ** Changed in: resolvconf (Ubuntu Cosmic) 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/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf Status in resolvconf package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in resolvconf source package in Trusty: Invalid Status in systemd source package in Trusty: Invalid Status in resolvconf source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in resolvconf source package in Bionic: Fix Committed Status in systemd source package in Bionic: Invalid Status in resolvconf source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Invalid Status in resolvconf source package in Disco: Fix Released Status in systemd source package in Disco: Invalid Bug description: [impact] systems upgraded from pre-Bionic releases to Bionic or later will continue to use ifupdown/resolvconf for network conf and management, but resolvconf has a new systemd service in Bionic and later that pulls systemd-resolved stub-resolv.conf into its local configuration. With the recent addition of edns0 option to the stub resolver conf in systemd to fix bug 1811471, this means resolvconf now sets up the /etc/resolv.conf file to include upstream servers but also use edns. For any systems where the upstream resolver(s) don't support edns, dns lookups will break. [test case] == upgrade from pre-bionic (e.g. xenial) to bionic or later == 1) create a xenial system with ifupdown/resolvconf. The ifupdown config needs to include an upstream name server (must be static). At this point, once the network is configured and up, the resolvconf should have put the upstream name server(s) and search domain into the /etc/resolv.conf. As is usual for pre-systemd releases, there should be no local dns resolver in /etc/resolv.conf (i.e. 127.0.0.53 should not be included) at this point. 2) upgrade the system to bionic (alternately it should be possible to install bionic, then remove netplan and install/configure ifupdown and resolvconf, but I have not specifically tested this). The upgrade will retain the ifupdown/resolvconf configuration, and will not change to netplan/systemd-networkd. After upgrade is finished, the /etc/resolv.conf will contain: a) the upstream name server(s) b) options edns0 c) the local stub resolver (127.0.0.53) d) search domain the fixed resolvconf will remove (b). As mentioned, this case also should cover the situation of a native Bionic install, where netplan is removed and ifupdown/resolvconf is manually installed. == bionic or later install == with a bionic install, ifupdown is not installed, instead netplan /systemd-networkd handle networking. In this case, systemd-networkd manages the /etc/resolv.conf, and symlinks it to networkd's stub- resolv.conf which always contains only the local stub resolver (127.0.0.53) and (recently) options edns0, and local search domain. If resolvconf is installed while systemd-networkd is managing the network, then currently the resolv.conf contents will remain completely unchanged, still pointing to the local stub resolver. This resolvconf change will alter that, to remove 'options edns0'. No other changes will be made from the stub-resolv.conf. [regression potential] Regressions due to this change would likely be seen in dns query failures with other system configurations. This will cause systems with resolvconf installed to lose the fix from bug 1811471, and again experience that bug. [other info] This affects only Bionic and later; in Xenial and earlier, systemd does not handle dns, and the 'edns0' option was not added to that systemd-resolved anyway. This also does not affect Debian, as it does not include the 'resolvconf-pull-resolved' service either. original description: -- Mint 19 (Ubuntu 18.04) Following latest mint update done on 24/02/2019, DNS is broken nslookup and dig of certain domain names work as expected, ping does not (ip works but not domain name) After a day of trial and error, testing I found that the problem lies with the presence of "options edns0" in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf) With option present many dns lookups fail with both FF and chrome br
[Group.of.nepali.translators] [Bug 1822579] [NEW] Remove btrfs module after a failed fallocate attempt will cause error on 4.4 i386
Public bug reported: If one issues a rmmod (or modprobe -r) command after a failed fallocate attempt, it will cause error with call trace: = BUG btrfs_extent_map (Not tainted): Objects remaining in btrfs_extent_map on kmem_cache_close() - Disabling lock debugging due to kernel taint INFO: Slab 0xf7526fb0 objects=34 used=1 fp=0xf43fef78 flags=0x2800080 CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 c1b0d967 35a7d73c 0286 f4ed9ddc c13c034f f7526fb0 f4ed9dfc f4ed9e70 c11ccc42 c1a164b0 f7526fb0 0022 0001 f43fef78 02800080 656a624f 20737463 616d6572 6e696e69 6e692067 72746220 655f7366 6e657478 616d5f74 Call Trace: [] dump_stack+0x58/0x79 [] slab_err+0x82/0xa0 [] ? __kmalloc+0x22d/0x240 [] ? __free_slab+0xa0/0x130 [] ? free_partial+0xa9/0x1b0 [] ? free_partial+0xa9/0x1b0 [] free_partial+0xce/0x1b0 [] ? __flush_cpu_slab+0x40/0x40 [] __kmem_cache_shutdown+0x42/0x80 [] kmem_cache_destroy+0x162/0x1e0 [] extent_map_exit+0x16/0x20 [btrfs] [] exit_btrfs_fs+0x26/0x206 [btrfs] [] SyS_delete_module+0x1af/0x200 [] ? fput+0xd/0x10 [] ? task_work_run+0x8f/0xa0 [] ? exit_to_usermode_loop+0xb6/0xe0 [] do_fast_syscall_32+0x9f/0x160 [] sysenter_past_esp+0x3d/0x61 INFO: Object 0xf43fe078 @offset=120 kmem_cache_destroy btrfs_extent_map: Slab cache still has objects CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 c1b0d967 35a7d73c 0286 f4ed9ed4 c13c034f ef34f600 ef34f674 f4ed9f0c c119e630 c1a14d18 f55f3220 f4ed9f04 000d96ab f4ed9eec f4ed9eec f4ed9ef4 f4ed9ef4 35a7d73c 022ffd44 f8e46880 f4ed8000 f4ed9f14 f8dc0ac6 f4ed9f1c Call Trace: [] dump_stack+0x58/0x79 [] kmem_cache_destroy+0x1b0/0x1e0 [] extent_map_exit+0x16/0x20 [btrfs] [] exit_btrfs_fs+0x26/0x206 [btrfs] [] SyS_delete_module+0x1af/0x200 [] ? fput+0xd/0x10 [] ? task_work_run+0x8f/0xa0 [] ? exit_to_usermode_loop+0xb6/0xe0 [] do_fast_syscall_32+0x9f/0x160 [] sysenter_past_esp+0x3d/0x61 Steps to reproduce this: TMP=/tmp MNT=/tmp/mnt mkdir $MNT TMPIMG0=$TMP/test0.img DEV0=`losetup -f` truncate --size 512M $TMPIMG0 losetup $DEV0 $TMPIMG0 mkfs.btrfs -f $DEV0 >& /dev/null mount $DEV0 $MNT btrfs quota enable $MNT btrfs sub create $MNT/subv btrfs qgroup limit 10M $MNT/subv fallocate --length 20M $MNT/subv/data rmmod btrfs ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169 ProcVersionSignature: User Name 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 1 11:43 seq crw-rw 1 root audio 116, 33 Apr 1 11:43 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Apr 1 11:55:56 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6aaa11f6-d386-4c0c-b4b8-38e6c408980a ro RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd09/18/2012:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: apport-bug i386 uec-images xenial ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- 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/1822579 Title: Remove btrfs module after a failed fallocate
[Group.of.nepali.translators] [Bug 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
4.4.0-145.171 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) svm (bug 1821903) debug (bug 1821906) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify11 timeouted (bug 1808107) xfstests - xfs generic/475 timed out 48 / 49 tests were run, missing: xfstests Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_kvm_unit_tests - pmu on ms10-34-mcdivittB0-kernel (bug 1751000) gicv2-ipi and gicv2-active on starmie ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify11 timeouted (bug 1808107) Issue to note in i386: ubuntu_btrfs_kernel_fixes - aa9ddcd4 on 4.4 i386 (bug 1821913) e755f780 on 4.4 i386 (bug 1822560) ubuntu_kvm_smoke_test - timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify11 timeouted (bug 1808107) xfstests - xfs generic/308 timed out (bug 1738152) Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_ltp_syscalls - fallocate04 fallocate05 fdatasync03 fgetxattr01 fremovexattr01 fremovexattr02 fsetxattr01 fsync01 fsync04 inotify07 inotify08 lremovexattr01 msync04 preadv03 preadv03_64 pwritev03 pwritev03_64 setxattr01 sync03 (btrfs failed with ENOSPC) inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) sync_file_range02 (bug 1819116) xfstests - btrfs generic/176 timed out Issue to note in s390x (KVM): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1812189) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - All tests failed on s390x KVM (bug 1822542) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify11 timeouted (bug 1808107) ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in ubuntu-cloud container) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option hould be enable on X s390x (bug 1813721) Issue to note in s390x (Ubuntu on LPAR): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1812189) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify11 timeouted (bug 1808107) ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in ubuntu-cloud container) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option hould be enable on X s390x (bug 1813721) Issue to note in s390x (zVM): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1812189) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify11 timeouted (bug 1808107) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable on X s390x (bug 1813721) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1821724 Title: linux: 4.4.0-145.171 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released
[Group.of.nepali.translators] [Bug 1818673] Re: [SRU] Please accept wslu to supported releases
This bug was fixed in the package wslu - 2.0.0-0ubuntu2~18.04.0 --- wslu (2.0.0-0ubuntu2~18.04.0) bionic; urgency=medium * Rebuild for Bionic (LP: #1818673) wslu (2.0.0-0ubuntu2) disco; urgency=medium * Only Suggest imagemagick and print error message when convert is missing wslu (2.0.0-0ubuntu1) disco; urgency=medium * New upstream release * Include src/etc/wsl.ico again in original source. The problematic image was replaced by upstream with one with DFSG-free license. * debian/gbp.conf: Set upstream tag format * debian/copyright: Update copyright info * Stop shipping mime info for wslview. Also drop fixing executable bits of runHidden.vbs * Fix running tests * Skip interop check in scripts * Run full test suite in WSL environments and only a subset on Linux * Makefile: Honor DESTDIR * debian/dirs: Create install dirs * Keep installing the Ubuntu logo as the default for shortcuts Using the logo of the distribution makes it visible which WSL installation will run the command executed by the shortcut. * Stop build-depending on dh-exec, it is not needed anymore * Fix one test failing on Windows wslu (1.9+dfsg1-0ubuntu1) disco; urgency=medium * Initial release -- Balint Reczey Tue, 19 Mar 2019 00:04:28 +0100 ** Changed in: wslu (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1818673 Title: [SRU] Please accept wslu to supported releases Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: Fix Committed Status in wslu source package in Bionic: Fix Released Status in wslu source package in Cosmic: Fix Released Bug description: [Impact] The package is new to the releases and contains integration utilities for Ubuntu when Ubuntu is run in WSL. [Test Case] * Install the package in Ubuntu on WSL and observe the shipped commands working: wslfetch wslupath wslview [Regression Potential] Since the package is new it may not cause regressions by being broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1818673/+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 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
This bug was fixed in the package resolvconf - 1.79ubuntu10.18.04.3 --- resolvconf (1.79ubuntu10.18.04.3) bionic; urgency=medium * d/resolvconf.resolvconf-pull-resolved.service Hack out the 'edns0' option that systemd-resolved has recently added to its stub-resolv.conf. (LP: #1817903) -- Dan Streetman Thu, 14 Mar 2019 17:35:23 -0400 ** Changed in: resolvconf (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf Status in resolvconf package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in resolvconf source package in Trusty: Invalid Status in systemd source package in Trusty: Invalid Status in resolvconf source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in resolvconf source package in Bionic: Fix Released Status in systemd source package in Bionic: Invalid Status in resolvconf source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Invalid Status in resolvconf source package in Disco: Fix Released Status in systemd source package in Disco: Invalid Bug description: [impact] systems upgraded from pre-Bionic releases to Bionic or later will continue to use ifupdown/resolvconf for network conf and management, but resolvconf has a new systemd service in Bionic and later that pulls systemd-resolved stub-resolv.conf into its local configuration. With the recent addition of edns0 option to the stub resolver conf in systemd to fix bug 1811471, this means resolvconf now sets up the /etc/resolv.conf file to include upstream servers but also use edns. For any systems where the upstream resolver(s) don't support edns, dns lookups will break. [test case] == upgrade from pre-bionic (e.g. xenial) to bionic or later == 1) create a xenial system with ifupdown/resolvconf. The ifupdown config needs to include an upstream name server (must be static). At this point, once the network is configured and up, the resolvconf should have put the upstream name server(s) and search domain into the /etc/resolv.conf. As is usual for pre-systemd releases, there should be no local dns resolver in /etc/resolv.conf (i.e. 127.0.0.53 should not be included) at this point. 2) upgrade the system to bionic (alternately it should be possible to install bionic, then remove netplan and install/configure ifupdown and resolvconf, but I have not specifically tested this). The upgrade will retain the ifupdown/resolvconf configuration, and will not change to netplan/systemd-networkd. After upgrade is finished, the /etc/resolv.conf will contain: a) the upstream name server(s) b) options edns0 c) the local stub resolver (127.0.0.53) d) search domain the fixed resolvconf will remove (b). As mentioned, this case also should cover the situation of a native Bionic install, where netplan is removed and ifupdown/resolvconf is manually installed. == bionic or later install == with a bionic install, ifupdown is not installed, instead netplan /systemd-networkd handle networking. In this case, systemd-networkd manages the /etc/resolv.conf, and symlinks it to networkd's stub- resolv.conf which always contains only the local stub resolver (127.0.0.53) and (recently) options edns0, and local search domain. If resolvconf is installed while systemd-networkd is managing the network, then currently the resolv.conf contents will remain completely unchanged, still pointing to the local stub resolver. This resolvconf change will alter that, to remove 'options edns0'. No other changes will be made from the stub-resolv.conf. [regression potential] Regressions due to this change would likely be seen in dns query failures with other system configurations. This will cause systems with resolvconf installed to lose the fix from bug 1811471, and again experience that bug. [other info] This affects only Bionic and later; in Xenial and earlier, systemd does not handle dns, and the 'edns0' option was not added to that systemd-resolved anyway. This also does not affect Debian, as it does not include the 'resolvconf-pull-resolved' service either. original description: -- Mint 19 (Ubuntu 18.04) Following latest mint update done on 24/02/2019, DNS is broken nslookup and dig of certain domain names work as expected, ping does not (ip works but not domain name) After a day of trial and error, testing I found that the problem lies with the presence of "options edns0" in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf) With option present many dns lookups fail with both FF and chrome bro
[Group.of.nepali.translators] [Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** No longer affects: horizon (Ubuntu Xenial) ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/pike Importance: Undecided Status: New ** Also affects: cloud-archive/stein Importance: Undecided Status: New ** Also affects: cloud-archive/rocky Importance: Undecided Status: New ** Also affects: cloud-archive/queens Importance: Undecided Status: New -- 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/1822129 Title: [SRU] leave device name empty so that nova can determine it instead Status in Ubuntu Cloud Archive: New Status in Ubuntu Cloud Archive pike series: New Status in Ubuntu Cloud Archive queens series: New Status in Ubuntu Cloud Archive rocky series: New Status in Ubuntu Cloud Archive stein series: New Status in horizon package in Ubuntu: In Progress Status in horizon source package in Bionic: New Status in horizon source package in Cosmic: New Status in horizon source package in Disco: In Progress Bug description: [IMPACT] Horizon hardcoded 'vda' no matter what (legacy code) for boot volume scenarios. Meaning that if for instance we use an image with scsi decoration[1] horizon will name the device_name as 'vda' when it should be 'sda'. Inside the instance, it will be 'sda' but horizon will show 'vda', if you then attach a second volume the volume will be seen as 'sda' in horizon, but 'sdb' in the instance and so on ... creating a inconsistency, and can also cause in certain circumstance VM to have issue to successfully reboot, hanging with "No bootable device". There is 2 functions separated as follow: * setFinalSpecBootImageToVolume() which already uses BDMv2, in this case it was just a matter to remove the 'device_name' attribute as suggested per documentation[2]. This function take care of boot image from volume scenario. * setFinalSpecBootFromVolumeDevice() which currently uses BDMv1 (legacy), in this case an upgrade to BDMv2 without setting up a 'device_name' attribute is sufficient to fix the issue. This function take care of booting from existing volume and snapshot. Basically, with theses 2 fixes, it is no longer relying on "vol_device_name= 'vda'" as it was before as it is no longer needed since Liberty (again as per documentation) An instance with scsi decoration will properly show 'sda' and without will show 'vda'.'vda' will still be taken when it's the right thing to do, but not because it is hardcorded like it used to before these fixes. [1] - scsi meta decoration: hw_disk_bus='scsi' hw_scsi_model='virtio-scsi' [2]- https://docs.openstack.org/nova/stein/user/block-device-mapping [TEST CASE] Here's some use case I can think of * Test #1 : Use Xen as hypervisor 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance should starts with /dev/xvda as root device, instead of 'dev/vda' * Test #2: Use scsi meta data image decoration: hw_disk_bus='scsi' hw_scsi_model='virtio-scsi' 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance should starts with /dev/sda as root device, instead of 'dev/vda' * Test #3: Use no scsi meta data image decoration 1. Go to the Horizon dashboard and launch an instance 2. Select "Boot from image (creates a new volume)" as Instance Boot Source Expected result: Instance will remain with /dev/vda as root device. No behaviour change here. * Test #4: This above also applies to boot from existing volume and snapshot. [POTENTIAL REGRESSION] * none expected, we basically leave nova to determine the device_name instead of having it force for Horizon by removing the 'device_name' attribute, and we also take benefit of it to upgrade some part of the code from legacy BDMv1 in flavor of BDMv2. * Note: This will not fix device name inconsistency already created instance, but will fix newly created instance after having applied the package from where these fixes have been first introduced. [OTHER INFORMATION] * Upstream bug: https://bugs.launchpad.net/nova/+bug/1560965 * Upstream git-review: # Taking care of bootimagefromvolume https://review.openstack.org/644982/ https://github.com/openstack/horizon/commit/4788c4d2f59b8aa08e5f599a6d2c327b6004dc0c # Taking care of existing volume and snapshot https://review.openstack.org/648328/ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.ne
[Group.of.nepali.translators] [Bug 1818880] Re: Deadlock when detaching network interface
We don't have qemu in the rocky cloud archive so this is fixed via bionic. ** Changed in: cloud-archive/rocky Status: Triaged => Won't Fix -- 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/1818880 Title: Deadlock when detaching network interface Status in Ubuntu Cloud Archive: Triaged Status in Ubuntu Cloud Archive ocata series: Triaged Status in Ubuntu Cloud Archive pike series: Triaged Status in Ubuntu Cloud Archive queens series: Triaged Status in Ubuntu Cloud Archive rocky series: Won't Fix Status in Ubuntu Cloud Archive stein series: Triaged Status in qemu package in Ubuntu: Fix Released Status in qemu source package in Xenial: Fix Released Status in qemu source package in Bionic: Fix Released Status in qemu source package in Cosmic: Fix Released Status in qemu source package in Disco: Fix Released Bug description: [Impact] Qemu guests hang indefinitely [Description] When running a Qemu guest with VirtIO network interfaces, detaching an interface that's currently being used can result in a deadlock. The guest instance will hang and become unresponsive to commands, and the only option is to kill -9 the instance. The reason for this is a dealock between a monitor and an RCU thread, which will fight over the BQL (qemu_global_mutex) and the critical RCU section locks. The monitor thread will acquire the BQL for detaching the network interface, and fire up a helper thread to deal with detaching the network adapter. That new thread needs to wait on the RCU thread to complete the deletion, but the RCU thread wants the BQL to commit its transactions. This bug is already fixed upstream (73c6e4013b4c rcu: completely disable pthread_atfork callbacks as soon as possible) and included for other series (see below), so we don't need to backport it to Bionic onwards. Upstream commit: https://git.qemu.org/?p=qemu.git;a=commit;h=73c6e4013b4c $ git describe --contains 73c6e4013b4c v2.10.0-rc2~1^2~8 $ rmadison qemu ===> qemu | 1:2.5+dfsg-5ubuntu10.34 | xenial-updates/universe | amd64, ... qemu | 1:2.11+dfsg-1ubuntu7| bionic/universe | amd64, ... qemu | 1:2.12+dfsg-3ubuntu8| cosmic/universe | amd64, ... qemu | 1:3.1+dfsg-2ubuntu2 | disco/universe| amd64, ... [Test Case] Being a racing condition, this is a tricky bug to reproduce consistently. We've had reports of users running into this with OpenStack deployments and Windows Server guests, and the scenario is usually like this: 1) Deploy a 16vCPU Windows Server 2012 R2 guest with a virtio network interface 2) Stress the network interface with e.g. Windows HLK test suite or similar 3) Repeatedly attach/detach the network adapter that's in use It usually takes more than ~4000 attach/detach cycles to trigger the bug. [Regression Potential] Regressions for this might arise from the fact that the fix changes RCU lock code. Since this patch has been upstream and in other series for a while, it's unlikely that it would regressions in RCU code specifically. Other code that makes use of the RCU locks (MMIO and some monitor events) will be thoroughly tested for any regressions with use-case scenarios and scripted runs. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+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 1818673] Re: [SRU] Please accept wslu to supported releases
This bug was fixed in the package wslu - 2.0.0-0ubuntu2~16.04.0 --- wslu (2.0.0-0ubuntu2~16.04.0) xenial; urgency=medium * Rebuild for Xenial (LP: #1818673) * Build-depend on debhelper (>= 9) with compat level 9 wslu (2.0.0-0ubuntu2) disco; urgency=medium * Only Suggest imagemagick and print error message when convert is missing wslu (2.0.0-0ubuntu1) disco; urgency=medium * New upstream release * Include src/etc/wsl.ico again in original source. The problematic image was replaced by upstream with one with DFSG-free license. * debian/gbp.conf: Set upstream tag format * debian/copyright: Update copyright info * Stop shipping mime info for wslview. Also drop fixing executable bits of runHidden.vbs * Fix running tests * Skip interop check in scripts * Run full test suite in WSL environments and only a subset on Linux * Makefile: Honor DESTDIR * debian/dirs: Create install dirs * Keep installing the Ubuntu logo as the default for shortcuts Using the logo of the distribution makes it visible which WSL installation will run the command executed by the shortcut. * Stop build-depending on dh-exec, it is not needed anymore * Fix one test failing on Windows wslu (1.9+dfsg1-0ubuntu1) disco; urgency=medium * Initial release -- Balint Reczey Tue, 19 Mar 2019 11:04:18 +0100 ** Changed in: wslu (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1818673 Title: [SRU] Please accept wslu to supported releases Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: Fix Released Status in wslu source package in Bionic: Fix Released Status in wslu source package in Cosmic: Fix Released Bug description: [Impact] The package is new to the releases and contains integration utilities for Ubuntu when Ubuntu is run in WSL. [Test Case] * Install the package in Ubuntu on WSL and observe the shipped commands working: wslfetch wslupath wslview [Regression Potential] Since the package is new it may not cause regressions by being broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1818673/+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 1821582] Re: Don't rely on SysV init script in logrotate config
This bug was fixed in the package rsyslog - 8.16.0-1ubuntu3.1 --- rsyslog (8.16.0-1ubuntu3.1) xenial; urgency=medium * Add d/rsyslog-rotate * Modify d/rsyslog.install & d/rsyslog.logrotate Don't rely on SysV init script in logrotate config Add a small helper to send SIGHUP to rsyslogd to close open log files. Use systemctl directly if systemd is the active PID 1. Keep the SysV init script as fallback only. (LP: #1821582) -- Eric Desrochers Tue, 19 Mar 2019 22:09:50 -0400 ** Changed in: rsyslog (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1821582 Title: Don't rely on SysV init script in logrotate config Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Xenial: Fix Released Bug description: [IMPACT] Xenial uses systemd as default now, debian salsa 4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script, taking advantage of systemctl directly if systemd is active by still keeping Sysv init script as fallback only. While there is no 'real' impact, I think it make total sense for a systemd Xenial system, to use the systemctl approach for log rotation It has been brought to my attention by a Ubuntu user that: "Xenial logrotate is not able to perform full log rotation on a LXC container without the 'sys_ptrace' capability[1] using the Sysv approach, invoke-rc.d just fails" I have created a test pkg for this user, and the same user was able to conclude that it was working as expected with the systemd approach (systemctl) when sys_ptrace is disable inside the container. [1] - lxc config set raw.lxc lxc.cap.drop=sys_ptrace [TEST CASE] == [1] - On a Xenial active systemd system: == Determine the script pick the right decision (systemd approach). # bash -vx /usr/lib/rsyslog/rsyslog-rotate Run logrotate which contains 'include /etc/logrotate.d', thus will use the rsyslog log rotation information, now using '/usr/lib/rsyslog/rsyslog-rotate' helper. # logrotate -vdf /etc/logrotate.conf Check if logs rotation happened in /var/log. # ls -altr /var/log == [2] - On a Xenial active upstart system: == Determine the script pick the right decision (non-systemd approach). # bash -vx /usr/lib/rsyslog/rsyslog-rotate Run logrotate which contains 'include /etc/logrotate.d', thus will use the rsyslog log rotation information, now using '/usr/lib/rsyslog/rsyslog-rotate' helper. # logrotate -vdf /etc/logrotate.conf Check if logs rotation happened in /var/log. # ls -altr /var/log [POTENTIAL REGRESSION * None, this commit introduced a new shell script (rsyslog-rotate) which uses systemctl directly if systemd is active (default in Xenial) but keeps the original Sysv init script as fallback only. Meaning no behaviour change for users who decided not to use systemd on their Xenial system. * I don't see any reported bug about this new helper for Bionic/Cosmic which has it since their released. /usr/lib/rsyslog/rsyslog-rotate: 1) Check if existence of systemd, if yes: systemctl kill -s HUP rsyslog.service 2) Check if existence of systemd, if no: invoke-rc.d rsyslog rotate > /dev/null [OTHER INFO] * Salsa rsyslog repository: https://salsa.debian.org/debian/rsyslog/commit/4a49edf26d405726041bee12a42d6f064145c87e * First introduced: git describe --contains 4a49edf26d405726041bee12a42d6f064145c87e debian/8.27.0-4~1 * rmadison: => rsyslog | 8.16.0-1ubuntu3 | xenial rsyslog | 8.32.0-1ubuntu4 | bionic rsyslog | 8.32.0-1ubuntu5 | cosmic rsyslog | 8.32.0-1ubuntu7 | disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1821582/+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 1817287] Re: SRU xdg-desktop-portal-gtk 1.0.2
This bug was fixed in the package xdg-desktop-portal-gtk - 1.0.2-0ubuntu0.0 --- xdg-desktop-portal-gtk (1.0.2-0ubuntu0.0) xenial-proposed; urgency=medium * New upstream release 1.0.2 (LP: #1817287) -- Ken VanDine Mon, 10 Dec 2018 16:23:19 -0500 ** Changed in: xdg-desktop-portal-gtk (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1817287 Title: SRU xdg-desktop-portal-gtk 1.0.2 Status in xdg-desktop-portal-gtk package in Ubuntu: Fix Released Status in xdg-desktop-portal-gtk source package in Xenial: Fix Released Status in xdg-desktop-portal-gtk source package in Bionic: Fix Committed Bug description: [Impact] * To improve the snap experience on the desktop we have been working with xdg-desktop-portal-gtk upstream to enable snap support. Portals will greatly improve the snap experience. Full snap support landed in xdg-desktop-portal-gtk 1.0. We're SRU'ing 1.0.2 as it includes bug fixes. * There is now an approved MIR for xdg-desktop-portal-gtk for bionic and xenial, so these will be promoted to main as well. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 Also requires xdg-desktop-portal https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285 [Test Case] * This can be tested by installing the portal-test snap from the edge channel and xdg-desktop-portal also from proposed. Verify the file selection lets you select a file and open local opens test.txt in a text editor of your choice. [Regression Potential] * No regression potential. This package was not seeded by default. It could only have been used by flatpak, however the version in bionic had limited functionality. The package was never available in xenial. [Other Info] * xdg-desktop-portal-gtk is in main and seeded by ubuntu-desktop in cosmic and disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1817287/+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 1818880] Re: Deadlock when detaching network interface
The Stein cloud archive has qemu 1:3.1+dfsg-2ubuntu3~cloud0 which corresponds to the current version in disco, so I'm marking this as fix released for Stein. ** Changed in: cloud-archive/stein Status: Triaged => 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/1818880 Title: Deadlock when detaching network interface Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive ocata series: Triaged Status in Ubuntu Cloud Archive pike series: Triaged Status in Ubuntu Cloud Archive queens series: Triaged Status in Ubuntu Cloud Archive rocky series: Won't Fix Status in Ubuntu Cloud Archive stein series: Fix Released Status in qemu package in Ubuntu: Fix Released Status in qemu source package in Xenial: Fix Released Status in qemu source package in Bionic: Fix Released Status in qemu source package in Cosmic: Fix Released Status in qemu source package in Disco: Fix Released Bug description: [Impact] Qemu guests hang indefinitely [Description] When running a Qemu guest with VirtIO network interfaces, detaching an interface that's currently being used can result in a deadlock. The guest instance will hang and become unresponsive to commands, and the only option is to kill -9 the instance. The reason for this is a dealock between a monitor and an RCU thread, which will fight over the BQL (qemu_global_mutex) and the critical RCU section locks. The monitor thread will acquire the BQL for detaching the network interface, and fire up a helper thread to deal with detaching the network adapter. That new thread needs to wait on the RCU thread to complete the deletion, but the RCU thread wants the BQL to commit its transactions. This bug is already fixed upstream (73c6e4013b4c rcu: completely disable pthread_atfork callbacks as soon as possible) and included for other series (see below), so we don't need to backport it to Bionic onwards. Upstream commit: https://git.qemu.org/?p=qemu.git;a=commit;h=73c6e4013b4c $ git describe --contains 73c6e4013b4c v2.10.0-rc2~1^2~8 $ rmadison qemu ===> qemu | 1:2.5+dfsg-5ubuntu10.34 | xenial-updates/universe | amd64, ... qemu | 1:2.11+dfsg-1ubuntu7| bionic/universe | amd64, ... qemu | 1:2.12+dfsg-3ubuntu8| cosmic/universe | amd64, ... qemu | 1:3.1+dfsg-2ubuntu2 | disco/universe| amd64, ... [Test Case] Being a racing condition, this is a tricky bug to reproduce consistently. We've had reports of users running into this with OpenStack deployments and Windows Server guests, and the scenario is usually like this: 1) Deploy a 16vCPU Windows Server 2012 R2 guest with a virtio network interface 2) Stress the network interface with e.g. Windows HLK test suite or similar 3) Repeatedly attach/detach the network adapter that's in use It usually takes more than ~4000 attach/detach cycles to trigger the bug. [Regression Potential] Regressions for this might arise from the fact that the fix changes RCU lock code. Since this patch has been upstream and in other series for a while, it's unlikely that it would regressions in RCU code specifically. Other code that makes use of the RCU locks (MMIO and some monitor events) will be thoroughly tested for any regressions with use-case scenarios and scripted runs. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+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 1818880] Re: Deadlock when detaching network interface
I've just accepted qemu version 1:2.11+dfsg-1ubuntu7.12~cloud0 into queens-proposed however the changelog doesn't mention (LP: #1818880) anywhere. Seeing that bionic is marked as fix released I assume queens can be marked as fix released. ** Changed in: cloud-archive/queens Status: Triaged => 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/1818880 Title: Deadlock when detaching network interface Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive mitaka series: New Status in Ubuntu Cloud Archive ocata series: Triaged Status in Ubuntu Cloud Archive pike series: Triaged Status in Ubuntu Cloud Archive queens series: Fix Released Status in Ubuntu Cloud Archive rocky series: Won't Fix Status in Ubuntu Cloud Archive stein series: Fix Released Status in qemu package in Ubuntu: Fix Released Status in qemu source package in Xenial: Fix Released Status in qemu source package in Bionic: Fix Released Status in qemu source package in Cosmic: Fix Released Status in qemu source package in Disco: Fix Released Bug description: [Impact] Qemu guests hang indefinitely [Description] When running a Qemu guest with VirtIO network interfaces, detaching an interface that's currently being used can result in a deadlock. The guest instance will hang and become unresponsive to commands, and the only option is to kill -9 the instance. The reason for this is a dealock between a monitor and an RCU thread, which will fight over the BQL (qemu_global_mutex) and the critical RCU section locks. The monitor thread will acquire the BQL for detaching the network interface, and fire up a helper thread to deal with detaching the network adapter. That new thread needs to wait on the RCU thread to complete the deletion, but the RCU thread wants the BQL to commit its transactions. This bug is already fixed upstream (73c6e4013b4c rcu: completely disable pthread_atfork callbacks as soon as possible) and included for other series (see below), so we don't need to backport it to Bionic onwards. Upstream commit: https://git.qemu.org/?p=qemu.git;a=commit;h=73c6e4013b4c $ git describe --contains 73c6e4013b4c v2.10.0-rc2~1^2~8 $ rmadison qemu ===> qemu | 1:2.5+dfsg-5ubuntu10.34 | xenial-updates/universe | amd64, ... qemu | 1:2.11+dfsg-1ubuntu7| bionic/universe | amd64, ... qemu | 1:2.12+dfsg-3ubuntu8| cosmic/universe | amd64, ... qemu | 1:3.1+dfsg-2ubuntu2 | disco/universe| amd64, ... [Test Case] Being a racing condition, this is a tricky bug to reproduce consistently. We've had reports of users running into this with OpenStack deployments and Windows Server guests, and the scenario is usually like this: 1) Deploy a 16vCPU Windows Server 2012 R2 guest with a virtio network interface 2) Stress the network interface with e.g. Windows HLK test suite or similar 3) Repeatedly attach/detach the network adapter that's in use It usually takes more than ~4000 attach/detach cycles to trigger the bug. [Regression Potential] Regressions for this might arise from the fact that the fix changes RCU lock code. Since this patch has been upstream and in other series for a while, it's unlikely that it would regressions in RCU code specifically. Other code that makes use of the RCU locks (MMIO and some monitor events) will be thoroughly tested for any regressions with use-case scenarios and scripted runs. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+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 1818880] Re: Deadlock when detaching network interface
** Also affects: cloud-archive/mitaka Importance: Undecided Status: New -- 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/1818880 Title: Deadlock when detaching network interface Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive mitaka series: New Status in Ubuntu Cloud Archive ocata series: Triaged Status in Ubuntu Cloud Archive pike series: Triaged Status in Ubuntu Cloud Archive queens series: Fix Released Status in Ubuntu Cloud Archive rocky series: Won't Fix Status in Ubuntu Cloud Archive stein series: Fix Released Status in qemu package in Ubuntu: Fix Released Status in qemu source package in Xenial: Fix Released Status in qemu source package in Bionic: Fix Released Status in qemu source package in Cosmic: Fix Released Status in qemu source package in Disco: Fix Released Bug description: [Impact] Qemu guests hang indefinitely [Description] When running a Qemu guest with VirtIO network interfaces, detaching an interface that's currently being used can result in a deadlock. The guest instance will hang and become unresponsive to commands, and the only option is to kill -9 the instance. The reason for this is a dealock between a monitor and an RCU thread, which will fight over the BQL (qemu_global_mutex) and the critical RCU section locks. The monitor thread will acquire the BQL for detaching the network interface, and fire up a helper thread to deal with detaching the network adapter. That new thread needs to wait on the RCU thread to complete the deletion, but the RCU thread wants the BQL to commit its transactions. This bug is already fixed upstream (73c6e4013b4c rcu: completely disable pthread_atfork callbacks as soon as possible) and included for other series (see below), so we don't need to backport it to Bionic onwards. Upstream commit: https://git.qemu.org/?p=qemu.git;a=commit;h=73c6e4013b4c $ git describe --contains 73c6e4013b4c v2.10.0-rc2~1^2~8 $ rmadison qemu ===> qemu | 1:2.5+dfsg-5ubuntu10.34 | xenial-updates/universe | amd64, ... qemu | 1:2.11+dfsg-1ubuntu7| bionic/universe | amd64, ... qemu | 1:2.12+dfsg-3ubuntu8| cosmic/universe | amd64, ... qemu | 1:3.1+dfsg-2ubuntu2 | disco/universe| amd64, ... [Test Case] Being a racing condition, this is a tricky bug to reproduce consistently. We've had reports of users running into this with OpenStack deployments and Windows Server guests, and the scenario is usually like this: 1) Deploy a 16vCPU Windows Server 2012 R2 guest with a virtio network interface 2) Stress the network interface with e.g. Windows HLK test suite or similar 3) Repeatedly attach/detach the network adapter that's in use It usually takes more than ~4000 attach/detach cycles to trigger the bug. [Regression Potential] Regressions for this might arise from the fact that the fix changes RCU lock code. Since this patch has been upstream and in other series for a while, it's unlikely that it would regressions in RCU code specifically. Other code that makes use of the RCU locks (MMIO and some monitor events) will be thoroughly tested for any regressions with use-case scenarios and scripted runs. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+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 1820419] Re: linux-generic should depend on linux-base >=4.1
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1820419 Title: linux-generic should depend on linux-base >=4.1 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: [ SRU Justification ] == Impact == Due to unversioned dependencies to linux-base, minimal installations will not pull in the latest requirements. == Fix == Depend on linux-base (>= 4.5ubuntu1~16.04.1) specifically == Testcase == See below (but also can be checked on dependencies). == Risk of Regression == Low, no actual code change. --- Hi, we run a automated pipeline which automatically installs ubuntu 16.04 by pxe / netinstall. This pipeline stopped working tonight, so I did some research. Looks like linux-generic depends on linux-base, but requires a tool/script which was added in 4.1 (linux-update-symlinks). packages.ubuntu.com only shows linux-base 4.5, but if I take a look into the packages.gz of /ubuntu/ there is still a 4.0 available. So somehow(tm) it seems netinstall is installing the 4.0 version of linux-base instead of the required 4.5 (4.1+). In my opinion if a pkg needs a feature which is only available in a newer version of a pkg, this pkg should be a depend, so linux-generic should depend on linux-base >= 4.1 instead of just depend on linux- base. I workarounded the problem by installing the hwe-kernel which has a correct dependency on linux-base 4.5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820419/+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 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes
** Also affects: apport (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1658188 Title: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport- gtk@597:run_argv:run_crashes Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Released Status in apport source package in Bionic: New Status in apport source package in Cosmic: New Bug description: [Test Case] Check Error Tracker bucket and make sure version from -proposed doesn't show up there. Given that this happens a whole bunch we should know pretty quick if its fixed. [Regression Potential] The test being modified is designed to not report crashes that happen during logout. It's possible that some reports don't have a Date in them but in that case we couldn't compare the logind_session information to the Date anyway so those crashes would have been reported anyway. Regardless, the potential is that we'll have some more crashes reported about things crashing on logout which is better than the hundreds of crashes we get like this one. The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.3-0ubuntu8.2, the problem page at https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1658188/+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 1822692] [NEW] Please ship the ib_uverbs driver module in the main modules package
Public bug reported: Please include the module drivers/infiniband/core/ib_uverbs.ko and its companion ib_umad.ko in the main linux-modules-*-aws package, in order to support upcoming Amazon features. +++ b/debian.aws/control.d/aws.inclusion-list +drivers/infiniband/core/ib_umad.ko +drivers/infiniband/core/ib_uverbs.ko ** Affects: linux-aws (Ubuntu) Importance: High Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux-aws (Ubuntu Xenial) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux-aws (Ubuntu Bionic) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux-aws (Ubuntu Cosmic) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux-aws (Ubuntu Disco) Importance: High Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Disco) Importance: High Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Cosmic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1822692 Title: Please ship the ib_uverbs driver module in the main modules package Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Xenial: In Progress Status in linux-aws source package in Bionic: In Progress Status in linux-aws source package in Cosmic: In Progress Status in linux-aws source package in Disco: In Progress Bug description: Please include the module drivers/infiniband/core/ib_uverbs.ko and its companion ib_umad.ko in the main linux-modules-*-aws package, in order to support upcoming Amazon features. +++ b/debian.aws/control.d/aws.inclusion-list +drivers/infiniband/core/ib_umad.ko +drivers/infiniband/core/ib_uverbs.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1822692/+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 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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/1821724 Title: linux: 4.4.0-145.171 -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: Fix Released 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: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed 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 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Signoff phase-changed: Monday, 01. April 2019 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821724/+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
