date:20180208

This bug was fixed in the package gce-compute-image-packages -
20180129+dfsg1-0ubuntu1~17.10.0

---
gce-compute-image-packages (20180129+dfsg1-0ubuntu1~17.10.0) artful; 
urgency=medium

  [ Balint Reczey ]
  * Override false positive maintainer-script-empty Lintian warning
  * Suggest libpam-cracklib instead of recommending it
libpam-cracklib was not installed on cloud images before due to using
--no-install-recommends when installing gce-compute-image-packages, but this
state could have been surprising for users. (LP: #1741989)
  * New upstream version 20180129+dfsg1 (LP: #1746588)
- Close socket connections when requesting metadata.
- Change the OS Login uid restriction to allow uid 1000.
- Improve hostname setting, including restarting rsyslog
  * Backport to Artful

  [ Zach Marano from Google Cloud Team ]
  * Update symlink to shared library with updated revision
  * Depend on rsyslog
  * Force IPv4 for Debian apt configs

 -- Balint Reczey   Wed, 31 Jan 2018 20:14:23 +0100

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1741989/+subscriptions

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

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

This bug was fixed in the package gce-compute-image-packages -
20180129+dfsg1-0ubuntu1~16.04.0

---
gce-compute-image-packages (20180129+dfsg1-0ubuntu1~16.04.0) xenial; 
urgency=medium

  [ Balint Reczey ]
  * Override false positive maintainer-script-empty Lintian warning
  * Suggest libpam-cracklib instead of recommending it
libpam-cracklib was not installed on cloud images before due to using
--no-install-recommends when installing gce-compute-image-packages, but this
state could have been surprising for users. (LP: #1741989)
  * New upstream version 20180129+dfsg1 (LP: #1746588)
- Close socket connections when requesting metadata.
- Change the OS Login uid restriction to allow uid 1000.
- Improve hostname setting, including restarting rsyslog
  * Backport to Xenial

  [ Zach Marano from Google Cloud Team ]
  * Update symlink to shared library with updated revision
  * Depend on rsyslog
  * Force IPv4 for Debian apt configs

 -- Balint Reczey   Wed, 31 Jan 2018 20:14:23 +0100

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

** Changed in: gce-compute-image-packages (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/1741989

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1741989/+subscriptions

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

[Group.of.nepali.translators] [Bug 1746588] Re: Update google compute-image-packages to 20180129

This bug was fixed in the package gce-compute-image-packages -
20180129+dfsg1-0ubuntu1~16.04.0

---
gce-compute-image-packages (20180129+dfsg1-0ubuntu1~16.04.0) xenial; 
urgency=medium

  [ Balint Reczey ]
  * Override false positive maintainer-script-empty Lintian warning
  * Suggest libpam-cracklib instead of recommending it
libpam-cracklib was not installed on cloud images before due to using
--no-install-recommends when installing gce-compute-image-packages, but this
state could have been surprising for users. (LP: #1741989)
  * New upstream version 20180129+dfsg1 (LP: #1746588)
- Close socket connections when requesting metadata.
- Change the OS Login uid restriction to allow uid 1000.
- Improve hostname setting, including restarting rsyslog
  * Backport to Xenial

  [ Zach Marano from Google Cloud Team ]
  * Update symlink to shared library with updated revision
  * Depend on rsyslog
  * Force IPv4 for Debian apt configs

 -- Balint Reczey   Wed, 31 Jan 2018 20:14:23 +0100

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

** Changed in: gce-compute-image-packages (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/1746588

Title:
  Update google compute-image-packages to 20180129

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

Bug description:
  [Impact]

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

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

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

  [Test Case]

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

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

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

  [Other Information]

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1746588/+subscriptions

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

[Group.of.nepali.translators] [Bug 1746588] Re: Update google compute-image-packages to 20180129

This bug was fixed in the package gce-compute-image-packages -
20180129+dfsg1-0ubuntu1~17.10.0

---
gce-compute-image-packages (20180129+dfsg1-0ubuntu1~17.10.0) artful; 
urgency=medium

  [ Balint Reczey ]
  * Override false positive maintainer-script-empty Lintian warning
  * Suggest libpam-cracklib instead of recommending it
libpam-cracklib was not installed on cloud images before due to using
--no-install-recommends when installing gce-compute-image-packages, but this
state could have been surprising for users. (LP: #1741989)
  * New upstream version 20180129+dfsg1 (LP: #1746588)
- Close socket connections when requesting metadata.
- Change the OS Login uid restriction to allow uid 1000.
- Improve hostname setting, including restarting rsyslog
  * Backport to Artful

  [ Zach Marano from Google Cloud Team ]
  * Update symlink to shared library with updated revision
  * Depend on rsyslog
  * Force IPv4 for Debian apt configs

 -- Balint Reczey   Wed, 31 Jan 2018 20:14:23 +0100

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

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

Title:
  Update google compute-image-packages to 20180129

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

Bug description:
  [Impact]

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

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

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

  [Test Case]

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

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

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

  [Other Information]

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1746588/+subscriptions

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

[Group.of.nepali.translators] [Bug 1746909] Re: linux-hwe: 4.13.0-33.36~16.04.1 -proposed tracker

2018-02-08 Thread Steve Beattie

** 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/1746909

Title:
  linux-hwe: 4.13.0-33.36~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746903
  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/1746909/+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 1746905] Re: linux-gcp: 4.13.0-1010.14 -proposed tracker

2018-02-08 Thread Steve Beattie

** 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/1746905

Title:
  linux-gcp: 4.13.0-1010.14 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746903
  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/1746905/+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 1746907] Re: linux-azure: 4.13.0-1010.13 -proposed tracker

2018-02-08 Thread Steve Beattie

** 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/1746907

Title:
  linux-azure: 4.13.0-1010.13 -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:
  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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746903
  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/1746907/+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 1746936] Re: linux: 4.4.0-113.136 -proposed tracker

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

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

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

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

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

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1746937,1746938
  derivatives: 1746939,1746941,1746942,1746944,1746945,1746946
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Thursday, 08. February 2018 07:33 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Friday, 09. February 2018 00:03 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1746937,1746938
  derivatives: 1746939,1746941,1746942,1746944,1746945,1746946
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Friday, 09. February 2018 00:03 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.4.0-113.136 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Confirmed
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
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  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

  backports: 1746937,1746938
  derivatives: 1746939,1746941,1746942,1746944,1746945,1746946
  -- swm properties --
  boot-testing-requested: 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/1746936/+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 1746081] Re: Daemon flags aren't supported ? or unclear how.

2018-02-08 Thread Bug Watch Updater

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

Title:
  Daemon flags aren't supported ? or unclear how.

Status in chrony package in Ubuntu:
  Fix Released
Status in chrony source package in Xenial:
  Triaged
Status in chrony package in Debian:
  Fix Released

Bug description:
  Using:

  Ubuntu 16.04.3 LTS
  Chrony package 2.1.1-1

  I wanted to limit a chrony install to be IPV4 only (-4 flag), but from
  the looks of /etc/init.d/chrony and /etc/defaults there doesn't appear
  to be a clean way to do so.

  /etc/init.d/chrony has FLAGS="defaults" set, but the variable never
  appears to be used.  There is also no reference to bring in anything
  from /etc/default/chrony (which doesn't exist either).

  Perhaps I'm overlooking something.  Is there any way to cleanly add a
  startup flag to the service?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1746081/+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 1746942] Re: linux-snapdragon: 4.4.0-1085.90 -proposed tracker

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

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

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

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

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746936
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 08. February 2018 20:34 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746936
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Thursday, 08. February 2018 20:34 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746936
  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/1746942/+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 1746941] Re: linux-raspi2: 4.4.0-1083.91 -proposed tracker

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

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

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

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

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746936
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 08. February 2018 19:04 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746936
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Thursday, 08. February 2018 19:04 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746936
  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/1746941/+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 1746946] Re: linux-aws: 4.4.0-1051.60 -proposed tracker

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

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

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

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

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746936
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 08. February 2018 19:00 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746936
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Thursday, 08. February 2018 19:00 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-aws: 4.4.0-1051.60 -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:
  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:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746936
  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/1746946/+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 1748247] Re: [CVE] Arbitrary command execution in the removable device notifier

2018-02-08 Thread Rik Mills

** Changed in: plasma-workspace (Ubuntu Bionic)
   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/1748247

Title:
  [CVE] Arbitrary command execution in the removable device notifier

Status in kde-runtime package in Ubuntu:
  New
Status in plasma-workspace package in Ubuntu:
  Fix Released
Status in kde-runtime source package in Trusty:
  In Progress
Status in plasma-workspace source package in Trusty:
  In Progress
Status in kde-runtime source package in Xenial:
  In Progress
Status in plasma-workspace source package in Xenial:
  In Progress
Status in kde-runtime source package in Artful:
  In Progress
Status in plasma-workspace source package in Artful:
  In Progress
Status in kde-runtime source package in Bionic:
  New
Status in plasma-workspace source package in Bionic:
  Fix Released

Bug description:
  KDE Project Security Advisory
  =

  Title:  Plasma Desktop: Arbitrary command execution in the removable 
device notifier
  Risk Rating:High
  CVE:CVE-2018-6791
  Versions:   Plasma < 5.12.0
  Date:   8 February 2018

  
  Overview
  
  When a vfat thumbdrive which contains `` or $() in its volume label is plugged
  and mounted trough the device notifier, it's interpreted as a shell command,
  leaving a possibility of arbitrary commands execution. an example of offending
  volume label is "$(touch b)" which will create a file called b in the
  home folder.

  Workaround
  ==
  Mount removable devices with Dolphin instead of the device notifier.

  Solution
  
  Update to Plasma >= 5.12.0 or Plasma >= 5.8.9

  Or apply the following patches:
  Plasma 5.8:
  
https://commits.kde.org/plasma-workspace/9db872df82c258315c6ebad800af59e81ffb9212
  Plasma 5.9/5.10/5.11:
  
https://commits.kde.org/plasma-workspace/f32002ce50edc3891f1fa41173132c820b917d57

  Credits
  ===
  Thanks to ksieluzyckih for the report and to Marco Martin for the fix.

  Patches for this bug should also contain fixes for CVE-2018-6790:

  KDE Project Security Advisory
  =

  Title:  Plasma: Notifications can expose user IP address
  Risk Rating:Low
  CVE:CVE-2018-6790
  Versions:   Plasma < 5.12.0
  Date:   8 February 2018

  
  Overview
  
  Plasma has support for the Desktop Nofications specification. That 
specification allows
  embedding images in notifications. Plasma was not sanitizing the HTML that 
forms the notification.
  That allowed for notifications to load a remote image leaking the user IP 
address. This is in turn
  made a bit worse by the fact that some chat software doesn't sanitize the 
text they send to the
  notification system either meaning that a third party could send a carefully 
crafted message
  to a chat room and get the IP addresses of the users in that chat room.

  Workaround
  ==
  Disable notifications

  Solution
  
  Update to Plasma >= 5.12.0 or Plasma >= 5.8.9

  Or apply the following patches:
  Plasma 5.8: 
https://cgit.kde.org/plasma-workspace.git/commit/?h=Plasma/5.8=5bc696b5abcdb460c1017592e80b2d7f6ed3107c

  Credits
  ===
  Thanks to David Edmundson for the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1748247/+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 1748247] [NEW] [CVE] Arbitrary command execution in the removable device notifier

2018-02-08 Thread Simon Quigley

*** This bug is a security vulnerability ***

Public security bug reported:

KDE Project Security Advisory
=

Title:  Plasma Desktop: Arbitrary command execution in the removable 
device notifier
Risk Rating:High
CVE:CVE-2018-6791
Versions:   Plasma < 5.12.0
Date:   8 February 2018


Overview

When a vfat thumbdrive which contains `` or $() in its volume label is plugged
and mounted trough the device notifier, it's interpreted as a shell command,
leaving a possibility of arbitrary commands execution. an example of offending
volume label is "$(touch b)" which will create a file called b in the
home folder.

Workaround
==
Mount removable devices with Dolphin instead of the device notifier.

Solution

Update to Plasma >= 5.12.0 or Plasma >= 5.8.9

Or apply the following patches:
Plasma 5.8:

https://commits.kde.org/plasma-workspace/9db872df82c258315c6ebad800af59e81ffb9212
Plasma 5.9/5.10/5.11:

https://commits.kde.org/plasma-workspace/f32002ce50edc3891f1fa41173132c820b917d57

Credits
===
Thanks to ksieluzyckih for the report and to Marco Martin for the fix.

Patches for this bug should also contain fixes for CVE-2018-6790:

KDE Project Security Advisory
=

Title:  Plasma: Notifications can expose user IP address
Risk Rating:Low
CVE:CVE-2018-6790
Versions:   Plasma < 5.12.0
Date:   8 February 2018


Overview

Plasma has support for the Desktop Nofications specification. That 
specification allows
embedding images in notifications. Plasma was not sanitizing the HTML that 
forms the notification.
That allowed for notifications to load a remote image leaking the user IP 
address. This is in turn
made a bit worse by the fact that some chat software doesn't sanitize the text 
they send to the
notification system either meaning that a third party could send a carefully 
crafted message
to a chat room and get the IP addresses of the users in that chat room.

Workaround
==
Disable notifications

Solution

Update to Plasma >= 5.12.0 or Plasma >= 5.8.9

Or apply the following patches:
Plasma 5.8: 
https://cgit.kde.org/plasma-workspace.git/commit/?h=Plasma/5.8=5bc696b5abcdb460c1017592e80b2d7f6ed3107c

Credits
===
Thanks to David Edmundson for the fix.

** Affects: kde-runtime (Ubuntu)
 Importance: High
 Assignee: Rik Mills (rikmills)
 Status: New

** Affects: plasma-workspace (Ubuntu)
 Importance: High
 Assignee: Rik Mills (rikmills)
 Status: Fix Released

** Affects: kde-runtime (Ubuntu Trusty)
 Importance: High
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Affects: plasma-workspace (Ubuntu Trusty)
 Importance: High
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Affects: kde-runtime (Ubuntu Xenial)
 Importance: High
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Affects: plasma-workspace (Ubuntu Xenial)
 Importance: High
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Affects: kde-runtime (Ubuntu Artful)
 Importance: High
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Affects: plasma-workspace (Ubuntu Artful)
 Importance: High
 Assignee: Simon Quigley (tsimonq2)
 Status: In Progress

** Affects: kde-runtime (Ubuntu Bionic)
 Importance: High
 Assignee: Rik Mills (rikmills)
 Status: New

** Affects: plasma-workspace (Ubuntu Bionic)
 Importance: High
 Assignee: Rik Mills (rikmills)
 Status: Fix Released

** Also affects: plasma-workspace (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: plasma-workspace (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: plasma-workspace (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: plasma-workspace (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: kde-runtime (Ubuntu)
   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/1748247

Title:
  [CVE] Arbitrary command execution in the removable device notifier

Status in kde-runtime package in Ubuntu:
  New
Status in plasma-workspace package in Ubuntu:
  Fix Released
Status in kde-runtime source package in Trusty:
  In Progress
Status in plasma-workspace source package in Trusty:
  In Progress
Status in kde-runtime source package in Xenial:
  In Progress
Status in plasma-workspace source package in Xenial:
  In Progress
Status in kde-runtime source package in Artful:
  In Progress
Status in plasma-workspace source package in Artful:
  In Progress
Status in kde-runtime source package in Bionic:
  New
Status in plasma-workspace

[Group.of.nepali.translators] [Bug 1746944] Re: linux-kvm: 4.4.0-1018.23 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1746936
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Thursday, 08. February 2018 15:00 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1746936
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Thursday, 08. February 2018 15:00 UTC
+ phase: Uploaded

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1746944/+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 1637984] Re: Disks shows all mounted snaps

This bug was fixed in the package gnome-disk-utility - 3.26.1-0ubuntu2

---
gnome-disk-utility (3.26.1-0ubuntu2) bionic; urgency=medium

  * debian/patches/hide-if-xgdu-hide.patch:
- Hide file systems mounted with x-gdu.hide userspace mount option
  * debian/patches/hide-snaps.patch:
- Workaround to hide snaps. This is needed because the existing installed
  snaps are not mounted with the x-gdu.hide option. (lp: #1637984)

 -- Andrea Azzarone   Wed, 07 Feb 2018
15:39:32 +0100

** Changed in: gnome-disk-utility (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Disks shows all mounted snaps

Status in GNOME Disks:
  Fix Released
Status in gnome-disk-utility package in Ubuntu:
  Fix Released
Status in udisks2 package in Ubuntu:
  Fix Committed
Status in gnome-disk-utility source package in Xenial:
  Fix Committed
Status in udisks2 source package in Xenial:
  Won't Fix
Status in gnome-disk-utility source package in Artful:
  Fix Committed
Status in udisks2 source package in Artful:
  Won't Fix
Status in gnome-disk-utility source package in Bionic:
  Fix Released
Status in udisks2 source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  In 16.04 and later any installed snaps show as loop devices in Disks.

  * Test Case
  - install a snap
  - open gnome-disks
  -> the snap shouldn't be listed on the left pane as a device

  * Regression potential
  Check that all your existing disks are still listed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1637984/+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 1746909] Re: linux-hwe: 4.13.0-33.36~16.04.1 -proposed tracker

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746903
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 08. February 2018 14:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746903
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Thursday, 08. February 2018 14:31 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-hwe: 4.13.0-33.36~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746903
  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/1746909/+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 1746942] Re: linux-snapdragon: 4.4.0-1085.90 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1746936
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Thursday, 08. February 2018 14:34 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1746936
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Thursday, 08. February 2018 14:34 UTC
+ phase: Uploaded

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1746942/+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 1747802] Re: Snapped applications launched from command line aren't properly matched

Hello Marco, or anyone else affected,

Accepted bamf into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bamf/0.5.3+17.10.20180208-0ubuntu1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

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

** Changed in: bamf (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed-artful

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

Title:
  Snapped applications launched from command line aren't properly
  matched

Status in BAMF:
  Fix Committed
Status in bamf package in Ubuntu:
  Fix Released
Status in bamf source package in Xenial:
  Fix Committed
Status in bamf source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Snapped applications non launched from their desktop file aren't
  properly matched by BAMF.

  [Test case]

  From terminal:
   1. snap install qml-hello-world
   2. qml-hello-world

  The application should start and the icon in the unity launcher should
  contain a Qt logo.

  [Regression Potential]

  Application with security profile might get a wrong desktop file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1747802/+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 1744882] Re: Add SPEC_CTRL and IBRS changes

2018-02-08 Thread Corey Bryant

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/kilo
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/pike
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/ocata
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/icehouse
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/mitaka
   Importance: Undecided
   Status: New

** Changed in: cloud-archive/pike
   Status: New => Fix Committed

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

Title:
  Add SPEC_CTRL and IBRS changes

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive icehouse series:
  New
Status in Ubuntu Cloud Archive kilo series:
  New
Status in Ubuntu Cloud Archive mitaka series:
  New
Status in Ubuntu Cloud Archive ocata series:
  New
Status in Ubuntu Cloud Archive pike series:
  Fix Committed
Status in qemu package in Ubuntu:
  Triaged
Status in qemu source package in Trusty:
  Fix Released
Status in qemu source package in Xenial:
  Fix Released
Status in qemu source package in Artful:
  Fix Released
Status in qemu source package in Bionic:
  Triaged

Bug description:
  The merge of [1] landed the spectre related changes for SPEC_CTRL and
  IBRS to qemu 2.12

  It is announced in [2] that there shall be a 2.11.1 with the backport that we 
intend to pick.
  The security team can use this merge at [1] to work on backwards security 
updates.
  For 18.04 (not yet released) the intention for now is to pick 2.11.1 once 
available.

  [1]: 
https://github.com/qemu/qemu/commit/5cad8ca516011695a37d5be905292722b5249da8
  [2]: https://www.qemu.org/2018/01/04/spectre/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1744882/+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 1746941] Re: linux-raspi2: 4.4.0-1083.91 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1746936
+ kernel-stable-phase-changed:Thursday, 08. February 2018 13:33 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1746936
- kernel-stable-phase-changed:Thursday, 08. February 2018 13:33 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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  upload package.
  This bug will contain status and testing results related to that
  upload.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1746941/+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 1747802] Re: Snapped applications launched from command line aren't properly matched

2018-02-08 Thread Treviño

Artful backport coming also in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3137/+packages

** Also affects: bamf/artful
   Importance: Undecided
   Status: New

** No longer affects: bamf/artful

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

** Changed in: bamf (Ubuntu Xenial)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Snapped applications launched from command line aren't properly
  matched

Status in BAMF:
  Fix Committed
Status in bamf package in Ubuntu:
  Fix Released
Status in bamf source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Snapped applications non launched from their desktop file aren't
  properly matched by BAMF.

  [Test case]

  From terminal:
   1. snap install qml-hello-world
   2. qml-hello-world

  The application should start and the icon in the unity launcher should
  contain a Qt logo.

  [Regression Potential]

  Application with security profile might get a wrong desktop file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1747802/+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 1584828] Re: s390/pci: fix use after free in dma_init

** Changed in: ubuntu-z-systems
   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/1584828

Title:
  s390/pci: fix use after free in dma_init

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #0 - Hendrik Brueckner  - 2016-05-23 
09:09:00 ==
  Please backport upstream Linux commit ID:

  commit dba599091c191d209b1499511a524ad9657c0e5a
  Author: Sebastian Ott 
  Date:   Fri Apr 15 09:41:35 2016 +0200

  s390/pci: fix use after free in dma_init
  
  After a failure during registration of the dma_table (because of the
  function being in error state) we free its memory but don't reset the
  associated pointer to zero.
  
  When we then receive a notification from firmware (about the function
  being in error state) we'll try to walk and free the dma_table again.
  
  Fix this by resetting the dma_table pointer. In addition to that make
  sure that we free the iommu_bitmap when appropriate.
  
  Signed-off-by: Sebastian Ott 
  Reviewed-by: Gerald Schaefer 
  Signed-off-by: Martin Schwidefsky 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1584828/+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 1644662] Re: Icons missing when appearance setting is "high contrast"

2018-02-08 Thread Dariusz Gadomski

** No longer affects: unity-control-center (Ubuntu)

** No longer affects: unity-control-center (Ubuntu Xenial)

** No longer affects: unity-control-center (Ubuntu Artful)

** No longer affects: unity-control-center (Ubuntu Bionic)

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

Title:
  Icons missing when appearance setting is "high contrast"

Status in gnome-themes-standard package in Ubuntu:
  New
Status in gnome-themes-standard source package in Xenial:
  New
Status in gnome-themes-standard source package in Artful:
  New
Status in gnome-themes-standard source package in Bionic:
  New

Bug description:
  [Impact]

   * Switching to HighContrast theme in System Settings/Appearance results in 
missing icons for some of the panels in System Settings.
   * Only Xenial is affected of the currently supported releases.
   * Current development release is not affected.

  [Test Case]

   * Open System Settings, select Appearance.
   * Choose the "High Contrast" theme.
   * Go back by selecting "All Settings".

  Expected result: there are icons to all items in the Settings window.
  Actual result: some items are missing icons.

  [Regression Potential]

   * There might be different icons used in some places depending on the
  fact that for Xenial HighContrast used Adwaita themes. Possibly icons
  may be missing in different places.

  [Other Info]
   * For some reason Trusty was using HighContrast icons and the change was 
made somewhere in between Trusty - Xenial.
   * Original bug description:

  To reproduce this:

  Open System Settings.

  Click Appearance

  Theme: High Contrast.

  Click All Settings tab:

  Many icons are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 24 14:45:30 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-06 (537 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to xenial on 2016-08-28 (88 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-themes-standard/+bug/1644662/+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 1644662] Re: Icons missing when appearance setting is "high contrast"

2018-02-08 Thread Eric Desrochers

** Also affects: gnome-themes-standard (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: unity-control-center (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: gnome-themes-standard (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: unity-control-center (Ubuntu Bionic)
   Importance: Undecided
   Status: 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/1644662

Title:
  Icons missing when appearance setting is "high contrast"

Status in gnome-themes-standard package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  Invalid
Status in gnome-themes-standard source package in Xenial:
  New
Status in unity-control-center source package in Xenial:
  Invalid
Status in gnome-themes-standard source package in Artful:
  New
Status in unity-control-center source package in Artful:
  New
Status in gnome-themes-standard source package in Bionic:
  New
Status in unity-control-center source package in Bionic:
  Invalid

Bug description:
  [Impact]

   * Switching to HighContrast theme in System Settings/Appearance results in 
missing icons for some of the panels in System Settings.
   * Only Xenial is affected of the currently supported releases.
   * Current development release is not affected.

  [Test Case]

   * Open System Settings, select Appearance.
   * Choose the "High Contrast" theme.
   * Go back by selecting "All Settings".

  Expected result: there are icons to all items in the Settings window.
  Actual result: some items are missing icons.

  [Regression Potential]

   * There might be different icons used in some places depending on the
  fact that for Xenial HighContrast used Adwaita themes. Possibly icons
  may be missing in different places.

  [Other Info]
   * For some reason Trusty was using HighContrast icons and the change was 
made somewhere in between Trusty - Xenial.
   * Original bug description:

  To reproduce this:

  Open System Settings.

  Click Appearance

  Theme: High Contrast.

  Click All Settings tab:

  Many icons are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 24 14:45:30 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-06 (537 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to xenial on 2016-08-28 (88 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-themes-standard/+bug/1644662/+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 1543455] Re: wget crashes with openssl-ibmca

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

** Changed in: openssl-ibmca (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: openssl-ibmca (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  wget crashes with openssl-ibmca

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl-ibmca package in Ubuntu:
  Fix Released
Status in openssl-ibmca source package in Xenial:
  Triaged
Status in openssl-ibmca source package in Zesty:
  Won't Fix
Status in openssl-ibmca source package in Artful:
  Fix Released

Bug description:
  WIth openssl-ibmca enabled, wget crashes downloading things from
  launchpad librarian.

  actual bug in openssl-ibmca package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1543455/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.8

---
apparmor (2.10.95-0ubuntu2.8) xenial; urgency=medium

  * d/p/0001-Allow-seven-digit-pid.patch:
On 64bit systems, /proc/sys/kernel/pid_max can be set to PID_MAX_LIMIT,
(2^22), which results in seven digit pids. Adjust the @{PID} variable in
tunables/global to accept this. (LP: #1717714)

 -- Seyeong Kim   Mon, 08 Jan 2018 07:43:46
-0800

** Changed in: apparmor (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/1717714

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.11 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Committed
Status in apparmor source package in Xenial:
  Fix Released
Status in apparmor source package in Artful:
  Fix Released
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor package in Debian:
  Fix Released

Bug description:
  [Impact]

  If PID is larger than 6 digits apparmor denies process which only
  affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
  to 7 digits at the maximum.

  This fix is committed, but not released. so all supporting version are
  affected.

  [1] - man 5 proc

  --
  /proc/sys/kernel/pid_max (since Linux 2.5.34)
  This file specifies the value at which PIDs wrap around (i.e., the value in 
this file is one greater than the maximum PID).  PIDs greater than this value 
are not allocated;  thus,  the value  in this file also acts as a system-wide 
limit on the total number of processes and threads.  The default value for this 
file, 32768, results in the same range of PIDs as on ear‐lier kernels.  On 
32-bit platforms, 32768 is the maximum value for pid_max.  On 64-bit systems, 
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 
million).
  --

  [Test Case]

  1. making pid over 6 digits
  #!/bin/bash

  for i in {1..100}
  do
    touch t
  done

  2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
  16-2.30 avoids using /proc/PID/cmdline, so need to use older version

  3. you can see DENIED msgs in syslog

  4. change /etc/apparmor.d/tunables/kernelvars
  5. service apparmor restart
  6. service snapd restart
  7. DENIED is gone

  This is one way, can't reproduce this issue again even if you change
  back to original kernelvars, and restart snapd

  OR

  instead of Seyeong's touch approach, things can be manually change to
  7 digits range via sysctl as long as the values are below
  approximately 4 millions :

  Example:
  $ sysctl -w kernel.pid_max=300
  $ sysctl -w kernel.ns_last_pid=100

  [Regression]
  * This is a minor/trivial fix which changes the pid regex only, allowing 7 
digits PID instead of only 6 digits PID, we don't think there is any potential 
regression.

  * If a regression arise, which we highly doubt, one can quickly revert
  the change manually and restart the service by modifying
  "/etc/apparmor.d/tunables/kernelvars" file to its original state
  (before this SRU).

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  * Debian bug:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732

  * commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
  Author: Vincas Dargis 
  Date:   Sat Sep 30 15:28:15 2017 +0300

  Allow seven digit pid

  * Affecting releases : TXZAB
  --
  $ git describe --contains 630cb2a9
  v2.11.95~5^2

  $ rmadison apparmor
   apparmor | 2.8.95~2430-0ubuntu5   | trusty
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
   apparmor | 2.10.95-0ubuntu2   | xenial
   apparmor | 2.10.95-0ubuntu2.6 | xenial-security
   apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
   apparmor | 2.11.0-2ubuntu4| zesty
   apparmor | 2.11.0-2ubuntu17   | artful
   apparmor | 2.11.0-2ubuntu18   | bionic

  $ rmadison -u debian apparmor
   apparmor | 2.11.1-4   | unstable
  --

  [Original Description]

  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any

[Group.of.nepali.translators] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

This bug was fixed in the package apparmor - 2.11.0-2ubuntu17.1

---
apparmor (2.11.0-2ubuntu17.1) artful; urgency=medium

  * d/p/0001-Allow-seven-digit-pid.patch:
On 64bit systems, /proc/sys/kernel/pid_max can be set to PID_MAX_LIMIT,
(2^22), which results in seven digit pids. Adjust the @{PID} variable in
tunables/global to accept this. (LP: #1717714)

 -- Seyeong Kim   Mon, 08 Jan 2018 07:49:55
-0800

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

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.11 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Committed
Status in apparmor source package in Xenial:
  Fix Released
Status in apparmor source package in Artful:
  Fix Released
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor package in Debian:
  Fix Released

Bug description:
  [Impact]

  If PID is larger than 6 digits apparmor denies process which only
  affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
  to 7 digits at the maximum.

  This fix is committed, but not released. so all supporting version are
  affected.

  [1] - man 5 proc

  --
  /proc/sys/kernel/pid_max (since Linux 2.5.34)
  This file specifies the value at which PIDs wrap around (i.e., the value in 
this file is one greater than the maximum PID).  PIDs greater than this value 
are not allocated;  thus,  the value  in this file also acts as a system-wide 
limit on the total number of processes and threads.  The default value for this 
file, 32768, results in the same range of PIDs as on ear‐lier kernels.  On 
32-bit platforms, 32768 is the maximum value for pid_max.  On 64-bit systems, 
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 
million).
  --

  [Test Case]

  1. making pid over 6 digits
  #!/bin/bash

  for i in {1..100}
  do
    touch t
  done

  2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
  16-2.30 avoids using /proc/PID/cmdline, so need to use older version

  3. you can see DENIED msgs in syslog

  4. change /etc/apparmor.d/tunables/kernelvars
  5. service apparmor restart
  6. service snapd restart
  7. DENIED is gone

  This is one way, can't reproduce this issue again even if you change
  back to original kernelvars, and restart snapd

  OR

  instead of Seyeong's touch approach, things can be manually change to
  7 digits range via sysctl as long as the values are below
  approximately 4 millions :

  Example:
  $ sysctl -w kernel.pid_max=300
  $ sysctl -w kernel.ns_last_pid=100

  [Regression]
  * This is a minor/trivial fix which changes the pid regex only, allowing 7 
digits PID instead of only 6 digits PID, we don't think there is any potential 
regression.

  * If a regression arise, which we highly doubt, one can quickly revert
  the change manually and restart the service by modifying
  "/etc/apparmor.d/tunables/kernelvars" file to its original state
  (before this SRU).

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  * Debian bug:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732

  * commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
  Author: Vincas Dargis 
  Date:   Sat Sep 30 15:28:15 2017 +0300

  Allow seven digit pid

  * Affecting releases : TXZAB
  --
  $ git describe --contains 630cb2a9
  v2.11.95~5^2

  $ rmadison apparmor
   apparmor | 2.8.95~2430-0ubuntu5   | trusty
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
   apparmor | 2.10.95-0ubuntu2   | xenial
   apparmor | 2.10.95-0ubuntu2.6 | xenial-security
   apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
   apparmor | 2.11.0-2ubuntu4| zesty
   apparmor | 2.11.0-2ubuntu17   | artful
   apparmor | 2.11.0-2ubuntu18   | bionic

  $ rmadison -u debian apparmor
   apparmor | 2.11.1-4   | unstable
  --

  [Original Description]

  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any

[Group.of.nepali.translators] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

Zesty is end of life.

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

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in linux source package in Zesty:
  Won't Fix
Status in procps source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

  ubuntu@zm93k8:~$  cat /proc/sys/fs/aio-max-nr
  65536


  # Attempt to start

[Group.of.nepali.translators] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

zesty is End Of Life

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Won't Fix

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in linux source package in Zesty:
  Won't Fix
Status in procps source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

  ubuntu@zm93k8:~$  cat /proc/sys/fs/aio-max-nr
  65536


  # Attempt to

[Group.of.nepali.translators] [Bug 1747970] Re: [Hyper-V] vsock: always call vsock_init_tables()

2018-02-08 Thread Stefan Bader

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

** Also affects: linux-azure-edge (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/1747970

Title:
  [Hyper-V] vsock: always call vsock_init_tables()

Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure-edge source package in Xenial:
  New

Bug description:
  Guest kernel panic for VMs in enhanced session mode when the XRDP
  channel connection happens too early in the boot.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c1eef220c1760762753b602c382127bfccee226d

  vsock: always call vsock_init_tables()
  Although CONFIG_VSOCKETS_DIAG depends on CONFIG_VSOCKETS,
  vsock_init_tables() is not always called, it is called only
  if other modules call its caller. Therefore if we only
  enable CONFIG_VSOCKETS_DIAG, it would crash kernel on uninitialized
  vsock_bind_table.

  This patch fixes it by moving vsock_init_tables() to its own
  module_init().

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1747970/+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 1747802] Re: Snapped applications launched from command line aren't properly matched

I'm wondering if it makes sense to also get this released for artful?
Unity is not the default experience but the package is still available,
so in theory someone upgrading from xenial to artful and insisting on
staying with Unity as his shell might experience a regression.

What do you think? I'll accept it for now, but maybe it's worth
considering?

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

** Changed in: bamf (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-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/1747802

Title:
  Snapped applications launched from command line aren't properly
  matched

Status in BAMF:
  Fix Committed
Status in bamf package in Ubuntu:
  Fix Released
Status in bamf source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Snapped applications non launched from their desktop file aren't
  properly matched by BAMF.

  [Test case]

  From terminal:
   1. snap install qml-hello-world
   2. qml-hello-world

  The application should start and the icon in the unity launcher should
  contain a Qt logo.

  [Regression Potential]

  Application with security profile might get a wrong desktop file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1747802/+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 1747814] Re: Snapped applications using ubuntu launcher integration needs desktop update

I'm wondering if it makes sense to also get this released for artful?
Unity is not the default experience but the package is still available,
so in theory someone upgrading from xenial to artful and insisting on
staying with Unity as his shell might experience a regression.

What do you think? I'll accept it for now, but maybe it's worth
considering?

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

** Changed in: libunity (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-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/1747814

Title:
  Snapped applications using ubuntu launcher integration needs desktop
  update

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

Bug description:
  [ Impact ]

  Launching a snapped application with ubuntu launcher icon integration
  doesn't properly work as the desktop ID does not use the proper
  namespace.

  Also, a snapped app could decorate other apps outside the snap scope.

  [ Test case ]

  git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git
  cd ubuntu-launcher-integration-snap
  snapcraft prime
  snap try prime

  Then launch those (you might do it from dash/activities to get proper 
matching):
   ubuntu-launcher-integration-snap.ubuntu-launcher
   ubuntu-launcher-integration-snap.ubuntu-launcher-2nd
   ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded

  All these apps should get an icon in the launcher with emblems (of
  different values when they're launched together).

  [ Regression potential ]

  Application with SNAP environments could point to wrong desktop-file
  to decorate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1747814/+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 1582725] Re: cinder_policy.json action does not match the Cinder policy.json file

2018-02-08 Thread James Page

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

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

** Also affects: cloud-archive/mitaka
   Importance: Undecided
   Status: New

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

** Changed in: cloud-archive/mitaka
   Status: New => Triaged

** Changed in: cloud-archive/mitaka
   Importance: Undecided => Medium

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

** Changed in: horizon (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/1582725

Title:
  cinder_policy.json action does not match the Cinder policy.json file

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Xenial:
  Triaged

Bug description:
  [Impact]
  cinder policies are not in horizon's policy.json
  so unset tab "consistency groups" is enabled by default.

  Affected to Xenial, UCA_Mitaka

  
  [Test Case]
  1. deploy simple openstack deployments via juju
  2. horizon -> volume -> check if there is consistency groups tab

  [Regression]
  after this patch, horizon needs to be restarted. so it is down shortly. this 
patch is actually config file changed ( and little source code ). so limited 
affection to behavior it self.

  [Other]

  related commit

  
https://git.openstack.org/cgit/openstack/horizon/commit/?id=388708b251b0487bb22fb3ebb8fcb36ee4ffdc4f

  [Original Description]

  The horizon/openstack_dashboard/conf/cinder_policy.json actions do not match 
the policy action that are used by the Cinder component.
  Cinder uses "volume_extension:volume_actions:upload_public"
  and Horizon policy.json and code uses "volume:upload_to_image"

  This is the only miss match of policy action between the 2 components.
  This also does not allow a user of Cinder and Horizon to update the
  Cinder policy.json and copy it to the Horizon directly and have the
  button function according to Cinder policy.json rules.

  This can be missed as the Cinder policy.json file is update and the
  Horizon file is updated.

  I think that the action that the Horizon code is using should match it
  component that it is supporting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1582725/+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 1547647] Proposed package removed from archive

The version of signon-ui in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

** Changed in: signon-ui (Ubuntu Xenial)
   Status: Fix Committed => Won't Fix

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

Title:
  [SRU] please remove libqt5webkit dependency

Status in signon-ui package in Ubuntu:
  Fix Released
Status in signon-ui source package in Xenial:
  Won't Fix
Status in signon-ui source package in Yakkety:
  Fix Released

Bug description:
  This is an SRU request, based on the process documented at
  https://wiki.ubuntu.com/StableReleaseUpdates

  
  [Impact]

   * When declaring online accounts for use by Ubuntu, the system uses a
  webview to authenticate to online services like Facebook or Google.

   * On X11 desktops, that webview currently uses an old qt5webkit
  component that is now unmaintained

   * Backporting this fix will simplify the maintenance work, by
  removing the need for that old component, and will improve the
  coherence of the system by using a supported Oxide webview

  [Test Case]

  To verify the change:

   * Go to system settings > Online Accounts
   * Add account of type Google, Facebook or Twitter (which uses webview for 
authentication)
   * Verify that a webview opens to log onto the online service
   * Verify that the account is listed in the account list at the end of this 
process
   * Verify that the related apps and services can use the online account as 
before (ie Shotwell photo uploads, Photos scope, etc.)

  [Regression Potential]

   * On architectures not supported by Oxide, namely ppc64el and s390x,
  the change will trigger a runtime error when trying to use that part
  of signon-ui.

   * The problem affects users of Ubuntu desktop systems based on X11.
  The change is already in effect on Unity8/Mir devices for a few
  months.

  [Other Info]

   * signon-ui-x11(http://packages.ubuntu.com/xenial/signon-ui-x11)
  depends on libqt5webkit5

   * See also: https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-
  security-updates/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1547647/+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 1724896] Re: [MRE] Please update to latest upstream release 7.0.25

This bug was fixed in the package php7.0 - 7.0.25-0ubuntu0.16.04.1

---
php7.0 (7.0.25-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream release (7.0.25)
- LP: #1724896
- LP: #1721607

 -- Nishanth Aravamudan   Wed, 01 Nov
2017 10:18:38 -0700

** Changed in: php7.0 (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/1724896

Title:
  [MRE] Please update to latest upstream release 7.0.25

Status in php7.0 package in Ubuntu:
  Invalid
Status in php7.0 source package in Xenial:
  Fix Released
Status in php7.0 source package in Zesty:
  Fix Committed

Bug description:
  There have been a number of microreleases of PHP 7.0 upstream since the
  last update to Xenial (which corresponded to the last update in Zesty). As
  it has been a few months, it feels appropriate to provide another
  MRE update to php7.0. A number of critical security and bug-fixes are
  present in each 7.0.x. Rather than backporting individual patches (e.g.,
  Bug # 1569509), I believe it makes significantly more sense to follow
  the upstream 7.0.x. Upstream PHP is demonstrating an improved approach
  of bugfixes only in 7.0.x:

   - 7.0.25: http://php.net/ChangeLog-7.php

  The upstream CI is at: https://travis-ci.org/php/php-src and is run
  regularly.

  Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php,
  cgi, fpm and cli. We have also updated the packing to run the source
  tests during the build itself.

  I do not believe there is a firm statement from upstream on API/ABI
  stability, but the general approach seems to be a BC-break would result
  in 7.1.0 (which is present in Artful, and is why the Artful task is invalid).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1724896/+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 1644662] Re: Icons missing when appearance setting is "high contrast"

2018-02-08 Thread Dariusz Gadomski

** Also affects: gnome-themes-standard (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-control-center (Ubuntu Xenial)
   Status: Confirmed => Invalid

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

Title:
  Icons missing when appearance setting is "high contrast"

Status in gnome-themes-standard package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  Invalid
Status in gnome-themes-standard source package in Xenial:
  New
Status in unity-control-center source package in Xenial:
  Invalid

Bug description:
  [Impact]

   * Switching to HighContrast theme in System Settings/Appearance results in 
missing icons for some of the panels in System Settings.
   * Only Xenial is affected of the currently supported releases.
   * Current development release is not affected.

  [Test Case]

   * Open System Settings, select Appearance.
   * Choose the "High Contrast" theme.
   * Go back by selecting "All Settings".

  Expected result: there are icons to all items in the Settings window.
  Actual result: some items are missing icons.

  [Regression Potential]

   * There might be different icons used in some places depending on the
  fact that for Xenial HighContrast used Adwaita themes. Possibly icons
  may be missing in different places.

  [Other Info]
   * For some reason Trusty was using HighContrast icons and the change was 
made somewhere in between Trusty - Xenial.
   * Original bug description:

  To reproduce this:

  Open System Settings.

  Click Appearance

  Theme: High Contrast.

  Click All Settings tab:

  Many icons are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 24 14:45:30 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-06 (537 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to xenial on 2016-08-28 (88 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-themes-standard/+bug/1644662/+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 1721607] Re: please update to latest upstream release 7.0.24

This bug was fixed in the package php7.0 - 7.0.25-0ubuntu0.16.04.1

---
php7.0 (7.0.25-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream release (7.0.25)
- LP: #1724896
- LP: #1721607

 -- Nishanth Aravamudan   Wed, 01 Nov
2017 10:18:38 -0700

** Changed in: php7.0 (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/1721607

Title:
  please update to latest upstream release 7.0.24

Status in php7.0 package in Ubuntu:
  Incomplete
Status in php7.0 source package in Xenial:
  Fix Released
Status in php7.0 source package in Zesty:
  Fix Committed

Bug description:
  There are serious vulnerabilties in php7.0.22, which is what is
  currently considered up to date.

  https://www.cisecurity.org/advisory/multiple-vulnerabilities-in-php-
  could-allow-for-arbitrary-code-execution_2017-093/

  There is a patched version at
  https://launchpad.net/~ondrej/+archive/ubuntu/php?field.series_filter=xenial

  Is there a reason not to make it the current version?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1721607/+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 1734983] Re: Request to backport sosreport v3.5

This bug was fixed in the package sosreport - 3.5-1~ubuntu14.04.2

---
sosreport (3.5-1~ubuntu14.04.2) trusty; urgency=medium

  * d/p/0003-fix-name-containers-is-not-defined.patch:
"containers" is an unknown variable, "insp" is the correct one.
(LP: #1734983)

sosreport (3.5-1~ubuntu14.04.1) trusty; urgency=medium

  * New upstream release v3.5 (LP: #1734983)
New features include :
New plugins for :
* perl
* boom
* vdo
* os_net_config
* conntrackd
* ovirt_imageio
* nss
* sas3ircu
* openstack_aodh
* docker_distribution
* gluster_block
* snappy

  * Plugin API enhancements
* Plugin triggers by executable name
* Improved log size limit handling
* Better handling of compressed log files
* Per-plugin package verification lists

  * Updates to 227 plugins

  * Debian modifications:
- Addition of DEP8 tests
- Do not run Python2 only tests

  * d/p/0002-reset-to-expected-variable-order-for-packagemanager.patch:
Fixing severe regression where many "packages = " lines are no
longer working in Debian/Ubuntu. Preventing automatic package detection.

 -- Eric Desrochers   Thu, 25 Jan 2018
16:01:03 -0500

** Changed in: sosreport (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/1734983

Title:
  Request to backport sosreport v3.5

Status in sosreport:
  New
Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  Fix Released
Status in sosreport source package in Xenial:
  Fix Released
Status in sosreport source package in Zesty:
  Won't Fix
Status in sosreport source package in Artful:
  Fix Released
Status in sosreport source package in Bionic:
  Fix Released
Status in sosreport package in Debian:
  New

Bug description:
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new bugfixes,
  new features such as new plugins[1],  that can be interesting to
  have in a support context.

  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.

  [1] - New plugins for :
  * perl
  * boom
  * vdo
  * os_net_config
  * conntrackd
  * ovirt_imageio
  * nss
  * sas3ircu
  * openstack_aodh
  * docker_distribution
  * gluster_block
  * snappy

  Plugin API enhancements
  * Plugin triggers by executable name
  * Improved log size limit handling
  * Better handling of compressed log files
  * Per-plugin package verification lists

  Updates to 227 plugins

  This will also allow us to close some sosreport LP bugs:
  *Docker plugin uses the wrong command for Ubuntu (LP: #1693574)

  [Test Case]

   * Install sosreport
     $ apt-get install sosreport

   * Run sosreport
     $ sosreport -a
     $ sosreport -o 
     $ ...

   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport--.tar.xz"

   * Extract files from archive
     $ tar Jxvf /tmp/sosreport--.tar.xz

   * Look the content of sosreport, make sure the information is
  accurate and valid, 

   * Make sure all files that should to be collected by sosreport aren't 0 
size. (Files that should be collected may varies from one system to another, it 
depends on what packages are installed, ...)
     $ find /tmp/sosreport-- -size 0

  # Note :
  It is normal to see some 0 size files here and there, again it depend on how 
the plugin is run (package detection or not inside the plugins, ...) and if the 
package is installed or not on the system where you run sosreport. But in most 
cases, if the package is installed and if sosreport has a plugin for it then it 
should gather information, if not then it might be a problem with the plugins 
itself that need adjustments.

  [Regression Potential]

   * autopkgtest[2] didn't reveal any
  [2] - See Comment #1

   * We,STS, have intensively tested the package.

  During our testing, we found a severe regression that we already took
  action to fix it via :

  - Upstream issue - https://github.com/sosreport/sos/issues/1155
  - Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537
  - Fix Released in Ubuntu Devel release (bionic) via debdiff : 
lp1734983_bionic.debdiff

  [Other Info]

   * Sosreport upstream :
     https://github.com/sosreport/sos

   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2| oldstable  | source, amd64, 
arm64,

[Group.of.nepali.translators] [Bug 1117944] Re: [SRU] intltool confused by separate build-dir

This bug was fixed in the package intltool - 0.51.0-2ubuntu1.16.04.1

---
intltool (0.51.0-2ubuntu1.16.04.1) xenial; urgency=medium

* no-guess-builddir.patch: new patch by Aleksander Morgado.
Fixes build of various projects when builddir is not the same
as srcdir (e.g. when running make distcheck). (LP: #1117944)

-- Vlad Orlov Sat, 23 Sep 2017 14:01:01 +0300

** Changed in: intltool (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/1117944

Title:
[SRU] intltool confused by separate build-dir

Status in intltool:
Confirmed
Status in intltool package in Ubuntu:
Fix Released
Status in intltool source package in Xenial:
Fix Released
Status in intltool source package in Artful:
Fix Released

Bug description:
[Impact]

An old bug in intltool breaks out-of-tree builds, including "make
distcheck", in a lot of intltool-using projects when automake version
is 1.15 or newer.

The fix for this issue (by Aleksander Morgado) is provided in the
debdiffs attached to the report.

It's a long-standing bug which is present in all current Ubuntu releases,
starting from Xenial. Would be really nice to get it finally fixed. The
developers have to patch their intltool locally just to have a working
distcheck target (which is used when making release tarballs).

[Test Case]

Try making release tarball for some upstream package. For example, it
can be mate-desktop, a base project for various MATE components.

$ sudo apt-get build-dep mate-desktop
$ git clone https://github.com/mate-desktop/mate-desktop
$ cd mate-desktop
$ ./autogen.sh --enable-gtk-doc --enable-deprecated --disable-strict
$ make -j5 && make dist -j5 && make distcheck -j5

This will build the project, make release tarball and check it by
unpacking it into a new directory and building (again) in it. The last
step will fail:

---

srcdir=../../../po /usr/bin/intltool-update -m
The following files contain translations and are currently not in use. Please
consider adding these to the POTFILES.in file, located in the po/ directory.

sub/mate-about/mate-about.desktop.in
sub/tools/mate-color-select.desktop.in

If some of these files are left out on purpose then please add them to
POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list
of left out files has been written in the current directory.
Please report to https://github.com/mate-desktop/mate-desktop/
if [ -r missing -o -r notexist ]; then \
exit 1; \
fi
Makefile:179: recipe for target 'check' failed

---

The out-of-tree build breaks here.

[Regression Potential]

None. This is a fix for a broken feature, it doesn't affects other ones.
Also the fix had been tested by MATE developers in various distros, including
Debian, Ubuntu and Fedora.

[Original Description]

systemd uses 'intltool-update -m' from intltoolize in its 'make check'.
$(top_srcdir)/po/POTFILES.skip contains the name of a generated file
(src/core/org.freedesktop.systemd1.policy.in), which will be generated as
$(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If
$(builddir)==$(srcdir) than everything works fine. When they are different,
there's no way to instruct intltool-update to skip the file. Since the name of
the build directory is not known and can be arbitrary, there should be a way to
instruct intltool-update to ignore files relative to the $(top_builddir), or
something like that. One option would be to turn the file list into a list of
globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in
our case).

To manage notifications about this bug go to:
https://bugs.launchpad.net/intltool/+bug/1117944/+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 1734983] Re: Request to backport sosreport v3.5

This bug was fixed in the package sosreport - 3.5-1~ubuntu16.04.2

---
sosreport (3.5-1~ubuntu16.04.2) xenial; urgency=medium

  * d/p/0003-fix-name-containers-is-not-defined.patch:
"containers" is an unknown variable, "insp" is the correct one.
(LP: #1734983)

sosreport (3.5-1~ubuntu16.04.1) xenial; urgency=medium

  * New upstream release v3.5 (LP: #1734983)
New features include :
New plugins for :
* perl
* boom
* vdo
* os_net_config
* conntrackd
* ovirt_imageio
* nss
* sas3ircu
* openstack_aodh
* docker_distribution
* gluster_block
* snappy

  * Plugin API enhancements
* Plugin triggers by executable name
* Improved log size limit handling
* Better handling of compressed log files
* Per-plugin package verification lists

  * Updates to 227 plugins

  * Debian modifications:
- Addition of DEP8 tests
- Do not run Python2 only tests

  * d/p/0002-reset-to-expected-variable-order-for-packagemanager.patch:
Fixing severe regression where many "packages = " lines are no
longer working in Debian/Ubuntu. Preventing automatic package detection.

 -- Eric Desrochers   Thu, 25 Jan 2018
15:55:05 -0500

** Changed in: sosreport (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/1734983

Title:
  Request to backport sosreport v3.5

Status in sosreport:
  New
Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  Fix Released
Status in sosreport source package in Xenial:
  Fix Released
Status in sosreport source package in Zesty:
  Won't Fix
Status in sosreport source package in Artful:
  Fix Released
Status in sosreport source package in Bionic:
  Fix Released
Status in sosreport package in Debian:
  New

Bug description:
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new bugfixes,
  new features such as new plugins[1],  that can be interesting to
  have in a support context.

  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.

  [1] - New plugins for :
  * perl
  * boom
  * vdo
  * os_net_config
  * conntrackd
  * ovirt_imageio
  * nss
  * sas3ircu
  * openstack_aodh
  * docker_distribution
  * gluster_block
  * snappy

  Plugin API enhancements
  * Plugin triggers by executable name
  * Improved log size limit handling
  * Better handling of compressed log files
  * Per-plugin package verification lists

  Updates to 227 plugins

  This will also allow us to close some sosreport LP bugs:
  *Docker plugin uses the wrong command for Ubuntu (LP: #1693574)

  [Test Case]

   * Install sosreport
     $ apt-get install sosreport

   * Run sosreport
     $ sosreport -a
     $ sosreport -o 
     $ ...

   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport--.tar.xz"

   * Extract files from archive
     $ tar Jxvf /tmp/sosreport--.tar.xz

   * Look the content of sosreport, make sure the information is
  accurate and valid, 

   * Make sure all files that should to be collected by sosreport aren't 0 
size. (Files that should be collected may varies from one system to another, it 
depends on what packages are installed, ...)
     $ find /tmp/sosreport-- -size 0

  # Note :
  It is normal to see some 0 size files here and there, again it depend on how 
the plugin is run (package detection or not inside the plugins, ...) and if the 
package is installed or not on the system where you run sosreport. But in most 
cases, if the package is installed and if sosreport has a plugin for it then it 
should gather information, if not then it might be a problem with the plugins 
itself that need adjustments.

  [Regression Potential]

   * autopkgtest[2] didn't reveal any
  [2] - See Comment #1

   * We,STS, have intensively tested the package.

  During our testing, we found a severe regression that we already took
  action to fix it via :

  - Upstream issue - https://github.com/sosreport/sos/issues/1155
  - Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537
  - Fix Released in Ubuntu Devel release (bionic) via debdiff : 
lp1734983_bionic.debdiff

  [Other Info]

   * Sosreport upstream :
     https://github.com/sosreport/sos

   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2| oldstable  | source, amd64, 
arm64,

[Group.of.nepali.translators] [Bug 1741300] Re: mount-image-callback fails on qcow image on xenial

This bug was fixed in the package cloud-utils - 0.27-0ubuntu25

---
cloud-utils (0.27-0ubuntu25) xenial; urgency=medium

  * mount-image-callback: update partitions and settle on nbd mounts.
(LP: #1741300)

 -- Scott Moser   Fri, 26 Jan 2018 13:27:32 -0500

** Changed in: cloud-utils (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/1741300

Title:
  mount-image-callback fails on qcow image on xenial

Status in cloud-utils package in Ubuntu:
  Fix Released
Status in cloud-utils source package in Xenial:
  Fix Released
Status in cloud-utils source package in Artful:
  Fix Released
Status in cloud-utils source package in Bionic:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact] 
  mount-image-callback fails to mount images that are qcow2 formatted.

  This function in mount-image-callback works in other Ubuntu releases
  but not on xenial.  The function does succeed some times, but is
  brittle.

  The fix applied is also applied upstream, and consists mainly of
  adding

   blockdev --rereadpt /dev/nbdX
   udevadm settle

  where 'nbdX' is the device that mount-image-callback has set up to
  point to the file that is to be mounted.

  These above added function should not be harmful in any case.

  [Test Case]
  In a fresh install:

  $ sudo apt-get update -q && sudo apt-get install -qy cloud-image-utils

  $ 
url=http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
  $ wget "$url" -O xenial-server-cloudimg-amd64-disk1.img
  $ cp -a xenial-server-cloudimg-amd64-disk1.img disk.img

  $ sudo mount-image-callback -v disk.img true
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected disk.img (qcow2) to /dev/nbd0. waiting for device.

  [Regression Potential] 
  The regression potential stems from additional udev events
  caused by calling blockdev --rereadpt.

  udev events should not cause unwanted side effects, but could.

  [Other Info]

  === End SRU Template ===

  On xenial only:

  $ wget 
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
  $ cp -a xenial-server-cloudimg-amd64-disk1.img disk.img
  $ sudo mount-image-callback -v disk.img true
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected disk.img (qcow2) to /dev/nbd0. waiting for device.
  partitioned disk.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  gave up on waiting for /dev/nbd0p1
  $ echo $?
  1

  This fix seems to work and should be safe.
  === modified file 'bin/mount-image-callback'
  --- bin/mount-image-callback2018-01-03 15:44:47 +
  +++ bin/mount-image-callback2018-01-04 17:21:23 +
  @@ -316,6 +316,8 @@
  fi

  i=0
  +   [ -b "$mdev" ] || blockdev --rereadpt $nbd ||
  +   { error "blockdev --rereadpt $nbd failed"; return 1; }
  while :; do
  [ -b "$mdev" ] && break
  i=$(($i+1))

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cloud-image-utils 0.27-0ubuntu24
  ProcVersionSignature: User Name 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  Date: Thu Jan  4 17:23:15 2018
  Ec2AMI: ami-0388
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cloud-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1741300/+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 1746909] Re: linux-hwe: 4.13.0-33.36~16.04.1 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1746903
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Thursday, 08. February 2018 09:01 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1746903
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Thursday, 08. February 2018 09:01 UTC
+ phase: Uploaded

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

Title:
  linux-hwe: 4.13.0-33.36~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Xenial:
  Confirmed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1746909/+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 1734983] Re: Request to backport sosreport v3.5

This bug was fixed in the package sosreport - 3.5-1~ubuntu17.10.2

---
sosreport (3.5-1~ubuntu17.10.2) artful; urgency=medium

  * d/p/0003-fix-name-containers-is-not-defined.patch:
"containers" is an unknown variable, "insp" is the correct one.
(LP: #1734983)

sosreport (3.5-1~ubuntu17.10.1) artful; urgency=medium

  * New upstream release v3.5 (LP: #1734983)
New features include :
New plugins for :
* perl
* boom
* vdo
* os_net_config
* conntrackd
* ovirt_imageio
* nss
* sas3ircu
* openstack_aodh
* docker_distribution
* gluster_block
* snappy

  * Plugin API enhancements
* Plugin triggers by executable name
* Improved log size limit handling
* Better handling of compressed log files
* Per-plugin package verification lists

  * Updates to 227 plugins

  * Debian modifications:
- Addition of DEP8 tests
- Do not run Python2 only tests

  * d/p/0002-reset-to-expected-variable-order-for-packagemanager.patch:
Fixing severe regression where many "packages = " lines are no
longer working in Debian/Ubuntu. Preventing automatic package detection.

 -- Eric Desrochers   Thu, 25 Jan 2018
16:10:26 -0500

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

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

Title:
  Request to backport sosreport v3.5

Status in sosreport:
  New
Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  Fix Committed
Status in sosreport source package in Xenial:
  Fix Released
Status in sosreport source package in Zesty:
  Won't Fix
Status in sosreport source package in Artful:
  Fix Released
Status in sosreport source package in Bionic:
  Fix Released
Status in sosreport package in Debian:
  New

Bug description:
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new bugfixes,
  new features such as new plugins[1],  that can be interesting to
  have in a support context.

  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.

  [1] - New plugins for :
  * perl
  * boom
  * vdo
  * os_net_config
  * conntrackd
  * ovirt_imageio
  * nss
  * sas3ircu
  * openstack_aodh
  * docker_distribution
  * gluster_block
  * snappy

  Plugin API enhancements
  * Plugin triggers by executable name
  * Improved log size limit handling
  * Better handling of compressed log files
  * Per-plugin package verification lists

  Updates to 227 plugins

  This will also allow us to close some sosreport LP bugs:
  *Docker plugin uses the wrong command for Ubuntu (LP: #1693574)

  [Test Case]

   * Install sosreport
     $ apt-get install sosreport

   * Run sosreport
     $ sosreport -a
     $ sosreport -o 
     $ ...

   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport--.tar.xz"

   * Extract files from archive
     $ tar Jxvf /tmp/sosreport--.tar.xz

   * Look the content of sosreport, make sure the information is
  accurate and valid, 

   * Make sure all files that should to be collected by sosreport aren't 0 
size. (Files that should be collected may varies from one system to another, it 
depends on what packages are installed, ...)
     $ find /tmp/sosreport-- -size 0

  # Note :
  It is normal to see some 0 size files here and there, again it depend on how 
the plugin is run (package detection or not inside the plugins, ...) and if the 
package is installed or not on the system where you run sosreport. But in most 
cases, if the package is installed and if sosreport has a plugin for it then it 
should gather information, if not then it might be a problem with the plugins 
itself that need adjustments.

  [Regression Potential]

   * autopkgtest[2] didn't reveal any
  [2] - See Comment #1

   * We,STS, have intensively tested the package.

  During our testing, we found a severe regression that we already took
  action to fix it via :

  - Upstream issue - https://github.com/sosreport/sos/issues/1155
  - Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537
  - Fix Released in Ubuntu Devel release (bionic) via debdiff : 
lp1734983_bionic.debdiff

  [Other Info]

   * Sosreport upstream :
     https://github.com/sosreport/sos

   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2| oldstable  | source, amd64, 
arm64,

[Group.of.nepali.translators] [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex

This bug was fixed in the package preseed - 1.71ubuntu5.1

---
preseed (1.71ubuntu5.1) artful; urgency=medium

  * Fix for netcfg/hostname, if set, to take precedence. (LP: #1745531)
- Modify debian/network-preseed.postinst to make it more robust

 -- Zhang Hua   Fri, 26 Jan 2018 13:32:11
+0800

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

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

Title:
  [SRU] Reinforce hostname preseed regex

Status in debian-installer package in Ubuntu:
  In Progress
Status in preseed package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  In Progress
Status in preseed source package in Trusty:
  Fix Committed
Status in debian-installer source package in Xenial:
  In Progress
Status in preseed source package in Xenial:
  Fix Committed
Status in debian-installer source package in Artful:
  Fix Released
Status in preseed source package in Artful:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in preseed source package in Bionic:
  Fix Released

Bug description:
  [Special notes]

  Rebuilding debian-installer will be necessary in order to get a new
  mini.iso (Minimal ISO image of Ubuntu) containing this particular fix.

  Despite the fact that a full ISO are no longer built for some of the
  affected stable releases, one can use what is called a minimal ISO
  image (mini.iso) of Ubuntu. This mini.iso uses a text-based installer,
  resulting in a smaller image. The minimal ISO image will download
  packages from online archives at installation time instead of
  providing them on the install media itself.

  [Impact]

  This is the same issue reported in 
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202
  However that is marked as 'Fix Released' and the issue is still occurring so 
it seems best to just open a new bug according to Eric's comment.

  The present hostname preseed regex looks like:

  if ! echo "$RET" | grep -q 'ubuntu'; then
     ...
     /bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hosts
     ...
  fi

  There are still multiple problems with them according to Peter's
  comment
  (https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/comments/64)
  and Mathieu's comment
  (https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/comments/93).

  - The default hostname is 'ubuntu', and is the value you will get if
  nothing is preseeded -- we *do* need to skip it in this case, although
  the grep may need to be more precise. A name like 'ubuntuxenial'
  should match this grep.

  - The sed needs to be fixed to more appropriately catch for the exact
  string, rather than any substring -- ie. it should not match
  'ipv6-allnodes' if the name received from DHCP was 'node'. It should
  only match and replace for 'node'.

  So the fix will try to:

  1) Keep the if statement and add the -w option to grep to be more robust
  2) Modify the sed cmd with word boundaries (\b) to be more robust as well.

  [Test Case]

  Install Ubuntu using a preseed[1] file[2] and add the following line in the 
preseed recipe :
  d-i netcfg/hostname string 

  Change the HOSTNAME to see if the hostname in /etc/hosts can be
  updated correctly.

  [1] - url=http:///
  [2] - https://help.ubuntu.com/lts/installation-guide/example-preseed.txt

  [Regression Potential]

   * none expected, the actual changes are as follows:

  -if ! echo "$RET" | grep -q 'ubuntu'; then
  +if ! echo "$RET" | grep -qw 'ubuntu'; then
  ...
  - /bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hosts
  + /bin/sed -i "s/\b${CURRENT_HOSTNAME}\b/${NETCFG_HOSTNAME}/g" 
/etc/hosts

  In other words, we simply make it more robust to select only pattern
  containing matches that form whole word... catching 'ubuntu' hostname
  as-is but not catching pattern where ubuntu is part of the user chosen
  hostname as follow :

  "sometextubuntu"
  "sometextubuntusometext"
  "ubuntusometext"
  ...

  [Original Description]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1745531/+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 1745531] Re: [SRU] Reinforce hostname preseed regex

This bug was fixed in the package debian-installer - 20101020ubuntu523.2

---
debian-installer (20101020ubuntu523.2) artful; urgency=medium

  * No change rebuild to pick up the latest change in preseed (LP:
#1745531)

 -- Zhang Hua   Fri, 26 Jan 2018 13:53:02
+0800

** Changed in: debian-installer (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Reinforce hostname preseed regex

Status in debian-installer package in Ubuntu:
  In Progress
Status in preseed package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  In Progress
Status in preseed source package in Trusty:
  Fix Committed
Status in debian-installer source package in Xenial:
  In Progress
Status in preseed source package in Xenial:
  Fix Committed
Status in debian-installer source package in Artful:
  Fix Released
Status in preseed source package in Artful:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in preseed source package in Bionic:
  Fix Released

Bug description:
  [Special notes]

  Rebuilding debian-installer will be necessary in order to get a new
  mini.iso (Minimal ISO image of Ubuntu) containing this particular fix.

  Despite the fact that a full ISO are no longer built for some of the
  affected stable releases, one can use what is called a minimal ISO
  image (mini.iso) of Ubuntu. This mini.iso uses a text-based installer,
  resulting in a smaller image. The minimal ISO image will download
  packages from online archives at installation time instead of
  providing them on the install media itself.

  [Impact]

  This is the same issue reported in 
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202
  However that is marked as 'Fix Released' and the issue is still occurring so 
it seems best to just open a new bug according to Eric's comment.

  The present hostname preseed regex looks like:

  if ! echo "$RET" | grep -q 'ubuntu'; then
     ...
     /bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hosts
     ...
  fi

  There are still multiple problems with them according to Peter's
  comment
  (https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/comments/64)
  and Mathieu's comment
  (https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1452202/comments/93).

  - The default hostname is 'ubuntu', and is the value you will get if
  nothing is preseeded -- we *do* need to skip it in this case, although
  the grep may need to be more precise. A name like 'ubuntuxenial'
  should match this grep.

  - The sed needs to be fixed to more appropriately catch for the exact
  string, rather than any substring -- ie. it should not match
  'ipv6-allnodes' if the name received from DHCP was 'node'. It should
  only match and replace for 'node'.

  So the fix will try to:

  1) Keep the if statement and add the -w option to grep to be more robust
  2) Modify the sed cmd with word boundaries (\b) to be more robust as well.

  [Test Case]

  Install Ubuntu using a preseed[1] file[2] and add the following line in the 
preseed recipe :
  d-i netcfg/hostname string 

  Change the HOSTNAME to see if the hostname in /etc/hosts can be
  updated correctly.

  [1] - url=http:///
  [2] - https://help.ubuntu.com/lts/installation-guide/example-preseed.txt

  [Regression Potential]

   * none expected, the actual changes are as follows:

  -if ! echo "$RET" | grep -q 'ubuntu'; then
  +if ! echo "$RET" | grep -qw 'ubuntu'; then
  ...
  - /bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /etc/hosts
  + /bin/sed -i "s/\b${CURRENT_HOSTNAME}\b/${NETCFG_HOSTNAME}/g" 
/etc/hosts

  In other words, we simply make it more robust to select only pattern
  containing matches that form whole word... catching 'ubuntu' hostname
  as-is but not catching pattern where ubuntu is part of the user chosen
  hostname as follow :

  "sometextubuntu"
  "sometextubuntusometext"
  "ubuntusometext"
  ...

  [Original Description]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1745531/+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 1117944] Re: [SRU] intltool confused by separate build-dir

This bug was fixed in the package intltool - 0.51.0-4ubuntu1.17.04.1

---
intltool (0.51.0-4ubuntu1.17.04.1) artful; urgency=medium

* no-guess-builddir.patch: new patch by Aleksander Morgado.
Fixes build of various projects when builddir is not the same
as srcdir (e.g. when running make distcheck). (LP: #1117944)

-- Vlad Orlov Mon, 11 Sep 2017 17:56:28 +0300

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

Title:
[SRU] intltool confused by separate build-dir

Status in intltool:
Confirmed
Status in intltool package in Ubuntu:
Fix Released
Status in intltool source package in Xenial:
Fix Committed
Status in intltool source package in Artful:
Fix Released

Bug description:
[Impact]

An old bug in intltool breaks out-of-tree builds, including "make
distcheck", in a lot of intltool-using projects when automake version
is 1.15 or newer.

The fix for this issue (by Aleksander Morgado) is provided in the
debdiffs attached to the report.

[Test Case]

Try making release tarball for some upstream package. For example, it
can be mate-desktop, a base project for various MATE components.

This will build the project, make release tarball and check it by
unpacking it into a new directory and building (again) in it. The last
step will fail:

---

sub/mate-about/mate-about.desktop.in
sub/tools/mate-color-select.desktop.in

---

The out-of-tree build breaks here.

[Regression Potential]

None. This is a fix for a broken feature, it doesn't affects other ones.
Also the fix had been tested by MATE developers in various distros, including
Debian, Ubuntu and Fedora.

[Original Description]

To manage notifications about this bug go to:
https://bugs.launchpad.net/intltool/+bug/1117944/+subscriptions

[Group.of.nepali.translators] [Bug 1745081] Re: Add support for Realtek WiFi device [10ec:b822]

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

** No longer affects: linux (Ubuntu Xenial)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1745081/+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 1740231] Re: Add support for Realtek WiFi device [10ec:c821]

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

** No longer affects: linux (Ubuntu Xenial)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Jesse Sung (wenchien)

** Also affects: hwe-next/bb
   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/1740231

Title:
  Add support for Realtek WiFi device [10ec:c821]

Status in HWE Next:
  Fix Released
Status in HWE Next bionic series:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  PCI ID: 10ec:c821

  The off-tree driver is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740231/+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 1742613] Re: Add support for Realtek Bluetooth device [0bda:b00a]

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

** No longer affects: linux (Ubuntu Xenial)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Jesse Sung (wenchien)

** Also affects: hwe-next/bb
   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/1742613

Title:
  Add support for Realtek Bluetooth device [0bda:b00a]

Status in HWE Next:
  Fix Released
Status in HWE Next bionic series:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  These two devices are supported by the same rtk-btusb module, share
  the same firmware, while they have different config files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742613/+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 1742613] Re: Add support for Realtek Bluetooth device [0bda:b00a]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Add support for Realtek Bluetooth device [0bda:b00a]

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

Bug description:
  These two devices are supported by the same rtk-btusb module, share
  the same firmware, while they have different config files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742613/+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 1740231] Re: Add support for Realtek WiFi device [10ec:c821]