[Group.of.nepali.translators] [Bug 1781242] Re: as segfault with invalid -march= option

[Andrew Cloke]

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

Title:
  as segfault with invalid -march= option

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

Bug description:
  [Impact]

   * as segfaults, instead of exiting gracefully, when one specifies 
unsupported arch option (ie. one from future - cause xenial did not support z14)
   * this is bad, as detection fails around supported march options - as if 
binutils are completely broken, rather than just not supporting this or that 
CPU level of optimisations.

  [Test Case]

  Bad result:
   $ as -march=foo
  Segmentation fault

  Expected result:
  # as -march=foo
  Assembler messages:
  Error: invalid switch -march=foo
  Error: unrecognized option -march=foo

  [Regression Potential]

   * The result is still a failure condition, but with a proper exit
  code and standard error messages, rather than an unexplainable generic
  segfault.

  [Other Info]
   
   * Original bug report

  The GNU assembler segfaults with an invalid -march= option

  Contact Information = n/a

  ---uname output---
  n/a

  Machine Type = n/a

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   $ as -march=foo
  Segmentation fault

  Expected result:
  # as -march=foo
  Assembler messages:
  Error: invalid switch -march=foo
  Error: unrecognized option -march=foo

  Userspace tool common name: as

  The userspace tool has the following bit modes: 64

  Userspace rpm: binutils-2.26.1-1ubuntu1~16.04.6

  Userspace tool obtained from project website:  na

  *Additional Instructions for n/a:
  -Attach ltrace and strace of userspace application.

  The problem is not critical since usually 'as' is invoked through the
  gcc driver which itself errors out for wrong -march= options. It will
  only be a problem if somebody builds a more recent GCC from source and
  uses an -march= option for a machine not supported by the default
  binutils.

  Please consider integrating the attached patch into 16.04 binutils.

  The problem has been fixed in later binutils already. Ubuntu 18.04
  does not appear to be affected.

  --> Package has to set corectly by Canonical

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781242/+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 1793461] [NEW] Improvements to the kernel source package preparation

[Marcelo Cerri]

Public bug reported:

We need to improve the automation of the process that we use to prepare
kernel source packages. That requires changes in both the tooling and in
the kernels.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Precise)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Trusty)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Cosmic)
 Importance: Undecided
 Status: Incomplete

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

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

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

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

** Also affects: linux (Ubuntu Cosmic)
   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/1793461

Title:
  Improvements to the kernel source package preparation

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Precise:
  Incomplete
Status in linux source package in Trusty:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  We need to improve the automation of the process that we use to
  prepare kernel source packages. That requires changes in both the
  tooling and in the kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793461/+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 1778041] Re: browser-plugin-freshplayer-pepperflash broken

[Launchpad Bug Tracker]

This bug was fixed in the package freshplayerplugin -
0.3.9-0ubuntu0.16.04.1

---
freshplayerplugin (0.3.9-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream release (LP: #1778041)
  * debian/browser-plugin-freshplayer-libpdf.install:
  * debian/browser-plugin-freshplayer-nacl.install:
  * debian/browser-plugin-freshplayer-pepperflash.install:
  * debian/control:
  * debian/rules:
- libpdf and NaCl wrappers dropped upstream, so dropping the
  browser-plugin-freshplayer-libpdf and
  browser-plugin-freshplayer-nacl binaries.
- Avoid duplication of libfreshwrapper-flashplayer.so.
  * debian/control:
- Add libicu-dev to Build-Depends.
- Only build amd64 and i386.

 -- Gunnar Hjalmarsson   Mon, 16 Jul 2018 18:06:00
+0200

** Changed in: freshplayerplugin (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/1778041

Title:
  browser-plugin-freshplayer-pepperflash broken

Status in freshplayerplugin package in Ubuntu:
  Fix Released
Status in freshplayerplugin source package in Xenial:
  Fix Released
Status in freshplayerplugin source package in Bionic:
  Fix Released
Status in freshplayerplugin package in Debian:
  New

Bug description:
  [Impact]

  browser-plugin-freshplayer-pepperflash prevents sites which require
  Flash from working with the latest versions of Firefox. If you select
  "Ask to Activate" in FF, the contents requiring Flash is not shown. If
  you select "Always Activate", the tab with the page requiring Flash
  simply crashes.

  Issue identified via . A "no change
  rebuild" does not help.

  The proposed version in the PPA fixes the issue, so the wrapper works
  as intended also with the latest FF version.

  https://launchpad.net/~gunnarhj/+archive/ubuntu/freshplayerplugin

  This suggests an upgrade to a newer upstream version. This is the
  upstream changelog:

  2017-12-23  Rinat Ibragimov  

   * release v0.3.9
   * network: stop using files with NPN_PostURL

  2017-12-09  Rinat Ibragimov  

   * release: v0.3.8
   * misc: add NPN_PluginThreadAsyncCall emulation for Firefox 58

  2017-05-31  Rinat Ibragimov  

   * release: v0.3.7
   * graphics: add more fullscreen _NET_WM controls
   * misc: drop libpdf wrapper
   * misc: drop NaCl wrapper
   * misc: search for PepperFlash in Chrome component update
   directories

  2016-10-05  Rinat Ibragimov  

   * release: v0.3.6
   * graphics: fix off-by-one pixel issue in fullscreen scaling
   mode
   * graphics: try to flicker less
   * misc: use ICU for character set conversion, use WhatWG
   canonical encoding name conversion
   * misc: guess default character encoding from locale name
   * misc: guess GTK+ major version at run time

  Admittedly it includes a few minor improvements, but hopefully this
  can still pass as an SRUable microrelease (or something...).

  [Test Case]

  1. Install adobe-flashplugin and the {xenial,bionic}-release
     version of browser-plugin-freshplayer-pepperflash.

  2. (Re)start Firefox and visit
     .

  => Find that it doesn't confirm that Flash is installed.

  3. Install browser-plugin-freshplayer-pepperflash from
 {xenial,bionic}-proposed.

  4. Repeat 2.

  => Confirmation that the latest Flash version is installed.

  [Regression Potential]

  Considering that the {xenial,bionic}-release version of
  browser-plugin-freshplayer-pepperflash breaks Flash completely on
  Firefox, the risk that this upload makes the situation worse is
  non-existent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freshplayerplugin/+bug/1778041/+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 1791749] Re: linux-aws: 4.4.0-1068.78 -proposed tracker

[Po-Hsu Lin]

4.4.0-1068.78 - aws
Regression test CMPL, RTB.

Issue to note in x86_64 (aws):
  libhugetlbfs - 1 failed (brk_near_huge, bug 1653597), Killed by signal 1, bad 
config 3, only spotted on t2.small, passed on the rest
  ubuntu_kvm_unit_tests - test skipped due to no KVM support
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed (bug 1774387), inotify08 (bug 1775784) 
fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153) quotactl01 failed (bug 1790028) mlock203 failed (bug 1793451)

Skipped / blacklisted:
 * ubuntu_ltp
 * ubuntu_nbd_smoke_test
 * ubuntu_quota_smoke_test
 * ubuntu_seccomp
 * ubuntu_sysdig_smoke_test
 * ubuntu_zram_smoke_test

Note: ubuntu_ltp_syscalls test must be reviewed on the Jenkins server,
the hang issue (bug 179) will prevent it from copy the test report


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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux-aws: 4.4.0-1068.78 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  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:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
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: 1791745
  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/1791749/+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 1787245] Re: Auto-hosts do not include fqdn

[Launchpad Bug Tracker]

This bug was fixed in the package sshuttle - 0.76-1ubuntu1

---
sshuttle (0.76-1ubuntu1) xenial; urgency=medium

  * Make hostwatch find both fqdn and hostname (LP: #1787245)
- d/p/make-hostwatch-find-fqdn-and-hostname.patch: cherry-pick
  patch from upstream to add both the FQDN and the hostname
  so they are both resolvable.

 -- Billy Olsen   Wed, 29 Aug 2018 20:49:40
-0700

** Changed in: sshuttle (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/1787245

Title:
  Auto-hosts do not include fqdn

Status in sshuttle package in Ubuntu:
  Fix Released
Status in sshuttle source package in Xenial:
  Fix Released
Status in sshuttle source package in Bionic:
  Fix Released

Bug description:
  The --H, --auto-hosts option does not currently include fqdn and in
  fact removes the fqdn entries. This is blocking the use of sshuttle
  for things like accessing a Graylog server which links back to itself
  via fqdn.

  This has been fixed with pull request #173 [0] in Oct of 2017 adds
  this functionality and works for the Graylog forwarding which I've
  been trying to use it for.

  [0]: https://github.com/sshuttle/sshuttle/pull/173

  [Impact]

  Some services which may be remotely accessed over an sshuttle vpn
  tunnel may require full fqdn access to remote machines. Depending on
  the remote application, it may fail to function properly if the
  initiator system cannot resolve hosts by fqdn's. Graylog mentioned
  above, is one such example of this.

  This patch works by changing the host watch functionality to match
  more than just hostnames found at the remote site. If fqdns are also
  found, then this patch will ensure they get included in the initator's
  local /etc/host file.

  [Test Case]

  1. Initiate an sshuttle connection at a remote endpoint w/ the -H or
  --auto-hosts parameter.

  $ sshuttle 10.5.0.0/16 -r 10.230.65.47 --daemon -H

  2. Observe the initiator's /etc/hosts file
   - Without the patch, observe only hostnames are populated
   - With the patch, hostnames and fqdns are populated

  [Regression Potential]

  This area of code is limited to only affecting those users using the
  --auto-hosts parameter. That being said, the change is to expand the
  regular expressions which identify remote hostnames to include/allow
  fqdns. It may be possible that this introduces a naming collision with
  the initiator's DNS resolution where they relied on foo and
  foo.some.domain resolve to uniquely different hosts. This may be an
  unwanted side-effect, but upstream seems not to be concerned with
  this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1787245/+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 1781242] Re: as segfault with invalid -march= option

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.26.1-1ubuntu1~16.04.7

---
binutils (2.26.1-1ubuntu1~16.04.7) xenial; urgency=medium

  * binutils-march-fix.patch: Fix -march= option parsing bound check.
LP: #1781242

 -- Dimitri John Ledkov   Thu, 30 Aug 2018 14:39:04
+0100

** Changed in: binutils (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/1781242

Title:
  as segfault with invalid -march= option

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * as segfaults, instead of exiting gracefully, when one specifies 
unsupported arch option (ie. one from future - cause xenial did not support z14)
   * this is bad, as detection fails around supported march options - as if 
binutils are completely broken, rather than just not supporting this or that 
CPU level of optimisations.

  [Test Case]

  Bad result:
   $ as -march=foo
  Segmentation fault

  Expected result:
  # as -march=foo
  Assembler messages:
  Error: invalid switch -march=foo
  Error: unrecognized option -march=foo

  [Regression Potential]

   * The result is still a failure condition, but with a proper exit
  code and standard error messages, rather than an unexplainable generic
  segfault.

  [Other Info]
   
   * Original bug report

  The GNU assembler segfaults with an invalid -march= option

  Contact Information = n/a

  ---uname output---
  n/a

  Machine Type = n/a

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   $ as -march=foo
  Segmentation fault

  Expected result:
  # as -march=foo
  Assembler messages:
  Error: invalid switch -march=foo
  Error: unrecognized option -march=foo

  Userspace tool common name: as

  The userspace tool has the following bit modes: 64

  Userspace rpm: binutils-2.26.1-1ubuntu1~16.04.6

  Userspace tool obtained from project website:  na

  *Additional Instructions for n/a:
  -Attach ltrace and strace of userspace application.

  The problem is not critical since usually 'as' is invoked through the
  gcc driver which itself errors out for wrong -march= options. It will
  only be a problem if somebody builds a more recent GCC from source and
  uses an -march= option for a machine not supported by the default
  binutils.

  Please consider integrating the attached patch into 16.04 binutils.

  The problem has been fixed in later binutils already. Ubuntu 18.04
  does not appear to be affected.

  --> Package has to set corectly by Canonical

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781242/+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 1787245] Re: Auto-hosts do not include fqdn

[Launchpad Bug Tracker]

This bug was fixed in the package sshuttle - 0.78.3-1ubuntu1

---
sshuttle (0.78.3-1ubuntu1) bionic; urgency=medium

  * Make hostwatch find both fqdn and hostname (LP: #1787245)
- d/p/make-hostwatch-find-fqdn-and-hostname.patch: cherry-pick
  patch from upstream to add both the FQDN and the hostname
  so they are both resolvable.

 -- Billy Olsen   Wed, 29 Aug 2018 15:00:55
-0700

** Changed in: sshuttle (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/1787245

Title:
  Auto-hosts do not include fqdn

Status in sshuttle package in Ubuntu:
  Fix Released
Status in sshuttle source package in Xenial:
  Fix Committed
Status in sshuttle source package in Bionic:
  Fix Released

Bug description:
  The --H, --auto-hosts option does not currently include fqdn and in
  fact removes the fqdn entries. This is blocking the use of sshuttle
  for things like accessing a Graylog server which links back to itself
  via fqdn.

  This has been fixed with pull request #173 [0] in Oct of 2017 adds
  this functionality and works for the Graylog forwarding which I've
  been trying to use it for.

  [0]: https://github.com/sshuttle/sshuttle/pull/173

  [Impact]

  Some services which may be remotely accessed over an sshuttle vpn
  tunnel may require full fqdn access to remote machines. Depending on
  the remote application, it may fail to function properly if the
  initiator system cannot resolve hosts by fqdn's. Graylog mentioned
  above, is one such example of this.

  This patch works by changing the host watch functionality to match
  more than just hostnames found at the remote site. If fqdns are also
  found, then this patch will ensure they get included in the initator's
  local /etc/host file.

  [Test Case]

  1. Initiate an sshuttle connection at a remote endpoint w/ the -H or
  --auto-hosts parameter.

  $ sshuttle 10.5.0.0/16 -r 10.230.65.47 --daemon -H

  2. Observe the initiator's /etc/hosts file
   - Without the patch, observe only hostnames are populated
   - With the patch, hostnames and fqdns are populated

  [Regression Potential]

  This area of code is limited to only affecting those users using the
  --auto-hosts parameter. That being said, the change is to expand the
  regular expressions which identify remote hostnames to include/allow
  fqdns. It may be possible that this introduces a naming collision with
  the initiator's DNS resolution where they relied on foo and
  foo.some.domain resolve to uniquely different hosts. This may be an
  unwanted side-effect, but upstream seems not to be concerned with
  this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1787245/+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 1792905] Re: [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

[Francis Ginther]

Change not needed for xenial, livecd-rootfs is already creating
'/lib/modules' on the rootfs tarball.

** Changed in: livecd-rootfs (Ubuntu Xenial)
   Status: New => Invalid

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

Title:
  [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

Status in cloud-images:
  Triaged
Status in MAAS:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Xenial:
  Invalid
Status in open-iscsi source package in Xenial:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in open-iscsi source package in Bionic:
  New
Status in livecd-rootfs source package in Cosmic:
  New
Status in open-iscsi source package in Cosmic:
  Confirmed

Bug description:
  #! NB Foundations coding day task !#

  [Impact]

   * An explanation of the effects of the bug on users and

   * justification for backporting the fix to the stable release.

   * In addition, it is helpful, but not required, to include an
 explanation of how the upload fixes this bug.

  [Test Case]

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  [Regression Potential]

   * discussion of how regressions are most likely to manifest as a
  result of this change.

   * It is assumed that any SRU candidate patch is well-tested before
 upload and has a low overall risk of regression, but it's important
 to make the effort to think about what ''could'' happen in the
 event of a regression.

   * This both shows the SRU team that the risks have been considered,
 and provides guidance to testers in regression-testing the SRU.

  [Other Info]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

  ===

  Let me first start with saying MAAS is *not* using iSCSI anymore and
  is *NOT* in this case either.

  For some reason now using enlistment, commissioning, and deploying the
  ephemeral environment will block for 1 min 30 seconds waiting for the
  iSCSI daemon to succeed, which it never does.

  This increases the boot time drastically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1792905/+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 1662813] Re: Libjna-jni uses wrong path on package installation on s390x

[Tiago Stürmer Daitx]

** Changed in: libjna-java (Ubuntu Xenial)
   Status: New => Invalid

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

Title:
  Libjna-jni uses wrong path on package installation on s390x

Status in Ubuntu on IBM z Systems:
  Invalid
Status in libjna-java package in Ubuntu:
  Invalid
Status in libjna-java source package in Xenial:
  Invalid

Bug description:
  libjna-jni uses the wrong path for linking the library 
/usr/lib/s390x-linux-gnu/libjnidispatch.so
  on the z Systems s390x architecture, therefore applications relying on this 
library are unable to link to it, even if the package is installed.
  Creating the link manually fixes this problem.

  It should be linked from /usr/lib/s390x-linux-
  gnu/jni/libjnidispatch.system.so

  /sbin/ldconfig.real: Can't link /usr/lib/s390x-linux-gnu//build
  /libjna-java-D1S9TX/libjna-java-4.2.2/build/native-linux-
  s390x/libjnidispatch.system.so to libjnidispatch.so

  dpkg -S /usr/lib/s390x-linux-gnu/jni/libjnidispatch.system.so 
  libjna-jni: /usr/lib/s390x-linux-gnu/jni/libjnidispatch.system.so

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1662813/+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 1770271] Re: VegaM support

[Timo Aaltonen]

cosmic has 4.18 already

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

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

Title:
  VegaM support

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1770271/+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 1792905] Re: [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

[Robert C Jennings]

** Also affects: cloud-initramfs-tools (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/1792905

Title:
  [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

Status in cloud-images:
  Triaged
Status in MAAS:
  Triaged
Status in cloud-initramfs-tools package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  Confirmed
Status in cloud-initramfs-tools source package in Xenial:
  New
Status in livecd-rootfs source package in Xenial:
  Invalid
Status in open-iscsi source package in Xenial:
  Confirmed
Status in cloud-initramfs-tools source package in Bionic:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in open-iscsi source package in Bionic:
  Confirmed
Status in cloud-initramfs-tools source package in Cosmic:
  New
Status in livecd-rootfs source package in Cosmic:
  New
Status in open-iscsi source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

   * Affects environments where the base image is read-only but kernel
  modules are copied from the initramfs to the real root via cloud-
  initramfs-copymods package.

   * This affects users of our stable release images available from http
  ://cloud-images.ubuntu.com.

   * The attached fixes ensure /lib/modules always exists by creating it
  explicitly instead of relying on it to come from a package.

  [Test Case]

   * Download http://cloud-images.ubuntu.com/bionic/current/bionic-
  server-cloudimg-amd64.squashfs

   * Unpack it via `sudo unsquashfs bionic-server-cloudimg-
  amd64.squashfs`

   * Inspect the unpacked root filesystem and find that '/lib/modules'
  is missing.

   * Install local build scripts as described at
  https://github.com/chrisglass/ubuntu-old-fashioned (note: you will
  need ubuntu-old-fashioned master for cosmic)

  * Re-build the images using the updated livecd-rootfs package.

  * Unpack the resulting livecd.ubuntu-cpc.squashfs artifact using
  unsquashfs again.

  * Inspect the unpacked root filesystem and find that '/lib/modules'
  exists.

  * It is pure luck that package purges which are done analogously in
  Cosmic image builds do not remove '/lib/modules', hence this fix is
  introduced there, as well.

  * Xenial is not affected.

  * Test builds were carried out for Cosmic and Bionic with the expected
  results.

  [Regression Potential]

   * This is a fix to a regression. The existence of the directory had
  previously been ensured, but the mkdir call got lost in recent re-
  factoring. See also:

  https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/bionic-
  proposed/revision/1678

  https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-
  rootfs/trunk/revision/1681

   * Packaging tools should not take offense at the existence of a
  directory, even if it was not part of a package. So potential for
  unforseeable regressions is very low.

  ===ORIGINAL BUG DESCRIPTION===

  Let me first start with saying MAAS is *not* using iSCSI anymore and
  is *NOT* in this case either.

  For some reason now using enlistment, commissioning, and deploying the
  ephemeral environment will block for 1 min 30 seconds waiting for the
  iSCSI daemon to succeed, which it never does.

  This increases the boot time drastically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1792905/+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 1597908] Re: linux-kernel: Freeing IRQ from IRQ context

[Joseph Salisbury]

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

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

Title:
  linux-kernel: Freeing IRQ from IRQ context

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

Bug description:
  It looks like the Ubuntu 16.04 took the nvme driver from 4.5 kernel,
  but is missing some critical block updates that it was depending on.
  Specifically this one moving the timeout handler to a work queue
  instead of a irq context timer task:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=287922eb0b186e2a5bf54fdd04b734c25c90035c

  This mismatch causes lots of warnings and errors during recovery from
  failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908/+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 1754657] Re: [SRU] python-pylxd 2.0.7 (xenial), python-pylxd 2.2.6 (artful)

[Launchpad Bug Tracker]

This bug was fixed in the package python-pylxd - 2.0.7-0ubuntu1

---
python-pylxd (2.0.7-0ubuntu1) xenial; urgency=medium

  * New upstream point release (LP: #1754657).
  * d/control: Align (Build-)Depends with upstream.
  * d/p/cryptography-min-version.patch: Rebased.
  * d/p/ignore-unsupported-attributes.patch: Dropped. Included in
upstream release.

 -- Corey Bryant   Fri, 09 Mar 2018 08:33:06
-0500

** Changed in: python-pylxd (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/1754657

Title:
  [SRU] python-pylxd 2.0.7 (xenial), python-pylxd 2.2.6 (artful)

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive pike series:
  Fix Committed
Status in python-pylxd package in Ubuntu:
  Invalid
Status in python-pylxd source package in Xenial:
  Fix Released
Status in python-pylxd source package in Artful:
  Won't Fix

Bug description:
  [Impact]
  This SRU gets us to the latest pylxd point releases for xenial and artful.

  [Test Case]
  Upstream integration tests will be run against the python-pylxd installed 
from -proposed: https://github.com/lxc/pylxd/blob/master/run_integration_tests

  Instead of running 'tox -e integration' run 'nosetests integration'.

  [Regresion Potential]
  Regression potential is minimal. This is an upstream patch version update to 
the same major/minor 2.0.x version that is already in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1754657/+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 1792905] Re: [2.5] iSCSI systemd services fails and blocks for 1 min 30 seconds

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-initramfs-tools - 0.43ubuntu1

---
cloud-initramfs-tools (0.43ubuntu1) cosmic; urgency=medium

  [ Robert Jennings ]
  * copymods: Take ownership of lib/modules (LP: #1792905)
  * debian/control: Update Vcs-* to point to git.

 -- Scott Moser   Thu, 20 Sep 2018 08:43:53 -0400

** Changed in: cloud-initramfs-tools (Ubuntu Cosmic)
   Status: Confirmed => Fix Released

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

Title:
  [2.5] iSCSI systemd services fails and blocks for 1 min 30 seconds

Status in cloud-images:
  Triaged
Status in MAAS:
  Triaged
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Committed
Status in open-iscsi package in Ubuntu:
  Confirmed
Status in cloud-initramfs-tools source package in Xenial:
  Confirmed
Status in livecd-rootfs source package in Xenial:
  Invalid
Status in open-iscsi source package in Xenial:
  Confirmed
Status in cloud-initramfs-tools source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Bionic:
  Fix Committed
Status in open-iscsi source package in Bionic:
  Confirmed
Status in cloud-initramfs-tools source package in Cosmic:
  Fix Released
Status in livecd-rootfs source package in Cosmic:
  Fix Committed
Status in open-iscsi source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

   * Affects environments where the base image is read-only but kernel
  modules are copied from the initramfs to the real root via cloud-
  initramfs-copymods package.

   * This affects users of our stable release images available from http
  ://cloud-images.ubuntu.com.

   * The attached fixes ensure /lib/modules always exists by creating it
  explicitly instead of relying on it to come from a package.

  [Test Case]

   * Download http://cloud-images.ubuntu.com/bionic/current/bionic-
  server-cloudimg-amd64.squashfs

   * Unpack it via `sudo unsquashfs bionic-server-cloudimg-
  amd64.squashfs`

   * Inspect the unpacked root filesystem and find that '/lib/modules'
  is missing.

   * Install local build scripts as described at
  https://github.com/chrisglass/ubuntu-old-fashioned (note: you will
  need ubuntu-old-fashioned master for cosmic)

  * Re-build the images using the updated livecd-rootfs package.

  * Unpack the resulting livecd.ubuntu-cpc.squashfs artifact using
  unsquashfs again.

  * Inspect the unpacked root filesystem and find that '/lib/modules'
  exists.

  * It is pure luck that package purges which are done analogously in
  Cosmic image builds do not remove '/lib/modules', hence this fix is
  introduced there, as well.

  * Xenial is not affected.

  * Test builds were carried out for Cosmic and Bionic with the expected
  results.

  [Regression Potential]

   * This is a fix to a regression. The existence of the directory had
  previously been ensured, but the mkdir call got lost in recent re-
  factoring. See also:

  https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/bionic-
  proposed/revision/1678

  https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-
  rootfs/trunk/revision/1681

   * Packaging tools should not take offense at the existence of a
  directory, even if it was not part of a package. So potential for
  unforseeable regressions is very low.

  ===ORIGINAL BUG DESCRIPTION===

  Let me first start with saying MAAS is *not* using iSCSI anymore and
  is *NOT* in this case either.

  For some reason now using enlistment, commissioning, and deploying the
  ephemeral environment will block for 1 min 30 seconds waiting for the
  iSCSI daemon to succeed, which it never does.

  This increases the boot time drastically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1792905/+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 1791751] Re: linux-kvm: 4.4.0-1034.40 -proposed tracker

[Po-Hsu Lin]

4.4.0-1034.40 - kvm
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel (bug 
1763323)
  ubuntu_kvm_unit_tests - 18 failed on chico
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) mlock203 failed (bug 1793451) 
quotactl01 failed (bug 1790028)
  ubuntu_lxc - python3 API failed (bug 1764618)
  ubuntu_quota_smoke_test - failed with KVM kernel (bug 1784535)

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux-kvm: 4.4.0-1034.40 -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:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1791745
  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/1791751/+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 1792905] Re: [2.5] iSCSI systemd services fails and blocks for 1 min 30 seconds

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.540

---
livecd-rootfs (2.540) cosmic; urgency=medium

  * Ensure /lib/modules exists in root tarballs and sqashfs.
(LP: #1792905)

 -- Tobias Koch   Thu, 20 Sep 2018 09:38:34
+0200

** Changed in: livecd-rootfs (Ubuntu Cosmic)
   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/1792905

Title:
  [2.5] iSCSI systemd services fails and blocks for 1 min 30 seconds

Status in cloud-images:
  Triaged
Status in MAAS:
  Triaged
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in open-iscsi package in Ubuntu:
  Confirmed
Status in cloud-initramfs-tools source package in Xenial:
  In Progress
Status in livecd-rootfs source package in Xenial:
  Invalid
Status in open-iscsi source package in Xenial:
  Confirmed
Status in cloud-initramfs-tools source package in Bionic:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Fix Committed
Status in open-iscsi source package in Bionic:
  Confirmed
Status in cloud-initramfs-tools source package in Cosmic:
  Fix Released
Status in livecd-rootfs source package in Cosmic:
  Fix Released
Status in open-iscsi source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

   * Affects environments where the base image is read-only but kernel
  modules are copied from the initramfs to the real root via cloud-
  initramfs-copymods package.

   * This affects users of our stable release images available from http
  ://cloud-images.ubuntu.com.

   * The attached fixes ensure /lib/modules always exists by creating it
  explicitly instead of relying on it to come from a package.

  [Test Case]

   * Download http://cloud-images.ubuntu.com/bionic/current/bionic-
  server-cloudimg-amd64.squashfs

   * Unpack it via `sudo unsquashfs bionic-server-cloudimg-
  amd64.squashfs`

   * Inspect the unpacked root filesystem and find that '/lib/modules'
  is missing.

   * Install local build scripts as described at
  https://github.com/chrisglass/ubuntu-old-fashioned (note: you will
  need ubuntu-old-fashioned master for cosmic)

  * Re-build the images using the updated livecd-rootfs package.

  * Unpack the resulting livecd.ubuntu-cpc.squashfs artifact using
  unsquashfs again.

  * Inspect the unpacked root filesystem and find that '/lib/modules'
  exists.

  * It is pure luck that package purges which are done analogously in
  Cosmic image builds do not remove '/lib/modules', hence this fix is
  introduced there, as well.

  * Xenial is not affected.

  * Test builds were carried out for Cosmic and Bionic with the expected
  results.

  [Regression Potential]

   * This is a fix to a regression. The existence of the directory had
  previously been ensured, but the mkdir call got lost in recent re-
  factoring. See also:

  https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/bionic-
  proposed/revision/1678

  https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-
  rootfs/trunk/revision/1681

   * Packaging tools should not take offense at the existence of a
  directory, even if it was not part of a package. So potential for
  unforseeable regressions is very low.

  ===ORIGINAL BUG DESCRIPTION===

  Let me first start with saying MAAS is *not* using iSCSI anymore and
  is *NOT* in this case either.

  For some reason now using enlistment, commissioning, and deploying the
  ephemeral environment will block for 1 min 30 seconds waiting for the
  iSCSI daemon to succeed, which it never does.

  This increases the boot time drastically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1792905/+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