[Group.of.nepali.translators] [Bug 1559072] Re: [SRU] exceptions.from_response with webob 1.6.0 results in "AttributeError: 'unicode' object has no attribute 'get'"

[Zhao Chao]

** Also affects: python-troveclient
   Importance: Undecided
   Status: New

** Changed in: python-troveclient
   Importance: Undecided => Medium

** Changed in: python-troveclient
   Status: New => In Progress

** Changed in: python-troveclient
 Assignee: (unassigned) => Zhao Chao (zhaochao1984)

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

Title:
  [SRU] exceptions.from_response with webob 1.6.0 results in
  "AttributeError: 'unicode' object has no attribute 'get'"

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in Ubuntu Cloud Archive ocata series:
  Fix Released
Status in Ubuntu Cloud Archive pike series:
  Fix Released
Status in networking-midonet:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-novaclient:
  Fix Released
Status in python-openstackclient:
  Invalid
Status in python-troveclient:
  In Progress
Status in python-cinderclient package in Ubuntu:
  Fix Released
Status in python-novaclient package in Ubuntu:
  Fix Released
Status in python-cinderclient source package in Xenial:
  Fix Released
Status in python-novaclient source package in Xenial:
  Fix Released
Status in python-cinderclient source package in Yakkety:
  Won't Fix
Status in python-novaclient source package in Yakkety:
  Fix Released
Status in python-cinderclient source package in Zesty:
  Fix Released
Status in python-novaclient source package in Zesty:
  Fix Released

Bug description:
  [Impact] [Testcase]
  Running on Ubuntu 14.04.
  After installing nova from source in either the Liberty release or Mitaka, 
with WebOb 1.6.0, running any nova command generated this error:
  root@openstack-ubu-controller:~# nova service-list
  ERROR (AttributeError): 'unicode' object has no attribute 'get'

  The equivalent openstack commands work correctly. After downgrading
  WebOb to 1.5.1 AND restarting the nova-api service everything works.

  Detailed output from nova -debug service-list with the error:

  root@openstack-ubu-controller:~# nova --debug service-list
  DEBUG (extension:157) found extension EntryPoint.parse('v2token = 
keystoneauth1.loading._plugins.identity.v2:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('admin_token = 
keystoneauth1.loading._plugins.admin_token:AdminToken')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcauthcode = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAuthorizationCode')
  DEBUG (extension:157) found extension EntryPoint.parse('v2password = 
keystoneauth1.loading._plugins.identity.v2:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3password = 
keystoneauth1.loading._plugins.identity.v3:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcpassword = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectPassword')
  DEBUG (extension:157) found extension EntryPoint.parse('token = 
keystoneauth1.loading._plugins.identity.generic:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('v3token = 
keystoneauth1.loading._plugins.identity.v3:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('password = 
keystoneauth1.loading._plugins.identity.generic:Password')
  DEBUG (session:248) REQ: curl -g -i -X GET http://10.0.1.3:5000/v2.0 -H 
"Accept: application/json" -H "User-Agent: keystoneauth1/2.3.0 
python-requests/2.9.1 CPython/2.7.6"
  INFO (connectionpool:207) Starting new HTTP connection (1): 10.0.1.3
  DEBUG (connectionpool:387) "GET /v2.0 HTTP/1.1" 200 334
  DEBUG (session:277) RESP: [200] Content-Length: 334 Vary: X-Auth-Token 
Keep-Alive: timeout=5, max=100 Server: Apache/2.4.7 (Ubuntu) Connection: 
Keep-Alive Date: Fri, 18 Mar 2016 12:41:58 GMT Content-Type: application/json 
x-openstack-request-id: req-a0c68cd5-ea29-4391-942f-130cc69d15f8
  RESP BODY: {"version": {"status": "stable", "updated": 
"2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type": 
"application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links": 
[{"href": "http://10.0.1.3:5000/v2.0/;, "rel": "self"}, {"href": 
"http://docs.openstack.org/;, "type": "text/html", "rel": "describedby"}]}}

  DEBUG (v2:63) Making authentication request to 
http://10.0.1.3:5000/v2.0/tokens
  DEBUG (connectionpool:387) "POST /v2.0/tokens HTTP/1.1" 200 2465
  DEBUG (session:248) REQ: curl -g -i -X GET 
http://10.0.1.3:8774/v1.1/b77d640e127e488fb42a7c0716ba53a5 -H "User-Agent: 
python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: 
{SHA1}381893576ad46c62b587f4963d769b89441b919a"
  INFO (connectionpool:207) Starting new HTTP connection (1): 10.0.1.3
  DEBUG (connectionpool:387) "GET /v1.1/b77d640e127e488fb42a7c0716ba53a5 
HTTP/1.1" 404 112
  DEBUG (session:277) 

[Group.of.nepali.translators] [Bug 1746628] Re: New walinuxagent upstream version: 2.2.21

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.2.21-0ubuntu1

---
walinuxagent (2.2.21-0ubuntu1) bionic; urgency=medium

  * New upstream release (LP: #1746628).
  * debian/patches/disable_import_test.patch: refreshed patch.

 -- Łukasz 'sil2100' Zemczak   Mon, 05 Feb
2018 17:25:14 +0100

** Changed in: walinuxagent (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  New walinuxagent upstream version: 2.2.21

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  New
Status in walinuxagent source package in Xenial:
  New
Status in walinuxagent source package in Artful:
  New

Bug description:
  [Impact]
  This release contains both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/walinuxagentUpdates

  The Microsoft Azure Linux Agent team will execute their testsuite, which
  includes extension testing , against the walinuxagent that is in
  -proposed.  A successful run will be required before the proposed walinuxagent
  can be let into -updates.

  The CPC team will be in charge of attaching a summary of testing to the bug.  
CPC team members will not
  mark ‘verification-done’ until this has happened.

  [Changelog]

  * 2.2.21:
   - Nothing mentioned

  * 2.2.20:
   - [#945] Download operation failure

  * 2.2.19:
   - [#929] wire.py#update_goal_state does not handle out-of-date GoalState 
errors
   - [#908] Set Files to 0400 in /var/lib/waagent
   - [#906] Hardcoded value for sshd's ClientAliveInterval (180)
   - [#899] Improve HeartBeat Event
   - [#898] Send dummy status if extension fails to write a #.status file
   - [#897] 'Target handler state' wall of errors
   - [#896] End of Line Comments are Not Supported nor Handled
   - [#891] Create a Telemetry Event to Track Custom Data Execution
   - [#884] Cleanup Old Goal State and Extension Cache
   - [#876] The agent should use a scaling back-off when retrying HTTP requests
   - [#869] The agent should report OS information in the correct JSON format.
   - [#822] Update docs

  * 2.2.18
   - [#868] Fix for sudoer update
   - [#886] Agent should not update outside of goal state
   - [#889] Firewall removal should not retry

  [Original Description]

  Hi Canonical Team,
  We are pleased to announce a new release of the Linux Agent, 2.2.21, this has 
multiple fixes.

  https://github.com/Azure/WALinuxAgent/releases/tag/v2.2.21

  Please can you take this, and package it?

  After it is packaged in proposed, can the proposed agent package be
  baked into a daily image for full end to end testing?

  Thanks,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1746628/+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 1737364] Re: 16.04: Fix CVE-2016-1968 and CVE-2016-1624 for brotli

[Launchpad Bug Tracker]

This bug was fixed in the package brotli - 0.3.0+dfsg-2ubuntu1

---
brotli (0.3.0+dfsg-2ubuntu1) xenial-security; urgency=medium

  * SECURITY UPDATE: integer underflow in dec/decode.c (LP: #1737364)
- debian/patches/fix-integer-underflow.patch: upstream patch via Debian
- CVE-2016-1624
- CVE-2016-1968

 -- Jeremy Bicha   Sat, 09 Dec 2017 17:45:50 -0500

** Changed in: brotli (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/1737364

Title:
  16.04: Fix CVE-2016-1968 and CVE-2016-1624 for brotli

Status in brotli package in Ubuntu:
  Fix Released
Status in brotli source package in Xenial:
  Fix Released

Bug description:
  Impact
  --
  Integer underflow could be targeted as a buffer overflow
  https://security-tracker.debian.org/tracker/source-package/brotli

  Debdiff attached.

  Because brotli is embedded in web browsers for WOFF2 support (to be
  somewhat fixed by the proposed brotli MIR), this issue was already
  mentioned in

  https://usn.ubuntu.com/usn/USN-2917-1/ (Firefox)
  Luke Li discovered a buffer overflow during Brotli decompression in some
  circumstances. If a user were tricked in to opening a specially crafted
  website, an attacker could potentially exploit this to cause a denial of
  service via application crash, or execute arbitrary code with the
  privileges of the user invoking Firefox. (CVE-2016-1968)

  https://usn.ubuntu.com/usn/USN-2895-1/ (Oxide)
  An integer underflow was discovered in Brotli. If a user were tricked in
  to opening a specially crafted website, an attacker could potentially
  exploit this to cause a denial of service via application crash, or
  execute arbitrary code with the privileges of the user invoking the
  program. (CVE-2016-1624)

  Regression Potential
  
  This update was published in Debian unstable/testing as 0.3.0+dfsg-3 from 
late March to mid June 2016 when it was superseded by a newer version. The 
Ubuntu security sync tool wasn't able to retrieve this version now.

  brotli has no reverse dependencies in Ubuntu and is in universe.

  Testing Done
  
  Only a simple build test.

  There is a build test to ensure basic functionality of brotli with
  both python2 and python3.

  Other Info
  --
  The main purpose of this security update is to clear up the security history 
section of MIR LP: #1737053.

  It is mentioned in the MIR bug that it is intended for brotli 1.0.2 to
  be backported to Ubuntu 16.04 and 17.10 as a security update (and
  promoted to main there), after 17.04 reaches End of Life.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brotli/+bug/1737364/+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 1743762] Re: Security bug in XMLTooling-C before 1.6.3 [CVE-2018-0486]

[Marc Deslauriers]

I am unsubscribing ubuntu-security-sponsors for now since there is no
artful debdiff to review. Please subscribe ubuntu-security-sponsors
again once an appropriate debdiff is available. Thanks!

** Changed in: xmltooling (Ubuntu Bionic)
   Status: Triaged => Fix Released

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

Title:
  Security bug in XMLTooling-C before 1.6.3 [CVE-2018-0486]

Status in xmltooling package in Ubuntu:
  Fix Released
Status in xmltooling source package in Trusty:
  Fix Released
Status in xmltooling source package in Xenial:
  Fix Released
Status in xmltooling source package in Artful:
  Triaged
Status in xmltooling source package in Bionic:
  Fix Released

Bug description:
  From the Debian bug report at
  https://www.debian.org/security/2018/dsa-4085:

  Philip Huppert discovered the Shibboleth service provider is
  vulnerable to impersonation attacks and information disclosure due to
  mishandling of DTDs in the XMLTooling XML parsing library. For
  additional details please refer to the upstream advisory at
  https://shibboleth.net/community/advisories/secadv_20180112.txt

  For the oldstable distribution (jessie), this problem has been
  fixed in version 1.5.3-2+deb8u2.

  The stable distribution (stretch) is not affected.

  We recommend that you upgrade your xmltooling packages.

  For the detailed security status of xmltooling please refer to its
  security tracker page at: https://security-
  tracker.debian.org/tracker/xmltooling

  
  This bug is fixed upstream in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xmltooling/+bug/1743762/+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 1737364] Re: 16.04: Fix CVE-2016-1968 and CVE-2016-1624 for brotli

[Marc Deslauriers]

ACK on the debdiff in comment #1. Package is building now and will be
released as a security update. Thanks!

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

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

** Changed in: brotli (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/1737364

Title:
  16.04: Fix CVE-2016-1968 and CVE-2016-1624 for brotli

Status in brotli package in Ubuntu:
  Fix Released
Status in brotli source package in Xenial:
  Fix Committed

Bug description:
  Impact
  --
  Integer underflow could be targeted as a buffer overflow
  https://security-tracker.debian.org/tracker/source-package/brotli

  Debdiff attached.

  Because brotli is embedded in web browsers for WOFF2 support (to be
  somewhat fixed by the proposed brotli MIR), this issue was already
  mentioned in

  https://usn.ubuntu.com/usn/USN-2917-1/ (Firefox)
  Luke Li discovered a buffer overflow during Brotli decompression in some
  circumstances. If a user were tricked in to opening a specially crafted
  website, an attacker could potentially exploit this to cause a denial of
  service via application crash, or execute arbitrary code with the
  privileges of the user invoking Firefox. (CVE-2016-1968)

  https://usn.ubuntu.com/usn/USN-2895-1/ (Oxide)
  An integer underflow was discovered in Brotli. If a user were tricked in
  to opening a specially crafted website, an attacker could potentially
  exploit this to cause a denial of service via application crash, or
  execute arbitrary code with the privileges of the user invoking the
  program. (CVE-2016-1624)

  Regression Potential
  
  This update was published in Debian unstable/testing as 0.3.0+dfsg-3 from 
late March to mid June 2016 when it was superseded by a newer version. The 
Ubuntu security sync tool wasn't able to retrieve this version now.

  brotli has no reverse dependencies in Ubuntu and is in universe.

  Testing Done
  
  Only a simple build test.

  There is a build test to ensure basic functionality of brotli with
  both python2 and python3.

  Other Info
  --
  The main purpose of this security update is to clear up the security history 
section of MIR LP: #1737053.

  It is mentioned in the MIR bug that it is intended for brotli 1.0.2 to
  be backported to Ubuntu 16.04 and 17.10 as a security update (and
  promoted to main there), after 17.04 reaches End of Life.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brotli/+bug/1737364/+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 1717040] Re: Please backport libzstd 1.3.1+dfsg-1 (universe) from artful

[Launchpad Bug Tracker]

This bug was fixed in the package libzstd - 1.3.3+dfsg-1ubuntu1

---
libzstd (1.3.3+dfsg-1ubuntu1) bionic; urgency=medium

  * d/control: New transitional package libzstd1-dev to facilitate the release
upgrade from xenial (LP: #1717040)
  * d/rules: also run the clean Makefile target in the pzstd directory.

 -- Andreas Hasenack   Fri, 02 Feb 2018 11:29:34
-0200

** Changed in: libzstd (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  Please backport libzstd 1.3.1+dfsg-1 (universe) from artful

Status in libzstd package in Ubuntu:
  Fix Released
Status in libzstd source package in Xenial:
  In Progress
Status in libzstd source package in Zesty:
  Won't Fix
Status in libzstd source package in Artful:
  In Progress
Status in libzstd source package in Bionic:
  Fix Released

Bug description:
  [Special SRU Notes]

  The Artful SRU must be published before the Xenial SRU in order to
  preserve the upgrade path.

  [Impact]

   * libzstd v0.5.1 is an experimental version,
     which generates and read an experimental format
     incompatible with official libzstd v1+ format.

   * Backporting a newer version >= v1.0, such as artful's v1.3.1,
     fixes this issue

   * This backport/SRU is being requested by upstream.

  [Test Case]

  There are three major test cases: compression tests, package upgrade
  tests, and release upgrade tests.

  This SRU has so many tests because it's introducing a new package and
  a carefully thought out upgrade plan.

  a) compression tests

   * with the pristine package from each release, compress a big file.
  For example, /usr/bin/snap. Name the resulting compressed file
  according to the version that was used to compress it, like this:

  Xenial:
  $ zstd /usr/bin/snap -o snap.0.5.1.zst
  Compressed 15528016 bytes into 4134889 bytes ==> 26.63%

  Zesty:
  $ zstd /usr/bin/snap -o snap.1.1.2.zst
  /usr/bin/snap: 30.59%   (10825608 => 3311295 bytes, snap.1.1.2.zst)

   * Upgrade to the package made available through this SRU and compress
  it again:

  Xenial:
  $ zstd /usr/bin/snap -o snap.1.3.1.zst
  /usr/bin/snap: 25.11%   (15528016 => 3899137 bytes, snap.1.3.1.zst)

  Zesty:
  $ zstd /usr/bin/snap -o snap.1.3.1.zst
  /usr/bin/snap: 30.59%   (10825608 => 3311290 bytes, snap.1.3.1.zst)

  * Uncompress all the generated files using the new version. This
  proves it can handle files compressed by the old one:

  Xenial:
  $ zstd -d snap.0.5.1.zst -o snap.0.5.1
  snap.0.5.1.zst  : 15528016 bytes
  $ zstd -d snap.1.3.1.zst -o snap.1.3.1
  snap.1.3.1.zst  : 15528016 bytes

  Zesty:
  $ zstd -d snap.1.1.2.zst -o snap.1.1.2
  snap.1.1.2.zst  : 10825608 bytes
  $ zstd -d snap.1.3.1.zst -o snap.1.3.1
  snap.1.3.1.zst  : 10825608 bytes

   * Take md5sums of all uncompressed files and the original. They must
  of course match:

  Xenial:
  $ md5sum /usr/bin/snap snap.0.5.1 snap.1.3.1
  0fa4fa69d79ef4685aaa93be5b3aa33f  /usr/bin/snap
  0fa4fa69d79ef4685aaa93be5b3aa33f  snap.0.5.1
  0fa4fa69d79ef4685aaa93be5b3aa33f  snap.1.3.1

  Zesty:
  $ md5sum /usr/bin/snap snap.1.1.2 snap.1.3.1
  ba0a3ef5f519688bc5b0b58f190e73a4  /usr/bin/snap
  ba0a3ef5f519688bc5b0b58f190e73a4  snap.1.1.2
  ba0a3ef5f519688bc5b0b58f190e73a4  snap.1.3.1

  * Downgrade zstd back to the original version of the ubuntu release
  you are testing:

  Xenial:
  $ sudo apt install zstd=0.5.1-1

  Zesty:
  $ sudo apt install zstd=1.1.2-1 libzstd1=1.1.2-1

  * Try to decompress the zst file created with the 1.3.1 version from the 
previous test. In xenial only, it should fail to recognize the format:
  $ zstd -d snap.1.3.1.zst -o /dev/null
  zstd: /dev/null already exists; do you wish to overwrite (y/N) ? y
  zstd: snap.1.3.1.zst: not in zstd format

  In zesty it should work:
  $ zstd -d snap.1.3.1.zst -o snap.1.3.1-new
  snap.1.3.1.zst  : 9909192 bytes

  * Still in zesty, compare the md5, which should match:
  $ md5sum snap.1.3.1-new /usr/bin/snap
  7c980688861eef598a56c7970d952028  snap.1.3.1-new
  7c980688861eef598a56c7970d952028  /usr/bin/snap

  
  b) package upgrade tests
  b.1)XENIAL

  * Install the xenial original packages:
  $ sudo apt install zstd=0.5.1-1 libzstd0=0.5.1-1 libzstd-dev=0.5.1-1

  * Enable xenial-proposed and verify that a dist-upgrade will upgrade zstd, 
pull in the new libzstd1, and leave libzstd-dev alone:
  $ sudo apt dist-upgrade
  ...
  The following NEW packages will be installed:
libzstd1
  The following packages will be upgraded:
zstd
  1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.

  * In the end you will have these installed, at these versions:
  ii  libzstd-dev  0.5.1-1 
  ii  libzstd0 0.5.1-1 
  ii  libzstd1   

[Group.of.nepali.translators] [Bug 1709649] Re: 229 backport for race between explicit mount and handling automount

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu21.1

---
systemd (229-4ubuntu21.1) xenial-security; urgency=medium

  * SECURITY UPDATE: remote DoS in resolved (LP: #1725351)
- debian/patches/CVE-2017-15908.patch: fix loop on packets with pseudo
  dns types in src/resolve/resolved-dns-packet.c.
- CVE-2017-15908
  * SECURITY UPDATE: access to automounted volumes can lock up
(LP: #1709649)
- debian/patches/CVE-2018-1049.patch: ack automount requests even when
  already mounted in src/core/automount.c.
- CVE-2018-1049

 -- Marc Deslauriers   Thu, 01 Feb 2018
07:42:30 -0500

** Changed in: systemd (Ubuntu Xenial)
   Status: Triaged => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-1049

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

Title:
  229 backport for  race between explicit mount and handling automount

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  In systemd prior to 234 a race exists between .mount and .automount units 
such that automount requests from kernel may not be serviced by systemd 
resulting in kernel holding the mountpoint and any processes that try to use 
said mount will hang. A race like this may lead to denial of service, until 
mount points are unmounted.

  [Testcase]
  Create a race between .mount and .automount units, such that automout request 
is serviced after .mount unit has been started. Observe a hang.
  More detailed steps are available at 
https://github.com/systemd/systemd/pull/5916

  [Butfix]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/e7d54bf58789545a9eb0b3964233defa0b007318

  [Regression Potential]
  The underlying logic of starting/stopping/triggering units is unchanged. 
However, there the logic as to when to send automout_send_ready() is relaxed, 
such that it is always sent whenever unit is already mounted. This is done to 
explicitly cope with late arrival of the incoming [aircraft] automount request.

  [Original Bug report / request]

  Hi,

  We have a blocking issue in systemd for the following release

  ```
  NAME="Ubuntu"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.3 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
  ```

  This release runs systemd229, we are affected by the following auto-
  mouting race condition

  ```
  https://github.com/systemd/systemd/pull/5916
  ```

  Is back porting  the fix to the release 229 an option?

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1709649/+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 1733276] Re: Cannot resize partitions on NVME devices due to bad device name parsing

[Eric Desrochers]

patch for artful

** Patch added: "lp1733276-partman-artful.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1733276/+attachment/5049270/+files/lp1733276-partman-artful.debdiff

** Changed in: partman-partitioning (Ubuntu Artful)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: partman-partitioning (Ubuntu Zesty)
   Status: New => Won't Fix

** Changed in: partman-partitioning (Ubuntu Xenial)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: partman-partitioning (Ubuntu Trusty)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: partman-partitioning (Ubuntu Artful)
   Status: New => In Progress

** Changed in: partman-partitioning (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: partman-partitioning (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: partman-partitioning (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: partman-partitioning (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: partman-partitioning (Ubuntu Trusty)
   Status: New => In Progress

** Description changed:

  [Impact]
  
  It is not possible to resize NVME partitions in the Ubiquity installer.
  NVME devices have an unusual device format, specifically e.g. /dev/nvme0n1p1 
that has two 'sections' that potentially look like partitions.
  
  Based on the error message, it seems that this device name is being
  parsed incorrectly and it attempts to use the device path /dev/nvme0n1
  instead of /dev/nvme0n1p1
  
  ** See attachment (screenshot) took in action :
  - resize.png
  - resize_impossible.png
  
  [Test Case]
  
  You can test this using qemu and a virtual NVME device. If you toggle
  the same device/partition between a virtual SCSI/IDE and an NVME device
  - the issue appears and disappears.
  
  Commands you can use to replicate the issue - unpack netboot.tar.gz into
  the local directory and then
  
  dd if=/dev/zero of=nvme.disk bs=1M count=16384
  
  NVME:
  qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw -device 
nvme,drive=drv0,serial=foo -enable-kvm -smp 2 -m 1024 -kernel 
xenial/ubuntu-installer/amd64/linux -initrd 
xenial/ubuntu-installer/amd64/initrd.gz
  
  SCSI:
  qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drv0,id=virtio-disk0,bootindex=1
 -enable-kvm -smp 2 -m 1024 -kernel ubuntu-installer/amd64/linux -initrd 
ubuntu-installer/amd64/initrd.gz
  
  [Regression Potential]
  
   * Low risk of regression, with this patch, partman, will be more robust and 
align with what disk_name() in the kernel does 
(linux.git/tree/block/partition-generic.c). It is sufficient to check
  whether the last character is a digit.
  
  * The patch may also fixes (or at least prevent for the future) other
  potential similar devices issue and not explicitly fixing and/or benefit
  NVMe device types.
  
  [Other Info]
+ 
+ * Debian upstream bug :
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820818
  
  * Debian upstream fix :
  
https://anonscm.debian.org/cgit/d-i/partman-partitioning.git/commit/?id=01087125e07a7b22da589e8116f9ef7a26275006
  
  * Commit [01087125]
  Make get_real_device() both simpler and more generic (See: #820818).
  Looking at the implementation of the disk_name() function in the kernel
  (linux.git/tree/block/partition-generic.c), it is sufficient to check
  whether the last character is a digit.
  
  * $ git describe --contains 01087125e07a7b22da589e8116f9ef7a26275006
  116~2
  
  * $ rmadison partman-partitioning
   partman-partitioning | 85ubuntu2| precise/main/debian-installer
   partman-partitioning | 99ubuntu1| trusty/main/debian-installer
   partman-partitioning | 110ubuntu4.1 | xenial-updates/main/debian-installer
   partman-partitioning | 114ubuntu2   | zesty/main/debian-installer
   partman-partitioning | 114ubuntu2   | artful/main/debian-installer
   partman-partitioning | 120ubuntu1   | bionic/main/debian-installer
  
  [Original Description]
  
  It is not possible to resize NVME partitions in the Ubiquity installer.
  This appears to affect multiple filesystem types including NTFS and
  ext4.
  
  NVME devices have an unusual device format, specifically e.g.
  /dev/nvme0n1p1 that has two 'sections' that potentially look like
  partitions.
  
  Based on the error message, it seems that this device name is being
  parsed incorrectly and it attempts to use the device path /dev/nvme0n1
  instead of /dev/nvme0n1p1
  
  You can test this using qemu and a virtual NVME device.  If you toggle
  the same device/partition between a virtual SCSI/IDE and an NVME device
  - the issue appears and disappears.
  
  Commands you can use to replicate the issue - unpack netboot.tar.gz into
  the local directory and then
  
  dd if=/dev/zero of=nvme.disk bs=1M count=16384
  
  NVME:
  qemu-system-x86_64 -drive 

[Group.of.nepali.translators] [Bug 1741989] Re: Drop libpam-cracklib from gce-compute-image-packages Recommends

[Łukasz Zemczak]

Hello Dan, or anyone else affected,

Accepted gce-compute-image-packages into artful-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/gce-compute-image-packages/20180129+dfsg1-0ubuntu1~17.10.0 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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

** Also affects: gce-compute-image-packages (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gce-compute-image-packages (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: gce-compute-image-packages (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: gce-compute-image-packages (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  Drop libpam-cracklib from gce-compute-image-packages Recommends

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  New
Status in gce-compute-image-packages source package in Xenial:
  Fix Committed
Status in gce-compute-image-packages source package in Artful:
  Fix Committed

Bug description:
  The GCE image build process currently installs gce-compute-image-
  packages (amongst others) with --no-install-recommends.  We would like
  to be able to install Recommends, but including libpam-cracklib on the
  image would represent a substantial change in behaviour for users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1741989/+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 1746588] Re: Update google compute-image-packages to 20180129

[Łukasz Zemczak]

Hello Balint, or anyone else affected,

Accepted gce-compute-image-packages into artful-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/gce-compute-image-packages/20180129+dfsg1-0ubuntu1~17.10.0 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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

** Also affects: gce-compute-image-packages (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gce-compute-image-packages (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: gce-compute-image-packages (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: gce-compute-image-packages (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  Update google compute-image-packages to 20180129

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  New
Status in gce-compute-image-packages source package in Xenial:
  Fix Committed
Status in gce-compute-image-packages source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  compute-image-packages is provided by Google for installation within
  guests that run on Google Compute Engine. It is a collection of tools
  and daemons, packaged as gce-compute-image-packages, that ensure that
  the Ubuntu images published to GCE run properly on their platform.

  Cloud platforms evolve at a rate that can't be handled in six-month
  increments, and they will often develop features that they would like
  to be available to customers who don't want to upgrade from earlier
  Ubuntu releases. As such, updating gce-compute-image-packages to more
  recent upstream releases is required within all Ubuntu releases, so
  they continue to function properly in their environment.

  With this release we also add a new binary package to the suite -
  google-compute-engine-oslogin which is for a future feature of using
  OS Login on GCE VM instances.

  [Test Case]

  When a new version of gce-compute-image-packages is uploaded to
  -proposed, the following will be done:

   * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
   * the CPC team will write new automated tests to cover new testable 
functionality (if any) in the new package
   * the automated testing that the CPC team normally runs against GCE images 
before they are published will be run against the -proposed image
   * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

  If all the testing indicates that the image containing the new package
  is acceptable, verification will be considered to be done.

  [Other Information]

  This bug is used for tracking of releasing the new upstream version
  for all supported series, as per the approved policy mentioned in the
  following MRE:

  https://wiki.ubuntu.com/gce-compute-image-packages-Updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1746588/+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 1731595] Re: L3 HA: multiple agents are active at the same time

[Corey Bryant]

This bug was fixed in the package neutron - 2:8.4.0-0ubuntu6~cloud0
---

 neutron (2:8.4.0-0ubuntu6~cloud0) trusty-mitaka; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 neutron (2:8.4.0-0ubuntu6) xenial; urgency=medium
 .
   * d/p/set-ha-network-port-to-down-when-l3-agent-starts.patch,
 d/p/call-update_all_ha_network_port_statuses-on-agent-start.patch:
 Cherry-pick from upstream stable/ocata branch to prevent multiple
 masters for L3HA (LP: #1731595).


** Changed in: cloud-archive/mitaka
   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/1731595

Title:
  L3 HA: multiple agents are active at the same time

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in Ubuntu Cloud Archive ocata series:
  Fix Released
Status in Ubuntu Cloud Archive pike series:
  Fix Released
Status in Ubuntu Cloud Archive queens series:
  Fix Released
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Xenial:
  Fix Released
Status in neutron source package in Zesty:
  Won't Fix
Status in neutron source package in Artful:
  Fix Released
Status in neutron source package in Bionic:
  Fix Released

Bug description:
  OS: Xenial, Ocata from Ubuntu Cloud Archive
  We have three neutron-gateway hosts, with L3 HA enabled and a min of 2, max 
of 3.  There are approx. 400 routers defined.

  At some point (we weren't monitoring exactly) a number of the routers
  changed from being one active, and 1+ others standby, to >1 active.
  This included each of the 'active' namespaces having the same IP
  addresses allocated, and therefore traffic problems reaching
  instances.

  Removing the routers from all but one agent, and re-adding, resolved
  the issue.  Restarting one l3 agent also appeared to resolve the
  issue, but very slowly, to the point where we needed the system alive
  again faster and reverted to removing/re-adding.

  At the same time, a number of routers were listed without any agents
  active at all.  This situation appears to have been resolved by adding
  routers to agents, after several minutes downtime.

  I'm finding it very difficult to find relevant keepalived messages to
  indicate what's going on, but what I do notice is that all the agents
  have equal priority and are configured as 'backup'.

  I am trying to figure out a way to get a reproducer of this, it might
  be that we need to have a large number of routers configured on a
  small number of gateways.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1731595/+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 1708245] Re: shim can't enable validation and enroll keys in one sitting

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.02~beta3-4ubuntu7.1

---
grub2 (2.02~beta3-4ubuntu7.1) artful; urgency=medium

  * Cherry-pick upstream patch to change the default TSC calibration method
to pmtimer on EFI systems (LP: #1734278)
  * util/grub-install.c: Use fallback and MokManager EFI binary names without
the .signed extension now that shim handles signing via sbsigntool
natively. (LP: #1708245)
- debian/patches/grub-install-extra-removable.patch
- debian/patches/install_signed.patch

 -- Mathieu Trudel-Lapierre   Wed, 17 Jan 2018
11:51:20 -0500

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

** Changed in: grub2 (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/1708245

Title:
  shim can't enable validation and enroll keys in one sitting

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Zesty:
  Won't Fix
Status in grub2-signed source package in Zesty:
  Won't Fix
Status in shim source package in Zesty:
  Won't Fix
Status in shim-signed source package in Zesty:
  Won't Fix
Status in grub2 source package in Artful:
  Fix Released
Status in grub2-signed source package in Artful:
  Fix Released
Status in shim source package in Artful:
  Fix Committed
Status in shim-signed source package in Artful:
  Fix Released

Bug description:
  [Impact]

  
  [Test cases]
  First, update shim to the newest version.

  = Boot test =
  1) Reboot.
  2) Validate that the system boots correctly in UEFI mode.

  
  = Key enrollment =
  1) Create a new x.509 certificate to import into MOK.
  2) Run 'mokutil --import cert.der'
  3) Reboot
  4) Execute the steps described on screen to enroll the new key.

  
  = Toggling validation =
  1) Run 'mokutil --disable-validation'
  2) Reboot.
  3) Follow the steps on screen to toggle validation.
  4) Boot to the system, validate that validation is disabled:
  $ sudo hexdump -Cv /sys/firmware/efi/efivars/MokSBStateRT-*

  The output should read the last byte as a 1.

  5) Run 'mokutil --enable-validation'
  6) Reboot.
  7) Follow the steps on screen to toggle validation.
  8) Boot to the system, validate that validation is enabled again:
  $ hexdump -Cv /sys/firmware/efi/efivars/MokSBStateRT-*

  The file should not exist.

  
  = Toggling validation and enrolling =
  1) Disable validation, as above, and reboot into the system.
  2) Create a new x.509 certificate to import into MOK.
  3) Run 'mokutil --import cert.der'
  4) Run 'mokutil --enable-validation'
  5) Reboot.
  6) Follow the steps on screen to proceed through toggling validation in shim.
  Once that step is done, you should be returned to the MokManager menu to 
complete further steps.
  7) Follow the steps on screen to enroll the new key.
  Once completed, you should have the option at the bottom of the menu to 
Reboot.
  8) Reboot into the system.
  9) Validate that MOK validation is enabled and the new key is enrolled:

  Run:

  $ sudo hexdump -Cv /sys/firmware/efi/efivars/MokSBStateRT-*

  The file should not exist.

  Then run:
  $ sudo cat /proc/keys

  And make sure the key you enrolled is present.

  
  [Regression potential]
  Failure to boot or validate validly signed EFI binaries (bootloader) might be 
possible regressions. The shim update modifies the enrollment process for new 
keys, and as such it might also be possible for the enrollment of a new key to 
fail in MokManager, rendering the validation process unstable: it may fail to 
validate validly signed EFI binaries signed by keys already present in the 
database or that were to be enrolled.

  
  ---

  We want to enable validation and enroll a new key in shim all at the
  same time on upgrade from previous releases.

  Curently, shim will wipe out all pending variables when it's done
  processing one of them (because it wants to reboot immediately after
  that action). That means if we re-enable validation, we lose the
  request to enroll the key, and vice-versa.

  This needs fixing as it would otherwise badly impact upgrades from
  zesty and earlier; where we might have walked users through disabling
  validation.

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

___
Mailing list: 

[Group.of.nepali.translators] [Bug 722950] Re: ctrl-x does not work in grub-efi

[Launchpad Bug Tracker]

This bug was fixed in the package grub2-signed - 1.66.16

---
grub2-signed (1.66.16) xenial; urgency=medium

  * Rebuild against grub2 2.02~beta2-36ubuntu3.16. (LP: #722950,
#1708245)

 -- dann frazier   Thu, 11 Jan 2018 10:04:44
-0700

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

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

Title:
  ctrl-x does not work in grub-efi

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  New
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Zesty:
  Won't Fix
Status in grub2-signed source package in Zesty:
  Won't Fix
Status in grub2 source package in Artful:
  Fix Released
Status in grub2-signed source package in Artful:
  Fix Released

Bug description:
  [Impact]
  On some UEFI platforms, useful key combinations fail to work over the serial 
console. In particular, ^x/F10 - one of which is needed to boot after 
interactively editing the boot menu. This leaves end users without a sane way 
to tweak command line arguments, and potentially other system recovery tasks.

  [Test Case]
  Boot such a UEFI system to the GRUB menu. Press 'e' to edit the commandline, 
then attempt to continue the boot using "^x".

  [Regression Risk]
  The proposed fix is a cherry-pick from upstream that we've been shipping in 
Ubuntu since 17.10 w/o any any known regressions. However, it is possible that 
such regressions exist - e.g. if a platform's firmware has a buggy 
implementation fo the EFI_SIMPLE_TEXT_INPUT_EX protocol.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/722950/+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 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Launchpad Bug Tracker]

This bug was fixed in the package modemmanager - 1.6.4-1ubuntu0.16.04.1

---
modemmanager (1.6.4-1ubuntu0.16.04.1) xenial; urgency=medium

  * Backport to xenial (LP: #1725190).
  * debian/control: bump down debhelper to xenial vesion.

 -- Łukasz 'sil2100' Zemczak   Tue, 28 Nov
2017 12:40:02 +0100

** Changed in: modemmanager (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/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Fix Released
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Released
Status in libqmi source package in Xenial:
  Fix Released
Status in modemmanager source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+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 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Yuan-Chen Cheng]

** Changed in: oem-priority
   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/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Fix Released
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Released
Status in libqmi source package in Xenial:
  Fix Released
Status in modemmanager source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+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 1731595] Re: L3 HA: multiple agents are active at the same time

[Launchpad Bug Tracker]

This bug was fixed in the package neutron - 2:8.4.0-0ubuntu6

---
neutron (2:8.4.0-0ubuntu6) xenial; urgency=medium

  * d/p/set-ha-network-port-to-down-when-l3-agent-starts.patch,
d/p/call-update_all_ha_network_port_statuses-on-agent-start.patch:
Cherry-pick from upstream stable/ocata branch to prevent multiple
masters for L3HA (LP: #1731595).

 -- Corey Bryant   Tue, 12 Dec 2017 13:36:08
-0500

** Changed in: neutron (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/1731595

Title:
  L3 HA: multiple agents are active at the same time

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in Ubuntu Cloud Archive ocata series:
  Fix Released
Status in Ubuntu Cloud Archive pike series:
  Fix Released
Status in Ubuntu Cloud Archive queens series:
  Fix Released
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Xenial:
  Fix Released
Status in neutron source package in Zesty:
  Won't Fix
Status in neutron source package in Artful:
  Fix Released
Status in neutron source package in Bionic:
  Fix Released

Bug description:
  OS: Xenial, Ocata from Ubuntu Cloud Archive
  We have three neutron-gateway hosts, with L3 HA enabled and a min of 2, max 
of 3.  There are approx. 400 routers defined.

  At some point (we weren't monitoring exactly) a number of the routers
  changed from being one active, and 1+ others standby, to >1 active.
  This included each of the 'active' namespaces having the same IP
  addresses allocated, and therefore traffic problems reaching
  instances.

  Removing the routers from all but one agent, and re-adding, resolved
  the issue.  Restarting one l3 agent also appeared to resolve the
  issue, but very slowly, to the point where we needed the system alive
  again faster and reverted to removing/re-adding.

  At the same time, a number of routers were listed without any agents
  active at all.  This situation appears to have been resolved by adding
  routers to agents, after several minutes downtime.

  I'm finding it very difficult to find relevant keepalived messages to
  indicate what's going on, but what I do notice is that all the agents
  have equal priority and are configured as 'backup'.

  I am trying to figure out a way to get a reproducer of this, it might
  be that we need to have a large number of routers configured on a
  small number of gateways.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1731595/+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 722950] Re: ctrl-x does not work in grub-efi

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.16

---
grub2 (2.02~beta2-36ubuntu3.16) xenial; urgency=medium

  [ dann frazier ]
  * Use EFI_SIMPLE_TEXT_INPUT_EX to support key combinations.
(LP: #722950)

  [ Mathieu Trudel-Lapierre ]
  * util/grub-install.c: Use MokManager EFI binary name without
the .signed extension now that shim handles signing via sbsigntool
natively. (LP: #1708245)
- debian/patches/install_signed.patch
  * debian/control: Breaks shim << 13 due to the renamed MokManager binary.

 -- dann frazier   Wed, 10 Jan 2018 17:04:34 -0700

** Changed in: grub2 (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/722950

Title:
  ctrl-x does not work in grub-efi

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  New
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Zesty:
  Won't Fix
Status in grub2-signed source package in Zesty:
  Won't Fix
Status in grub2 source package in Artful:
  Fix Released
Status in grub2-signed source package in Artful:
  Fix Released

Bug description:
  [Impact]
  On some UEFI platforms, useful key combinations fail to work over the serial 
console. In particular, ^x/F10 - one of which is needed to boot after 
interactively editing the boot menu. This leaves end users without a sane way 
to tweak command line arguments, and potentially other system recovery tasks.

  [Test Case]
  Boot such a UEFI system to the GRUB menu. Press 'e' to edit the commandline, 
then attempt to continue the boot using "^x".

  [Regression Risk]
  The proposed fix is a cherry-pick from upstream that we've been shipping in 
Ubuntu since 17.10 w/o any any known regressions. However, it is possible that 
such regressions exist - e.g. if a platform's firmware has a buggy 
implementation fo the EFI_SIMPLE_TEXT_INPUT_EX protocol.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/722950/+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 1744166] Re: East-Saskatchewan timezone removed in latest tzdata

[Launchpad Bug Tracker]

This bug was fixed in the package php-sabre-vobject-3 - 3.5.0-1ubuntu1.1

---
php-sabre-vobject-3 (3.5.0-1ubuntu1.1) xenial; urgency=medium

  * debian/patches/tzdata_remove_east_saskatchewan.patch: Remove the
Canada/East-Saskatchewan timezone.  Closes #880337, LP: #1744166.

 -- Nishanth Aravamudan   Thu, 18 Jan
2018 15:30:41 -0800

** Changed in: php-sabre-vobject-3 (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/1744166

Title:
  East-Saskatchewan timezone removed in latest tzdata

Status in php-sabre-vobject-3 package in Ubuntu:
  Fix Released
Status in php-sabre-vobject-3 source package in Xenial:
  Fix Released
Status in php-sabre-vobject-3 source package in Artful:
  Fix Committed
Status in php-sabre-vobject-3 package in Debian:
  Fix Committed

Bug description:
  [Impact]

  * DEP8 tests for php-sabre-vobject-3 currently fail in 16.04 because
  the 2017c version of tzdata dropped the East-Saskatchewan timezone,
  which is hardcoded in the package.

  * This in turn blocks SRUs of new PHP7.0 microreleases.

  [Test Case]

  * Run the autopkgtests for this source package before and after the
  change. They should pass after.

  [Regression Potential]

  * None, this timezone is no longer valid in 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-sabre-vobject-3/+bug/1744166/+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 1734278] Re: Grub2 cannot boot up when 8254 time function disable

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.02~beta3-4ubuntu7.1

---
grub2 (2.02~beta3-4ubuntu7.1) artful; urgency=medium

  * Cherry-pick upstream patch to change the default TSC calibration method
to pmtimer on EFI systems (LP: #1734278)
  * util/grub-install.c: Use fallback and MokManager EFI binary names without
the .signed extension now that shim handles signing via sbsigntool
natively. (LP: #1708245)
- debian/patches/grub-install-extra-removable.patch
- debian/patches/install_signed.patch

 -- Mathieu Trudel-Lapierre   Wed, 17 Jan 2018
11:51:20 -0500

** Changed in: grub2 (Ubuntu Artful)
   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/1734278

Title:
  Grub2 cannot boot up when 8254 time function disable

Status in HWE Next:
  Triaged
Status in OEM Priority Project:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  New
Status in debian-installer source package in Artful:
  New
Status in grub2 source package in Artful:
  Fix Released
Status in grub2-signed source package in Artful:
  Fix Released
Status in debian-installer source package in Bionic:
  Fix Released
Status in grub2 source package in Bionic:
  Fix Released
Status in grub2-signed source package in Bionic:
  Fix Released
Status in grub2 package in Debian:
  New
Status in grub2 package in Fedora:
  Fix Committed

Bug description:
  [Impact]
  Some Intel SoC-based systems.

  [Test cases]
  1) Boot an affected system.

  [Regression potential]
  Some systems may rely on the current state of the timer selection in order to 
be able to boot successfully, or to catch key presses before the end of a 
timeout in the menu.
  These systems may then fail to boot correctly, stuck in a timeout of crashing 
in grub. The new default, pmtimer, should be available on all ACPI-capable 
systems without being power-gated such as for the PIT, so the impact of this 
possible regression is minimal.

  ---

  Fail to boot into Ubuntu GRUB on the platforms which legacy(8254) timer 
function is disabled.
  "8254 clock gating" is provided to disable 8254 timer to get rid of legacy 
and save power. The platforms with the firmware which disable the 8254 timer 
will fail to boot up and block on grub2 which uses the 8254 timer to calibrate 
the TSC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1734278/+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 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core

[Anthony Wong]

** Changed in: hwe-next
   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/1736393

Title:
  [Artful][Wyse 3040] System hang when trying to enable an offlined CPU
  core

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online
  2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online

  System will hang on step 2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1736393/+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 1708245] Re: shim can't enable validation and enroll keys in one sitting

[Launchpad Bug Tracker]

This bug was fixed in the package grub2-signed - 1.66.16

---
grub2-signed (1.66.16) xenial; urgency=medium

  * Rebuild against grub2 2.02~beta2-36ubuntu3.16. (LP: #722950,
#1708245)

 -- dann frazier   Thu, 11 Jan 2018 10:04:44
-0700

** Changed in: shim-signed (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  shim can't enable validation and enroll keys in one sitting

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Zesty:
  Won't Fix
Status in grub2-signed source package in Zesty:
  Won't Fix
Status in shim source package in Zesty:
  Won't Fix
Status in shim-signed source package in Zesty:
  Won't Fix
Status in grub2 source package in Artful:
  Fix Released
Status in grub2-signed source package in Artful:
  Fix Released
Status in shim source package in Artful:
  Fix Committed
Status in shim-signed source package in Artful:
  Fix Released

Bug description:
  [Impact]

  
  [Test cases]
  First, update shim to the newest version.

  = Boot test =
  1) Reboot.
  2) Validate that the system boots correctly in UEFI mode.

  
  = Key enrollment =
  1) Create a new x.509 certificate to import into MOK.
  2) Run 'mokutil --import cert.der'
  3) Reboot
  4) Execute the steps described on screen to enroll the new key.

  
  = Toggling validation =
  1) Run 'mokutil --disable-validation'
  2) Reboot.
  3) Follow the steps on screen to toggle validation.
  4) Boot to the system, validate that validation is disabled:
  $ sudo hexdump -Cv /sys/firmware/efi/efivars/MokSBStateRT-*

  The output should read the last byte as a 1.

  5) Run 'mokutil --enable-validation'
  6) Reboot.
  7) Follow the steps on screen to toggle validation.
  8) Boot to the system, validate that validation is enabled again:
  $ hexdump -Cv /sys/firmware/efi/efivars/MokSBStateRT-*

  The file should not exist.

  
  = Toggling validation and enrolling =
  1) Disable validation, as above, and reboot into the system.
  2) Create a new x.509 certificate to import into MOK.
  3) Run 'mokutil --import cert.der'
  4) Run 'mokutil --enable-validation'
  5) Reboot.
  6) Follow the steps on screen to proceed through toggling validation in shim.
  Once that step is done, you should be returned to the MokManager menu to 
complete further steps.
  7) Follow the steps on screen to enroll the new key.
  Once completed, you should have the option at the bottom of the menu to 
Reboot.
  8) Reboot into the system.
  9) Validate that MOK validation is enabled and the new key is enrolled:

  Run:

  $ sudo hexdump -Cv /sys/firmware/efi/efivars/MokSBStateRT-*

  The file should not exist.

  Then run:
  $ sudo cat /proc/keys

  And make sure the key you enrolled is present.

  
  [Regression potential]
  Failure to boot or validate validly signed EFI binaries (bootloader) might be 
possible regressions. The shim update modifies the enrollment process for new 
keys, and as such it might also be possible for the enrollment of a new key to 
fail in MokManager, rendering the validation process unstable: it may fail to 
validate validly signed EFI binaries signed by keys already present in the 
database or that were to be enrolled.

  
  ---

  We want to enable validation and enroll a new key in shim all at the
  same time on upgrade from previous releases.

  Curently, shim will wipe out all pending variables when it's done
  processing one of them (because it wants to reboot immediately after
  that action). That means if we re-enable validation, we lose the
  request to enroll the key, and vice-versa.

  This needs fixing as it would otherwise badly impact upgrades from
  zesty and earlier; where we might have walked users through disabling
  validation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1708245/+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 1743618] Re: sru curtin 2018-01-18 - 17.1-11-ga4c9636b-0ubuntu1

[Launchpad Bug Tracker]

This bug was fixed in the package curtin - 17.1-11-ga4c9636b-
0ubuntu1~16.04.1

---
curtin (17.1-11-ga4c9636b-0ubuntu1~16.04.1) xenial; urgency=medium

  * New upstream snapshot. (LP: #1743618)
- tests: cleanup the apt custom sources test.
- apt: Be more lenient when replacing mirrors in /etc/apt/sources.list
- vmtest: Drop Zesty release
- vmtest: initialize logger with class names for easy parsing
- packaging: Do not mention primary contributors in debian/changelog.

curtin (17.1-6-g8b145067-0ubuntu1~16.04.1) xenial; urgency=medium

  * New upstream snapshot. (LP: #1743618)
- packaging: Update new-upstream-snapshot to work with git.
- Bump pylint to 1.8.1.
- vmtests: switch to MAAS v3 streams for images and kernels [Ryan Harper]
- tests: update pack tests to clear out pyc files more completely.
- debian/control: drop conflicts that had bzr version
- Switch uses of bzr to git, borrow from cloud-init git workflow.
- Release 17.1
- packaging: update debian/build-deb to remove ~bzrREV when using equal tag
- pack: fix packing when curtin is installed inside a snap.
- tox: move to pylint 1.7.4
- vmtests: iscsi minor cleanup.
- vmtests: exercise rootfs over an lvm logical volume [Ryan Harper]
- Switch network dep filter to test for ifupdown/nplan instead of release
  name [Ryan Harper]
- Allow control of curtin install unmounting [Ryan Harper]
- vmtests: Add Bionic release to tests and update classes.
- storage: add 'options' key mount type to specify mount parameters for
  filesystems [Ryan Harper]
- Re-add curthooks.write_files method for backwards compat
  [Ryan Harper]
- vmtest: Remove ArtfulTestBridging skip_by_date check, bug fixed
- Drop Precise from vmtest [Ryan Harper]
- clear_holders: bcache log IO/OS exceptions but do not raise [Ryan Harper]
- vmtest: Support newer qemu and multipath.
- block: enable control over exclusive_open use when wiping volumes
  [Ryan Harper]
- block: handle wiping bcache parts [Ryan Harper]
- vmtests: Defer ArtfulNetworkMtu SkipbyDate to 2018 [Ryan Harper]
- bcache: accept sysfs write failure in shutdown handler if path missing
  [Ryan Harper]
- vmtest: Rephrase a message about no disks to be less scary
- block_meta: use block.wipe_volume(mode=superblock) to clear MBR/GPT
  tables [Ryan Harper]

 -- Ryan Harper   Thu, 18 Jan 2018 15:30:09
-0600

** Changed in: curtin (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/1743618

Title:
  sru curtin 2018-01-18 - 17.1-11-ga4c9636b-0ubuntu1

Status in curtin source package in Xenial:
  Fix Released
Status in curtin source package in Artful:
  Fix Released

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these improvements.
  The notable ones are:

     * storage: add 'options' key mount type to specify mount parameters for
   filesystems (LP: #1709284)
     * Re-add curthooks.write_files method for backwards compat
   (LP: #1731709)
     * block: handle wiping bcache parts (LP: #1718699)
     * bcache: accept sysfs write failure in shutdown handler if path
   missing (LP: #1700564)
     * block_meta: use block.wipe_volume(mode=superblock) to clear MBR/GPT
   tables (LP: #1722322)
     * apt: Be more lenient when replacing mirrors in /etc/apt/sources.list
   (LP: #1744038)
     * vmtest: Drop Zesty release

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CurtinUpdates

  Curtin now contains an extensive integration test suite that is ran using
  the SRU package for each releases. These suite has documentation here:
  https://curtin.readthedocs.io/en/latest/topics/integration-testing.html

  In order to avoid regression to existing MAAS product, the MAAS team will
  run their continuous integration test against the curtin that is in
  -proposed.  A successful run will be required before the proposed curtin
  can be let into -updates.

  The curtin team will be in charge of attaching the artifacts and console
  output of the appropriate run to the bug.  Curtin team members will not
  mark ‘verification-done’ until this has happened.

  [Verification]
  integration tests for xenial:
   * log: see attached curtin-vmtest-proposed-x-console.log
   * artifacts: see attached curtin-vmtest-proposed-x-artifacts.tar.xz
   Note: one test case failed due to transient Bionic Kernel bug
   which is unrelated to curtin (LP: #1730717)

  integration tests for artful:
   * log: 

[Group.of.nepali.translators] [Bug 1708245] Re: shim can't enable validation and enroll keys in one sitting

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.16

---
grub2 (2.02~beta2-36ubuntu3.16) xenial; urgency=medium

  [ dann frazier ]
  * Use EFI_SIMPLE_TEXT_INPUT_EX to support key combinations.
(LP: #722950)

  [ Mathieu Trudel-Lapierre ]
  * util/grub-install.c: Use MokManager EFI binary name without
the .signed extension now that shim handles signing via sbsigntool
natively. (LP: #1708245)
- debian/patches/install_signed.patch
  * debian/control: Breaks shim << 13 due to the renamed MokManager binary.

 -- dann frazier   Wed, 10 Jan 2018 17:04:34 -0700

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

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

Title:
  shim can't enable validation and enroll keys in one sitting

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Zesty:
  Won't Fix
Status in grub2-signed source package in Zesty:
  Won't Fix
Status in shim source package in Zesty:
  Won't Fix
Status in shim-signed source package in Zesty:
  Won't Fix
Status in grub2 source package in Artful:
  Fix Released
Status in grub2-signed source package in Artful:
  Fix Released
Status in shim source package in Artful:
  Fix Committed
Status in shim-signed source package in Artful:
  Fix Released

Bug description:
  [Impact]

  
  [Test cases]
  First, update shim to the newest version.

  = Boot test =
  1) Reboot.
  2) Validate that the system boots correctly in UEFI mode.

  
  = Key enrollment =
  1) Create a new x.509 certificate to import into MOK.
  2) Run 'mokutil --import cert.der'
  3) Reboot
  4) Execute the steps described on screen to enroll the new key.

  
  = Toggling validation =
  1) Run 'mokutil --disable-validation'
  2) Reboot.
  3) Follow the steps on screen to toggle validation.
  4) Boot to the system, validate that validation is disabled:
  $ sudo hexdump -Cv /sys/firmware/efi/efivars/MokSBStateRT-*

  The output should read the last byte as a 1.

  5) Run 'mokutil --enable-validation'
  6) Reboot.
  7) Follow the steps on screen to toggle validation.
  8) Boot to the system, validate that validation is enabled again:
  $ hexdump -Cv /sys/firmware/efi/efivars/MokSBStateRT-*

  The file should not exist.

  
  = Toggling validation and enrolling =
  1) Disable validation, as above, and reboot into the system.
  2) Create a new x.509 certificate to import into MOK.
  3) Run 'mokutil --import cert.der'
  4) Run 'mokutil --enable-validation'
  5) Reboot.
  6) Follow the steps on screen to proceed through toggling validation in shim.
  Once that step is done, you should be returned to the MokManager menu to 
complete further steps.
  7) Follow the steps on screen to enroll the new key.
  Once completed, you should have the option at the bottom of the menu to 
Reboot.
  8) Reboot into the system.
  9) Validate that MOK validation is enabled and the new key is enrolled:

  Run:

  $ sudo hexdump -Cv /sys/firmware/efi/efivars/MokSBStateRT-*

  The file should not exist.

  Then run:
  $ sudo cat /proc/keys

  And make sure the key you enrolled is present.

  
  [Regression potential]
  Failure to boot or validate validly signed EFI binaries (bootloader) might be 
possible regressions. The shim update modifies the enrollment process for new 
keys, and as such it might also be possible for the enrollment of a new key to 
fail in MokManager, rendering the validation process unstable: it may fail to 
validate validly signed EFI binaries signed by keys already present in the 
database or that were to be enrolled.

  
  ---

  We want to enable validation and enroll a new key in shim all at the
  same time on upgrade from previous releases.

  Curently, shim will wipe out all pending variables when it's done
  processing one of them (because it wants to reboot immediately after
  that action). That means if we re-enable validation, we lose the
  request to enroll the key, and vice-versa.

  This needs fixing as it would otherwise badly impact upgrades from
  zesty and earlier; where we might have walked users through disabling
  validation.

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

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

[Group.of.nepali.translators] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Launchpad Bug Tracker]

This bug was fixed in the package libqmi - 1.16.2-1ubuntu0.16.04.1

---
libqmi (1.16.2-1ubuntu0.16.04.1) xenial; urgency=medium

  * Backport to xenial (LP: #1725190).
  * debian/control: bump down debhelper to xenial vesion.

 -- Łukasz 'sil2100' Zemczak   Tue, 28 Nov
2017 12:55:17 +0100

** Changed in: libqmi (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: libmbim (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/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Fix Committed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Released
Status in libqmi source package in Xenial:
  Fix Released
Status in modemmanager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+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 1708245] Re: shim can't enable validation and enroll keys in one sitting

[Launchpad Bug Tracker]

This bug was fixed in the package grub2-signed - 1.85.1

---
grub2-signed (1.85.1) artful; urgency=medium

  * Rebuild against grub2 2.02~beta3-4ubuntu7.1. (LP: #1734278,
#1708245)

 -- Mathieu Trudel-Lapierre   Wed, 13 Dec 2017
14:36:57 -0500

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

** Changed in: shim-signed (Ubuntu Artful)
   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/1708245

Title:
  shim can't enable validation and enroll keys in one sitting

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Fix Released
Status in shim-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 shim source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Committed
Status in grub2 source package in Zesty:
  Won't Fix
Status in grub2-signed source package in Zesty:
  Won't Fix
Status in shim source package in Zesty:
  Won't Fix
Status in shim-signed source package in Zesty:
  Won't Fix
Status in grub2 source package in Artful:
  Fix Committed
Status in grub2-signed source package in Artful:
  Fix Released
Status in shim source package in Artful:
  Fix Committed
Status in shim-signed source package in Artful:
  Fix Released

Bug description:
  [Impact]

  
  [Test cases]
  First, update shim to the newest version.

  = Boot test =
  1) Reboot.
  2) Validate that the system boots correctly in UEFI mode.

  
  = Key enrollment =
  1) Create a new x.509 certificate to import into MOK.
  2) Run 'mokutil --import cert.der'
  3) Reboot
  4) Execute the steps described on screen to enroll the new key.

  
  = Toggling validation =
  1) Run 'mokutil --disable-validation'
  2) Reboot.
  3) Follow the steps on screen to toggle validation.
  4) Boot to the system, validate that validation is disabled:
  $ sudo hexdump -Cv /sys/firmware/efi/efivars/MokSBStateRT-*

  The output should read the last byte as a 1.

  5) Run 'mokutil --enable-validation'
  6) Reboot.
  7) Follow the steps on screen to toggle validation.
  8) Boot to the system, validate that validation is enabled again:
  $ hexdump -Cv /sys/firmware/efi/efivars/MokSBStateRT-*

  The file should not exist.

  
  = Toggling validation and enrolling =
  1) Disable validation, as above, and reboot into the system.
  2) Create a new x.509 certificate to import into MOK.
  3) Run 'mokutil --import cert.der'
  4) Run 'mokutil --enable-validation'
  5) Reboot.
  6) Follow the steps on screen to proceed through toggling validation in shim.
  Once that step is done, you should be returned to the MokManager menu to 
complete further steps.
  7) Follow the steps on screen to enroll the new key.
  Once completed, you should have the option at the bottom of the menu to 
Reboot.
  8) Reboot into the system.
  9) Validate that MOK validation is enabled and the new key is enrolled:

  Run:

  $ sudo hexdump -Cv /sys/firmware/efi/efivars/MokSBStateRT-*

  The file should not exist.

  Then run:
  $ sudo cat /proc/keys

  And make sure the key you enrolled is present.

  
  [Regression potential]
  Failure to boot or validate validly signed EFI binaries (bootloader) might be 
possible regressions. The shim update modifies the enrollment process for new 
keys, and as such it might also be possible for the enrollment of a new key to 
fail in MokManager, rendering the validation process unstable: it may fail to 
validate validly signed EFI binaries signed by keys already present in the 
database or that were to be enrolled.

  
  ---

  We want to enable validation and enroll a new key in shim all at the
  same time on upgrade from previous releases.

  Curently, shim will wipe out all pending variables when it's done
  processing one of them (because it wants to reboot immediately after
  that action). That means if we re-enable validation, we lose the
  request to enroll the key, and vice-versa.

  This needs fixing as it would otherwise badly impact upgrades from
  zesty and earlier; where we might have walked users through disabling
  validation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1708245/+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 1743618] Re: sru curtin 2018-01-18 - 17.1-11-ga4c9636b-0ubuntu1

[Launchpad Bug Tracker]

This bug was fixed in the package curtin - 17.1-11-ga4c9636b-
0ubuntu1~17.10.1

---
curtin (17.1-11-ga4c9636b-0ubuntu1~17.10.1) artful; urgency=medium

  * New upstream snapshot. (LP: #1743618)
- tests: cleanup the apt custom sources test.
- apt: Be more lenient when replacing mirrors in /etc/apt/sources.list
- vmtest: Drop Zesty release
- vmtest: initialize logger with class names for easy parsing
- packaging: Do not mention primary contributors in debian/changelog.

curtin (17.1-6-g8b145067-0ubuntu1~17.10.1) artful; urgency=medium

  * New upstream snapshot. (LP: #1743618)
- packaging: Update new-upstream-snapshot to work with git.
- Bump pylint to 1.8.1.
- vmtests: switch to MAAS v3 streams for images and kernels [Ryan Harper]
- tests: update pack tests to clear out pyc files more completely.
- debian/control: drop conflicts that had bzr version
- Switch uses of bzr to git, borrow from cloud-init git workflow.
- Release 17.1
- packaging: update debian/build-deb to remove ~bzrREV when using equal tag
- pack: fix packing when curtin is installed inside a snap.
- tox: move to pylint 1.7.4
- vmtests: iscsi minor cleanup.
- vmtests: exercise rootfs over an lvm logical volume [Ryan Harper]
- Switch network dep filter to test for ifupdown/nplan instead of release
  name [Ryan Harper]
- Allow control of curtin install unmounting [Ryan Harper]
- vmtests: Add Bionic release to tests and update classes.
- storage: add 'options' key mount type to specify mount parameters for
  filesystems [Ryan Harper]
- Re-add curthooks.write_files method for backwards compat
  [Ryan Harper]
- vmtest: Remove ArtfulTestBridging skip_by_date check, bug fixed
- Drop Precise from vmtest [Ryan Harper]
- clear_holders: bcache log IO/OS exceptions but do not raise [Ryan Harper]
- vmtest: Support newer qemu and multipath.
- block: enable control over exclusive_open use when wiping volumes
  [Ryan Harper]
- block: handle wiping bcache parts [Ryan Harper]
- vmtests: Defer ArtfulNetworkMtu SkipbyDate to 2018 [Ryan Harper]
- bcache: accept sysfs write failure in shutdown handler if path missing
  [Ryan Harper]
- vmtest: Rephrase a message about no disks to be less scary
- block_meta: use block.wipe_volume(mode=superblock) to clear MBR/GPT
  tables [Ryan Harper]

 -- Ryan Harper   Thu, 18 Jan 2018 15:47:59
-0600

** Changed in: curtin (Ubuntu Artful)
   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/1743618

Title:
  sru curtin 2018-01-18 - 17.1-11-ga4c9636b-0ubuntu1

Status in curtin source package in Xenial:
  Fix Committed
Status in curtin source package in Artful:
  Fix Released

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these improvements.
  The notable ones are:

     * storage: add 'options' key mount type to specify mount parameters for
   filesystems (LP: #1709284)
     * Re-add curthooks.write_files method for backwards compat
   (LP: #1731709)
     * block: handle wiping bcache parts (LP: #1718699)
     * bcache: accept sysfs write failure in shutdown handler if path
   missing (LP: #1700564)
     * block_meta: use block.wipe_volume(mode=superblock) to clear MBR/GPT
   tables (LP: #1722322)
     * apt: Be more lenient when replacing mirrors in /etc/apt/sources.list
   (LP: #1744038)
     * vmtest: Drop Zesty release

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CurtinUpdates

  Curtin now contains an extensive integration test suite that is ran using
  the SRU package for each releases. These suite has documentation here:
  https://curtin.readthedocs.io/en/latest/topics/integration-testing.html

  In order to avoid regression to existing MAAS product, the MAAS team will
  run their continuous integration test against the curtin that is in
  -proposed.  A successful run will be required before the proposed curtin
  can be let into -updates.

  The curtin team will be in charge of attaching the artifacts and console
  output of the appropriate run to the bug.  Curtin team members will not
  mark ‘verification-done’ until this has happened.

  [Verification]
  integration tests for xenial:
   * log: see attached curtin-vmtest-proposed-x-console.log
   * artifacts: see attached curtin-vmtest-proposed-x-artifacts.tar.xz
   Note: one test case failed due to transient Bionic Kernel bug
   which is unrelated to curtin (LP: #1730717)

  integration tests for artful:
   * 

[Group.of.nepali.translators] [Bug 1734278] Re: Grub2 cannot boot up when 8254 time function disable

[Launchpad Bug Tracker]

This bug was fixed in the package grub2-signed - 1.85.1

---
grub2-signed (1.85.1) artful; urgency=medium

  * Rebuild against grub2 2.02~beta3-4ubuntu7.1. (LP: #1734278,
#1708245)

 -- Mathieu Trudel-Lapierre   Wed, 13 Dec 2017
14:36:57 -0500

** Changed in: grub2-signed (Ubuntu Artful)
   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/1734278

Title:
  Grub2 cannot boot up when 8254 time function disable

Status in HWE Next:
  Triaged
Status in OEM Priority Project:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  New
Status in debian-installer source package in Artful:
  New
Status in grub2 source package in Artful:
  Fix Committed
Status in grub2-signed source package in Artful:
  Fix Released
Status in debian-installer source package in Bionic:
  Fix Released
Status in grub2 source package in Bionic:
  Fix Released
Status in grub2-signed source package in Bionic:
  Fix Released
Status in grub2 package in Debian:
  New
Status in grub2 package in Fedora:
  Fix Committed

Bug description:
  [Impact]
  Some Intel SoC-based systems.

  [Test cases]
  1) Boot an affected system.

  [Regression potential]
  Some systems may rely on the current state of the timer selection in order to 
be able to boot successfully, or to catch key presses before the end of a 
timeout in the menu.
  These systems may then fail to boot correctly, stuck in a timeout of crashing 
in grub. The new default, pmtimer, should be available on all ACPI-capable 
systems without being power-gated such as for the PIT, so the impact of this 
possible regression is minimal.

  ---

  Fail to boot into Ubuntu GRUB on the platforms which legacy(8254) timer 
function is disabled.
  "8254 clock gating" is provided to disable 8254 timer to get rid of legacy 
and save power. The platforms with the firmware which disable the 8254 timer 
will fail to boot up and block on grub2 which uses the 8254 timer to calibrate 
the TSC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1734278/+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 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying

[Launchpad Bug Tracker]

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

---
linux-firmware (1.169.3) artful; urgency=medium

  * QCA6174 stops working on newer kernels after second group rekeying
(LP: #1743279)
- ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00051-QCARMSWP-1

 -- Seth Forshee   Thu, 25 Jan 2018 14:23:42
-0600

** Changed in: linux-firmware (Ubuntu Artful)
   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/1743279

Title:
  QCA6174 stops working on newer kernels after second group rekeying

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

Bug description:
  After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my
  WiFi would stop working after every 20 minutes or so. The problem
  initially seems related to some DNS services crashing because of what
  happend in browsers and other software that usually rely on DNS but
  I've noticed I couldn't ping my router and other local devices for
  which I knew the IP addresses. The connection is still presented as
  being connected, but it just doesn't work.

  After googling a lot, I came across this question on askubuntu.com

  https://askubuntu.com/questions/967355/wifi-unstable-
  after-17-10-update

  Which led me to this bug report on Debian's bug tracker:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184

  Which led me to this bug in upstream:

  http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html

  I've tested the proposed fixes myself and I can confirm they work.

  What causes the WiFi to stop working is a bug related to the group
  rekeying routines.

  It seems it only happens in >4.12 kernels, hence why I've only had
  problems after 4.13 was pushed as the current rolling HWE kernel for
  16.04.3.

  kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1
  of the firmware-6.bin file, which is the current one present in
  upstream.

  Updating the firmware-6.bin (and board-2.bin, optionally) to any
  version equal or later than that fixes the issue completely.

  -

  SRU Justification:
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in 
numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, 
silently stops working after the second group rekeying, which is usually few 
minutes after the user has connected to a WiFi network. The connection status 
remains unchanged but there's no connectivity at all. This effectively 
disconnects the user without notifying it of what's occurred.

  Additionally, this happens for the only HWE kernel that's been patched
  against the recent Meltdown vulnerability, leaving the user without
  the option of using a recent kernel and a secure kernel at the same
  time.

  [Test Case]
  After applying the required firmwares, check if the connectivity is 
unaffected after the second group rekeying, which can be checked with

  $ cat /var/log/syslog | grep wpa_.*rekeying

  [How to fix it]

  Update the firmware-6.bin file to version
  WLAN.RM.4.4.1-00051-QCARMSWP-1 or later.

  [Regression Potential]
  The new firmware overwrites the old one, but since it's been in upstream 
since October 2017, it should be good.

  -

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  linux-firmware:
    Instalado: 1.157.14
    Candidato: 1.157.14
    Tabela de versão:
   *** 1.157.14 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

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