date:20160908

This bug was fixed in the package update-manager - 1:16.10.5

---
update-manager (1:16.10.5) yakkety; urgency=medium

  [ Brian Murray ]
  * UpdateManager/UpdateManager.py: when marking HWE packages for install pass
on a SystemError and let the problem resolver sort it out.
  * HweSupportStatus/consts.py: Improve wording of the messages.
  * hwe-support-status:
- decode output when checking for foreign architectures so that the result
  is unicode not bytes.
- add libwayland-egl1-mesa to the list of metapackages.
- utilize a virtualbox metapackage set.
- Do not show replacements that are already installed on
  the system.  (LP: #1607983)
  * source_update-manager.py: collect information about the state of HWE
support on the system. (LP: #1617080)
  * source_update-manager.py: only collect HWE information if it exists.

  [ Jeremy Bicha ]
  * Add gi.require_version in a few more places to reduce the annoying
warnings. (LP: #1573177)

 -- Brian Murray   Thu, 08 Sep 2016 16:01:13 -0700

** Changed in: update-manager (Ubuntu)
   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/1617080

Title:
  update-manager apport package hook should gather HWE information

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Trusty:
  Fix Released
Status in update-manager source package in Xenial:
  Triaged

Bug description:
  Sometimes systems can have a hard time installing the HWE
  replacements,
  https://errors.ubuntu.com/problem/fc13839a8f1631b1e1907d410c7f161d7fc9,
  it'd be helpful if apport were to gather information about what HWE
  packages are installed and which HWE replacement packages are
  recommended.

  Test Case
  -
  1) Run ubuntu-bug update-manager
  2) Observe there are no HWE fields in the report

  With the version of update-manager from -proposed you'll now see
  HWEunsupported (the output of hwe-support-status --show-all-
  unsupported) and HWEreplacements (the output of hwe-support-status
  --show-replacements).  If you are running the -lts-xenial stack these
  may be empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1617080/+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 1616533] Re: weather.noaa.gov was shut down - MATE unable to retrieve weather forecasts

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

** Changed in: libmateweather (Ubuntu Trusty)
   Importance: Undecided => High

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

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

Title:
  weather.noaa.gov was shut down - MATE unable to retrieve weather
  forecasts

Status in libmateweather package in Ubuntu:
  Fix Released
Status in libmateweather source package in Trusty:
  Triaged
Status in libmateweather source package in Xenial:
  Fix Committed

Bug description:
  The provider which libmateweather was using was shut down in August.

  We need to update libmateweather in Xenial to new upstream micro
  release, 1.12.2, which switched to a new METAR data provider.

  Impact: this affects all libmateweather-using applications, makes them
  unable to retrieve weather data.

  Test Case: make sure Weather applet in mate-applets is able to display
  weather information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmateweather/+bug/1616533/+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 1570923] Re: bacula-dir won't start with "undefined symbol: mysql_init"

2016-09-08 Thread Mathew Hodson

** Project changed: bacula => ubuntu-translations

** No longer affects: ubuntu-translations

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

Title:
  bacula-dir won't start with "undefined symbol: mysql_init"

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

Bug description:
  [Impact]

   * bacula-dir fails to start after installation.

  [Test Case]

   * Install bacula-director-mysql after installing mysql-server.
  bacula-dir fails to start (and the installation fails).

   * In a successful case, the bacula-dir process will start (and be
  running after installation).

  [Regression Potential]

   * The fix for this is to backport an upstream fix that changes the
  build to not use libmysqlclient_r.* files (which are no longer
  shiipped with MySQL 5.7). The regression potential should be low, as
  bacula-dir currently does not start at all.

  1. Ubuntu release :
  Description:Ubuntu Xenial Xerus (development branch)
  Release:16.04

  2. Version of package
  bacula-director-mysql:
    Installed: 7.0.5+dfsg-4build1
    Candidate: 7.0.5+dfsg-4build1
    Version table:
   *** 7.0.5+dfsg-4build1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  3. Expectation : bacula-dir should start

  4. bacula-dir did not start because of :

  root@xenial:~# bacula-dir -d 99
  bacula-dir: dird.c:194-0 Debug level = 99
  bacula-dir: address_conf.c:264-0 Initaddr 0.0.0.0:9101
  root@xenial:~# bacula-dir: dir_plugins.c:148-0 Load dir plugins
  bacula-dir: dir_plugins.c:150-0 No dir plugin dir!
  bacula-dir: symbol lookup error: /usr/lib/bacula/libbaccats-7.0.5.so: 
undefined symbol: mysql_init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1570923/+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 1620779] Re: update jtreg in 16.04 LTS to the version required by openjdk-9

2016-09-08 Thread Mathew Hodson

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

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

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

** Changed in: jtreg (Ubuntu Xenial)
   Importance: Medium => High

** Changed in: jtreg (Ubuntu)
   Importance: Medium => High

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

Title:
  update jtreg in 16.04 LTS to the version required by openjdk-9

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

Bug description:
  update jtreg in 16.04 LTS to the version required by openjdk-9.
  Starting with recent openjdk-9 snapshot, openjdk-9 expects jtreg
  version 4.2-b03 for running the tests.  Proposing to update xenial to
  this new upstream version.

  jtreg is only used for opendjk, and the openjdk-8 tests still run with
  the new jtreg version.

  acceptance criteria: jtreg builds, and a (PPA) build for openjdk-8
  succeeds as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jtreg/+bug/1620779/+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 1577824] Re: Map should wrap left and right ends

This has been fixed in Ubuntu 16.10 Beta with gnome-maps 3.21.91-1 and
https://launchpad.net/ubuntu/+source/libchamplain/0.12.14-1

This should work in Ubuntu 16.04 with the GNOME3 Staging PPA in a few
hours once gnome-maps 3.20.3.1-0ubuntu1~ppa1 successfully builds and is
published there.

** Also affects: gnome-maps (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: gnome-maps (Ubuntu Xenial)
   Importance: Undecided => Wishlist

** Changed in: gnome-maps (Ubuntu Xenial)
   Status: New => Triaged

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

Title:
  Map should wrap left and right ends

Status in Gnome Maps:
  Fix Released
Status in Ubuntu GNOME:
  Fix Released
Status in gnome-maps package in Ubuntu:
  Fix Released
Status in gnome-maps source package in Xenial:
  Triaged

Bug description:
  Currently if one goes right to the far left of the map they get this:

  Maps_Ubuntu_No_Wrap.png

  And the same for the far right of the map:

  Maps_Ubuntu_No_Wrap2.png

  But instead of just stopping one from being able to go beyond these
  points (like with bug #1577823) I think that it would be better if the
  map actually wrapped around and behaved more like a globe or at least
  cylinder so that one can go left or right for ever and the map will
  just continue wrapping round so that there is no ugly end. Also having
  the text going off the right side and then one having to go to the
  right side to read it isn't very nice. So I think that a better design
  is needed, and a wrap function would also possibly allow something
  like bug #1577825. I am running Ubuntu GNOME 15.10 with GNOME 3.18 but
  the issue is also present on Ubuntu GNOME 16.04 with GNOME 3.20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-maps/+bug/1577824/+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 1171236] Re: file-roller may delete the content of linked folder (?)

2016-09-08 Thread Tyler Hicks

** Changed in: file-roller (Ubuntu)
   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/1171236

Title:
  file-roller may delete the content of linked folder (?)

Status in File Roller:
  Fix Released
Status in file-roller package in Ubuntu:
  Fix Released
Status in file-roller source package in Trusty:
  Fix Released
Status in file-roller source package in Xenial:
  Fix Released

Bug description:
  (Excuse my english, I'm not a native speaker. I will try to be as
  clear as possible).

  After attempting to create an archive from folders who where actually
  just links, it seems that file-roller deleted all their content.

  Here are the steps I did :
  - Inside a folder, I had a dozen subfolders. Half of them where just links to 
folders placed elsewhere.
  - In Nautilus, I selected all these subfolders, choosed "compress", then 
choosed "zip" as the format.
  - The archive was created without any error message.

  I was expecting all the folders to be added to the archive, regardless
  of them being links or not.

  The disastrous result :
  - The archive is unusable. Attempting to expand it results in an error 
message (I didn't take note, but it was something generic saying the archive 
couldn't be expanded).
  - But more importantly, the content of the folders who where linked has 
disappeared. That is, the links are still here, the folders which they link to 
are still here, but they have been emptied.
  The files are not in the dustbin, they just disappeared.

  I noticed this right after I created the archive, I didn't touch my computer 
in-between.
  That's why I suspect file-roller.

  I will try to reproduce this bug in order to confirm it.
  But not before I find a way to recover my files, I lost a week of work 
because of this.

  Ubuntu 12.10 x64
  file-roller 3.6.1.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1171236/+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 1171236] Re: file-roller may delete the content of linked folder (?)

This bug was fixed in the package file-roller - 3.16.5-0ubuntu1.2

---
file-roller (3.16.5-0ubuntu1.2) xenial-security; urgency=medium

  * SECURITY UPDATE: Path traversal flaw allows arbitrary file deletion via
malicious archive (LP: #1171236)
- debian/patches/CVE-2016-7162.patch: Do not follow symlinks when deleting
  a folder recursively. Based on upstream patch.
- CVE-2016-7162

 -- Tyler Hicks   Thu, 08 Sep 2016 09:17:37 -0500

** Changed in: file-roller (Ubuntu Xenial)
   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/1171236

Title:
  file-roller may delete the content of linked folder (?)

Status in File Roller:
  Fix Released
Status in file-roller package in Ubuntu:
  Fix Committed
Status in file-roller source package in Trusty:
  Fix Released
Status in file-roller source package in Xenial:
  Fix Released

Bug description:
  (Excuse my english, I'm not a native speaker. I will try to be as
  clear as possible).

  After attempting to create an archive from folders who where actually
  just links, it seems that file-roller deleted all their content.

  Here are the steps I did :
  - Inside a folder, I had a dozen subfolders. Half of them where just links to 
folders placed elsewhere.
  - In Nautilus, I selected all these subfolders, choosed "compress", then 
choosed "zip" as the format.
  - The archive was created without any error message.

  I was expecting all the folders to be added to the archive, regardless
  of them being links or not.

  The disastrous result :
  - The archive is unusable. Attempting to expand it results in an error 
message (I didn't take note, but it was something generic saying the archive 
couldn't be expanded).
  - But more importantly, the content of the folders who where linked has 
disappeared. That is, the links are still here, the folders which they link to 
are still here, but they have been emptied.
  The files are not in the dustbin, they just disappeared.

  I noticed this right after I created the archive, I didn't touch my computer 
in-between.
  That's why I suspect file-roller.

  I will try to reproduce this bug in order to confirm it.
  But not before I find a way to recover my files, I lost a week of work 
because of this.

  Ubuntu 12.10 x64
  file-roller 3.6.1.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1171236/+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 1171236] Re: file-roller may delete the content of linked folder (?)

This bug was fixed in the package file-roller - 3.10.2.1-0ubuntu4.2

---
file-roller (3.10.2.1-0ubuntu4.2) trusty-security; urgency=medium

  * SECURITY UPDATE: Path traversal flaw allows arbitrary file deletion via
malicious archive (LP: #1171236)
- debian/patches/CVE-2016-7162.patch: Do not follow symlinks when deleting
  a folder recursively. Based on upstream patch.
- CVE-2016-7162

 -- Tyler Hicks   Thu, 08 Sep 2016 09:17:49 -0500

** Changed in: file-roller (Ubuntu Trusty)
   Status: In Progress => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-7162

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

Title:
  file-roller may delete the content of linked folder (?)

Status in File Roller:
  Fix Released
Status in file-roller package in Ubuntu:
  Fix Committed
Status in file-roller source package in Trusty:
  Fix Released
Status in file-roller source package in Xenial:
  In Progress

Bug description:
  (Excuse my english, I'm not a native speaker. I will try to be as
  clear as possible).

  After attempting to create an archive from folders who where actually
  just links, it seems that file-roller deleted all their content.

  Here are the steps I did :
  - Inside a folder, I had a dozen subfolders. Half of them where just links to 
folders placed elsewhere.
  - In Nautilus, I selected all these subfolders, choosed "compress", then 
choosed "zip" as the format.
  - The archive was created without any error message.

  I was expecting all the folders to be added to the archive, regardless
  of them being links or not.

  The disastrous result :
  - The archive is unusable. Attempting to expand it results in an error 
message (I didn't take note, but it was something generic saying the archive 
couldn't be expanded).
  - But more importantly, the content of the folders who where linked has 
disappeared. That is, the links are still here, the folders which they link to 
are still here, but they have been emptied.
  The files are not in the dustbin, they just disappeared.

  I noticed this right after I created the archive, I didn't touch my computer 
in-between.
  That's why I suspect file-roller.

  I will try to reproduce this bug in order to confirm it.
  But not before I find a way to recover my files, I lost a week of work 
because of this.

  Ubuntu 12.10 x64
  file-roller 3.6.1.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1171236/+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 1620686] Re: linux-raspi2: 4.4.0-1023.29 -proposed tracker

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

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

Title:
  linux-raspi2: 4.4.0-1023.29 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1620658
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1620658
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

Title:
  linux: 4.4.0-38.57 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1618040
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1618153/+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 1619718] Re: ubuntu-image created vfat eats itself after a while (mcopy creates wrong subdirs)

2016-09-08 Thread Steve Langasek

** Changed in: snappy
   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/1619718

Title:
  ubuntu-image created vfat eats itself after a while (mcopy creates
  wrong subdirs)

Status in Snappy:
  Fix Released
Status in Ubuntu Image:
  Invalid
Status in mtools package in Ubuntu:
  Fix Released
Status in ubuntu-image package in Ubuntu:
  Fix Released
Status in mtools source package in Xenial:
  Fix Committed
Status in ubuntu-image source package in Xenial:
  Invalid

Bug description:
  [SRU Justification]
  Since trusty, using mcopy to create directories will result in corrupted FAT 
entries due to uninitialized memory.  This leads to data loss when an fsck is 
run on the filesystem.

  [Test case] 
  1. Run the script from 
https://bugs.launchpad.net/ubuntu/+source/mtools/+bug/1619718/comments/2
  2. Observe that you are prompted to fix corrupted filesystem entries
  3. Install mtools from xenial-proposed
  4. Run the reproducer.sh script again
  5. Observe that the newly-created filesystem passes fsck with no errors.

  [Regresion potential]
  This is a one-line fix to correct uninitialized memory.  The only regression 
potential is that associated with rebuilding the tools with a new toolchain 
(the last rebuild of these binary packages was in vivid, with gcc-4.9).

  [Original bug description]

  on arm images the vfat used for the boot partition corrupts itself
  after a few reboots (it is noteworthy that on uboot/arm installations
  we write a lot more to the vfat. i would actually expect this to
  happen on x86 systems as well, just a lot later, i.e. after a few
  kernel updates)

  there seem to be various differences in how ubuntu-image creates the
  vfat ...

  in ubuntu-device-flash we use:
  mkfs.vfat -F 32 -S 512 -n ... against a loop mounted partition, the -S 512 
value gets actually matched against blockdev --getss (and adjusted accordingly 
if needed)

  ubuntu-image currently only calls:
  "mkfs.vfat" without any options against an img file that represents the vfat 
content.

  u-d-f also just uses cp against the loop mounted partition while
  ubuntu-image uses mtools' mcopy to put the files in place ...

  the result is that at random boots fsck suddenly starts to rename files in an 
8+3 scheme like:
  http://paste.ubuntu.com/23124260/ or http://paste.ubuntu.com/23124139/ which 
results in http://paste.ubuntu.com/23123498/

  i spent the whole day trying to tweak the mkfs options but to no
  avail, the corruption always happens at some point, so my suspicion
  goes more towards mtools/mcopy now

  http://paste.ubuntu.com/23123789/ is the original code that u-d-f uses
  which does not show such behaviour (i have upgraded the u-d-f rpi2
  image over the last 6 weeks daily with new ubuntu-core and
  occasionally with new pi2-kernel packages without any corruption)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1619718/+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 1621557] Re: Refresh go-lxc in Xenial for upcoming LXD stable release

2016-09-08 Thread Stéphane Graber

** Patch added: "go-lxc.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/golang-gopkg-lxc-go-lxc.v2/+bug/1621557/+attachment/4736970/+files/go-lxc.debdiff

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu)
   Status: New => Fix Released

** Also affects: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  Refresh go-lxc in Xenial for upcoming LXD stable release

Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu:
  Fix Released
Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial:
  In Progress

Bug description:
  Hello,

  The next LXD stable release (2.0.5) will be depending on a couple of
  recent additions to the go-lxc package. Those additions export a few
  more flags from CRIU that liblxc support which allow fixing a large
  number of race conditions around live migration.

  So while those extra flags may count as features as far as go-lxc is
  concerned, they are needed for bugfixes to LXD.

  lxd is the only downstream user of go-lxc in the archive and those
  changes are perfectly backward compatible so out of archive packages
  will not break with this.

  The version we'd like to get in Xenial has now been in Yakkety for
  over a month.

  Changelog from 0.0~git20160405.0.85d46fc-0ubuntu2 to 
0.0~git20160803.0.f8a6938-0ubuntu1:
   - BUGFIX: removed definition check at restore
   - BUGFIX: fixed restore from checkpoint (was always failing)
   - EXTRA FLAG: c/r: add support for liblxc's ghost_limit
   - EXTRA FLAG: c/r: add support for liblxc's action_script
   - BUGFIX: actually send the predump dir through
   - EXTRA FLAG: c/r: add support for lxc's preserves_inodes
   - CLEANUP: remove commented out code
   - BUGFIX: Silence go get warning

  Debdiff attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-gopkg-lxc-go-lxc.v2/+bug/1621557/+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 1620557] Re: weather.noaa.gov was shut down

Don't worry about marking this a duplicate. We repurposed the other bug
to just track the libmateweather SRU instead.

Do you want to upload the fix for Trusty too?

gnome-applets in Precise is technically no longer supported which I
think was the only thing using this library for actual weather data
there so I'm not personally going to do a precise upload but someone
else could if they wanted to.

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

** Changed in: libgweather (Ubuntu Trusty)
   Importance: Undecided => High

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

** Tags added: precise trusty yakkety

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

Title:
  weather.noaa.gov was shut down

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Trusty:
  Triaged
Status in libgweather source package in Xenial:
  In Progress

Bug description:
  The provider which libgweather was using was shut down in August.

  We need to update libgweather in Xenial to new upstream micro release,
  3.18.2, which switched to a new METAR data provider.

  Impact: this affects all libgweather-using applications, makes them
  unable to retrieve weather data.

  Test Case: make sure Weather applet in gnome-applets is able to
  display weather information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1620557/+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 1621539] Re: Unable to schedule "PM" events in Gnome Calendar 3.20.2

** Changed in: gnome-calendar (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-calendar (Ubuntu)
   Status: New => Triaged

** Also affects: gnome-calendar (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: gnome-calendar (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: gnome-calendar (Ubuntu Xenial)
   Status: New => Triaged

** Bug watch added: GNOME Bug Tracker #770195
   https://bugzilla.gnome.org/show_bug.cgi?id=770195

** Also affects: gnome-calendar via
   https://bugzilla.gnome.org/show_bug.cgi?id=770195
   Importance: Unknown
   Status: Unknown

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

Title:
  Unable to schedule "PM" events in Gnome Calendar 3.20.2

Status in GNOME Calendar:
  Unknown
Status in gnome-calendar package in Ubuntu:
  Triaged
Status in gnome-calendar source package in Xenial:
  Triaged

Bug description:
  The bug is 100% reproducible. I can schedule "AM" events and all day
  events, but no "PM" events. I would expect the part of to advance
  after I had passed noon, but I can keep cycling through the first 12
  hours of the day.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-calendar 3.20.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep  8 10:56:05 2016
  InstallationDate: Installed on 2013-04-26 (1231 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to xenial on 2016-04-02 (159 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calendar/+bug/1621539/+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 1619718] Re: ubuntu-image created vfat eats itself after a while (mcopy creates wrong subdirs)

This bug was fixed in the package mtools - 4.0.18-2ubuntu1

---
mtools (4.0.18-2ubuntu1) yakkety; urgency=medium

  * debian/patches/initialize-direntry.patch: initialize direntry with
memset to correct invalid bitfields.  Thanks to
Ronny Nilsson .  LP: #1619718.

 -- Steve Langasek   Wed, 07 Sep 2016
23:40:07 -0700

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

Title:
  ubuntu-image created vfat eats itself after a while (mcopy creates
  wrong subdirs)

Status in Snappy:
  New
Status in Ubuntu Image:
  Invalid
Status in mtools package in Ubuntu:
  Fix Released
Status in ubuntu-image package in Ubuntu:
  Fix Released
Status in mtools source package in Xenial:
  Fix Committed
Status in ubuntu-image source package in Xenial:
  Invalid

Bug description:
  [SRU Justification]
  Since trusty, using mcopy to create directories will result in corrupted FAT 
entries due to uninitialized memory.  This leads to data loss when an fsck is 
run on the filesystem.

  [Test case] 
  1. Run the script from 
https://bugs.launchpad.net/ubuntu/+source/mtools/+bug/1619718/comments/2
  2. Observe that you are prompted to fix corrupted filesystem entries
  3. Install mtools from xenial-proposed
  4. Run the reproducer.sh script again
  5. Observe that the newly-created filesystem passes fsck with no errors.

  [Regresion potential]
  This is a one-line fix to correct uninitialized memory.  The only regression 
potential is that associated with rebuilding the tools with a new toolchain 
(the last rebuild of these binary packages was in vivid, with gcc-4.9).

  [Original bug description]

  on arm images the vfat used for the boot partition corrupts itself
  after a few reboots (it is noteworthy that on uboot/arm installations
  we write a lot more to the vfat. i would actually expect this to
  happen on x86 systems as well, just a lot later, i.e. after a few
  kernel updates)

  there seem to be various differences in how ubuntu-image creates the
  vfat ...

  in ubuntu-device-flash we use:
  mkfs.vfat -F 32 -S 512 -n ... against a loop mounted partition, the -S 512 
value gets actually matched against blockdev --getss (and adjusted accordingly 
if needed)

  ubuntu-image currently only calls:
  "mkfs.vfat" without any options against an img file that represents the vfat 
content.

  u-d-f also just uses cp against the loop mounted partition while
  ubuntu-image uses mtools' mcopy to put the files in place ...

  the result is that at random boots fsck suddenly starts to rename files in an 
8+3 scheme like:
  http://paste.ubuntu.com/23124260/ or http://paste.ubuntu.com/23124139/ which 
results in http://paste.ubuntu.com/23123498/

  i spent the whole day trying to tweak the mkfs options but to no
  avail, the corruption always happens at some point, so my suspicion
  goes more towards mtools/mcopy now

  http://paste.ubuntu.com/23123789/ is the original code that u-d-f uses
  which does not show such behaviour (i have upgraded the u-d-f rpi2
  image over the last 6 weeks daily with new ubuntu-core and
  occasionally with new pi2-kernel packages without any corruption)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1619718/+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 1619718] Re: ubuntu-image created vfat eats itself after a while (mcopy creates wrong subdirs)

This bug was fixed in the package ubuntu-image - 0.6ubuntu3

---
ubuntu-image (0.6ubuntu3) yakkety; urgency=medium

  * Make the mtools a versioned dep for real, not a versioned build-dep.

 -- Steve Langasek   Thu, 08 Sep 2016
00:45:37 -0700

** Changed in: ubuntu-image (Ubuntu)
   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/1619718

Title:
  ubuntu-image created vfat eats itself after a while (mcopy creates
  wrong subdirs)

Status in Snappy:
  New
Status in Ubuntu Image:
  Invalid
Status in mtools package in Ubuntu:
  Fix Committed
Status in ubuntu-image package in Ubuntu:
  Fix Released
Status in mtools source package in Xenial:
  Fix Committed
Status in ubuntu-image source package in Xenial:
  Invalid

Bug description:
  [SRU Justification]
  Since trusty, using mcopy to create directories will result in corrupted FAT 
entries due to uninitialized memory.  This leads to data loss when an fsck is 
run on the filesystem.

  [Test case] 
  1. Run the script from 
https://bugs.launchpad.net/ubuntu/+source/mtools/+bug/1619718/comments/2
  2. Observe that you are prompted to fix corrupted filesystem entries
  3. Install mtools from xenial-proposed
  4. Run the reproducer.sh script again
  5. Observe that the newly-created filesystem passes fsck with no errors.

  [Regresion potential]
  This is a one-line fix to correct uninitialized memory.  The only regression 
potential is that associated with rebuilding the tools with a new toolchain 
(the last rebuild of these binary packages was in vivid, with gcc-4.9).

  [Original bug description]

  on arm images the vfat used for the boot partition corrupts itself
  after a few reboots (it is noteworthy that on uboot/arm installations
  we write a lot more to the vfat. i would actually expect this to
  happen on x86 systems as well, just a lot later, i.e. after a few
  kernel updates)

  there seem to be various differences in how ubuntu-image creates the
  vfat ...

  in ubuntu-device-flash we use:
  mkfs.vfat -F 32 -S 512 -n ... against a loop mounted partition, the -S 512 
value gets actually matched against blockdev --getss (and adjusted accordingly 
if needed)

  ubuntu-image currently only calls:
  "mkfs.vfat" without any options against an img file that represents the vfat 
content.

  u-d-f also just uses cp against the loop mounted partition while
  ubuntu-image uses mtools' mcopy to put the files in place ...

  the result is that at random boots fsck suddenly starts to rename files in an 
8+3 scheme like:
  http://paste.ubuntu.com/23124260/ or http://paste.ubuntu.com/23124139/ which 
results in http://paste.ubuntu.com/23123498/

  i spent the whole day trying to tweak the mkfs options but to no
  avail, the corruption always happens at some point, so my suspicion
  goes more towards mtools/mcopy now

  http://paste.ubuntu.com/23123789/ is the original code that u-d-f uses
  which does not show such behaviour (i have upgraded the u-d-f rpi2
  image over the last 6 weeks daily with new ubuntu-core and
  occasionally with new pi2-kernel packages without any corruption)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1619718/+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 1615210] Re: [SRU] Please SRU MAAS 2.0 (final) into Xenial

This bug was fixed in the package maas - 2.0.0+bzr5189-0ubuntu1~16.04.1

---
maas (2.0.0+bzr5189-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release, 2.0.0 bzr5189 (SRU LP: #1615210):
- Cluster Controllers now deprecated. Introducing Rack Controllers.
  + Machine no longer belong to Rack Controllers.
  + High availability it is now supported.
  + Rack Controllers manage DHCP on the Fabric Level.
- Region Controller high availability and scalability.
  + Ability to configure multiple Region Controller API endpoints.
- API 1.0 has been deprecated. Introducing new API 2.0.
- MAAS is introducing IP Ranges and deprecated the Static Range.
  + MAAS now controls the whole subnet.
  + The static Range has now been deprecated.
  + Users can now only create a dynamic or reserved range.
- MAAS Static Range has been deprecated. MAAS Controls the whole Subnet.
- New networks GUI.
- MAAS now fully manages DNS.
- Extended Storage Support. Includes:
  + XFS, Mount Options, Swap Partitions, tmpfs/ramfs.
- Adding support for DHCP Snippets.
  + Creates extra custom DHCP config at the Node, Subnet and Global level.
- MAAS Proxy is now managed by MAAS.
- Service Tracking. MAAS now tracks status of the several services it runs.

 -- Andres Rodriguez   Mon, 22 Aug 2016 16:25:57
+0100

** Changed in: maas (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/1615210

Title:
  [SRU] Please SRU MAAS 2.0 (final) into Xenial

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

Bug description:
  Following the SRU of MAAS 2.0rc2 (LP #1599523) in Xenial, we would
  like to request the SRU of MAAS 2.0 Final.

  [Impact]
  This is a new version of MAAS that provides bugfixes only. It addresses 
various upstream bugs, that were fixed after RC2 was released (and before it 
landed in Xenial).

  [Regression Potential]
  Minimal. MAAS has been thoroughly tested stand alone as well as via upgrades. 
It has been QA'd in a CI lab as well as other production deployments:

  Tests done:

  1. Upgraded a production lab.

  2. MAAS CI Lab:
   - Tests Installation (from pkgs), configuration / customization of MAAS, 
enlistment, commissioning. It also tests deployments with Juju.
   - Tests various API's
   - Tests are performed against Xenial

  3. Other manual testing include:
   - Installation (both fresh and upgrades)
   - Configuration
   - Taking nodes through the lifecycle for regression testing.
   - Custom configuration to ensure proper operation.
   - Tests API's for regressions, and keeping backwards compatibility.

  2.0.0 (rc4)
  ===

  Issues fixed in this release
  

  LP: #1592666Mirror URL contains double slash (/) after hostname, 
impacting proxy cachaility.
  LP: #1604461[2.0rc2] Static IP address are allowed to be created in a 
dynamic range.
  LP: #1610397When juju adds containers to MAAS, ensure they inherit the 
parent machine domain name, if none is passed by Juju.
  LP: #1611342UI error while generating a MAAS key (token).
  LP: #1610414apiclient.maas_client.MAASClient.post() always sets an op in 
the query string

  2.0.0 (rc3)
  ===

  Issues fixed in this release
  

  LP: #1557434For the MAAS CLI, mimic the error behaviour provided by 
argparse 1.1 on PyPI when insufficient arguments are given.
  LP: #1594991MAAS displays every power query on the summarized view of 
node event log.
  LP: #1603147Commissioning dropdown is grey and checkmarks are missing.
  LP: #1576116[2.0rc1] MAAS does not respect default subnet's DNS server 
when choosing default DNS
  LP: #1600720[2.0rc1] MAAS doesn't honor DNS settings for a subnet for DHCP
  LP: #1598028[2.0] Loading latest machine events can make web browser 
unresponsive
  LP: #1604128[2.0rc2] Unable to add a public SSH Key due to lp1604147
  LP: #1604169[2.0] maas login yields "ImportError: No module named 
'maasserver'"
  LP: #1604962Fixes to correctly log cloud-init/curtin FAIL events in the 
node event log.
  LP: #1604987Fixes to correctly log "mark_failed" events.
  LP: #1602721[2.0rc2] Can't get node-results via cli/api
  LP: #1604465[2.0] RackController.get_image_sync_status causes huge load 
on regiond process
  LP: #1598149[2.0rc2] MAAS is not automatically monitoring timeouts for 
commissioning.
  LP: #1605252[2.0] Error messaging about monitor expiry has been dropped

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

[Group.of.nepali.translators] [Bug 1591868] Re: fwupd consuming 100% CPU

This bug was fixed in the package appstream-glib - 0.5.13-1ubuntu3

---
appstream-glib (0.5.13-1ubuntu3) xenial; urgency=medium

  * Catch errors from libyaml and display proper warnings
rather than spin on them. (LP: #1591868)

 -- Mario Limonciello   Tue, 30 Aug 2016
13:51:56 -0500

** Changed in: appstream-glib (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/1591868

Title:
  fwupd consuming 100% CPU

Status in appstream-glib package in Ubuntu:
  Fix Released
Status in appstream-glib source package in Xenial:
  Fix Released
Status in appstream-glib source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * Corrupt yaml data is causing consumers of appstream data (such as
  gnome-software or fwupd) to get stuck in a spin and consume CPU and
  battery.

  [Test Case]

   * Introduce corrupt data into /var/lib/app-info/yaml/
   * Execute sudo /usr/lib/x86_64-linux-gnu/fwupd/fwupd -v
   * Check CPU usage calms down after initialization

  [Regression Potential]

   * This patch has been backported from a newer stable release upstream.
   * Due to the nature of backporting, it doesn't directly apply to Ubuntu and 
will need some adjustments made.
   * Regressions would occur in gnome-software not displaying software or fwupd 
not running properly.

  [Other Info]
   
  Original bug report: 

  fwupd process has been consuming 100% of my CPU for several days now
  (IBM Thinkpad x250 running fully updated 16.04).

  gdb backtrace below.

  Thread 2 (Thread 0x7f3272cf5700 (LWP 4496)):
  #0  0x7f3279b79e8d in poll () at ../sysdeps/unix/syscall-template.S:84
  No locals.
  #1  0x7f327ae9331c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #2  0x7f327ae9342c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #3  0x7f327ae93469 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #4  0x7f327aeb9b45 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #5  0x7f3279e4f6fa in start_thread (arg=0x7f3272cf5700) at 
pthread_create.c:333
  __res = 
  pd = 0x7f3272cf5700
  now = 
  unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139854651283200, 
418179942412000561, 0, 140731891236207,
  139854651283904, 0, -312637405101744847, 
-312613451844084431}, mask_was_saved = 0}}, priv = {pad = {
    0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
  not_first_call = 
  pagesize_m1 = 
  sp = 
  freesize = 
  __PRETTY_FUNCTION__ = "start_thread"
  #6  0x7f3279b85b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
  No locals.

  Thread 1 (Thread 0x7f327c926900 (LWP 4486)):
  #0  0x7f3279e542b7 in __GI___pthread_rwlock_rdlock (rwlock=0x7f3279e43920 
<__libc_setlocale_lock>)
  at pthread_rwlock_rdlock.c:135
  result = 0
  wake = false
  #1  0x7f3279aaf0e9 in __dcigettext (domainname=0x7f327aedee63 "glib20",
  msgid1=0x7f327b4ca11a "Invalid compressed data", msgid2=0x0, plural=0, 
n=0, category=5) at dcigettext.c:527
  __p = 
  domain = 
  binding = 
  categoryname = 
  categoryvalue = 
  dirname = 
  xdomainname = 
  single_locale = 
  retval = 
  retlen = 93892446493824
  saved_errno = 0
  search = {domainname = 0x7ffeb262bb00 "`\234\353\teU", category = 
166588464,
    localename = 0x556509ededa8 "p\362\355\teU", counter = 166589040, 
domain = 0x23,
    translation = 0x5565fffb ,
    translation_length = 93892446493792, msgid = {appended = 
0x7ffeb262bb08 "",
  ptr = 0x52fb0a5631f15a00 }}
  foundp = 0x0
  localename = 
  domainname_len = 
  #2  0x7f327b44338c in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  No symbol table info available.
  #3  0x7f327b3e95f9 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  No symbol table info available.
  #4  0x7f327b40d315 in g_input_stream_read () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  No symbol table info available.
  #5  0x7f327c1ae569 in ?? () from 
/usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
  No symbol table info available.
  #6  0x7f3278c51a15 in ?? () from /usr/lib/x86_64-linux-gnu/libyaml-0.so.2
  No symbol table info available.
  #7  0x7f3278c51cde in yaml_parser_update_buffer () from 
/usr/lib/x86_64-linux-gnu/libyaml-0.so.2
  No symbol table info available.
  #8  0x7f3278c56498 in yaml_parser_fetch_more_tokens () from

[Group.of.nepali.translators] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

This bug was fixed in the package isc-dhcp - 4.2.4-7ubuntu12.6

---
isc-dhcp (4.2.4-7ubuntu12.6) trusty; urgency=medium

  * Fixed missing broadcast flag for Infiniband interfaces (LP: #1529815)
- added:
  + d/p/dhcp-4.2.4-dhclient-options-changed.patch

 -- Rafael David Tinoco   Tue, 07 Jun 2016
15:29:50 +0200

** Changed in: isc-dhcp (Ubuntu Trusty)
   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/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in isc-dhcp source package in Wily:
  Won't Fix
Status in isc-dhcp source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Infiniband users relying on DHCP can't use DHCP relay.

  [Test Case]

   * Comment #13
   * Mellanox has tested themselves.
   * Clear way of knowing if fix worked (tcpdump).

  [Regression Potential]

   * Only related to Infiniband.
   * Infiniband support could stop working (unlikely, already tested).

  [Other Info]

  DHCP client is sending discover with Unicast type request for the
  offer, in this configuration of IB to ETH through a relay we need the
  type to be broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  DHCP CLIENT (IPoIB)
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+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 1612423] Re: Suggest python-ldap/python-ldappool packages

This bug was fixed in the package keystone - 2:10.0.0~b3-0ubuntu1~cloud0
---

 keystone (2:10.0.0~b3-0ubuntu1~cloud0) xenial-newton; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 keystone (2:10.0.0~b3-0ubuntu1) yakkety; urgency=medium
 .
   [ James Page ]
   * d/control: Add python-freezegun to BD's.
 .
   [ Corey Bryant ]
   * d/p/*: Rebased.
 .
   [ James Page ]
   * New upstream release.
   * d/control: Add python-ldap and python-ldappool to Suggests (LP: #1612423).
 .
   [ Corey Bryant ]
   * d/control: Add python-pep8 to BDs.
   * New upstream version.
 .
   [ James Page ]
   * New upstream release.
   * Align (Build-)Depends with upstream.


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

Title:
  Suggest  python-ldap/python-ldappool packages

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive liberty series:
  Won't Fix
Status in keystone package in Ubuntu:
  Fix Released
Status in keystone source package in Xenial:
  Won't Fix

Bug description:
  [Description]

  Some customers require to configure LDAP or AD as the authentication backend
  for Keystone. 

  Since Juno, the LDAP auth backend of keystone requires the ldappool module to 
exists
  on the system.

  
https://github.com/openstack/keystone/blob/d07f59ff38e3993d288b71d55436e507366cf98c/keystone/identity/backends/ldap/common.py#L25

  If the system doesn't have this package installed or gets removed by any of 
its
  reverse dependencies or auto remove, the following exception is raised by 
keystone:

  2016-08-07 06:47:24.486089 Traceback (most recent call last): 
  2016-08-07 06:47:24.486107 File "/var/www/cgi-bin/keystone/admin", line 25, 
in  
  2016-08-07 06:47:24.486164 application = 
wsgi_server.initialize_application(name) 
  2016-08-07 06:47:24.486176 File 
"/usr/lib/python2.7/dist-packages/keystone/server/wsgi.py", line 64, in 
initialize_application 
  2016-08-07 06:47:24.486223 startup_application_fn=loadapp) 
  2016-08-07 06:47:24.486234 File 
"/usr/lib/python2.7/dist-packages/keystone/server/common.py", line 49, in 
setup_backends 
  2016-08-07 06:47:24.486275 drivers = backends.load_backends() 
  2016-08-07 06:47:24.486285 File 
"/usr/lib/python2.7/dist-packages/keystone/server/backends.py", line 39, in 
load_backends 
  2016-08-07 06:47:24.486327 _IDENTITY_API = identity.Manager() 
  2016-08-07 06:47:24.486338 File 
"/usr/lib/python2.7/dist-packages/keystone/notifications.py", line 333, in 
__new_init__ 
  2016-08-07 06:47:24.486501 init(self, *args, **kwargs) 
  2016-08-07 06:47:24.486515 File 
"/usr/lib/python2.7/dist-packages/keystone/common/dependency.py", line 95, in 
__wrapped_init__ 
  2016-08-07 06:47:24.486594 init(self, *args, **kwargs) 
  2016-08-07 06:47:24.486606 File 
"/usr/lib/python2.7/dist-packages/keystone/common/dependency.py", line 154, in 
wrapper 
  2016-08-07 06:47:24.486622 self.__wrapped_init__(*args, **kwargs) 
  2016-08-07 06:47:24.486630 File 
"/usr/lib/python2.7/dist-packages/keystone/identity/core.py", line 507, in 
__init__ 
  2016-08-07 06:47:24.486884 super(Manager, 
self).__init__(CONF.identity.driver) 
  2016-08-07 06:47:24.486899 File 
"/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 103, in 
__init__ 
  2016-08-07 06:47:24.486957 self.driver = load_driver(self.driver_namespace, 
driver_name) 
  2016-08-07 06:47:24.486968 File 
"/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 69, in 
load_driver 
  2016-08-07 06:47:24.486982 invoke_args=args) 
  2016-08-07 06:47:24.486993 File 
"/usr/lib/python2.7/dist-packages/stevedore/driver.py", line 45, in __init__ 
  2016-08-07 06:47:24.487053 verify_requirements=verify_requirements, 
  2016-08-07 06:47:24.487064 File 
"/usr/lib/python2.7/dist-packages/stevedore/named.py", line 55, in __init__ 
  2016-08-07 06:47:24.487119 verify_requirements) 
  2016-08-07 06:47:24.487132 File 
"/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 170, in 
_load_plugins 
  2016-08-07 06:47:24.487265 self._on_load_failure_callback(self, ep, err) 
  2016-08-07 06:47:24.487278 File 
"/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 162, in 
_load_plugins 
  2016-08-07 06:47:24.487295 verify_requirements, 
  2016-08-07 06:47:24.487304 File 
"/usr/lib/python2.7/dist-packages/stevedore/named.py", line 123, in 
_load_one_plugin 
  2016-08-07 06:47:24.487330 verify_requirements, 
  2016-08-07 06:47:24.487340 File 
"/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 183, in 
_load_one_plugin 
  2016-08-07 06:47:24.487352 plugin = ep.resolve() 
  2016-08-07 06:47:24.487360 File 
"/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2361, in 
resolve 
  2016-08-07 06:47:24.487815 module

[Group.of.nepali.translators] [Bug 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS

2016-09-08 Thread Mathieu Trudel-Lapierre

** Description changed:

+ [Impact]
+ All VPN users meaning to use split-tunnelling in a situation where leaking 
DNS data to the internet about what might be behind their VPN is undesirable.
+ 
+ [Test case]
+ 1) connect to VPN
+ 2) Use dig to request a name that should be on the VPN
+ 3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only 
gone through the VPN nameservers (only its request number should have increased 
by one)
+ 4) Use dig to request a name off-VPN, such as google.com.
+ 5) Verify (kill -USR1 again) that the request has caused the non-VPN 
nameserver request number to increase, and that the VPN number has not 
increased.
+ 
+ It is easier to verify this when there is as little traffic as possible
+ on the system, to avoid spurious DNS requests which would make it harder
+ to validate the counters.
+ 
+ [Regression potential]
+ This change modifies the way in which DNS nameservers and search domains are 
passed to dnsmasq, as such, if a VPN is configured in a non-standard way and 
intended to be used to resolve all network requests (which is typically not the 
case for split-tunnelling) or if the public network is intended to always 
resolve all requests while the VPN still provides search domains, one might 
observe incorrect behavior.
+ 
+ Possible failure cases would include failure to resolve names correctly
+ (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving to the
+ incorrect values (if the wrong nameserver is used).
+ 
+ ---
+ 
  Currently, NM will write all search domains to both any DNS-handling
  plugins running, and also to resolv.conf / resolvconf; in all cases.
  
  The issue is that doing so means that in the split-DNS case on VPNs, you
  might get a negative response from all nameservers, then a new request
  by glibc with the search tacked on, to nameservers again, which might
  cause DNS requests for "private" resources (say, on the VPN) to be sent
  to external, untrusted resolvers, or for DNS queries not meant for VPN
  nameservers to be sent through the VPN anyway.
  
  This is fixable in the case where we have a caching plugin running (such
  as dnsmasq). dnsmasq will already know about the search domains and use
  that to limit queries to the right nameservers when a VPN is running.
  Writing search domains to resolv.conf is unnecessary in this case.
  
  We should still write search domains if no caching gets done, as we then
  need to expect glibc to send requests as it otherwise would.

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Xenial)
   Importance: Undecided => Medium

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

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

Title:
  Don't write search domains to resolv.conf in the case of split DNS

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress

Bug description:
  [Impact]
  All VPN users meaning to use split-tunnelling in a situation where leaking 
DNS data to the internet about what might be behind their VPN is undesirable.

  [Test case]
  1) connect to VPN
  2) Use dig to request a name that should be on the VPN
  3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only 
gone through the VPN nameservers (only its request number should have increased 
by one)
  4) Use dig to request a name off-VPN, such as google.com.
  5) Verify (kill -USR1 again) that the request has caused the non-VPN 
nameserver request number to increase, and that the VPN number has not 
increased.

  It is easier to verify this when there is as little traffic as
  possible on the system, to avoid spurious DNS requests which would
  make it harder to validate the counters.

  [Regression potential]
  This change modifies the way in which DNS nameservers and search domains are 
passed to dnsmasq, as such, if a VPN is configured in a non-standard way and 
intended to be used to resolve all network requests (which is typically not the 
case for split-tunnelling) or if the public network is intended to always 
resolve all requests while the VPN still provides search domains, one might 
observe incorrect behavior.

  Possible failure cases would include failure to resolve names
  correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving
  to the incorrect values (if the wrong nameserver is used).

  ---

  Currently, NM will write all search domains to both any DNS-handling
  plugins running, and also to resolv.conf / resolvconf; in all cases.

  The issue is that doing so means that in the split-DNS case on VPNs,

[Group.of.nepali.translators] [Bug 1621500] Re: SRU: backport fwupd 0.7.3 to xenial

2016-09-08 Thread Mario Limonciello

** Changed in: fwupd (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  SRU: backport fwupd 0.7.3 to xenial

Status in fwupd package in Ubuntu:
  Invalid
Status in fwupd source package in Xenial:
  Triaged

Bug description:
  [background]

  fwupd 0.7.3 adds support for flashing capsule updates not placed in
  the ESRT.  It uses libsmbios to query the flashability of these
  packages.

  It also resolves the fwupd half of https://launchpad.net/bugs/1589585
  which will fix unplugging a USB device causing gnome-software to check
  for software updates.

  
  Currently this bug will be blocked by a variety of other bugs:
  1) MIR of libsmbios 
  https://bugs.launchpad.net/ubuntu/+source/libsmbios/+bug/1603072
  If/when that MIR is resolved it will need to be made effective in xenial and 
development release both.  If any changes are required for libsmbios, they'll 
need to be backported to xenial too.

  2) FFe for EFI tools transition in yakkety:
  https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1620698
  The rest of the tools don't need to be backported to xenial, only fwupd.  In 
development release upgrading the other tools REQUIRES upgrading fwupd though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1621500/+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 1621500] [NEW] SRU: backport fwupd 0.7.3 to xenial

2016-09-08 Thread Mario Limonciello

Public bug reported:

[background]

fwupd 0.7.3 adds support for flashing capsule updates not placed in the
ESRT.  It uses libsmbios to query the flashability of these packages.

It also resolves the fwupd half of https://launchpad.net/bugs/1589585
which will fix unplugging a USB device causing gnome-software to check
for software updates.


Currently this bug will be blocked by a variety of other bugs:
1) MIR of libsmbios 
https://bugs.launchpad.net/ubuntu/+source/libsmbios/+bug/1603072
If/when that MIR is resolved it will need to be made effective in xenial and 
development release both.  If any changes are required for libsmbios, they'll 
need to be backported to xenial too.

2) FFe for EFI tools transition in yakkety:
https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1620698
The rest of the tools don't need to be backported to xenial, only fwupd.  In 
development release upgrading the other tools REQUIRES upgrading fwupd though.

** Affects: fwupd (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: fwupd (Ubuntu Xenial)
 Importance: Undecided
 Status: Triaged

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

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

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

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

Title:
  SRU: backport fwupd 0.7.3 to xenial

Status in fwupd package in Ubuntu:
  Triaged
Status in fwupd source package in Xenial:
  Triaged

Bug description:
  [background]

  fwupd 0.7.3 adds support for flashing capsule updates not placed in
  the ESRT.  It uses libsmbios to query the flashability of these
  packages.

  It also resolves the fwupd half of https://launchpad.net/bugs/1589585
  which will fix unplugging a USB device causing gnome-software to check
  for software updates.

  
  Currently this bug will be blocked by a variety of other bugs:
  1) MIR of libsmbios 
  https://bugs.launchpad.net/ubuntu/+source/libsmbios/+bug/1603072
  If/when that MIR is resolved it will need to be made effective in xenial and 
development release both.  If any changes are required for libsmbios, they'll 
need to be backported to xenial too.

  2) FFe for EFI tools transition in yakkety:
  https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1620698
  The rest of the tools don't need to be backported to xenial, only fwupd.  In 
development release upgrading the other tools REQUIRES upgrading fwupd though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1621500/+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 1171236] Re: file-roller may delete the content of linked folder (?)

2016-09-08 Thread Tyler Hicks

** Also affects: file-roller (Ubuntu Xenial)
Importance: Undecided
Status: New

** Also affects: file-roller (Ubuntu Trusty)
Importance: Undecided
Status: New

** Changed in: file-roller (Ubuntu Trusty)
Status: New => In Progress

** Changed in: file-roller (Ubuntu Xenial)
Status: New => In Progress

** Changed in: file-roller (Ubuntu Trusty)
Importance: Undecided => Medium

** Changed in: file-roller (Ubuntu Trusty)
Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: file-roller (Ubuntu Xenial)
Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: file-roller (Ubuntu Xenial)
Importance: Undecided => Medium

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

Title:
file-roller may delete the content of linked folder (?)

Status in File Roller:
Fix Released
Status in file-roller package in Ubuntu:
Fix Committed
Status in file-roller source package in Trusty:
In Progress
Status in file-roller source package in Xenial:
In Progress

Bug description:
(Excuse my english, I'm not a native speaker. I will try to be as
clear as possible).

After attempting to create an archive from folders who where actually
just links, it seems that file-roller deleted all their content.

Here are the steps I did :
- Inside a folder, I had a dozen subfolders. Half of them where just links to
folders placed elsewhere.
- In Nautilus, I selected all these subfolders, choosed "compress", then
choosed "zip" as the format.
- The archive was created without any error message.

I was expecting all the folders to be added to the archive, regardless
of them being links or not.

The disastrous result :
- The archive is unusable. Attempting to expand it results in an error
message (I didn't take note, but it was something generic saying the archive
couldn't be expanded).
- But more importantly, the content of the folders who where linked has
disappeared. That is, the links are still here, the folders which they link to
are still here, but they have been emptied.
The files are not in the dustbin, they just disappeared.

I noticed this right after I created the archive, I didn't touch my computer
in-between.
That's why I suspect file-roller.

I will try to reproduce this bug in order to confirm it.
But not before I find a way to recover my files, I lost a week of work
because of this.

Ubuntu 12.10 x64
file-roller 3.6.1.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1171236/+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 1616533] Re: weather.noaa.gov was shut down - MATE unable to retrieve weather forecasts

2016-09-08 Thread Martin Wimpress

** Summary changed:

- "Forecast not available" error in GNOME Weather app
+ weather.noaa.gov was shut down - MATE unable to retrieve weather forecasts

** No longer affects: libgweather (Ubuntu)

** No longer affects: libgweather (Ubuntu Xenial)

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

Title:
  weather.noaa.gov was shut down - MATE unable to retrieve weather
  forecasts

Status in libgweather:
  Fix Released
Status in libmateweather package in Ubuntu:
  Fix Released
Status in libmateweather source package in Xenial:
  Triaged

Bug description:
  The provider which libmateweather was using was shut down in August.

  We need to update libmateweather in Xenial to new upstream micro
  release, 1.12.2, which switched to a new METAR data provider.

  Impact: this affects all libmateweather-using applications, makes them
  unable to retrieve weather data.

  Test Case: make sure Weather applet in mate-applets is able to display
  weather information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1616533/+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 1600000] Re: libnss-resolve treats two trailing dots on a domain name incorrectly

2016-09-08 Thread Martin Pitt

Fix sent upstream: https://github.com/systemd/systemd/issues/3978

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

** Changed in: systemd (Ubuntu)
   Status: Triaged => In Progress

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

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

Title:
  libnss-resolve treats two trailing dots on a domain name incorrectly

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  Triaged

Bug description:
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  208.118.235.148 STREAM wildebeest.gnu.org
  208.118.235.148 DGRAM  
  208.118.235.148 RAW
  (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ resolve dns/ dns/' 
/etc/nsswitch.conf 
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ dns/ resolve dns/' 
/etc/nsswitch.conf 
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  208.118.235.148 STREAM wildebeest.gnu.org
  208.118.235.148 DGRAM  
  208.118.235.148 RAW
  (base)adconrad@nosferatu:~$ 

  This is responsible for the new regression in glibc:

  --
  FAIL: posix/tst-getaddrinfo5
  original exit status 1
  resolving "localhost." worked, proceeding to test
  resolving "localhost.." failed, test passed
  resolving "www.gnu.org." worked, proceeding to test
  resolving "www.gnu.org.." worked, test failed
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/160/+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 1582278] Re: [SR-IOV][CPU Pinning] nova compute can try to boot VM with CPUs from one NUMA node and PCI device from another NUMA node.

** Tags added: mitaka-backport-potential

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

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

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

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

** Changed in: nova (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: nova (Ubuntu Yakkety)
   Importance: Undecided => High

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

Title:
  [SR-IOV][CPU Pinning] nova compute can try to boot VM with CPUs from
  one NUMA node and PCI device from another NUMA node.

Status in OpenStack Compute (nova):
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Triaged
Status in nova source package in Yakkety:
  Fix Released

Bug description:
  Environment:
  Two NUMA nodes on compute host (node-0 and node-1).
  One SR-IOV PCI device associated with NUMA node-1.

  Steps to reproduce:

  Steps to reproduce:
   1) Deploy env with SR-IOV and CPU pinning enable
   2) Create new flavor with cpu pinning:
  nova flavor-show m1.small.performance
  
++---+
  | Property | Value |
  
++---+
  | OS-FLV-DISABLED:disabled | False |
  | OS-FLV-EXT-DATA:ephemeral | 0 |
  | disk | 20 |
  | extra_specs | {"hw:cpu_policy": "dedicated", "hw:numa_nodes": "1"} |
  | id | 7b0e5ee0-0bf7-4a46-9653-9279a947c650 |
  | name | m1.small.performance |
  | os-flavor-access:is_public | True |
  | ram | 2048 |
  | rxtx_factor | 1.0 |
  | swap | |
  | vcpus | 1 |
  
++
   3) download ubuntu image
   4) create sr-iov port and boot vm on this port with m1.small.performance 
flavor:
  NODE_1='node-4.test.domain.local'
  NODE_2='node-5.test.domain.local'
  NET_ID_1=$(neutron net-list | grep net_EW_2 | awk '{print$2}')
  neutron port-create $NET_ID_1 --binding:vnic-type direct --device_owner 
nova-compute --name sriov_23
  port_id=$(neutron port-list | grep 'sriov_23' | awk '{print$2}')
  nova boot vm23 --flavor m1.small.performance --image ubuntu_image 
--availability-zone nova:$NODE_1 --nic port-id=$port_id --key-name vm_key

  Expected results:
   VM is an ACTIVE state
  Actual result:
   In most cases the state is ERROR with following logs:

  2016-05-13 08:25:56.598 29097 ERROR nova.pci.stats 
[req-26138c0b-fa55-4ff8-8f3a-aad980e3c815 d864c4308b104454b7b46fb652f4f377 
9322dead0b5d440986b12596d9cbff5b - - -] Failed to allocate PCI devices for 
instance. Unassigning devices back to pools. This should not happen, since the 
scheduler should have accurate information, and allocation during claims is 
controlled via a hold on the compute node semaphore
  2016-05-13 08:25:57.502 29097 INFO nova.virt.libvirt.driver 
[req-26138c0b-fa55-4ff8-8f3a-aad980e3c815 d864c4308b104454b7b46fb652f4f377 
9322dead0b5d440986b12596d9cbff5b - - -] [instance: 
4e691469-893d-4b24-a0a8-00bbee0fa566] Creating image
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager 
[req-26138c0b-fa55-4ff8-8f3a-aad980e3c815 d864c4308b104454b7b46fb652f4f377 
9322dead0b5d440986b12596d9cbff5b - - -] Instance failed network setup after 1 
attempt(s)
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager Traceback (most 
recent call last):
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1570, in 
_allocate_network_async
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager 
bind_host_id=bind_host_id)
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 666, in 
allocate_for_instance
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager 
self._delete_ports(neutron, instance, created_port_ids)
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager 
self.force_reraise()
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager 
six.reraise(self.type_, self.value, self.tb)
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager   File

[Group.of.nepali.translators] [Bug 1612423] Re: Suggest python-ldap/python-ldappool packages

** Changed in: cloud-archive/liberty
   Status: New => Won't Fix

** Changed in: keystone (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: cloud-archive
   Importance: Undecided => Low

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

Title:
  Suggest  python-ldap/python-ldappool packages

Status in Ubuntu Cloud Archive:
  Fix Committed
Status in Ubuntu Cloud Archive liberty series:
  Won't Fix
Status in keystone package in Ubuntu:
  Fix Released
Status in keystone source package in Xenial:
  Won't Fix

Bug description:
  [Description]

  Some customers require to configure LDAP or AD as the authentication backend
  for Keystone. 

  Since Juno, the LDAP auth backend of keystone requires the ldappool module to 
exists
  on the system.

  
https://github.com/openstack/keystone/blob/d07f59ff38e3993d288b71d55436e507366cf98c/keystone/identity/backends/ldap/common.py#L25

  If the system doesn't have this package installed or gets removed by any of 
its
  reverse dependencies or auto remove, the following exception is raised by 
keystone:

  2016-08-07 06:47:24.486089 Traceback (most recent call last): 
  2016-08-07 06:47:24.486107 File "/var/www/cgi-bin/keystone/admin", line 25, 
in  
  2016-08-07 06:47:24.486164 application = 
wsgi_server.initialize_application(name) 
  2016-08-07 06:47:24.486176 File 
"/usr/lib/python2.7/dist-packages/keystone/server/wsgi.py", line 64, in 
initialize_application 
  2016-08-07 06:47:24.486223 startup_application_fn=loadapp) 
  2016-08-07 06:47:24.486234 File 
"/usr/lib/python2.7/dist-packages/keystone/server/common.py", line 49, in 
setup_backends 
  2016-08-07 06:47:24.486275 drivers = backends.load_backends() 
  2016-08-07 06:47:24.486285 File 
"/usr/lib/python2.7/dist-packages/keystone/server/backends.py", line 39, in 
load_backends 
  2016-08-07 06:47:24.486327 _IDENTITY_API = identity.Manager() 
  2016-08-07 06:47:24.486338 File 
"/usr/lib/python2.7/dist-packages/keystone/notifications.py", line 333, in 
__new_init__ 
  2016-08-07 06:47:24.486501 init(self, *args, **kwargs) 
  2016-08-07 06:47:24.486515 File 
"/usr/lib/python2.7/dist-packages/keystone/common/dependency.py", line 95, in 
__wrapped_init__ 
  2016-08-07 06:47:24.486594 init(self, *args, **kwargs) 
  2016-08-07 06:47:24.486606 File 
"/usr/lib/python2.7/dist-packages/keystone/common/dependency.py", line 154, in 
wrapper 
  2016-08-07 06:47:24.486622 self.__wrapped_init__(*args, **kwargs) 
  2016-08-07 06:47:24.486630 File 
"/usr/lib/python2.7/dist-packages/keystone/identity/core.py", line 507, in 
__init__ 
  2016-08-07 06:47:24.486884 super(Manager, 
self).__init__(CONF.identity.driver) 
  2016-08-07 06:47:24.486899 File 
"/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 103, in 
__init__ 
  2016-08-07 06:47:24.486957 self.driver = load_driver(self.driver_namespace, 
driver_name) 
  2016-08-07 06:47:24.486968 File 
"/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 69, in 
load_driver 
  2016-08-07 06:47:24.486982 invoke_args=args) 
  2016-08-07 06:47:24.486993 File 
"/usr/lib/python2.7/dist-packages/stevedore/driver.py", line 45, in __init__ 
  2016-08-07 06:47:24.487053 verify_requirements=verify_requirements, 
  2016-08-07 06:47:24.487064 File 
"/usr/lib/python2.7/dist-packages/stevedore/named.py", line 55, in __init__ 
  2016-08-07 06:47:24.487119 verify_requirements) 
  2016-08-07 06:47:24.487132 File 
"/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 170, in 
_load_plugins 
  2016-08-07 06:47:24.487265 self._on_load_failure_callback(self, ep, err) 
  2016-08-07 06:47:24.487278 File 
"/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 162, in 
_load_plugins 
  2016-08-07 06:47:24.487295 verify_requirements, 
  2016-08-07 06:47:24.487304 File 
"/usr/lib/python2.7/dist-packages/stevedore/named.py", line 123, in 
_load_one_plugin 
  2016-08-07 06:47:24.487330 verify_requirements, 
  2016-08-07 06:47:24.487340 File 
"/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 183, in 
_load_one_plugin 
  2016-08-07 06:47:24.487352 plugin = ep.resolve() 
  2016-08-07 06:47:24.487360 File 
"/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2361, in 
resolve 
  2016-08-07 06:47:24.487815 module = __import__(self.module_name, 
fromlist=['__name__'], level=0) 
  2016-08-07 06:47:24.487841 File 
"/usr/lib/python2.7/dist-packages/keystone/identity/backends/ldap.py", line 24, 
in  
  2016-08-07 06:47:24.487947 from keystone.common import ldap as common_ldap 
  2016-08-07 06:47:24.487959 File 
"/usr/lib/python2.7/dist-packages/keystone/common/ldap/__init__.py", line 15, 
in  
  2016-08-07 06:47:24.487994 from keystone.common.ldap.core import * # noqa 
  2016-08-07 06:47:24.488005 File 
"/usr/lib/python2.7/dist-packages/keystone/common/ldap/core.py", line 24,

[Group.of.nepali.translators] [Bug 1586900] Re: [SRU] keystoneauth1 2.4.1 for Xenial/Mitaka

** Changed in: cloud-archive/newton
   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/1586900

Title:
  [SRU] keystoneauth1 2.4.1 for Xenial/Mitaka

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 python-keystoneauth1 package in Ubuntu:
  Fix Released
Status in python-keystoneauth1 source package in Xenial:
  Fix Released
Status in python-keystoneauth1 source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Pretty much every OpenStack service generates warning messages when 
configuring keystone authentication.

  [Test Case]
  Install and configure OpenStack services
  deprecation warning in message logs.

  [Regression Potential]
  Minimal - just flips round username/user-name as the supported/deprecated 
option.  Point release also includes a py3 compat fix (already held as a patch) 
and a typo fix for help.

  [Original Bug Report]
  This fixes the username deprecation issue, see 
https://bugs.launchpad.net/python-keystoneclient/+bug/1552634

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1586900/+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 1493303] Re: [OSSA 2016-004] Swift proxy memory leak on unfinished read (CVE-2016-0738)

** Changed in: cloud-archive
   Status: New => Invalid

** Changed in: swift (Ubuntu Wily)
   Status: Triaged => Won't Fix

** Changed in: swift (Ubuntu Trusty)
   Status: Triaged => Won't Fix

** Changed in: swift (Ubuntu Trusty)
   Status: Won't Fix => New

** Changed in: swift (Ubuntu Trusty)
   Importance: Undecided => High

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

Title:
  [OSSA 2016-004] Swift proxy memory leak on unfinished read
  (CVE-2016-0738)

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive icehouse series:
  Triaged
Status in Ubuntu Cloud Archive kilo series:
  Triaged
Status in Ubuntu Cloud Archive liberty series:
  Triaged
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in OpenStack Security Advisory:
  Fix Released
Status in OpenStack Object Storage (swift):
  Fix Released
Status in swift package in Ubuntu:
  Fix Released
Status in swift source package in Trusty:
  New
Status in swift source package in Wily:
  Won't Fix
Status in swift source package in Xenial:
  Fix Released
Status in swift source package in Yakkety:
  Fix Released

Bug description:
  It looks like the Swift proxy will leak memory if the connection is
  closed and the full response is not read. This opens for a potential
  DoS attacks.

  Reproduce:

  $ swift -A http://localhost:/auth/v1.0 -U .. -K .. upload --use-slo 
--segment-size 1048576  
  $ curl -H'X-Auth-Token: AUTH_...' 
"http://localhost:/v1/AUTH_..//" -m 0.001 > /dev/null

  Repeat the curl command a couple of times and you will have more
  information in netstat and sockstat. The important part is the -m
  which sets the max time curl spends at downloading. After that point,
  it'll close the connection.

  $ sudo netstat -ant -p | grep :6000
  $ cat /proc/net/sockstat

  tcp0  0 127.0.0.1:6000  0.0.0.0:*   LISTEN
  1358/python
  tcp0  43221 127.0.0.1:6000  127.0.0.1:48350 FIN_WAIT1 
  -
  tcp0  43221 127.0.0.1:6000  127.0.0.1:48882 FIN_WAIT1 
  -
  tcp   939820  0 127.0.0.1:48350 127.0.0.1:6000  
ESTABLISHED 17897/python
  tcp   939820  0 127.0.0.1:48882 127.0.0.1:6000  
ESTABLISHED 17890/python
  tcp   983041  0 127.0.0.1:48191 127.0.0.1:6000  
CLOSE_WAIT  17897/python
  tcp   983041  0 127.0.0.1:48948 127.0.0.1:6000  
CLOSE_WAIT  17892/python

  Restarting the proxy frees up the lingering memory.

  This problem did not exist in 2.2.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: swift 2.2.2-0ubuntu1~cloud0 [origin: Canonical]
  ProcVersionSignature: Ubuntu 3.16.0-48.64~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CrashDB:
   {
  "impl": "launchpad",
  "project": "cloud-archive",
  "bug_pattern_url": 
"http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml;,
   }
  Date: Tue Sep  8 09:55:05 2015
  InstallationDate: Installed on 2015-06-22 (77 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: swift
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1493303/+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 1576093] Re: [SRU] block migration fail with libvirt since version 1.2.17

** Changed in: cloud-archive
   Status: New => Invalid

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

Title:
  [SRU] block migration fail with libvirt since version  1.2.17

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Fix Released
Status in nova source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Try to do block migration but fail and libvirt reports that

  "Selecting disks to migrate is not implemented for tunneled migration"

  Nova:  a4e15e329f9adbcfe72fbcd6acb94f0743ad02f8

  libvirt: 1.3.1

  [Test Case]

  reproduce:

  default devstack setting and do block migration (no shared
  instance_dir and shared instance storage used)

  [Regression Potential]

  Patch was cherry picked from upstream gerrit review, which was cherry
  picked with little change from master branch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1576093/+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 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled