[Group.of.nepali.translators] [Bug 1656847] Re: neutron security group rules not applied to nova-lxd containers

[Launchpad Bug Tracker]

This bug was fixed in the package nova-lxd - 13.2.0-0ubuntu1.16.04.1

---
nova-lxd (13.2.0-0ubuntu1.16.04.1) xenial-security; urgency=medium

  * SECURITY UPDATE: ensure correct application of security group rules.
- d/p/host-device-naming.patch: Cherry pick fix to ensure that the
  host part of the veth pair used to wire LXD containers into neutron
  has the correct naming, resolving issues with application of
  neutron security group rules in container deployments (LP: #1656847).
- CVE not yet assigned

 -- James Page   Tue, 07 Feb 2017 17:06:46 +0100

** Changed in: nova-lxd (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/1656847

Title:
  neutron security group rules not applied to nova-lxd containers

Status in nova-lxd:
  Fix Released
Status in nova-lxd package in Ubuntu:
  Fix Released
Status in nova-lxd source package in Xenial:
  Fix Released
Status in nova-lxd source package in Yakkety:
  Fix Released
Status in nova-lxd source package in Zesty:
  Fix Released

Bug description:
  I noted this when testing the changes for lxd:isolated in Ubuntu
  Xenial; neutron sets up iptables rules against tap devices (as used in
  the libvirt driver); however nova-lxd does not use tap devices - LXD
  plumbs the instance in to the neutron bridge using an veth pair.

  I think the net result of this is that security rules are just not
  getting applied in LXD instances.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova-lxd/+bug/1656847/+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 1642298] Re: UEFI Xenial install sets computer to boot from hard disk

[dann frazier]

The grub2 changes are in zesty as of 2.02~beta3-4ubuntu1. Could I ask
the curtin developers to take a look at implementing the necessary
changes there? Specifically, using the new grub2/update_nvram preseed
instead of manually passing --no-nvram to grub-install during install.

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

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

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

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

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

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

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

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

Title:
  UEFI Xenial install sets computer to boot from hard disk

Status in curtin:
  Confirmed
Status in MAAS:
  Invalid
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Trusty:
  Triaged
Status in grub2 source package in Xenial:
  Triaged
Status in grub2 source package in Yakkety:
  Triaged

Bug description:
  This bug is a regression of bug #1311827.

  On a current MAAS 2.0 installation, I've discovered that MAAS is now
  overriding the PXE-boot settings, causing the system to attempt to
  boot directly from the grubx64.efi on the hard disk's EFI System
  Partition (ESP). After installation, the result looks like this:

  ubuntu@oil-hatanaka:~$ sudo efibootmgr
  BootCurrent: 0005
  Timeout: 1 seconds
  BootOrder: 0005,0001,0002,0003,0004
  Boot0001* UEFI: IP4 ELX NIC Bus:Dev:Func 3:0:0 - Fujitsu DynamicLoM Emulex 
OCl14000-LOM
  Boot0002* UEFI: IP6 ELX NIC Bus:Dev:Func 3:0:0 - Fujitsu DynamicLoM Emulex 
OCl14000-LOM
  Boot0003* UEFI: IP4 ELX NIC Bus:Dev:Func 3:0:1 - Fujitsu DynamicLoM Emulex 
OCl14000-LOM
  Boot0004* UEFI: IP6 ELX NIC Bus:Dev:Func 3:0:1 - Fujitsu DynamicLoM Emulex 
OCl14000-LOM
  Boot0005* ubuntu

  Note that BootOrder specifies Boot0005 as the first option, causing
  the computer to attempt to boot from the hard disk rather than PXE-
  boot (any of the other Boot options on this computer). This causes
  at least two problems:

  * If Secure Boot is enabled, the computer may fail to boot, because the 
"ubuntu" entry points
to grubx64.efi, not shimx64.efi. (If the computer silently falls past the 
SB failure, it
will boot; but on the Fujitsu system I tested, it displays a console 
message about the SB
failure that requires human interaction, and therefore hangs indefinitely 
in a MAAS
environment.)
  * Re-deploying the node is impossible without manual intervention, because 
the system
will try to boot from the hard disk rather than PXE-booting under MAAS 
control.

  This problem has occurred on a server running MAAS
  2.0.0+bzr5189-0ubuntu1~16.04.1 (see below for detailed version
  information). Another server running MAAS
  2.1.0+bzr5480-0ubuntu1~16.04.1 does NOT have the problem. I suspect
  the problem is with the ephemeral images, though, not the MAAS version
  per se. I'm attaching the log files from the MAAS 2.0 system as
  requested.

  I've tested this with three systems: A Fujitsu RX2530M2R2, a Fujitsu
  RX2540M2R1, and an IBM x3650 M2. (The MAAS 2.1 server controlled an
  Intel NUC DC53427HYE.) The Fujitsu systems are new (to us), but the
  IBM has been in our possession for an extended period and has never
  exhibited this problem (except perhaps when bug #1311827 was current),
  so I'm confident this is a regression.

  All tests involved deployments of Ubuntu 16.04. Most used the
  certification custom images (for 16.04.1), but I've verified the
  results on one system deploying the standard MAAS image for xenial.

  MAAS version information:

  rodsmith@weavile:~$ dpkg -l '*maas*'|cat
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersion
Architecture Description
  
+++-===-==--==
  ii  maas2.0.0+bzr5189-0ubuntu1~16.04.1 all
  "Metal as a Service" is a physical cloud and IPAM
  ii  maas-cert-server0.2.25-0~64~ubuntu16.04.1  all
  Ubuntu certification support files for MAAS server
  ii  maas-cli2.0.0+bzr5189-0ubuntu1~16.04.1 all
  MAAS client and command-line interface
  un  maas-cluster-controller   
  (no description available)
  ii  maas-common 

[Group.of.nepali.translators] [Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

[Launchpad Bug Tracker]

This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu3~0.16.10

---
freeipmi (1.4.11-1.1ubuntu3~0.16.10) yakkety; urgency=medium

  * Backport to yakkety.
Add ipv6 ipmi-discovery. LP: #1645912.  See also:

https://github.com/chu11/freeipmi-mirror/pull/12/commits/32721f88cd37aa4ca1564c243669f96628089986

 -- LaMont Jones   Thu, 26 Jan 2017 09:43:29 -0700

** Changed in: freeipmi (Ubuntu Yakkety)
   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/1645912

Title:
  freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

Status in MAAS:
  Fix Committed
Status in freeipmi package in Ubuntu:
  Fix Released
Status in freeipmi source package in Xenial:
  Fix Released
Status in freeipmi source package in Yakkety:
  Fix Released

Bug description:
  See also https://github.com/chu11/freeipmi-mirror/issues/8 and
  https://github.com/chu11/freeipmi-mirror/issues/12 -- freeipmi needs
  to successfully discover the ipv6 address of a hosts BMC.

  [Impact]

   * Machines with BMCs configured to use IPv6 addresses, ipmi-config
     (silently) fails to show those values.

   * MAAS 2.2 supports IPv6 BMC addresses, and depends on ipmi-config
     finding the IPv6 address of the BMC.

   * This upload is a backport of an upstream work-in-progress to add IPv6
     configuration parameters to ipmi-config.  While the eventual upstream
     source may differ slightly as the branch lands, this delivers the
     information for use.  ANYONE USING THIS CODE NEEDS TO BE PREPARED TO
     CHANGE TO MATCH THE ACTUAL DELIVERY WHEN 1.6 LANDS.

  [Test Case]

   * Start with an HP DL360 Proliant Gen9 (iLO4 is required) with an IPv6
     address configured on the iLO.  Try to get ipmi-config to give you
     that address.

   * This upload introduces the Lan6_Conf section (which may change when
     1.6 finally arrives.)  The following displays the IPv6 Addresses of
     the BMC:
    ipmi-config --checkout --category=core --section=Lan6_Conf

  [Regression Potential]

   * Scripting that uses --checkout and no section/key-pair specification
     will now see the additional Lan6_Conf section, which has the potential
     to confuse said script.

   * If upstream changes the presentation of the data, anyone who has
     adopted this pre-release of same may see differences.  The section is
     clearly marked as subject to change in 1.6, and missing in 1.5.  (If
     Ubuntu syncs 1.5, MAAS is committed to porting this change forward.
     Upstream has committed to the feature being present in 1.6.)

  [Other Info]

  Once the changes are available, MAAS will need to change to use the
  new Lan6_Conf section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1645912/+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 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

[Launchpad Bug Tracker]

This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu3~0.16.04

---
freeipmi (1.4.11-1.1ubuntu3~0.16.04) xenial; urgency=medium

  * Backport to xenial.
Add ipv6 ipmi-discovery. LP: #1645912.  See also:

https://github.com/chu11/freeipmi-mirror/pull/12/commits/32721f88cd37aa4ca1564c243669f96628089986

 -- LaMont Jones   Thu, 26 Jan 2017 09:43:29 -0700

** Changed in: freeipmi (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/1645912

Title:
  freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

Status in MAAS:
  Fix Committed
Status in freeipmi package in Ubuntu:
  Fix Released
Status in freeipmi source package in Xenial:
  Fix Released
Status in freeipmi source package in Yakkety:
  Fix Released

Bug description:
  See also https://github.com/chu11/freeipmi-mirror/issues/8 and
  https://github.com/chu11/freeipmi-mirror/issues/12 -- freeipmi needs
  to successfully discover the ipv6 address of a hosts BMC.

  [Impact]

   * Machines with BMCs configured to use IPv6 addresses, ipmi-config
     (silently) fails to show those values.

   * MAAS 2.2 supports IPv6 BMC addresses, and depends on ipmi-config
     finding the IPv6 address of the BMC.

   * This upload is a backport of an upstream work-in-progress to add IPv6
     configuration parameters to ipmi-config.  While the eventual upstream
     source may differ slightly as the branch lands, this delivers the
     information for use.  ANYONE USING THIS CODE NEEDS TO BE PREPARED TO
     CHANGE TO MATCH THE ACTUAL DELIVERY WHEN 1.6 LANDS.

  [Test Case]

   * Start with an HP DL360 Proliant Gen9 (iLO4 is required) with an IPv6
     address configured on the iLO.  Try to get ipmi-config to give you
     that address.

   * This upload introduces the Lan6_Conf section (which may change when
     1.6 finally arrives.)  The following displays the IPv6 Addresses of
     the BMC:
    ipmi-config --checkout --category=core --section=Lan6_Conf

  [Regression Potential]

   * Scripting that uses --checkout and no section/key-pair specification
     will now see the additional Lan6_Conf section, which has the potential
     to confuse said script.

   * If upstream changes the presentation of the data, anyone who has
     adopted this pre-release of same may see differences.  The section is
     clearly marked as subject to change in 1.6, and missing in 1.5.  (If
     Ubuntu syncs 1.5, MAAS is committed to porting this change forward.
     Upstream has committed to the feature being present in 1.6.)

  [Other Info]

  Once the changes are available, MAAS will need to change to use the
  new Lan6_Conf section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1645912/+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 1588330] Re: Incompatible builds of libodb and libodb-mysql

[Launchpad Bug Tracker]

This bug was fixed in the package libodb-pgsql - 2.4.0-1build1

---
libodb-pgsql (2.4.0-1build1) zesty; urgency=medium

  * No change rebuild for c++11 abi. LP: #1588330

 -- Dimitri John Ledkov   Thu, 09 Feb 2017 16:07:35
+

** Changed in: libodb-sqlite (Ubuntu Zesty)
   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/1588330

Title:
  Incompatible builds of libodb and libodb-mysql

Status in libodb package in Ubuntu:
  Fix Released
Status in libodb-boost package in Ubuntu:
  Fix Released
Status in libodb-pgsql package in Ubuntu:
  Fix Released
Status in libodb-qt package in Ubuntu:
  Fix Released
Status in libodb-sqlite package in Ubuntu:
  Fix Released
Status in libodb source package in Xenial:
  New
Status in libodb-boost source package in Xenial:
  New
Status in libodb-pgsql source package in Xenial:
  New
Status in libodb-qt source package in Xenial:
  New
Status in libodb-sqlite source package in Xenial:
  New
Status in libodb source package in Yakkety:
  New
Status in libodb-boost source package in Yakkety:
  New
Status in libodb-pgsql source package in Yakkety:
  New
Status in libodb-qt source package in Yakkety:
  New
Status in libodb-sqlite source package in Yakkety:
  New
Status in libodb source package in Zesty:
  Fix Released
Status in libodb-boost source package in Zesty:
  Fix Released
Status in libodb-pgsql source package in Zesty:
  Fix Released
Status in libodb-qt source package in Zesty:
  Fix Released
Status in libodb-sqlite source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  * libodb stack changes abi when build with new enough g++ (due to c++11 abi 
tagging)
  * things that are compiled with new abi are ok (libodb-mysql); linking 
against mixed build things does not work (e.g. 3rd party apps, like odb-tests 
building against new libodb-mysql and old libodb)

  [Solution]
  * In debian, simply binNMUs were done without bumping the ABI =/

  * Whilst libodb-boost and libodb-qt do not appear to be affected, imho
  it is best to rebuild them too.

  [Testcase]
  * download odb-tests
  * autoreconf -fi
  * Build and link with following configs (./configure; make clean; make)
  + ./configure --with-database=sqlite
  + ./configure --with-database=mysql
  + ./configure --with-database=pgsql

  
  There appears to be some incompatibility between libodb and libodb-mysql in 
that the latter cannot resolve symbols from the former. More details are in 
this odb-users mailing list thread:

  http://www.codesynthesis.com/pipermail/odb-users/2016-May/003277.html

  My suspicion (discussed in the second post of the above thread) is
  that libodb is built in the C++11 mode while the rest of the ODB
  runtimes (libodb-mysql and libodb-pgsql were confirmed by the users)
  -- C++98. I, however, couldn't find the package build logs (neither on
  Ubuntu nor on Debian) to confirm this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libodb/+bug/1588330/+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 1588330] Re: Incompatible builds of libodb and libodb-mysql

[Launchpad Bug Tracker]

This bug was fixed in the package libodb-qt - 2.4.0-2build1

---
libodb-qt (2.4.0-2build1) zesty; urgency=medium

  * No change rebuild for c++11 abi. LP: #1588330

 -- Dimitri John Ledkov   Thu, 09 Feb 2017 16:07:41
+

** Changed in: libodb-qt (Ubuntu Zesty)
   Status: New => Fix Released

** Changed in: libodb-boost (Ubuntu Zesty)
   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/1588330

Title:
  Incompatible builds of libodb and libodb-mysql

Status in libodb package in Ubuntu:
  Fix Released
Status in libodb-boost package in Ubuntu:
  Fix Released
Status in libodb-pgsql package in Ubuntu:
  Fix Released
Status in libodb-qt package in Ubuntu:
  Fix Released
Status in libodb-sqlite package in Ubuntu:
  Fix Released
Status in libodb source package in Xenial:
  New
Status in libodb-boost source package in Xenial:
  New
Status in libodb-pgsql source package in Xenial:
  New
Status in libodb-qt source package in Xenial:
  New
Status in libodb-sqlite source package in Xenial:
  New
Status in libodb source package in Yakkety:
  New
Status in libodb-boost source package in Yakkety:
  New
Status in libodb-pgsql source package in Yakkety:
  New
Status in libodb-qt source package in Yakkety:
  New
Status in libodb-sqlite source package in Yakkety:
  New
Status in libodb source package in Zesty:
  Fix Released
Status in libodb-boost source package in Zesty:
  Fix Released
Status in libodb-pgsql source package in Zesty:
  Fix Released
Status in libodb-qt source package in Zesty:
  Fix Released
Status in libodb-sqlite source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  * libodb stack changes abi when build with new enough g++ (due to c++11 abi 
tagging)
  * things that are compiled with new abi are ok (libodb-mysql); linking 
against mixed build things does not work (e.g. 3rd party apps, like odb-tests 
building against new libodb-mysql and old libodb)

  [Solution]
  * In debian, simply binNMUs were done without bumping the ABI =/

  * Whilst libodb-boost and libodb-qt do not appear to be affected, imho
  it is best to rebuild them too.

  [Testcase]
  * download odb-tests
  * autoreconf -fi
  * Build and link with following configs (./configure; make clean; make)
  + ./configure --with-database=sqlite
  + ./configure --with-database=mysql
  + ./configure --with-database=pgsql

  
  There appears to be some incompatibility between libodb and libodb-mysql in 
that the latter cannot resolve symbols from the former. More details are in 
this odb-users mailing list thread:

  http://www.codesynthesis.com/pipermail/odb-users/2016-May/003277.html

  My suspicion (discussed in the second post of the above thread) is
  that libodb is built in the C++11 mode while the rest of the ODB
  runtimes (libodb-mysql and libodb-pgsql were confirmed by the users)
  -- C++98. I, however, couldn't find the package build logs (neither on
  Ubuntu nor on Debian) to confirm this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libodb/+bug/1588330/+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 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

[Bug Watch Updater]

** Changed in: systemd (Debian)
   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/1647485

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in maas-images:
  Fix Released
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1647485/+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 1588330] Re: Incompatible builds of libodb and libodb-mysql

[Launchpad Bug Tracker]

This bug was fixed in the package libodb-boost - 2.4.0-1build1

---
libodb-boost (2.4.0-1build1) zesty; urgency=medium

  * No change rebuild for c++11 abi. LP: #1588330

 -- Dimitri John Ledkov   Thu, 09 Feb 2017 16:07:28
+

** Changed in: libodb-pgsql (Ubuntu Zesty)
   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/1588330

Title:
  Incompatible builds of libodb and libodb-mysql

Status in libodb package in Ubuntu:
  Fix Released
Status in libodb-boost package in Ubuntu:
  Fix Released
Status in libodb-pgsql package in Ubuntu:
  Fix Released
Status in libodb-qt package in Ubuntu:
  Fix Released
Status in libodb-sqlite package in Ubuntu:
  Fix Released
Status in libodb source package in Xenial:
  New
Status in libodb-boost source package in Xenial:
  New
Status in libodb-pgsql source package in Xenial:
  New
Status in libodb-qt source package in Xenial:
  New
Status in libodb-sqlite source package in Xenial:
  New
Status in libodb source package in Yakkety:
  New
Status in libodb-boost source package in Yakkety:
  New
Status in libodb-pgsql source package in Yakkety:
  New
Status in libodb-qt source package in Yakkety:
  New
Status in libodb-sqlite source package in Yakkety:
  New
Status in libodb source package in Zesty:
  Fix Released
Status in libodb-boost source package in Zesty:
  Fix Released
Status in libodb-pgsql source package in Zesty:
  Fix Released
Status in libodb-qt source package in Zesty:
  Fix Released
Status in libodb-sqlite source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  * libodb stack changes abi when build with new enough g++ (due to c++11 abi 
tagging)
  * things that are compiled with new abi are ok (libodb-mysql); linking 
against mixed build things does not work (e.g. 3rd party apps, like odb-tests 
building against new libodb-mysql and old libodb)

  [Solution]
  * In debian, simply binNMUs were done without bumping the ABI =/

  * Whilst libodb-boost and libodb-qt do not appear to be affected, imho
  it is best to rebuild them too.

  [Testcase]
  * download odb-tests
  * autoreconf -fi
  * Build and link with following configs (./configure; make clean; make)
  + ./configure --with-database=sqlite
  + ./configure --with-database=mysql
  + ./configure --with-database=pgsql

  
  There appears to be some incompatibility between libodb and libodb-mysql in 
that the latter cannot resolve symbols from the former. More details are in 
this odb-users mailing list thread:

  http://www.codesynthesis.com/pipermail/odb-users/2016-May/003277.html

  My suspicion (discussed in the second post of the above thread) is
  that libodb is built in the C++11 mode while the rest of the ODB
  runtimes (libodb-mysql and libodb-pgsql were confirmed by the users)
  -- C++98. I, however, couldn't find the package build logs (neither on
  Ubuntu nor on Debian) to confirm this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libodb/+bug/1588330/+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 1649925] Re: Support for the G200eW3 server chipset needed

[Robert Hooker]

Won't be able to verify this anymore and it was removed from zesty so
I'll close it.

** Changed in: xserver-xorg-video-mga (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: hwe-next
   Status: New => 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/1649925

Title:
  Support for the G200eW3 server chipset needed

Status in HWE Next:
  Won't Fix
Status in xserver-xorg-video-mga package in Ubuntu:
  Won't Fix
Status in xserver-xorg-video-mga source package in Xenial:
  New
Status in xserver-xorg-video-mga source package in Yakkety:
  New

Bug description:
  Available in upstream git at

  https://cgit.freedesktop.org/xorg/driver/xf86-video-
  mga/commit/?id=12781f2e3deb7f6d86fde53134384996a6004894

  but not in any releases yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-mga 1:1.6.4-1build2
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Dec 14 10:23:13 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: rtl8812au, 4.3.8.12175.20140902+dfsg: added
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9]
  InstallationDate: Installed on 2016-01-06 (342 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: LENOVO 3443CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=1f36140c-def2-49da-a1f8-0e14cfc2d84c ro quiet splash 
intel_pstate=disable vt.handoff=7
  SourcePackage: xserver-xorg-video-mga
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
  Identifier  "Configured Video Device"
  Driver "modesetting"
  #Option "TearFree" "true" 
   EndSection
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3443CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET93WW(2.53):bd02/04/2013:svnLENOVO:pn3443CTO:pvrThinkPadX1Carbon:rvnLENOVO:rn3443CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3443CTO
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.73+git20161127.23d10b82-0ubuntu0ricotz~xenial
  version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.2-1ubuntu1~xenial0
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.2-1ubuntu1~xenial0
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.8.99+git20161127.487aa62a-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20161127.bde94605-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git20161127.1516d35b-0ubuntu0ricotz~xenial
  xserver.bootTime: Wed Dec 14 09:59:26 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1649925/+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 1648561] Re: HTX (htxubuntu) DASD exercisers fail

[Mathieu Trudel-Lapierre]

If os-prober is not running, I don't see what else might be poking the
disks to cause the warnings. We must ignore the other warning messages
that were listed from syslog earlier and look at it a different way. Is
the Redhat system showing the same write errors?

Is HTX doing raw writes to disk or are you writing files on a
filesystem? Again, what filesystems exist on the disks being exercised?
Could it be that the filesystem or the disk fails as a consequence of
the HTX workload?

Reassigning to 'linux' so that further investigation can be done on the
issue.

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: os-prober (Ubuntu)
Milestone: ubuntu-17.02 => None

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

Title:
  HTX (htxubuntu) DASD exercisers fail

Status in linux package in Ubuntu:
  Incomplete
Status in os-prober package in Ubuntu:
  Won't Fix
Status in linux source package in Xenial:
  Incomplete
Status in os-prober source package in Xenial:
  Won't Fix

Bug description:
  == Comment: #1 - Application Cdeadmin  - 2016-12-02 
04:55:07 ==
   State: Open by: tdylla on 01 December 2016 07:24:33 

  Notice: This Note entry was modified.  2 non-ascii character(s) were
  replaced with question marks.

   BMC yl13u2bmc

  OS  yl13u2os

  root@YL13U2OS:~# ver
  cat: /proc/device-tree/openprom/model: No such file or directory
     ver 1.5.4.5 - OS, HTX, Firmware and Machine details

     OS: GNU/Linux
     OS Version: Ubuntu 16.04.1 LTS \n \l
     Kernel Version: 4.4.0-47-generic
    HTX Version: htxubuntu-422
  Host Name: YL13U2OS
  Machine Serial No: 100CC9A
     Machine Type/Model: 8335-GTB

  root@YL13U2OS:~# uname -a
  Linux YL13U2OS 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:38:24 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@YL13U2OS:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.04.1 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.1 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  Dasd exercisers fail with a write error.  These have never failed
  before.

  root@YL13U2OS:~# lsblk -o KNAME,TYPE,SIZE,MODEL,ROTA
  KNAME TYPE   SIZE MODELROTA
  sda   disk   1.8T ST2000NX02531
  sda1  part   1.8T 1
  sdb   disk   1.8T ST2000NX02531
  sdb1  part   1.8T 1

  Getting HTX erros from yl13u2os.rch.stglabs.ibm.com

   Result Starts Here 
  Currently running ECG/MDT : /usr/lpp/htx//mdt/mdt.whit
  ===

  -
  Device id:/dev/sda1
  Timestamp:Dec 1 01:22:57 2016
  err=0001
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:rule_1_3 numopers= 1907729 loop= 1322123 blk=0xc08768b0 len=262144 
dir=DOWN min_blkno=0xaea86084 max_blkno=0xe8e080af
  BWRC LBA fencepost Detail:
  th_num min_lba max_lba status
  0 0 2476e9ff R
  1 4766ee58 74704057 R
  2 74704058 99783457 R
  3 c0876ab0 e8e080af R
  write error - errno: 1(?)

  -

  -
  Device id:/dev/sda1
  Timestamp:Dec 1 01:22:57 2016
  err=0001
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:Hardware Exerciser stopped on error

  -

  -
  Device id:/dev/sdb1
  Timestamp:Dec 1 01:23:08 2016
  err=0001
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:rule_1_1 numopers= 1907729 loop= 1394165 blk=0x49e45458 len=262144 
dir=DOWN min_blkno=0x3a38202c max_blkno=0x74704057
  BWRC LBA fencepost Detail:
  

[Group.of.nepali.translators] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

[Scott Moser]

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Yakkety)
   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/1582323

Title:
  Commissioning fails when competing cloud metadata resides on disk

Status in cloud-init:
  Fix Released
Status in MAAS:
  Fix Committed
Status in MAAS 2.1 series:
  Fix Released
Status in MAAS trunk series:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  === Begin SRU Information ===
  [Impact]
  The issue originally reported was that when MAAS attempted to enlist a
  system by booting it with a remote iscsi disk with intent to have cloud-init
  utilize the MAAS metadata service, cloud-init found some metadata from a
  previous use of the system on the local disk.  cloud-init then went on
  to use that data and did not respond to maas.

  The impact in this case was that cloud-init failed to enlist.  The same 
problem
  could occur in any other case where there was data on the local disk that
  provided a datasource for cloud-init.

  The fix provided was for the scenario provided was for MAAS to provide
  configuration on the maas provided kernel command line that tells cloud-init
  it should read only attempt to use the MAAS datasource.

  Specifically, as mentioned in comment 7, this looked like:
 root=iscsi: cc:{'datasource_list': ['MAAS']}end_cc \
 cloud-config-url=http://maas/path/to/config ...

  cloud-init then reads that information on boot and it overrides the settings
  found inside the iscsi root device.

  [Test Case]
  A test case lives in unit tests now that ensures kernel config overrides
  system config.

  To further test this we could
  a.) cause this situation by
1.) installing a node in maas
2.) putting config drive or nocloud data onto one of the partitions
3.) returning the system to maas
4.) attempt re-deploy.

  b.) use a cloud image, kernel and initramfs and web server
1.) download image, update cloud-init to -proposed.
2.) set up a web service to serve files like MAAS described at
https://maas.ubuntu.com/docs/development/metadata.html
3.) boot image with kernel command line including the cc: and 
cloud-config-url  referencing that web service.
4.) have provided a config drive or nocloud seed disk to the vm.

  The 'b' test above is easier to reproduce in that it does not rely on
  MAAS.

  [Regression Potential]
  Regression potential is low, in that this feature worked for some time
  in previous releases.  A bad reading of the code made me (smoser) change
  the code intending to fix the problem, but in fact regressed it.  So this
  change is actually reverting a previous change in behavior.

  This was first broken in 16.04 in 0.7.7~bzr1245-0ubuntu1~16.04.1 .

  [Other Info]
  The upstream commit that fixed this behavior (including the added tests)
  is 0b0f254a [1]

  --
  [1] 
https://git.launchpad.net/cloud-init/commit/?id=0b0f254a6935a1b1fff128fa177152dd519e1a3d

  === End SRU Information ===

  A customer reused hardware that had previously deployed a RHEL
  Overcloud-controller which places metadata on the disk as a legitimate
  source, that cloud-init looks at by default.  When the newly enlisted
  node appeared it had the name of "overcloud-controller-0" vs. maas-
  enlist, pulled from the disk metadata which had overridden MAAS'
  metadata.  Commissioning continually failed on all of the nodes until
  the disk metadata was manually removed (KVM boot Ubuntu ISO, rm -f
  data or dd zeros to disk).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1582323/+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 1647910] Re: hostname is set incorrectly if localhostname is fully qualified

[Scott Moser]

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Yakkety)
   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/1647910

Title:
  hostname is set incorrectly if localhostname is fully qualified

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  If no data source is available and the local hostname is set to
  "localhost.localdomain", and /etc/hosts looks like:

127.0.0.1   localhost localhost.localdomain localhost4
  localhost4.localdomain4

  Then in sources/__init__.py in get_hostname:

  - util.get_hostname() will return 'localhost.localdomain'
  - util.get_fqdn_from_hosts(hostname) will return 'localhost'
  - 'toks' will be set to [ 'localhost.localdomain', 'localdomain'

  And ultimately the system hostname will be set to
  'localhost.localdomain.localdomain', which isn't useful to anybody.

  Also reported in:

  https://bugzilla.redhat.com/show_bug.cgi?id=1389048

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1647910/+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 1656847] Re: neutron security group rules not applied to nova-lxd containers

[James Page]

Part of 13.1.1  - Marking Fix Released for nova-lxd

** Changed in: nova-lxd
   Status: In Progress => Fix Committed

** Changed in: nova-lxd
   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/1656847

Title:
  neutron security group rules not applied to nova-lxd containers

Status in nova-lxd:
  Fix Released
Status in nova-lxd package in Ubuntu:
  Fix Released
Status in nova-lxd source package in Xenial:
  Confirmed
Status in nova-lxd source package in Yakkety:
  Fix Released
Status in nova-lxd source package in Zesty:
  Fix Released

Bug description:
  I noted this when testing the changes for lxd:isolated in Ubuntu
  Xenial; neutron sets up iptables rules against tap devices (as used in
  the libvirt driver); however nova-lxd does not use tap devices - LXD
  plumbs the instance in to the neutron bridge using an veth pair.

  I think the net result of this is that security rules are just not
  getting applied in LXD instances.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova-lxd/+bug/1656847/+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 1588330] Re: Incompatible builds of libodb and libodb-mysql

[Dimitri John Ledkov]

** Also affects: libodb-pgsql (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libodb-qt (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libodb-boost (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

- There appears to be some incompatibility between libodb and libodb-mysql
- in that the latter cannot resolve symbols from the former. More details
- are in this odb-users mailing list thread:
+ [Impact]
+ 
+ * libodb stack changes abi when build with new enough g++ (due to c++11 abi 
tagging)
+ * things that are compiled with new abi are ok (libodb-mysql); linking 
against mixed build things does not work (e.g. 3rd party apps, like odb-tests 
building against new libodb-mysql and old libodb)
+ 
+ [Solution]
+ * In debian, simply binNMUs were done without bumping the ABI =/
+ 
+ * Whilst libodb-boost and libodb-qt do not appear to be affected, imho
+ it is best to rebuild them too.
+ 
+ [Testcase]
+ * download odb-tests
+ * autoreconf -fi
+ * Build and link with following configs (./configure; make clean; make)
+ + ./configure --with-database=sqlite
+ + ./configure --with-database=mysql
+ + ./configure --with-database=pgsql
+ 
+ 
+ There appears to be some incompatibility between libodb and libodb-mysql in 
that the latter cannot resolve symbols from the former. More details are in 
this odb-users mailing list thread:
  
  http://www.codesynthesis.com/pipermail/odb-users/2016-May/003277.html
  
  My suspicion (discussed in the second post of the above thread) is that
  libodb is built in the C++11 mode while the rest of the ODB runtimes
  (libodb-mysql and libodb-pgsql were confirmed by the users) -- C++98. I,
  however, couldn't find the package build logs (neither on Ubuntu nor on
  Debian) to confirm this.

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

** Also affects: libodb-sqlite (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: libodb-pgsql (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: libodb-boost (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: libodb-qt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: libodb (Ubuntu Zesty)
   Importance: Undecided
   Status: Confirmed

** Also affects: libodb-sqlite (Ubuntu Zesty)
   Importance: Undecided
   Status: Confirmed

** Also affects: libodb-pgsql (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: libodb-boost (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: libodb-qt (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: libodb (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: libodb-sqlite (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: libodb-pgsql (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: libodb-boost (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: libodb-qt (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: libodb (Ubuntu Zesty)
Milestone: None => ubuntu-17.02

** Changed in: libodb (Ubuntu Zesty)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: libodb-boost (Ubuntu Zesty)
Milestone: None => ubuntu-17.02

** Changed in: libodb-boost (Ubuntu Zesty)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: libodb-pgsql (Ubuntu Zesty)
Milestone: None => ubuntu-17.02

** Changed in: libodb-pgsql (Ubuntu Zesty)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: libodb-qt (Ubuntu Zesty)
Milestone: None => ubuntu-17.02

** Changed in: libodb-qt (Ubuntu Zesty)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: libodb-sqlite (Ubuntu Zesty)
Milestone: None => ubuntu-17.02

** Changed in: libodb-sqlite (Ubuntu Zesty)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  Incompatible builds of libodb and libodb-mysql

Status in libodb package in Ubuntu:
  Confirmed
Status in libodb-boost package in Ubuntu:
  New
Status in libodb-pgsql package in Ubuntu:
  New
Status in libodb-qt package in Ubuntu:
  New
Status in libodb-sqlite package in Ubuntu:
  Confirmed
Status in libodb source package in Xenial:
  New
Status in libodb-boost source package in Xenial:
  New
Status in libodb-pgsql source package in Xenial:
  New
Status in libodb-qt source package in Xenial:
  New
Status in libodb-sqlite source package in Xenial:
  New
Status in libodb source package in Yakkety:
  New
Status in libodb-boost source package in Yakkety:
  New
Status in libodb-pgsql source package in Yakkety:
  

[Group.of.nepali.translators] [Bug 1662116] Re: open-vm-tools 2:10.0.7-3227872-2ubuntu1 ADT test failure with linux-hwe 4.8.0-37.39~16.04.2

[Launchpad Bug Tracker]

This bug was fixed in the package open-vm-tools -
2:10.0.7-3227872-5ubuntu1~16.04.1

---
open-vm-tools (2:10.0.7-3227872-5ubuntu1~16.04.1) xenial; urgency=low

  * Backport to xenial for kernel 4.8 support.  (LP: #1662116)

 -- Andy Whitcroft   Mon, 06 Feb 2017 16:15:40 +

** Changed in: open-vm-tools (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/1662116

Title:
  open-vm-tools 2:10.0.7-3227872-2ubuntu1 ADT test failure with linux-
  hwe 4.8.0-37.39~16.04.2

Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Xenial:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/o/open-vm-tools/20170205_185226_c750f@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/i386/o/open-vm-tools/20170205_185956_c750f@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1662116/+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 1663229] [NEW] [SRU] New stable micro release 2.27

[Sergio Schvezov]

Public bug reported:

This is an SRU bug to release 2.27 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.27 and
https://launchpad.net/snapcraft/+milestone/2.27

** Affects: snapcraft (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: snapcraft (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: snapcraft (Ubuntu Yakkety)
 Importance: Undecided
 Status: New

** Affects: snapcraft (Ubuntu Zesty)
 Importance: Undecided
 Status: New

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

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

** Also affects: snapcraft (Ubuntu Yakkety)
   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/1663229

Title:
  [SRU] New stable micro release 2.27

Status in snapcraft package in Ubuntu:
  New
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  New
Status in snapcraft source package in Zesty:
  New

Bug description:
  This is an SRU bug to release 2.27 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.27 and
  https://launchpad.net/snapcraft/+milestone/2.27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1663229/+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 1607666] Re: sudo fails with host netgroup returned from freeipa

[Launchpad Bug Tracker]

This bug was fixed in the package sudo - 1.8.16-0ubuntu1.3

---
sudo (1.8.16-0ubuntu1.3) xenial; urgency=medium

  * sssd-doesnt-handle-netgroups.diff, sssd-fix-matching-loop.diff:
Only check username as part of the netgroup when netgroup_tuple is enabled.
(LP: #1607666)

 -- Timo Aaltonen   Sat, 14 Jan 2017 01:54:21 +0200

** Changed in: sudo (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/1607666

Title:
  sudo fails with host netgroup returned from freeipa

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Released
Status in sudo source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Sudo currently fails to validate netgroups against host netgroups returned 
from the sss plugin, see https://fedorahosted.org/freeipa/ticket/6139 for the 
glory details.

  This was fixed in sudo 1.8.17
  (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which
  I'd very much like to see backported to Ubuntu 16.04. If possible,
  updating sudo completely to 1.8.17 would be nice, since there have
  been quite a few improvements with regards to sss and freeipa and it
  would be a shame if we could not benefit from them given that 16.04 is
  LTS.

  [Test case]
  install the update, test that sudo works on a freeipa installation that uses 
netgroups

  [Regression potential]
   I looked at upstream commits to sssd.c, and there were no commits 
that touch this area, so chance of regressions should be slim

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1607666/+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 1662116] Re: open-vm-tools 2:10.0.7-3227872-2ubuntu1 ADT test failure with linux-hwe 4.8.0-37.39~16.04.2

[Adam Conrad]

Hello Andy, or anyone else affected,

Accepted open-vm-tools into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/open-vm-
tools/2:10.0.7-3227872-5ubuntu1~16.04.1 in a few hours, and then in the
-proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  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: open-vm-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: open-vm-tools (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: open-vm-tools (Ubuntu Xenial)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: open-vm-tools (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  open-vm-tools 2:10.0.7-3227872-2ubuntu1 ADT test failure with linux-
  hwe 4.8.0-37.39~16.04.2

Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Xenial:
  Fix Committed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/o/open-vm-tools/20170205_185226_c750f@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/i386/o/open-vm-tools/20170205_185956_c750f@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1662116/+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 1647036] Re: Client does not ACK auth/assoc responses from Cisco AP3800

[Launchpad Bug Tracker]

This bug was fixed in the package bcmwl - 6.30.223.271+bdcom-
0ubuntu1~1.1

---
bcmwl (6.30.223.271+bdcom-0ubuntu1~1.1) xenial; urgency=medium

  * debian/dkms.conf.in
- Drop obsolete patches.
  * New upstream release:
- Client does not ACK auth/assoc responses from Cisco AP3800 (LP: #1647036).

bcmwl (6.30.223.248+bdcom-0ubuntu11) yakkety; urgency=medium

  * debian/patches/0020-add-support-for-linux-4.8.patch:
- Fix whitespace issue that prevented DKMS from applying the patch.

bcmwl (6.30.223.248+bdcom-0ubuntu10) yakkety; urgency=medium

  * debian/dkms.conf.in,
debian/patches/0020-add-support-for-linux-4.8.patch:
- Add support for Linux 4.8. Thanks to Krzysztof Kolasa.

bcmwl (6.30.223.248+bdcom-0ubuntu9) yakkety; urgency=medium

  * debian/dkms.conf.in,
debian/patches/0020-add-support-for-linux-4.7.patch:
- Add support for Linux 4.7. Thanks to Vincent Gerris for pointing out
  the solution.

 -- Alberto Milone   Tue, 06 Dec 2016
16:29:07 +0100

** Changed in: bcmwl (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/1647036

Title:
  Client does not ACK auth/assoc responses from Cisco AP3800

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Trusty:
  Fix Committed
Status in bcmwl source package in Xenial:
  Fix Released
Status in bcmwl source package in Yakkety:
  Fix Committed
Status in bcmwl source package in Zesty:
  Fix Released

Bug description:
  This client does not ACK Assoc Responses from a Cisco 3800.  Traces
  attached.

  - Model:Dell XPS13 9343
  - OS Version:Ubuntu 14.04.5 LTS
  - WNIC:Broadcom BCM4352 rev. 03 driver version 6.30.223.248
  - SSID:user.wifi (WPA2/dot1x )
  - MAC address:c4:8e:8f:f5:4a:7f
  -Cisco AP : 3800 (wave 2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1647036/+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 1605974] Re: usbduxsigma_firmware.bin: old version causes driver crash

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.157.8

---
linux-firmware (1.157.8) xenial; urgency=medium

  * usbduxsigma_firmware.bin: old version causes driver crash (LP: #1605974)
- usbdux: usbduxsigma: created matching binary of the firmware

linux-firmware (1.157.7) xenial; urgency=medium

  * Intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22
(LP: #1647826)
- UBUNTU: SAUCE: Remove iwlwifi-8000C-22.ucode

 -- Seth Forshee   Fri, 06 Jan 2017 16:28:55
-0600

** Changed in: linux-firmware (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/1605974

Title:
  usbduxsigma_firmware.bin: old version causes driver crash

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released

Bug description:
  SRU Justification

  Impact: The usbduxsigma firmware is out of date and causes the driver
  to fail. This is fixed by updating the firmware from upstream linux-
  firmware.

  Test Case: Using the driver with the old firmware fails. Using it with
  the new firmware does not.

  Regression potential: The firmware is only used by the one driver so
  there is no potential for regression anywhere else, and the driver
  already isn't working with the old firmware.

  ---

  The firmware of the usbduxsigma (alongside with the usbduxsigma.c) was
  updated in 2015 during a major rewrite but its binary was still the
  old one which causes the kernel driver to fail.

  I've submitted a patch to the kernel people (see below).

  However, as a quick fix could you also apply the patch to the package
  directly to have this fixed now and then we can wait until it trickles
  down from the kernel.

  I'm the maintainer of both the firmware and the drivers.

  This affects both 32 and 64 bit distros.

  Best,
  /Bernd Porr (www.linux-usb-daq.co.uk)

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  linux-firmware:
    Installed: 1.157.2
    Candidate: 1.157.2
    Version table:
   *** 1.157.2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  Expect to happen: plug in a duxduxsigma device, start comedirecord and see 
the signals plotted
  Happens instead: plug in a duxduxsigma device, start comedirecord and GARBLED 
DATA shows up / crash
  Fix: install this patch (new version of the firmware binary)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.2 [modified: 
lib/firmware/usbduxsigma_firmware.bin]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 24 10:04:19 2016
  Dependencies:

  InstallationDate: Installed on 2013-12-09 (957 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131209)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to xenial on 2016-07-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1605974/+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 1647826] Re: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.157.8

---
linux-firmware (1.157.8) xenial; urgency=medium

  * usbduxsigma_firmware.bin: old version causes driver crash (LP: #1605974)
- usbdux: usbduxsigma: created matching binary of the firmware

linux-firmware (1.157.7) xenial; urgency=medium

  * Intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22
(LP: #1647826)
- UBUNTU: SAUCE: Remove iwlwifi-8000C-22.ucode

 -- Seth Forshee   Fri, 06 Jan 2017 16:28:55
-0600

** Changed in: linux-firmware (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/1647826

Title:
  intel 8260 doesn't work with linux kernel 4.8 when using ucode version
  22

Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Yakkety:
  Fix Released
Status in linux-firmware source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification

  Impact: The -22 firmware for iwlwifi introduces regressions with some
  hardware versus earlier firmware versions. As no newer firmware is
  available, the only fix is to revert back to the older firmware which
  does work.

  Test Case: Using the -22 firmware with affected hardware produces the
  behavior described below. The -21 firmware does not.

  Regression Potential: Switching back to -21 could cause some
  regressions with other hardware supported by this firmware. However as
  -22 causes some hardware to completely fail to work any regressions
  are almost certain to be less severe than the current problems.

  ---

  The -22 microcode for the intel 8260 wifi adapter has compatibility
  issues with Linux Kernel 4.8 under certain hardware configurations.

  The iwlwifi module crashes resulting in wifi failing with "device not
  ready" and kernel errors reported in dmesg.

  [   10.691115] iwlwifi :6e:00.0: Microcode SW error detected.
  Restarting 0x200.

  Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to
  fallback to the -21 ucode resolves the issue and wifi begins working
  normally again.

  This is an issue with Linux kernel 4.8 on both yakkety and xenial, so
  the bug doesn't currently affect users on xenial, but will begin to
  after the 16.04.2 HWE release.  Kernel 4.4 is unaffected because it
  doesn't attempt to use the -22 ucode

  The failure doesn't necessarily affect all machines of a given model
  with the 8260, but I can reproduce it on multiple laptops when 64GB of
  RAM are installed (4x16GB).  The RAM itself does not appear to be an
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+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