[Group.of.nepali.translators] [Bug 1562333] Re: iptstate assert failure: *** Error in `iptstate': munmap_chunk(): invalid pointer: 0x000000000193c990 ***

[Nish Aravamudan]

** Also affects: iptstate (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: iptstate (Ubuntu)
   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/1562333

Title:
  iptstate assert failure: *** Error in `iptstate': munmap_chunk():
  invalid pointer: 0x0193c990 ***

Status in iptstate package in Ubuntu:
  Fix Released
Status in iptstate source package in Xenial:
  New

Bug description:
  This is an automatic bug report.

  Steps to reproduce:

  just install and run.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: iptstate 2.2.5-1build1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AssertionMessage: *** Error in `iptstate': munmap_chunk(): invalid pointer: 
0x0193c990 ***
  Date: Sat Mar 26 22:30:25 2016
  ExecutablePath: /usr/sbin/iptstate
  InstallationDate: Installed on 2015-08-05 (233 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: iptstate
  ProcEnviron:
   TERM=screen
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
  Signal: 6
  SourcePackage: iptstate
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f479d8c2fb8 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=0x0, ptr=, str=0x7f479d8c2fe0 
"munmap_chunk(): invalid pointer", action=) at malloc.c:5007
   munmap_chunk (p=) at malloc.c:2843
   __GI___libc_free (mem=) at malloc.c:2964
   ?? ()
  Title: iptstate assert failure: *** Error in `iptstate': munmap_chunk(): 
invalid pointer: 0x0193c990 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptstate/+bug/1562333/+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 1177432] Re: [SRU] cloud-init archive template should match Ubuntu Server

[Joshua Powers]

** Changed in: cloud-init
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1177432

Title:
  [SRU] cloud-init archive template should match Ubuntu Server

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Precise:
  Fix Released
Status in cloud-init source package in Trusty:
  Fix Released
Status in cloud-init source package in Vivid:
  Fix Released
Status in cloud-init source package in Wily:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification]
  Ubuntu Cloud Images are inconsistent with desktop and bare-metal server 
installations since backports, restricted and multiverse are not enabled. This 
is effected via cloud-init that uses a template to select an in-cloud archive.

  [FIX] Make the cloud-init template match that of Ubuntu-server.

  [REGRESION] The potential for regression is low. However, all users
  will experience slower fetch times on apt-get updates especially on
  slower or high latency networks.

  [TEST]
  1. Build image from -proposed
  2. Boot up image
  3. Confirm that "sudo apt-get update" pulls in backports, restricted and 
multiverse.

  Backports are currently not enabled in the cloud-init template. This
  is needed in order to get the backport kernels on cloud images.

  Related bugs:
   * bug 997371:  Create command to add "multiverse" and "-backports" to apt 
sources
   * bug 1513529:  cloud image built-in /etc/apt/sources.list needs updating

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1177432/+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 1627656] Re: missing alembic migrations due to use of git based workflows

[Ricardo Noriega]

Patch released for networking-l2gw: https://review.openstack.org/#/c/376406/
I'm setting this bug as: Fix released

** Changed in: networking-l2gw
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1627656

Title:
  missing alembic migrations due to use of git based workflows

Status in networking-l2gw:
  Fix Released
Status in networking-odl:
  Fix Released
Status in networking-sfc:
  Fix Released
Status in tap-as-a-service:
  Fix Released
Status in networking-l2gw package in Ubuntu:
  Fix Released
Status in networking-odl package in Ubuntu:
  Fix Released
Status in neutron-taas package in Ubuntu:
  Fix Released
Status in networking-l2gw source package in Xenial:
  New
Status in networking-odl source package in Xenial:
  Triaged
Status in neutron-taas source package in Xenial:
  Invalid
Status in networking-l2gw source package in Yakkety:
  Fix Released
Status in networking-odl source package in Yakkety:
  Fix Released
Status in neutron-taas source package in Yakkety:
  Fix Released

Bug description:
  Various openstack related packages are missing required neutron
  database migrations due to the direct use of a git based workflow of
  merging upstream tags and generating orig.tar.xz directly from the git
  tree for packaging.  This is *not* the same process as generated a
  sdist tarball, and as a result, files that need to reside in the
  python module get missed - this includes alembic migrations.

  Known impacts:

networking-odl
vmware-nsx (bug 1574610)

  A simple fix is to switch to using the upstream published release
  artefacts, rather than directly using git.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-l2gw/+bug/1627656/+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 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM

[Brian Murray]

** Changed in: sudo (Ubuntu Yakkety)
   Status: Fix Committed => 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/1686803

Title:
  sudo returns exit code 0 if child is killed with SIGTERM

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Released
Status in sudo source package in Yakkety:
  Won't Fix
Status in sudo source package in Zesty:
  Fix Released
Status in sudo source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * sudo returns exit code 0 if child is killed with signals other than SIGINT
   * This can break scripts assuming successful execution of the command ran by
 sudo

  [Test Case]

   * Open two separate shells
 1. In shell 1. run:
   ubuntu@tough-calf:~$ sudo sleep 300; echo $?
 2. In shell 2. run:
   root@tough-calf:~# killall -TERM sleep
 3. In broken versions shell 1. shows this:
   ubuntu@tough-calf:~$ sudo sleep 300; echo $?
   0

 4. Install fixed version
 5. Execute steps 1. and 2.
 6. In fixed version shell 1. shows this:
   ubuntu@tough-calf:~$ sudo sleep 300; echo $?
   Terminated
   143

  [Regression Potential]

   *  sudo may exit with a different status than expected

  [Other Info]

  original bug description:

  Please backport upstream sudo changeset 10917:50b988d0c97f "The fix
  for Bug #722 contained a typo/thinko that resulted in the" to xenial,
  yakkety, and zesty versions of sudo.

  This will fix a regression documented by this upstream bug report:
  https://bugzilla.sudo.ws/show_bug.cgi?id=784

  sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is
  running is killed by a signal, sudo will" introduced a regression
  where the exit status is always 0 when a command is killed by a signal
  other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1

  This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f
  "The fix for Bug #722 contained a typo/thinko that resulted in the".
  https://www.sudo.ws/repos/sudo/rev/50b988d0c97f

  trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo
  based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty
  sudo based off 1.8.19 need the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sudo/+bug/1686803/+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 1684090] Re: Autopkgtest is failing on most architectures, ppc64el passes

[Steve Langasek]

Reopening this because although the autopkgtests have managed to pass,
the test is still racy and we aren't correctly capturing the error
message; we were grepping for 'loop deleted:' but the actual message (as
shown in the bug log) is 'loop deleted : /dev/loop0'.

Fix is inbound.

** Changed in: livecd-rootfs (Ubuntu Zesty)
   Status: Fix Released => In Progress

** Also affects: livecd-rootfs (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/1684090

Title:
  Autopkgtest is failing on most architectures, ppc64el passes

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  New
Status in livecd-rootfs source package in Yakkety:
  Invalid
Status in livecd-rootfs source package in Zesty:
  In Progress

Bug description:
  http://autopkgtest.ubuntu.com/packages/livecd-rootfs

  Log part from amd64:
  ...
  + udevadm settle
  + '[' -n /dev/mapper/loop0p1 -a -b /dev/mapper/loop0p1 ']'
  + '[' -e /etc/mtab ']'
  + apt-get -qqy install zerofree
  + e2fsck -y -E discard /dev/mapper/loop0p1
  e2fsck 1.43.4 (31-Jan-2017)
  cloudimg-rootfs: clean, 63584/274176 files, 284703/548091 blocks
  + zerofree /dev/mapper/loop0p1
  + rmdir mountpoint
  + clean_loops
  + '[' -n binary/boot/disk-uefi.ext4 ']'
  + kpartx -v -d binary/boot/disk-uefi.ext4
  device-mapper: remove ioctl on loop0p1 failed: Device or resource busy
  del devmap : loop0p15
  del devmap : loop0p14
  loop deleted : /dev/loop0
  + clean_loops
  + '[' -n binary/boot/disk-uefi.ext4 ']'
  + kpartx -v -d binary/boot/disk-uefi.ext4
  device-mapper: remove ioctl on loop0p1 failed: Device or resource busy
  loop deleted : /dev/loop0
  E: config/hooks/033-disk-image-uefi.binary failed (exit non-zero). You should 
check for errors.
  P: Begin unmounting filesystems...
  ...

  [Impact]

  * Having a working autopkgtest simplifies testing of future changes including
    package SRUs thus backporting both the new autopkgtest test and the fix
    making it succeed on every architecture seems to be beneficial.
    (SRU-ing the test was suggested here: 
https://code.launchpad.net/~rbalint/livecd-rootfs/livecd-rootfs-autopkgtest/+merge/322322/comments/845316
 )

  [Test Case]

  * Run the autopkgtest test itself. It also covers the parts needed to be
    changed for making the test pass, including the part changed in this bug.

  [Regression Potential]

  * Livecd-rootfs scripts had to be changed to make the autopkgtest test pass.
    The changes could make livecd-rootfs generate broken/invalid images, but
    this is highly unlikely because changes with regressions would also break
    the test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1684090/+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 1715656] Re: linux-gke: 4.4.0-1030.30 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1715651
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Monday, 11. September 2017 18:32 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1715651
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Monday, 11. September 2017 18:32 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

-- 
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/1715656

Title:
  linux-gke: 4.4.0-1030.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gke package in Ubuntu:
  Invalid
Status in linux-gke source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1715651
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1715656/+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 1673564] Re: ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on

[Raghuram Kota]

Backporting to the Xenial (Ubntu 16.04) kernel isn't feasible. 16.04
users are requested to use the hwe-z kernel as noted in the following
Wiki page :
https://wiki.ubuntu.com/HardwareSupport/Machines/Servers/Cavium/ThunderXCRB1S

** Changed in: linux (Ubuntu Xenial)
   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/1673564

Title:
  ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with
  vhost=on

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  VMs can cause interrupts to be disabled on the host CPU, resulting in hangs.

  [Test Case]
  Download the attached vm-start-stop.tar.gz and unpack it. Run the start.sh 
script within. This will start 30 parallel loops where a VM is defined, 
started, allowed 60s to run, then destroyed. If the bug exists, within 10 
minutes you'll see qemu processes start to hang, along with soft lockup 
messages on the console. Note that this script is compatible with xenial 
libvirt syntax - it likely needs tweaks to run in newer Ubuntu releases, just 
due to QEMU/libvirt changes.

  [Regression Risk]
  The code changes are restricted to ARM - but there are a lot of them. While 
we've attempted to stress test the proposed changes on both impacted and 
non-impacted (non-ThunderX) systems, it is possible that there are issues that 
our test isn't finding, which would likely surface as KVM guest crashes/hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673564/+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 1713471] Re: linux-hwe: 4.10.0-34.38~16.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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/1713471

Title:
  linux-hwe: 4.10.0-34.38~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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713470
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713471/+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 1716424] Please test proposed package

[Steve Langasek]

Hello Mathieu, or anyone else affected,

Accepted grub2 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.13 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: grub2-signed (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: grub2-signed (Ubuntu Artful)
   Status: New => Fix Released

** Changed in: grub2-signed (Ubuntu Xenial)
   Status: New => Fix Committed

-- 
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/1716424

Title:
  correctly parse PMEM memory ranges to pass it to the kernel

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in grub2 source package in Zesty:
  Triaged
Status in grub2-signed source package in Zesty:
  New
Status in grub2 source package in Artful:
  Fix Released
Status in grub2-signed source package in Artful:
  Fix Released

Bug description:
  [Impact]
  If trying to boot a system with PMEM:

  "Unknown memory type 14, considering reserved"

  The system will then not have access to EFIPresistentMemory ranges,
  because grub could not hand them over to the kernel to use. The
  resulting system would be missing a /dev/pmemN device.

  Grub requires 4 cherry-picked commits:

  - debian/patches/git_pmem_really_mark_mem_reserved_3d2c8048.patch
  - debian/patches/git_pmem_translate_persistent_type_76ce1de7.patch
  - debian/patches/git_pmem_mmap_handle_pmem_c79c59f1.patch
  - debian/patches/git_pmem_efiemu_handle_pmem_ae3b83a4.patch

  
  [Test case]
  - Boot PMEM-enabled system with updated grub

  [Regression Potential]
  This changes handling of memory ranges in grub, and may lead to incorrectly 
passing memory to the kernel, or otherwise allowing allocation of memory within 
reserved ranges. This would typically lead to a failure to boot the kernel, or 
missing memory-based devices (such a missing /dev/pmem0).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1716424/+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 1716424] [NEW] correctly parse PMEM memory ranges to pass it to the kernel

[Mathieu Trudel-Lapierre]

Public bug reported:

[Impact]
If trying to boot a system with PMEM:

"Unknown memory type 14, considering reserved"

The system will then not have access to EFIPresistentMemory ranges,
because grub could not hand them over to the kernel to use. The
resulting system would be missing a /dev/pmemN device.

Grub requires 4 cherry-picked commits:

- debian/patches/git_pmem_really_mark_mem_reserved_3d2c8048.patch
- debian/patches/git_pmem_translate_persistent_type_76ce1de7.patch
- debian/patches/git_pmem_mmap_handle_pmem_c79c59f1.patch
- debian/patches/git_pmem_efiemu_handle_pmem_ae3b83a4.patch


[Test case]
- Boot PMEM-enabled system with updated grub

[Regression Potential]
This changes handling of memory ranges in grub, and may lead to incorrectly 
passing memory to the kernel, or otherwise allowing allocation of memory within 
reserved ranges. This would typically lead to a failure to boot the kernel, or 
missing memory-based devices (such a missing /dev/pmem0).

** Affects: grub2 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: grub2 (Ubuntu Xenial)
 Importance: Critical
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: In Progress

** Affects: grub2 (Ubuntu Zesty)
 Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: Triaged

** Affects: grub2 (Ubuntu Artful)
 Importance: Undecided
 Status: Fix Released

** Also affects: grub2 (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: grub2 (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: grub2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: grub2 (Ubuntu Artful)
   Status: New => Fix Released

** Changed in: grub2 (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: grub2 (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: grub2 (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: grub2 (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: grub2 (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: grub2 (Ubuntu Zesty)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: grub2 (Ubuntu Xenial)
   Status: Triaged => 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/1716424

Title:
  correctly parse PMEM memory ranges to pass it to the kernel

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2 source package in Zesty:
  Triaged
Status in grub2 source package in Artful:
  Fix Released

Bug description:
  [Impact]
  If trying to boot a system with PMEM:

  "Unknown memory type 14, considering reserved"

  The system will then not have access to EFIPresistentMemory ranges,
  because grub could not hand them over to the kernel to use. The
  resulting system would be missing a /dev/pmemN device.

  Grub requires 4 cherry-picked commits:

  - debian/patches/git_pmem_really_mark_mem_reserved_3d2c8048.patch
  - debian/patches/git_pmem_translate_persistent_type_76ce1de7.patch
  - debian/patches/git_pmem_mmap_handle_pmem_c79c59f1.patch
  - debian/patches/git_pmem_efiemu_handle_pmem_ae3b83a4.patch

  
  [Test case]
  - Boot PMEM-enabled system with updated grub

  [Regression Potential]
  This changes handling of memory ranges in grub, and may lead to incorrectly 
passing memory to the kernel, or otherwise allowing allocation of memory within 
reserved ranges. This would typically lead to a failure to boot the kernel, or 
missing memory-based devices (such a missing /dev/pmem0).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1716424/+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 1715659] Re: linux-kvm: 4.4.0-1006.11 -proposed tracker

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1715659

Title:
  linux-kvm: 4.4.0-1006.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1715651
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1715659/+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 1712481] Re: HID: multitouch: Support ALPS PTP Stick and Touchpad devices

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.12.0-13.14

---
linux (4.12.0-13.14) artful; urgency=low

  * linux: 4.12.0-13.14 -proposed tracker (LP: #1714687)

  * vhost guest network randomly drops under stress (kvm) (LP: #1711251)
- Revert "vhost: cache used event for better performance"

  * EDAC sbridge: Failed to register device with error -22. (LP: #1714112)
- [Config] CONFIG_EDAC_GHES=n

  * Artful update to v4.12.10 stable release (LP: #1714525)
- sparc64: remove unnecessary log message
- bonding: require speed/duplex only for 802.3ad, alb and tlb
- bonding: ratelimit failed speed/duplex update warning
- af_key: do not use GFP_KERNEL in atomic contexts
- dccp: purge write queue in dccp_destroy_sock()
- dccp: defer ccid_hc_tx_delete() at dismantle time
- ipv4: fix NULL dereference in free_fib_info_rcu()
- net_sched/sfq: update hierarchical backlog when drop packet
- net_sched: remove warning from qdisc_hash_add
- bpf: fix bpf_trace_printk on 32 bit archs
- net: igmp: Use ingress interface rather than vrf device
- openvswitch: fix skb_panic due to the incorrect actions attrlen
- ptr_ring: use kmalloc_array()
- ipv4: better IP_MAX_MTU enforcement
- nfp: fix infinite loop on umapping cleanup
- tun: handle register_netdevice() failures properly
- sctp: fully initialize the IPv6 address in sctp_v6_to_addr()
- tipc: fix use-after-free
- ipv6: reset fn->rr_ptr when replacing route
- ipv6: repair fib6 tree in failure case
- tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP
- net/mlx4_core: Enable 4K UAR if SRIOV module parameter is not enabled
- irda: do not leak initialized list.dev to userspace
- net: sched: fix NULL pointer dereference when action calls some targets
- net_sched: fix order of queue length updates in qdisc_replace()
- bpf, verifier: add additional patterns to evaluate_reg_imm_alu
- bpf: fix mixed signed/unsigned derived min/max value bounds
- bpf/verifier: fix min/max handling in BPF_SUB
- Input: trackpoint - add new trackpoint firmware ID
- Input: elan_i2c - add ELAN0602 ACPI ID to support Lenovo Yoga310
- Input: ALPS - fix two-finger scroll breakage in right side on ALPS 
touchpad
- KVM: s390: sthyi: fix sthyi inline assembly
- KVM: s390: sthyi: fix specification exception detection
- KVM: x86: simplify handling of PKRU
- KVM, pkeys: do not use PKRU value in vcpu->arch.guest_fpu.state
- KVM: x86: block guest protection keys unless the host has them enabled
- ALSA: usb-audio: Add delay quirk for H650e/Jabra 550a USB headsets
- ALSA: core: Fix unexpected error at replacing user TLV
- ALSA: hda - Add stereo mic quirk for Lenovo G50-70 (17aa:3978)
- ALSA: firewire: fix NULL pointer dereference when releasing uninitialized
  data of iso-resource
- ALSA: firewire-motu: destroy stream data surely at failure of card
  initialization
- ARCv2: SLC: Make sure busy bit is set properly for region ops
- ARCv2: PAE40: Explicitly set MSB counterpart of SLC region ops addresses
- ARCv2: PAE40: set MSB even if !CONFIG_ARC_HAS_PAE40 but PAE exists in SoC
- PM/hibernate: touch NMI watchdog when creating snapshot
- mm, shmem: fix handling /sys/kernel/mm/transparent_hugepage/shmem_enabled
- dax: fix deadlock due to misaligned PMD faults
- i2c: designware: Fix system suspend
- mm/madvise.c: fix freeing of locked page with MADV_FREE
- fork: fix incorrect fput of ->exe_file causing use-after-free
- mm/memblock.c: reversed logic in memblock_discard()
- arm64: fpsimd: Prevent registers leaking across exec
- drm: Fix framebuffer leak
- drm: Release driver tracking before making the object available again
- drm/sun4i: Implement drm_driver lastclose to restore fbdev console
- drm/atomic: Handle -EDEADLK with out-fences correctly
- drm/atomic: If the atomic check fails, return its value first
- drm/i915/vbt: ignore extraneous child devices for a port
- drm/i915/gvt: Fix the kernel null pointer error
- Revert "drm/amdgpu: fix vblank_time when displays are off"
- ACPI: device property: Fix node lookup in 
acpi_graph_get_child_prop_value()
- tracing: Call clear_boot_tracer() at lateinit_sync
- tracing: Missing error code in tracer_alloc_buffers()
- tracing: Fix kmemleak in tracing_map_array_free()
- tracing: Fix freeing of filter in create_filter() when set_str is false
- RDMA/uverbs: Initialize cq_context appropriately
- kbuild: linker script do not match C names unless
  LD_DEAD_CODE_DATA_ELIMINATION is configured
- cifs: Fix df output for users with quota limits
- cifs: return ENAMETOOLONG for overlong names in cifs_open()/cifs_lookup()
- nfsd: Limit end of page list when decoding NFSv4 WRITE
- ring-buffer: Have ring_buffer_alloc_read_page() return error on offline 
CPU
- virtio_pci: fix 

[Group.of.nepali.translators] [Bug 1712024] Re: igb: Support using Broadcom 54616 as PHY

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.12.0-13.14

---
linux (4.12.0-13.14) artful; urgency=low

  * linux: 4.12.0-13.14 -proposed tracker (LP: #1714687)

  * vhost guest network randomly drops under stress (kvm) (LP: #1711251)
- Revert "vhost: cache used event for better performance"

  * EDAC sbridge: Failed to register device with error -22. (LP: #1714112)
- [Config] CONFIG_EDAC_GHES=n

  * Artful update to v4.12.10 stable release (LP: #1714525)
- sparc64: remove unnecessary log message
- bonding: require speed/duplex only for 802.3ad, alb and tlb
- bonding: ratelimit failed speed/duplex update warning
- af_key: do not use GFP_KERNEL in atomic contexts
- dccp: purge write queue in dccp_destroy_sock()
- dccp: defer ccid_hc_tx_delete() at dismantle time
- ipv4: fix NULL dereference in free_fib_info_rcu()
- net_sched/sfq: update hierarchical backlog when drop packet
- net_sched: remove warning from qdisc_hash_add
- bpf: fix bpf_trace_printk on 32 bit archs
- net: igmp: Use ingress interface rather than vrf device
- openvswitch: fix skb_panic due to the incorrect actions attrlen
- ptr_ring: use kmalloc_array()
- ipv4: better IP_MAX_MTU enforcement
- nfp: fix infinite loop on umapping cleanup
- tun: handle register_netdevice() failures properly
- sctp: fully initialize the IPv6 address in sctp_v6_to_addr()
- tipc: fix use-after-free
- ipv6: reset fn->rr_ptr when replacing route
- ipv6: repair fib6 tree in failure case
- tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP
- net/mlx4_core: Enable 4K UAR if SRIOV module parameter is not enabled
- irda: do not leak initialized list.dev to userspace
- net: sched: fix NULL pointer dereference when action calls some targets
- net_sched: fix order of queue length updates in qdisc_replace()
- bpf, verifier: add additional patterns to evaluate_reg_imm_alu
- bpf: fix mixed signed/unsigned derived min/max value bounds
- bpf/verifier: fix min/max handling in BPF_SUB
- Input: trackpoint - add new trackpoint firmware ID
- Input: elan_i2c - add ELAN0602 ACPI ID to support Lenovo Yoga310
- Input: ALPS - fix two-finger scroll breakage in right side on ALPS 
touchpad
- KVM: s390: sthyi: fix sthyi inline assembly
- KVM: s390: sthyi: fix specification exception detection
- KVM: x86: simplify handling of PKRU
- KVM, pkeys: do not use PKRU value in vcpu->arch.guest_fpu.state
- KVM: x86: block guest protection keys unless the host has them enabled
- ALSA: usb-audio: Add delay quirk for H650e/Jabra 550a USB headsets
- ALSA: core: Fix unexpected error at replacing user TLV
- ALSA: hda - Add stereo mic quirk for Lenovo G50-70 (17aa:3978)
- ALSA: firewire: fix NULL pointer dereference when releasing uninitialized
  data of iso-resource
- ALSA: firewire-motu: destroy stream data surely at failure of card
  initialization
- ARCv2: SLC: Make sure busy bit is set properly for region ops
- ARCv2: PAE40: Explicitly set MSB counterpart of SLC region ops addresses
- ARCv2: PAE40: set MSB even if !CONFIG_ARC_HAS_PAE40 but PAE exists in SoC
- PM/hibernate: touch NMI watchdog when creating snapshot
- mm, shmem: fix handling /sys/kernel/mm/transparent_hugepage/shmem_enabled
- dax: fix deadlock due to misaligned PMD faults
- i2c: designware: Fix system suspend
- mm/madvise.c: fix freeing of locked page with MADV_FREE
- fork: fix incorrect fput of ->exe_file causing use-after-free
- mm/memblock.c: reversed logic in memblock_discard()
- arm64: fpsimd: Prevent registers leaking across exec
- drm: Fix framebuffer leak
- drm: Release driver tracking before making the object available again
- drm/sun4i: Implement drm_driver lastclose to restore fbdev console
- drm/atomic: Handle -EDEADLK with out-fences correctly
- drm/atomic: If the atomic check fails, return its value first
- drm/i915/vbt: ignore extraneous child devices for a port
- drm/i915/gvt: Fix the kernel null pointer error
- Revert "drm/amdgpu: fix vblank_time when displays are off"
- ACPI: device property: Fix node lookup in 
acpi_graph_get_child_prop_value()
- tracing: Call clear_boot_tracer() at lateinit_sync
- tracing: Missing error code in tracer_alloc_buffers()
- tracing: Fix kmemleak in tracing_map_array_free()
- tracing: Fix freeing of filter in create_filter() when set_str is false
- RDMA/uverbs: Initialize cq_context appropriately
- kbuild: linker script do not match C names unless
  LD_DEAD_CODE_DATA_ELIMINATION is configured
- cifs: Fix df output for users with quota limits
- cifs: return ENAMETOOLONG for overlong names in cifs_open()/cifs_lookup()
- nfsd: Limit end of page list when decoding NFSv4 WRITE
- ring-buffer: Have ring_buffer_alloc_read_page() return error on offline 
CPU
- virtio_pci: fix 

[Group.of.nepali.translators] [Bug 1712345] Re: sort ABI files with C.UTF-8 locale

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.12.0-13.14

---
linux (4.12.0-13.14) artful; urgency=low

  * linux: 4.12.0-13.14 -proposed tracker (LP: #1714687)

  * vhost guest network randomly drops under stress (kvm) (LP: #1711251)
- Revert "vhost: cache used event for better performance"

  * EDAC sbridge: Failed to register device with error -22. (LP: #1714112)
- [Config] CONFIG_EDAC_GHES=n

  * Artful update to v4.12.10 stable release (LP: #1714525)
- sparc64: remove unnecessary log message
- bonding: require speed/duplex only for 802.3ad, alb and tlb
- bonding: ratelimit failed speed/duplex update warning
- af_key: do not use GFP_KERNEL in atomic contexts
- dccp: purge write queue in dccp_destroy_sock()
- dccp: defer ccid_hc_tx_delete() at dismantle time
- ipv4: fix NULL dereference in free_fib_info_rcu()
- net_sched/sfq: update hierarchical backlog when drop packet
- net_sched: remove warning from qdisc_hash_add
- bpf: fix bpf_trace_printk on 32 bit archs
- net: igmp: Use ingress interface rather than vrf device
- openvswitch: fix skb_panic due to the incorrect actions attrlen
- ptr_ring: use kmalloc_array()
- ipv4: better IP_MAX_MTU enforcement
- nfp: fix infinite loop on umapping cleanup
- tun: handle register_netdevice() failures properly
- sctp: fully initialize the IPv6 address in sctp_v6_to_addr()
- tipc: fix use-after-free
- ipv6: reset fn->rr_ptr when replacing route
- ipv6: repair fib6 tree in failure case
- tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP
- net/mlx4_core: Enable 4K UAR if SRIOV module parameter is not enabled
- irda: do not leak initialized list.dev to userspace
- net: sched: fix NULL pointer dereference when action calls some targets
- net_sched: fix order of queue length updates in qdisc_replace()
- bpf, verifier: add additional patterns to evaluate_reg_imm_alu
- bpf: fix mixed signed/unsigned derived min/max value bounds
- bpf/verifier: fix min/max handling in BPF_SUB
- Input: trackpoint - add new trackpoint firmware ID
- Input: elan_i2c - add ELAN0602 ACPI ID to support Lenovo Yoga310
- Input: ALPS - fix two-finger scroll breakage in right side on ALPS 
touchpad
- KVM: s390: sthyi: fix sthyi inline assembly
- KVM: s390: sthyi: fix specification exception detection
- KVM: x86: simplify handling of PKRU
- KVM, pkeys: do not use PKRU value in vcpu->arch.guest_fpu.state
- KVM: x86: block guest protection keys unless the host has them enabled
- ALSA: usb-audio: Add delay quirk for H650e/Jabra 550a USB headsets
- ALSA: core: Fix unexpected error at replacing user TLV
- ALSA: hda - Add stereo mic quirk for Lenovo G50-70 (17aa:3978)
- ALSA: firewire: fix NULL pointer dereference when releasing uninitialized
  data of iso-resource
- ALSA: firewire-motu: destroy stream data surely at failure of card
  initialization
- ARCv2: SLC: Make sure busy bit is set properly for region ops
- ARCv2: PAE40: Explicitly set MSB counterpart of SLC region ops addresses
- ARCv2: PAE40: set MSB even if !CONFIG_ARC_HAS_PAE40 but PAE exists in SoC
- PM/hibernate: touch NMI watchdog when creating snapshot
- mm, shmem: fix handling /sys/kernel/mm/transparent_hugepage/shmem_enabled
- dax: fix deadlock due to misaligned PMD faults
- i2c: designware: Fix system suspend
- mm/madvise.c: fix freeing of locked page with MADV_FREE
- fork: fix incorrect fput of ->exe_file causing use-after-free
- mm/memblock.c: reversed logic in memblock_discard()
- arm64: fpsimd: Prevent registers leaking across exec
- drm: Fix framebuffer leak
- drm: Release driver tracking before making the object available again
- drm/sun4i: Implement drm_driver lastclose to restore fbdev console
- drm/atomic: Handle -EDEADLK with out-fences correctly
- drm/atomic: If the atomic check fails, return its value first
- drm/i915/vbt: ignore extraneous child devices for a port
- drm/i915/gvt: Fix the kernel null pointer error
- Revert "drm/amdgpu: fix vblank_time when displays are off"
- ACPI: device property: Fix node lookup in 
acpi_graph_get_child_prop_value()
- tracing: Call clear_boot_tracer() at lateinit_sync
- tracing: Missing error code in tracer_alloc_buffers()
- tracing: Fix kmemleak in tracing_map_array_free()
- tracing: Fix freeing of filter in create_filter() when set_str is false
- RDMA/uverbs: Initialize cq_context appropriately
- kbuild: linker script do not match C names unless
  LD_DEAD_CODE_DATA_ELIMINATION is configured
- cifs: Fix df output for users with quota limits
- cifs: return ENAMETOOLONG for overlong names in cifs_open()/cifs_lookup()
- nfsd: Limit end of page list when decoding NFSv4 WRITE
- ring-buffer: Have ring_buffer_alloc_read_page() return error on offline 
CPU
- virtio_pci: fix 

[Group.of.nepali.translators] [Bug 1715654] Re: linux-snapdragon: 4.4.0-1075.80 -proposed tracker

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1715654

Title:
  linux-snapdragon: 4.4.0-1075.80 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1715651
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1715654/+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 1715656] Re: linux-gke: 4.4.0-1030.30 -proposed tracker

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1715656

Title:
  linux-gke: 4.4.0-1030.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gke package in Ubuntu:
  Invalid
Status in linux-gke source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1715651
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1715656/+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 1715368] Re: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream'

[Joseph Salisbury]

I'd like to perform a reverse bisect to figure out which commit upstream
fixes this regression.  We need to figure out  the last kernel that had
this issue and the first kernel that did not.

Can you test the following kernels and report back? We are looking for
the last kernel version that has the bug and the first that does not:

v4.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11
v4.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12
v4.13-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1

You don't have to test every kernel, just up until the first kernel that
does not have this bug.

Thanks in advance!

** Tags added: performing-bisect

** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: linux (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Zesty)
   Importance: Undecided => Medium

-- 
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/1715368

Title:
  Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03
  'kernel-fixed-upstream'

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03.
  CuW B1 device IDs are missing with Ubuntu 16.04.03 inbox bnxt_en 
driver(0.1.24) 

  Below is the modinfo output of Ubuntu 16.04.03 inbox bnxt_en driver.

  root@ubuntu160403:~# modinfo bnxt_en 
  filename: 
/lib/modules/4.4.0-87-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko
 
  version: 0.1.24 
  description: Broadcom BCM573xx network driver 
  license: GPL 
  srcversion: 0110469E9118262B301CA46 
  alias: pci:v14E4d16D3sv*sd*bc*sc*i* 
  alias: pci:v14E4d16CBsv*sd*bc*sc*i* 
  alias: pci:v14E4d16D2sv*sd*bc*sc*i* 
  alias: pci:v14E4d16D1sv*sd*bc*sc*i* 
  alias: pci:v14E4d16CAsv*sd*bc*sc*i* 
  alias: pci:v14E4d16C9sv*sd*bc*sc*i* 
  depends: vxlan 
  intree: Y 
  vermagic: 4.4.0-87-generic SMP mod_unload modversions 

  OS Details: 
  root@ubuntu160403:~# cat /etc/issue 
  Ubuntu 16.04.3 LTS \n \l 

  root@ubuntu160403:~# uname -a 
  Linux ubuntu160403 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715368/+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 1576066] Re: 32bit glibc calls old socketcall() syscall, causing seccomp problems

[Michael Vogt]

** Also affects: glibc (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: libseccomp (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: glibc (Ubuntu Artful)
   Importance: High
   Status: Fix Released

** Also affects: libseccomp (Ubuntu Artful)
   Importance: High
   Status: 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/1576066

Title:
  32bit glibc calls old socketcall() syscall, causing seccomp problems

Status in glibc package in Ubuntu:
  Fix Released
Status in libseccomp package in Ubuntu:
  Fix Released
Status in glibc source package in Trusty:
  Triaged
Status in libseccomp source package in Trusty:
  Triaged
Status in glibc source package in Xenial:
  Fix Released
Status in libseccomp source package in Xenial:
  Fix Released
Status in glibc source package in Zesty:
  New
Status in libseccomp source package in Zesty:
  New
Status in glibc source package in Artful:
  Fix Released
Status in libseccomp source package in Artful:
  Fix Released

Bug description:
  Back in the day when Linux was created for i386, for who knows what
  reason, all socket calls were multiplexed through a single syscall
  API, socketcall().  This was a strange thing to do, but it probably
  made sense from the standpoint of the same part of the kernel handling
  all of those calls.

  It was realised a long time ago that this was a strange and suboptimal
  arrangement.

  By the time they got around to doing amd64 and other architectures,
  they fixed this arrangement and gave each socket call a separate
  syscall entry point.  32bit systems continued to do it this old way,
  however, multiplexing all calls through socketcall().

  This is a problem for seccomp.  If we want to allow a program to make
  casual use of the network, but not bind a listener socket, we cannot
  currently do that.  On 64bits we just filter out the bind() and
  listen() calls, but on 32bit, it's all the same syscall.

  The kernel people fixed this problem up last summer by introducing
  new, separate, syscall entries for each separate call.

http://patchwork.sourceware.org/patch/7679/

  The problem is that glibc in Y is still using the old socketcall()
  interface on i386.  It needs to be updated to use the new calls.

  A possible caveat is that this might create problems for running newer
  binaries on older kernels on i386 (as we sometimes do with builders)
  because they won't have the new syscalls.  A solution could involve
  checking for ENOSYS and trying again via the old route.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1576066/+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 1715399] Re: [SRU] New stable micro release 2.34

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.34+17.10

---
snapcraft (2.34+17.10) artful; urgency=medium

  [ Sergio Schvezov ]
  * core: cache FileBase entries when a checksum is provided (#1433)
  * cli: better error message for missing mksquashfs (#1481)
  * core: improve source caching logic (#1486)
  * ci: speedup the CLA check (#1503)
  * ci: disable the travis deploy stage for docs (#1510)
  * vcs: ignore .vscode project settings (#1517)
  * docs: add github processed templates (#1514)
  * tour: remove the tour assets (#1520)
  * project: introduce build-snaps (#1518)
  * tests: update the meson test to latest meson requirements (#1532)
  * jhbuild plugin: remove dependency on pkgconf (#1535)
  * nodejs plugin: add prefix --prefix to global pkg add (#1539)
  * New upstream release (LP: #1715399)

  [ Christian Dywan ]
  * lxd: clean with no parts should only delete (#1434)
  * lxd: inject snapcraft and core snaps into the container (#1364)
  * lxd: wait on lock files before running apt commands (#1435)
  * kbuild plugin: support Makefiles without an install target (#1432)
  * kbuild plugin: move over the cross-compiling logic from the kernel plugin 
(#1417)
  * lxd: path cannot have extra forward slashes (#1483)
  * lxd: always remove existing device for project folder (#1488)
  * lifecycle: outdated step should raise SnapcraftError (#1513)
  * errors: introduce ContainerError (#1505)
  * lxd: LXD not installed when using remote (#1516)
  * lxd: use a unique temporary folder (#1519)

  [ Leo Arias ]
  * recording: record the original snapcraft.yaml (#1407)
  * ci: skip the CLA check for pull requests from the bot (#1482)
  * docs: fix typo in plugin help (#1496)
  * python plugin: record manifest (#1487)
  * tests: use assertThat instead of assertEqual (#1501)
  * python plugin: always record constraints and requirements contents (#1521)
  * demos: update the name of the remote mqtt part (#1533)

  [ Kyle Fazzari ]
  * options: properly handle missing compiler prefix (#1425)
  * catkin plugin: include-roscore is a boolean (#1472)
  * catkin plugin: default to release build (#1470)
  * catkin plugin: rosinstall-files is a pull property (#1473)
  * catkin plugin: support passing args to cmake (#1471)
  * catkin plugin: extract rosdep into new package (#1392)
  * cli: add global exception handler
  * cli: stop handling exceptions in lifecycle
  * plugins: use exceptions based on SnapcraftError
  * cli: stop handling exceptions in parts
  * cli: stop handling exceptions in assertions
  * cli: stop handling exceptions in store
  * many: use exceptions based on SnapcraftError
  * rosdep: add support for multiple dependency types (#1479)
  * errors: use function for exit code (#1491)
  * cli: don't raise from excepthook (#1495)
  * repo: make errors based on SnapcraftError (#1499)
  * project loader: refactor into package (#1504)
  * grammar: move into project_loader (#1500)
  * many: simplify plugin loading (#1507)
  * schema: version should have a max length of 32 (#1508)
  * project_loader: process stage package grammar (#1509)
  * project_loader: support grammar on build-packages (#1511)

  [ Alex T Newman ]
  * windows: add cx_Freeze options targeting bin/snapcraft (#1478)

  [ Michael Vogt ]
  * meta: add `base` as a type and top level property (#1419)

  [ Adam Collard ]
  * ant plugin, gradle plugin: add support for authenticated proxies (#1490)

  [ fmanea ]
  * demos: remove the unnecessary wrapper from the java demo (#1494)

  [ Neal Gompa (ニール・ゴンパ) ]
  * repo: use os-release(5) to detect supported Linux distributions (#1527)

  [ Daniel Llewellyn ]
  * jhbuild plugin: new plugin (#1298)
  * jhbuild plugin: fix UnboundLocalError for chmod_path (#1534)

 -- Sergio Schvezov   Wed, 06 Sep 2017
14:04:53 +

** Changed in: snapcraft (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1715399

Title:
  [SRU] New stable micro release 2.34

Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Zesty:
  New

Bug description:
  This is an SRU bug to release 2.34 of snapcraft which follows the
  guidelines defined in the wiki over at
  https://wiki.ubuntu.com/SnapcraftUpdates

  The list of bugs and features in this release are defined at
  https://launchpad.net/snapcraft/+milestone/2.34 and
  https://github.com/snapcore/snapcraft/milestone/9?closed=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1715399/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe :