[Group.of.nepali.translators] [Bug 1726879] Re: Unescaped left brace in regex is deprecated

[ChristianEhrhardt]

This actually doesn't affect T/X as the pearl there is older and does not 
complain.
Thanks Ahasenack for spotting this before I started to build all the test ppa's!

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

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

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

Title:
  Unescaped left brace in regex is deprecated

Status in spamassassin package in Ubuntu:
  Fix Released
Status in spamassassin source package in Trusty:
  Invalid
Status in spamassassin source package in Xenial:
  Invalid
Status in spamassassin source package in Artful:
  Triaged
Status in spamassassin package in Debian:
  Fix Released

Bug description:
  When using sa-learn, you receive this notification:

  Unescaped left brace in regex is deprecated here (and will be fatal in
  Perl 5.30), passed through in regex; marked by <-- HERE in m/^(.{ <--
  HERE ,200}).*$/ at /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm
  line 923.


  Bug similar to: 
  https://bugs.archlinux.org/task/54378

  Upstream patch to fix the issue:
  
https://github.com/apache/spamassassin/commit/edb00a8d76a625bf03227ee2f6e915c9a0d90bad.patch

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: spamassassin 3.4.1-7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 24 16:03:14 2017
  InstallationDate: Installed on 2012-03-01 (2062 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  PackageArchitecture: all
  SourcePackage: spamassassin
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.spamassassin.init.pre: [modified]
  modified.conffile..etc.spamassassin.v310.pre: [modified]
  modified.conffile..etc.spamassassin.v312.pre: [modified]
  modified.conffile..etc.spamassassin.v330.pre: [modified]
  modified.conffile..etc.spamassassin.v340.pre: [modified]
  modified.conffile..etc.spamassassin.v341.pre: [modified]
  mtime.conffile..etc.default.spamassassin: 2017-08-07T14:05:53.351115
  mtime.conffile..etc.spamassassin.init.pre: 2012-03-03T17:13:34.827338
  mtime.conffile..etc.spamassassin.v310.pre: 2012-03-03T17:16:33.359340
  mtime.conffile..etc.spamassassin.v312.pre: 2012-03-03T17:17:26.667341
  mtime.conffile..etc.spamassassin.v330.pre: 2012-03-03T17:17:53.215342
  mtime.conffile..etc.spamassassin.v340.pre: 2014-07-10T16:07:25.307684
  mtime.conffile..etc.spamassassin.v341.pre: 2016-11-12T12:43:21.082704

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1726879/+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 1452202] Re: ubuntu preseed install fails to set a hostname

[Eric Desrochers]

** Also affects: debian-installer (Ubuntu Bionic)
   Importance: Medium
 Assignee: Eric Desrochers (slashd)
   Status: Fix Released

** Also affects: preseed (Ubuntu Bionic)
   Importance: Medium
 Assignee: Eric Desrochers (slashd)
   Status: 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/1452202

Title:
  ubuntu preseed install fails to set a hostname

Status in debian-installer package in Ubuntu:
  Fix Released
Status in preseed package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  Fix Released
Status in preseed source package in Trusty:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Released
Status in preseed source package in Xenial:
  Fix Released
Status in debian-installer source package in Bionic:
  Fix Released
Status in preseed source package in Bionic:
  Fix Released
Status in netcfg package in Debian:
  New

Bug description:
  [Impact]

   * DHCP hostname take precedence over netcfg/hostname, if set.

  The problem is that the system read the preseed file after having run
  netcfg, thus the preseed parameter cannot be loaded straight from the
  start.

  [Test Case]

   * HOWTO reproduce :

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

  If the machine get a HOSTNAME from DHCP server or from a reverse
  lookup, netcfg/hostname doesn't take precedence.

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

  [Regression Potential]

   * none expected, the change is trivial and has been intensively
  jointly tested by myself and cyphermox.

  [Other Info]

   * Debian bug : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755848
     Patch has been submitted to Debian
   * There is an old patch introduced in 2012 [Use netcfg/hostname for the 
hostname if found. (Closes: #606636)] but that doesn't work as expected.

  [Original Description]

  == Comment: #0 - Edward R. Cheslek  - 2015-04-28 
18:04:01 ==
  ---Problem Description---
  An install using a preseed file fails to configure the hostname of the system 
being installed.

  Contact Information = eches...@us.ibm.com

  ---uname output---
  Ubuntu 15.04 ppc64le

  Machine Type = Tuleta pKVM guest

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

  ---Steps to Reproduce---
   set up an automated install using a preseed file.  Grub menu entry:

  menuentry "Test" {
  linux   ubuntu-installer/ppc64el/vmlinux tasks=standard 
pkgsel/language-pack-patterns= pkgsel/install-language-support=false auto=true 
preseed/url=http://10.33.11.31/data/autoinst/ted.preseed
  initrd  ubuntu-installer/ppc64el/initrd.gz
  }

  The install will begin, and reach the hostname configuration screen,
  then stop, waiting for input.  The hostname is set in the preseed
  file, which is attached.

  Install method: http from ports.ubuntu.com

  Install disk info: n/a

  Install ISO Information: n/a

  *Additional Instructions for eches...@us.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #1 - SANDHYA VENUGOPALA  - 2015-04-29 
06:08:18 ==
  Some literature that is floating around -

  when booting from an installation CD and using a preseed file on a
  network, the installer will need answers to some questions (hostname,
  network configuration, ...) before it can load the preseed file. On
  the other hand, including a customized preseed file in a setup CD will
  allow for more automation, but requires re-mastering of the CD.

  The configuration of domain and host name, and keymap are still being
  asked, even if you have them in your preseed file as shown above. So
  if you want to kickstart the preseeded installation without a single
  questions asked, append the following more options to kernel boot
  prompt:

  console-keymaps-at/keymap=us hostname=myhost domain=example.com
  locale=en_US

  Perhaps David Heller can throw some light on this and let us know if
  its bug.

  == Comment: #2 - Edward R. Cheslek  - 2015-04-29 
07:57:29 ==
  I'm booting and installing from the network.  Even if I leave the hostname 
related options out of my preseed, it still picks up and displays the correct 
hostname from dhcp.

  == Comment: #3 - David Heller  - 2015-05-05 14:12:52 ==
  I'm not very familiar with this particular preseed option so I'm not sure how 
it's supposed to behave.  However, in a quick test on Ubuntu 15.04, adding 
"netcfg/hostname=blah" to the kernel cmdline worked: it successfully overrode 
the hostname from DHCP (the way it is usually set in my environment) with no 
other changes required.

  In the preseed however, I could not 

[Group.of.nepali.translators] [Bug 1742933] Re: Regression in 2018-01-08 updates

[Bug Watch Updater]

** Changed in: intel-microcode (Debian)
   Status: New => Fix Released

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

Title:
  Regression in 2018-01-08 updates

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in intel-microcode source package in Trusty:
  Fix Released
Status in intel-microcode source package in Xenial:
  Fix Released
Status in intel-microcode source package in Zesty:
  Won't Fix
Status in intel-microcode source package in Artful:
  Fix Released
Status in intel-microcode source package in Bionic:
  Confirmed
Status in intel-microcode package in Debian:
  Fix Released

Bug description:
  There is a regression in the Intel 20180108 microcode updates that is
  causing issues for some devices:

  https://newsroom.intel.com/news/intel-security-issue-update-
  addressing-reboot-issues/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1742933/+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 1706247] Re: Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

[Joseph Salisbury]

** No longer affects: linux (Ubuntu Xenial)

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

Title:
  Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress

Bug description:
  16G Huge Pages are not supported on PowerNV (bare metal) installations. 
Ubuntu 16.04.2 still allows 16G huge pages to be turned on.
   
  Contact Information = Mike Hollinger (mchol...@us.ibm.com) 
   
  ---uname output---
  Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTB 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Add the following to the kernel boot args (either via editing the 
petitboot boot option manually, or updating /boot/grub/grub.cfg:

  default_hugepagesz=16G hugepagesz=16G hugepages=4

  2. Boot Linux
  3. Observe that the kernel believes 16G huge pages are available:
  ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge
  AnonHugePages:475136 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB
  ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages
  hugepages-1024kB  hugepages-16384kB  hugepages-16777216kB

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  
  This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I 
haven't checked other versions of Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706247/+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 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Launchpad Bug Tracker]

This bug was fixed in the package libjogl2-java - 2.3.2+dfsg-7

---
libjogl2-java (2.3.2+dfsg-7) unstable; urgency=medium

  * Reupload using correct .changes.

 -- Timo Aaltonen   Sat, 13 Jan 2018 09:17:50 +0200

** Changed in: libjogl2-java (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/1742894

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Invalid
Status in libjogl2-java source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Invalid
Status in scilab source package in Xenial:
  Invalid
Status in libjogl2-java source package in Artful:
  Fix Committed
Status in mesa source package in Artful:
  Invalid
Status in scilab source package in Artful:
  Invalid
Status in scilab package in Debian:
  Fix Released

Bug description:
  [Impact]

  Software that use libjogl2-java (Scilab, Matlab,...) fail to run,
  because Mesa dropped 'Gallium' from the renderer string.

  [Test case]
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped
   at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
   at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
   at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
   at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
   at java.security.AccessController.doPrivileged(Native Method)
   at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
   at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
   at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
   at org.scilab.modules.gui.SwingView.(Unknown Source)
   at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
   at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  [Regression potential]
  The fix is a simple oneliner that allows libjogl2-java to detect Mesa with 
both new and original version of Mesa.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1742894/+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 1744968] Re: [SRU] Juju 2.3.2

[Mathieu Trudel-Lapierre]

This affects netplan too in xenial (and by the same token, I'll land
this SRU fix to artful as well).

Code is ready in git, just needs a proper "backport" of netplan to the
affected releases.

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

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

** Also affects: juju-core (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: juju-core (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** Changed in: nplan (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: nplan (Ubuntu Artful)
   Status: New => In Progress

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

** Changed in: nplan (Ubuntu Artful)
   Importance: Undecided => High

** Changed in: nplan (Ubuntu Artful)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

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

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

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

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

Title:
  [SRU] Juju 2.3.2

Status in juju-core package in Ubuntu:
  In Progress
Status in nplan package in Ubuntu:
  In Progress
Status in juju-core source package in Xenial:
  New
Status in nplan source package in Xenial:
  In Progress
Status in juju-core source package in Artful:
  New
Status in nplan source package in Artful:
  In Progress

Bug description:
  This syncs juju with the upstream release bringing the latest bugfixes
  and enhancements.

  [SRU Information]
  juju-core has a stable release exception, including for major version 
updates, https://wiki.ubuntu.com/JujuUpdates.

  [Impact]
  A full list of targeted bugs can be seen against the milestone, and the 
intervening milestones:

  https://launchpad.net/juju/+milestone/2.3.2

  [QA/Testing]
  Juju practices continuous integration and testing of the juju source tree. 
The results for this release can be seen here:

  http://qa.jujucharms.com/releases/6159

  In addition, juju has adt test coverage for all supported archs,
  http://autopkgtest.ubuntu.com/packages/j/juju-core/.

  Finally, manual verification and testing of the package has been done
  per https://wiki.ubuntu.com/JujuUpdates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1744968/+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 1726879] Re: Unescaped left brace in regex is deprecated

[ChristianEhrhardt]

** Changed in: spamassassin (Ubuntu Trusty)
   Status: Confirmed => Triaged

** Changed in: spamassassin (Ubuntu Xenial)
   Status: Confirmed => Triaged

** Changed in: spamassassin (Ubuntu Zesty)
   Status: Confirmed => Triaged

** Changed in: spamassassin (Ubuntu Artful)
   Status: Confirmed => Triaged

** No longer affects: spamassassin (Ubuntu Zesty)

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

Title:
  Unescaped left brace in regex is deprecated

Status in spamassassin package in Ubuntu:
  Fix Released
Status in spamassassin source package in Trusty:
  Triaged
Status in spamassassin source package in Xenial:
  Triaged
Status in spamassassin source package in Artful:
  Triaged
Status in spamassassin package in Debian:
  Fix Released

Bug description:
  When using sa-learn, you receive this notification:

  Unescaped left brace in regex is deprecated here (and will be fatal in
  Perl 5.30), passed through in regex; marked by <-- HERE in m/^(.{ <--
  HERE ,200}).*$/ at /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm
  line 923.


  Bug similar to: 
  https://bugs.archlinux.org/task/54378

  Upstream patch to fix the issue:
  
https://github.com/apache/spamassassin/commit/edb00a8d76a625bf03227ee2f6e915c9a0d90bad.patch

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: spamassassin 3.4.1-7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 24 16:03:14 2017
  InstallationDate: Installed on 2012-03-01 (2062 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  PackageArchitecture: all
  SourcePackage: spamassassin
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.spamassassin.init.pre: [modified]
  modified.conffile..etc.spamassassin.v310.pre: [modified]
  modified.conffile..etc.spamassassin.v312.pre: [modified]
  modified.conffile..etc.spamassassin.v330.pre: [modified]
  modified.conffile..etc.spamassassin.v340.pre: [modified]
  modified.conffile..etc.spamassassin.v341.pre: [modified]
  mtime.conffile..etc.default.spamassassin: 2017-08-07T14:05:53.351115
  mtime.conffile..etc.spamassassin.init.pre: 2012-03-03T17:13:34.827338
  mtime.conffile..etc.spamassassin.v310.pre: 2012-03-03T17:16:33.359340
  mtime.conffile..etc.spamassassin.v312.pre: 2012-03-03T17:17:26.667341
  mtime.conffile..etc.spamassassin.v330.pre: 2012-03-03T17:17:53.215342
  mtime.conffile..etc.spamassassin.v340.pre: 2014-07-10T16:07:25.307684
  mtime.conffile..etc.spamassassin.v341.pre: 2016-11-12T12:43:21.082704

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1726879/+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 1743232] Re: set vm_info to kvm for digitalocean instances

[Launchpad Bug Tracker]

This bug was fixed in the package landscape-client - 16.03-0ubuntu5

---
landscape-client (16.03-0ubuntu5) bionic; urgency=medium

  * d/p/set-vm-info-to-kvm-for-aws-C5-instances.patch:
Sets vm_info to kvm for new AWS EC2 C5 instances. (LP: #1742531)

  * d/p/set-vm-info-to-kvm-for-digitalocean-instances.patch:
Sets vm_info to kvm for digitalocean instances. (LP: #1743232)

 -- Eric Desrochers   Sun, 14 Jan 2018
11:05:38 -0500

** Changed in: landscape-client (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/1743232

Title:
  set vm_info to kvm for digitalocean instances

Status in Landscape Client:
  Fix Committed
Status in landscape-client package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  In Progress
Status in landscape-client source package in Xenial:
  In Progress
Status in landscape-client source package in Artful:
  In Progress
Status in landscape-client source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  digitalocean instance type is not a recognised VM type in Landscape
  and thus won't allow use of a Virtual Guest asset to register with.

  The digitalocean type uses a KVM-family hypervisor (displaying
  "digitalocean" in sys_vendor which landscape-client doesn't recognise,
  thus cannot associate/map to kvm)

  [Test Case]

   * Deploy a digitalocean instance
   * Look sys_vendor
     $ cat /sys/class/dmi/id/sys_vendor
     digitalocean

   * Install landscape-client
   * Register the client to the desired landscape-server
   * Verify "VM Type" to be "kvm" under the computer info (in landscape-server)

  [Regression Potential]

   * No regression anticipated, the fix is only adding a new entry
  mapping to recognize digitalocean instances.

  [Other Info]

   * Upstream commit:
     https://github.com/CanonicalLtd/landscape-client/pull/24/files

To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1743232/+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 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM

[Launchpad Bug Tracker]

This bug was fixed in the package landscape-client - 16.03-0ubuntu5

---
landscape-client (16.03-0ubuntu5) bionic; urgency=medium

  * d/p/set-vm-info-to-kvm-for-aws-C5-instances.patch:
Sets vm_info to kvm for new AWS EC2 C5 instances. (LP: #1742531)

  * d/p/set-vm-info-to-kvm-for-digitalocean-instances.patch:
Sets vm_info to kvm for digitalocean instances. (LP: #1743232)

 -- Eric Desrochers   Sun, 14 Jan 2018
11:05:38 -0500

** Changed in: landscape-client (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/1742531

Title:
  New Amazon AWS C5 instances are not recognised as a VM

Status in Landscape Client:
  Fix Committed
Status in landscape-client package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  In Progress
Status in landscape-client source package in Xenial:
  In Progress
Status in landscape-client source package in Artful:
  In Progress
Status in landscape-client source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  The new Amazon AWS C5 instance type is not a recognised VM type in
  Landscape and thus won't allow use of a Virtual Guest asset to
  register with.

  The C5 instance type is a new type that uses a KVM-family hypervisor
  instead of Xen (displaying "Amazon EC2" in sys_vendor which landscape-
  client doesn't recognise, thus cannot associate/map to kvm)

  "AWS has revealed it has created a new hypervisor based on KVM, not
  the Xen hypervisor on which it has relied for years."

  From
  
https://www.theregister.co.uk/2017/11/07/aws_writes_new_kvm_based_hypervisor_to_make_its_cloud_go_faster

  [Test Case]

   * Deploy an AWS C5 instance
   * Look sys_vendor
     $ cat /sys/class/dmi/id/sys_vendor
     Amazon EC2

   * Install landscape-client
   * Register the client to the desired landscape-server
   * Verify "VM Type" to be "kvm" under the computer info (in landscape-server)

  [Regression Potential]

   * No regression anticipated, the fix is only adding a new entry
  mapping to recognize C5 instance (Amazon EC2)

  [Other Info]

   * Upstream commit:
     https://github.com/CanonicalLtd/landscape-client/pull/22/files

  [Original Description]
  The new Amazon AWS C5 instance type is not a recognised VM type in Landscape 
and thus won't allow use of a Virtual Guest asset to register with.

  The C5 instance type is a new type that uses a KVM-family hypervisor
  instead of Xen:

  "AWS has revealed it has created a new hypervisor based on KVM, not
  the Xen hypervisor on which it has relied for years."

  From
  
https://www.theregister.co.uk/2017/11/07/aws_writes_new_kvm_based_hypervisor_to_make_its_cloud_go_faster

  

  ubuntu@ip-172-31-54-123:~$ cat /sys/class/dmi/id/sys_vendor
  Amazon EC2

  

  dmidecode output:

  # dmidecode 3.0
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.
  5 structures occupying 233 bytes.
  Table at 0x000F9010.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: Amazon EC2
   Version: 1.0
   Release Date: 10/16/2017
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 64 kB
   Characteristics:
    PCI is supported
    EDD is supported
    ACPI is supported
    System is a virtual machine
   BIOS Revision: 1.0

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: Amazon EC2
   Product Name: c5.large
   Version: Not Specified
   Serial Number: ec23cdb5-a248-6935-b9f6-de3a34334018
   UUID: EC23CDB5-A248-6935-B9F6-DE3A34334018
   Wake-up Type: Power Switch
   SKU Number: Not Specified
   Family: Not Specified

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: Amazon EC2
   Product Name: Not Specified
   Version: Not Specified
   Serial Number: Not Specified
   Asset Tag: i-09898bff0b7b55c35
   Features: None
   Location In Chassis: Not Specified
   Chassis Handle: 0x0003
   Type: Other
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 21 bytes
  Chassis Information
   Manufacturer: Amazon EC2
   Type: Other
   Lock: Not Present
   Version: Not Specified
   Serial Number: Not Specified
   Asset Tag: Amazon EC2
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 0

  Handle 0x0004, DMI type 127, 4 bytes
  End Of Table

  

  contents of /proc/cpuinfo :

  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 85
  model name: Intel(R) Xeon(R) Platinum 8124M CPU @ 3.00GHz
  stepping  : 3
  microcode : 0x100013e
  cpu MHz   : 3000.000
  cache size: 25344 KB
  physical id   : 0
  siblings  : 2
  core id 

[Group.of.nepali.translators] [Bug 1437024] Re: Failure to PXE-boot from secondary NIC

[Mathieu Trudel-Lapierre]

This is already fixed in bionic / artful (given that it's landed there
as of grub2 2.02~beta3-4ubuntu6).

What is missing is landing the fixes for Xenial and possibly Trusty?

I can prepare the SRU for Trusty right now, but the one for Xenial will
be temporarily blocked by a shim update which just made it to -proposed.

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

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

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

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

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

** Changed in: grub2 (Ubuntu Trusty)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

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

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

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

Title:
  Failure to PXE-boot from secondary NIC

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

Bug description:
  On a Lenovo x3550 M5 with the standard 4-port 1Gbps NICs and a
  secondary (plug-in) 2-port 10Gbps NIC, an attempt to PXE-boot from the
  secondary NIC in UEFI mode causes a boot failure with a "grub>" prompt
  on the display.

  This server arrived for certification with both NICs enabled. I
  suspect, but am not positive, that which NIC is chosen for booting is
  semi-random, although it favors the secondary NIC. The system PXE-
  boots fine from the built-in ports (generally the first one, eth0),
  and when booting from eth0 is forced via the UEFI boot menu,
  enlistment, commissioning, deployment, and post-deployment booting all
  work fine.

  When the system PXE-boots from the secondary NIC, though, the normal
  UEFI PXE-boot messages appear on the screen, followed by the
  aforementioned "grub>" prompt. This obviously prevents normal
  operation of the server with MAAS. It appears from the logs (attached)
  that when using the failed NIC, the MAAS server doesn't receive
  follow-on requests from GRUB.

  As a workaround, the secondary NICs can be configured to not support
  PXE-booting in the firmware setup utility; this enables normal
  deployment via MAAS.

  MAAS version information:

  $ dpkg -l '*maas*'|cat
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  Version 
Architecture Description
  
+++-=-===--===
  ii  maas  
1.7.2+bzr3355-0ubuntu1~trusty1  all  MAAS server 
all-in-one metapackage
  ii  maas-cli  
1.7.2+bzr3355-0ubuntu1~trusty1  all  MAAS command 
line API tool
  ii  maas-cluster-controller   
1.7.2+bzr3355-0ubuntu1~trusty1  all  MAAS server 
cluster controller
  ii  maas-common   
1.7.2+bzr3355-0ubuntu1~trusty1  all  MAAS server 
common files
  ii  maas-dhcp 
1.7.2+bzr3355-0ubuntu1~trusty1  all  MAAS DHCP 
server
  ii  maas-dns  
1.7.2+bzr3355-0ubuntu1~trusty1  all  MAAS DNS server
  ii  maas-proxy
1.7.2+bzr3355-0ubuntu1~trusty1  all  MAAS Caching 
Proxy
  ii  maas-region-controller
1.7.2+bzr3355-0ubuntu1~trusty1  all  MAAS server 
complete region controller
  ii  maas-region-controller-min
1.7.2+bzr3355-0ubuntu1~trusty1  all  MAAS Server 
minimum region controller
  ii  python-django-maas
1.7.2+bzr3355-0ubuntu1~trusty1  all  MAAS server 
Django web framework
  ii  python-maas-client
1.7.2+bzr3355-0ubuntu1~trusty1  all  MAAS python 
API client
  ii  

[Group.of.nepali.translators] [Bug 1744949] Re: linux-oem: 4.13.0-1018.19 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

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

Title:
  linux-oem: 4.13.0-1018.19 -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:
  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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-1018.19 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: 1743412
  phase: Uploaded

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

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

** Description changed:

  This bug is for tracking the 4.13.0-1018.19 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: 1743412
+ kernel-stable-phase-changed:Tuesday, 23. January 2018 14:30 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.13.0-1018.19 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: 1743412
- kernel-stable-phase-changed:Tuesday, 23. January 2018 14:30 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/1744949

Title:
  linux-oem: 4.13.0-1018.19 -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:
  Confirmed
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-1018.19 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: 1743412
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1744949/+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 1744949] [NEW] linux-oem: 4.13.0-1018.19 -proposed tracker

[Timo Aaltonen]

Public bug reported:

This bug is for tracking the 4.13.0-1018.19 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: 1743412
phase: Uploaded

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: Fix Released

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: Fix Released

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-kernel-sru-cycle-2017.11.20-8 xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: xenial

** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Confirmed

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   

[Group.of.nepali.translators] [Bug 1737640] Re: [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-fan - 0.12.9

---
ubuntu-fan (0.12.9) bionic; urgency=medium

  [ Andy Whitcroft ]
  * fanctl: fix config_filename when the interface does not have a width
(LP: #1737640)

 -- Andreas Hasenack   Thu, 04 Jan 2018 15:41:32
-0200

** Changed in: ubuntu-fan (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Won't Fix
Status in ubuntu-fan source package in Artful:
  In Progress
Status in ubuntu-fan source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * This bug effects anyone deploying LXD with juju on a machine with
  interfaces configured as IP/mask. Since this is a very common use
  case, SRU is needed.

  [Test Case]

   * Detailed process can be seen at https://paste.ubuntu.com/26169937/

  [Regression Potential]

   * Potential for regression is low because of the nature of the error.
  It's just missing a case stanza for interfaces that are defined with
  IP/mask

  [Other Info]

   * Original report:

  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1737640/+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 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops

[Stefan Bader]

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

Title:
  the kernel is blackholing IPv6 packets to linkdown nexthops

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

Bug description:
  == SRU Justification ==
  When the 'ignore_routes_with_linkdown' sysctl is set, we should not
  consider linkdown nexthops during route lookup.

  While the code correctly verifies that the initially selected route
  ('match') has a carrier, it does not perform the same check in the
  subsequent multipath selection, resulting in a potential packet loss.

  In case the chosen route does not have a carrier and the sysctl is set,
  choose the initially selected route.

  This is a regression introduced by commit 35103d11173b in 4.3-rc1.  Commit
  bbfcd7763 resolves this regression and is mainline as of 4.15-rc1.

  == Fix ==
  commit bbfcd77631573ac4a9f57eb6169e04256a111bc1
  Author: Ido Schimmel 
  Date:   Tue Nov 21 09:50:12 2017 +0200

  ipv6: Do not consider linkdown nexthops during multipath

  == Regression Potential ==
  This fix is specific to ipv6 and fixes a current regression.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+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 1733281] Re: ubuntu/xr-usb-serial didn't get built in zesty and artful

[Stefan Bader]

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

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

** Changed in: linux-azure-edge (Ubuntu Artful)
   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/1733281

Title:
  ubuntu/xr-usb-serial didn't get built in zesty and artful

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Committed
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  New
Status in linux-azure-edge source package in Artful:
  Invalid

Bug description:
  The ubuntu/xr-usb-serial is expected to be built for i386 and x86_64,
  and in ubuntu/Makefile it says:

  ifneq ($(filter $(ARCH), i386 x86_64),)
  obj-y += xr-usb-serial/
  endif

  Since ARCH is x86 for both i386 and x86_64, this condition will never
  be true thus the module will never get a chance to be built.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733281/+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 1730550] Re: e1000e in 4.4.0-97-generic breaks 82574L under heavy load.

[Stefan Bader]

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

Title:
  e1000e in 4.4.0-97-generic breaks 82574L under heavy load.

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress

Bug description:
  
  == SRU Justification ==
  This issue was first reported on the netdev email list by Lennart Sorensen:
  https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html

  Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on
  the 82574L under heavy load.

  "Unfortunately this commit changed the driver to assume
  that the Other Causes interrupt can only mean link state change and
  hence sets the flag that (unfortunately) means both link is down and link
  state should be checked. Since this now happens 3000 times per second,
  the chances of it happening while the watchdog_task is checking the link
  state becomes pretty high, and it if does happen to coincice, then the
  watchdog_task will reset the adapter, which causes a real loss of link."

  The original reported experienced this issue on a Supermicro X7SPA-HF-D525 
server board. 
  However, the bug is now seen on many servers running X9DBL-1F server boards. 

  This bug is fixed by commits 19110cfbb34 and 4aea7a5c5e9, which were both 
added
  to mainline in v4.15-rc1.

  The commit that introduced this bug,16ecba5, was added to mainlien in 
v4.5-rc1.  However,
  Xenial recived this commit as well as commit 531ff577a.  Bionic master-next 
does not need
  these commits, since it got them via bug 1735843 and the 4.14.3 updates.

  == Fixes ==
  19110cfbb34 ("e1000e: Separate signaling for link check/link up")
  4aea7a5c5e9 ("e1000e: Avoid receiver overrun interrupt bursts")

  == Regression Potential ==
  These commits are specific to e1000.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  == Original Bug Descriptio ==
  This issue was first reported on the netdev email list by Lennart Sorensen:
  https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html

  Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on
  the 82574L under heavy load.

  "Unfortunately this commit changed the driver to assume
  that the Other Causes interrupt can only mean link state change and
  hence sets the flag that (unfortunately) means both link is down and link
  state should be checked.  Since this now happens 3000 times per second,
  the chances of it happening while the watchdog_task is checking the link
  state becomes pretty high, and it if does happen to coincice, then the
  watchdog_task will reset the adapter, which causes a real loss of link."

  A fix for this issue was accepted into the net-next branch, along with
  other e1000e/igb patches:
  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=f44dea3421b47d355a835e9cfcc59ca7318575a9

  The original reported experienced this issue on a Supermicro X7SPA-
  HF-D525 server board. We see this issue on many servers running X9DBL-
  1F server boards. Both boards use the Intel 82574L for the network
  interfaces.  We see messages like this under heavy load:

  [Nov 6 15:42] e1000e: eth0 NIC Link is Down
  [  +0.001670] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [Nov 6 16:10] e1000e: eth0 NIC Link is Down
  [  +0.008505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [Nov 7 00:49] e1000e: eth0 NIC Link is Down
  [  +2.235111] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx

  We have confirmed that the connected switch sees the link drops also,
  to these are not false alarms from the e1000e driver.

  # lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  I could not cleanly apply the net-next patch to 4.4.0 so I tested with just 
the following cherry picked changes on the latest 4.4.0 kernel source package.
  https://patchwork.ozlabs.org/patch/823942/
  https://patchwork.ozlabs.org/patch/823945/
  https://patchwork.ozlabs.org/patch/823940/
  https://patchwork.ozlabs.org/patch/823941/
  https://patchwork.ozlabs.org/patch/823939/

  Although it's my understanding the first two are the critical ones for
  the race condition. I have been running with the patches e1000e kernel
  driver, under network load for 7 days and I no longer see the network
  interface drops.

  Could we pull these changes into the Ubuntu 4.4.0 kernel ?

  Thanks
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 19 07:34 seq
   crw-rw 1 root 

[Group.of.nepali.translators] [Bug 1706247] Re: Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

[Stefan Bader]

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

Title:
  Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress

Bug description:
  16G Huge Pages are not supported on PowerNV (bare metal) installations. 
Ubuntu 16.04.2 still allows 16G huge pages to be turned on.
   
  Contact Information = Mike Hollinger (mchol...@us.ibm.com) 
   
  ---uname output---
  Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTB 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Add the following to the kernel boot args (either via editing the 
petitboot boot option manually, or updating /boot/grub/grub.cfg:

  default_hugepagesz=16G hugepagesz=16G hugepages=4

  2. Boot Linux
  3. Observe that the kernel believes 16G huge pages are available:
  ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge
  AnonHugePages:475136 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB
  ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages
  hugepages-1024kB  hugepages-16384kB  hugepages-16777216kB

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  
  This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I 
haven't checked other versions of Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706247/+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 1743672] Re: the wifi driver is always hard blocked on a lenovo laptop

[Timo Aaltonen]

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

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

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

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

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

Title:
  the wifi driver is always hard blocked on a lenovo laptop

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

Bug description:
  On this machine, there is no wifi enable/disable hw switch, but the
  wifi driver is always reported the wifi radio is hard blocked by
  switch.

  The kernel is Artful and OEM kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1743672/+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 1744041] Re: Firmware upgrade interface for CAC Reader BCM58102

[Timo Aaltonen]

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

** Changed in: linux-oem (Ubuntu)
   Status: In Progress => Invalid

** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  Firmware upgrade interface for CAC Reader BCM58102

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

Bug description:
  To support firmware upgrade for CAC Reader BCM58102, besides the user
  space tool, a kernel module is required to implement the interface for
  user space tool to work on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1744041/+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 1740972] Re: No external microphone be detected via headset jack on a dell machine

[Timo Aaltonen]

** Package changed: linux (Ubuntu) => linux-oem (Ubuntu)

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

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

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

** Changed in: linux-oem (Ubuntu)
   Status: Incomplete => 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/1740972

Title:
  No external microphone be detected via headset jack on a dell machine

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

Bug description:
  Plug a headset into the headset jack
  check external microphone

  Expected results: external microphone should wrok well

  Actual results: No external microphone be detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740972/+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 1740973] Re: Two front mics can't work on a lenovo machine

[Timo Aaltonen]

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

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

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

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

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

Title:
  Two front mics can't work on a lenovo machine

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

Bug description:
  There are two front mics on this lenovo machine.

  The test case 'audio/microphone-plug-detection' is always failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740973/+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 1741206] Re: QCA Rome bluetooth failed to work after applying reset-resume quirk

[Timo Aaltonen]

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

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

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

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

Title:
  QCA Rome bluetooth failed to work after applying reset-resume quirk

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

Bug description:
  == SRU Justification ==
  [Impact]
  Some QCA ROME bluetooth devices does not work after runtime suspend/resume 
after SRU LP: #1734020.

  [Fix]
  The commit let btusb reset at second time it resume, i.e. btusb_open(). The 
btusb stops working because the reset happens *after* btusb_open(). The reset 
should be done at hub port initialization, before btusb_probe().

  Revert the bad commit and use the reset-resume quirk in USB core
  stack.

  [Test]
  Cherry-picked the commit into Artful/OEM kernel and the issue is fixed.

  [Regression Potential]
  Low. This is limited to QCA Rome, also verified by the original quirk author.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741206/+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 1740974] Re: [800 G3 SFF] [800 G3 DM]External microphone of headset(3-ring) is working, 2-ring mic not working, both not shown in sound settings

[Timo Aaltonen]

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

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

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

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

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

Title:
  [800 G3 SFF] [800 G3 DM]External microphone of headset(3-ring) is
  working, 2-ring mic not working, both not shown in sound settings

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

Bug description:
  External microphone of headset(3-ring) is working, 2-ring mic not
  working, both not shown in sound settings.

  Steps:
  1. Plug headset(3-ring) or microphone (2-ring)
  2. Observe input device in sound setting

  Expected results: Microphone should be detected and working

  Actual results: Microphone is not detected, only 3-ring mic (from
  headset) is working

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740974/+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 1740971] Re: Can't detect external headset via line-out jack on some Dell machines

[Timo Aaltonen]

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

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

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

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

Title:
   Can't detect external headset via line-out jack on some Dell machines

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

Bug description:
  insert a headset to line-out jack

  Expected results: system should detect line-out port and sound output
  through line-out jack

  Actual results: Can't detect external headset via line-out jack

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740971/+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 1693574] Re: Docker plugin uses the wrong command for Ubuntu

[Eric Desrochers]

** Tags removed: patch
** Tags added: verification-needed verification-needed-artful 
verification-needed-trusty verification-needed-xenial

** Tags removed: verification-needed-artful verification-needed-trusty 
verification-needed-xenial
** Tags added: verification-done-artful verification-done-trusty 
verification-done-xenial

** Tags removed: verification-needed
** Tags added: verification-done

** Changed in: sosreport (Ubuntu Zesty)
   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/1693574

Title:
  Docker plugin uses the wrong command for Ubuntu

Status in sosreport:
  Fix Released
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 Committed
Status in sosreport source package in Zesty:
  Won't Fix
Status in sosreport source package in Artful:
  Fix Committed
Status in sosreport package in Debian:
  Fix Released

Bug description:
  [Impact]

  The docker plugin in sosreport doesn't collect informations for
  Ubuntu.

  In docker.py for the Ubuntu Plugin, the docker command is set to
  'docker.io'[1] which seems to be a old workaround that has been
  removed[2], thus the docker plugin is no longer calling an existing
  docker binary which as a result doesn't collect docker informations in
  Ubuntu.

  [1]- Plugin : docker.py

  # Name collision with another package requires docker binary rename
  docker_cmd = 'docker.io'

  [2]- docker.io package : debian/changelog

  docker.io (1.3.1~dfsg1-2) unstable; urgency=medium
  * Remove deprecated /usr/bin/docker.io symlink
  - added as a temporary shim in 1.0.0~dfsg1-1 (13 Jun 2014)
  - unused by package-installed files in 1.2.0~dfsg1-1 (13 Sep 2014)
  -- Tianon Gravi  Fri, 07 Nov 2014 13:11:34 -0700

  [Test Case]

  # Install sosreport from the Ubuntu archive
  $ apt-get update
  $ apt-get install sosreport

  # Install Docker from the Ubuntu archive
  $ apt-get install docker.io

  # Run sosreport with docker plugin only or all loaded plugins (for the
  sake of testing docker plugin the "-o" is more appropriate

  Docker plugin only :
  $ sosreport -o docker

  All loaded plugins:
  $ sosreport -a

  # Extract the sosreport*.tar.xz file generated by the above command
  found in /tmp and verify that information is gathered properly

  [Regression Potential]

  No regression, this is a trivial fix that will allow sosreport to
  start collecting the docker informations again.

  If for some reasons, a regression is found, it would be 100% limited
  to docker plugin of sosreport and not affecting the functionality the
  core functionality nor other plugins.

  [Other Info]

  Additional informations about the context can be found here :
  https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1338768

  * Upstream Bug
  https://github.com/sosreport/sos/issues/930

  * Pull Request
  https://github.com/sosreport/sos/pull/1009
  
https://github.com/sosreport/sos/pull/1009/commits/f8a939d792d8ac683f341458b8cf77a35c4db929

  * Debian Bug :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863374
  (Patch submitted to Debian on June 2 2017)

  * Ubuntu Bug :
  Working on a backport into stable release (SRU) which will include this 
change via (LP: #1734983).

  [Original Description]

  This Launchpad bug is based on an existing GitHub bug[1].

  The docker plugin is currently broken in sosreport. In docker.py[2]
  for Ubuntu the docker command is set to 'docker.io'.

  docker_cmd = 'docker.io'

  The docker.io package used to have a docker.io binary but this was
  reverted in this debian/changelog from Ubuntu Xenial/16.04 (LTS):

   docker.io (1.3.1~dfsg1-2) unstable; urgency=medium
  * Remove deprecated /usr/bin/docker.io symlink
    - added as a temporary shim in 1.0.0~dfsg1-1 (13 Jun 2014)
    - unused by package-installed files in 1.2.0~dfsg1-1 (13 Sep 2014)
     -- Tianon Gravi   Fri, 07 Nov 2014 13:11:34 -0700

  The Docker Community and Enterprise Editions (docker-ce and docker-ee
  packages) also use the plain docker binary and this change is
  necessary to make the sosreport docker module work again.

  There are currently two different pull requests that fix this issue:

  https://github.com/sosreport/sos/pull/1009
  https://github.com/sosreport/sos/pull/1012

  We should SRU this fix once one of them is accepted.

  [1] https://github.com/sosreport/sos/issues/930
  [2] https://github.com/sosreport/sos/blob/master/sos/plugins/docker.py

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

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

[Group.of.nepali.translators] [Bug 1680384] Re: libvirt-qemu apparmor profiles misses several important entries

[Bug Watch Updater]

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

Title:
  libvirt-qemu apparmor profiles misses several important entries

Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Trusty:
  Incomplete
Status in libvirt source package in Xenial:
  Fix Released
Status in libvirt source package in Yakkety:
  Fix Released
Status in libvirt source package in Zesty:
  Fix Released
Status in libvirt package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Attaching of virtual functions (SR-IOV) not possible without manually
     modification of apparmor rules
   * libvirt/qemu guest logfiles can not state the program that sent the
     shutdown signal
   * on ppc64el when starting on SMT enabled it failes (expected) but does
     not present the hint about SMT being the reasons that was added in
     >=zesty
   * various apparmor denials in the log hide other issues
   * Fix by opening up apparmor rules as needed for these use-cases

  [Test Case]

   * The rules covere a set of use cases, outlining them all here. Some only
     apply to >=Zesty, so I mark each subtest with release names.
   * All start with "Spawn a kvm guest e.g. via uvtool-libvirt"
   * A) >=Xenial - shutdown message
     - A1 - start the guest
     - A2 - stop the guest
     - A3 - check the log in /var/log/libvirt/qemu/.log
     - A-check: without the fix the log ends with 
    With the fix it shall contain the name of the process
    stopping it instead of. So libvirt shutdown will show
    libvirtd, kill from bash shows bash, ...)
   * B) >=Xenial
     - B1 - prepare a hotplug xml and a SR-IOV device - that depends on your
   system, one example is outlined here:
    # Prep VFs and attach
    $ echo 4 | sudo tee /sys/bus/pci/devices/0005\:01\:00.0/sriov_numvfs
    $ sudo modprobe vfio-pci
    $ lspci -n -s 0005:01:01.3
  0005:01:01.3 0200: 10df:e228 (rev 10)
    $ cat VF-5.1.1.3.xml
  
    
  
    
  
  - B2 until bug 1679704 is fixed you need to manually increase the
    locked memory limit of the qemu process before going on
  - B3 attach the device
    $ virsh attach-device z-test VF-5.1.1.3.xml
  - B-check: without the fix it will fail for a set of apparmor denials
     with the fix the attaching will succeed
   * C) >=Zesty
     - C1 - on a ppc64el system start and stop a guest
     - C-check: without the fix apparmor will hold many denies for ppc64_cpu
    and/or accessing /sys/devices/system/cpu/...
    With the fix not only the denies are gone, but also if you
    run on a system with SMT enabled (kvm will fail there) it
    will report to you in the log about "Error: You must disable
    SMT ..."

  [Regression Potential]

   * We are only further "opening up" the current apparmor profiles. So we
     should not end up affecting existing use cases by new blocks.
   * There is a very slight chance that due to accesses being allowed follow
     on actions are triggered which people are not used to like "the VF hot
     attach actually working". So if one relied on it not working it will be
     different for them.
   * Further I made some brainstorming on the potential effects but the only
     other one that came to my mind being a regression of some sort is that
     it now correctly states what send the shutdown signal. So when qemu did
     not end by itself (guest stops) but is stopped (shutdown) the old
     message was:
   terminating on signal 15 from pid 22938 ()
     And now will be like:
   terminating on signal 15 from pid 7714 (/usr/sbin/libvirtd)
     For the hopefully super unlikely case that someone e.g. grepped for
     unknown here it might be a regression.
     And making that message more useful (along with getting rid of the
     associated aa deny is part of the intended fix).

  [Other Info]

   * Tested manually and via regression tests in advance on bileto tickets.
     So all are green there now, there were two unrelated in some dep8 tests 
 due to what seems transient network timeouts (worked on retry) - if 
 showing up in proposed as well we will likely have to retrigger the 
 tests until good. Latest ticket for these to look at sniff builds:
   => https://bileto.ubuntu.com/#/ticket/2738
   * Upload will be directly, since in some of the releases I will need
     dpdk-genversion -v which bileto does not support (and it doesn't
     support publishing selective releases) yet I wanted to show the extra
     tests and checks made and therefore using bileto was beneficial even if
     eventually uploading "old 

[Group.of.nepali.translators] [Bug 1727228] Re: ath9k can't connect to wifi AP

[Timo Aaltonen]

** Package changed: linux (Ubuntu) => linux-oem (Ubuntu)

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

** Changed in: linux-oem (Ubuntu)
   Status: In Progress => 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/1727228

Title:
  ath9k can't connect to wifi AP

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

Bug description:
  [Impact]
  iwlist scan can search the available wifi APs, but can't get connected.

  On new Intel platforms like ApolloLake, legacy interrupt mechanism
  (INTx) is not supported, so WLAN modules are not working because
  interrupts are missing.

  The affected and listed platforms are
  Dell Inspiron 24-3460
  Dell Inspiron 14-3473
  Dell Inspiron 3472
  Dell Inspiron 3576
  Dell Vostro 3262
  Dell Vostro 15-3572
  Dell Vostro 3578

  [Fix]
  Qualcomm provided a MSI patch for ath9k, and it fixes the issue.

  [Test Case]
  Tested on the machines mentioned above, and they all work well.

  [Regression Potential]
  There shouldn't  be any regression potential. These are newly enabled 
machines and quirks are applied based on DMI_PRODUCT_NAME to only use MSI on 
such machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1727228/+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 1713002] Re: oem-config-gtk crashed when using some UTF-8 based languages

[Jeremy Bicha]

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

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

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

Title:
  oem-config-gtk crashed when using some UTF-8 based languages

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  [Summary]
  oem-config crashed when using some UTF-8 based languages

  [Reproduce Steps]
  1. Use live-build to generate a customized Ubuntu image with dell-recovery.
  2. Use the customized Ubuntu image to install the system.
  3. Select traditional Chinese language in oem-config-gtk's language page.
  4. Select the recovery media creation in oem-config-gtk's dell-recovery 
plugin.

  [Results]
  Expected: The installation process will work fine without any problem.
  Actual: Ubiquity crashed in the middle.

  [Additional Information]

  Traceback (most recent call last):
    File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 362, in run
  self.update_interface()
    File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 256, in 
update_interface
  self.status_change(pkgname, float(percent), status_str.strip())
    File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 341, in 
status_change
  self.db.subst(self.info, 'DESCRIPTION', status)
    File "/usr/lib/python3/dist-packages/debconf.py", line 62, in 
  lambda *args, **kw: self.command(command, *args, **kw))
    File "/usr/lib/python3/dist-packages/debconf.py", line 66, in command
  self.write.write("%s %s\n" % (command, ' '.join(map(str, params
  UnicodeEncodeError: 'ascii' codec can't encode characters in position 44-45: 
ordinal not in range(128)

  ...

  PROGRESS STOP
  Exception during installation:
  Traceback (most recent call last):
    File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 405, in run
  res = pm.do_install(self.write_stream.fileno())
  SystemError: E:寫入錯誤 - write (32: Broken pipe), E:寫入錯誤 - write (32: Broken 
pipe), E:寫入錯誤 - write (32: Broken pipe), E:寫入錯誤 - write (32: Broken pipe), 
E:寫入錯誤 - write (32: Broken pipe), E:寫入錯誤 - write (32: Broken pipe), E:寫入錯誤 - 
write (32: Broken pipe), E:寫入錯誤 - write (32: Broken pipe), E:寫入錯誤 - write (32: 
Broken pipe), E:寫入錯誤 - write (32: Broken pipe), E:寫入錯誤 - write (32: Broken 
pipe), E:寫入錯誤 - write (32: Broken pipe), E:寫入錯誤 - write (32: Broken pipe), 
E:寫入錯誤 - write (32: Broken pipe), E:寫入錯誤 - write (32: Broken pipe), E:寫入錯誤 - 
write (32: Broken pipe), E:寫入錯誤 - write (32: Broken pipe), E:寫入錯誤 - write (32: 
Broken pipe), E:寫入錯誤 - write (32: Broken pipe), E:寫入錯誤 - write (32: Broken pipe)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/share/ubiquity/plugininstall.py", line 1779, in 
  install.run()
    File "/usr/share/ubiquity/plugininstall.py", line 78, in wrapper
  func(self)
    File "/usr/share/ubiquity/plugininstall.py", line 249, in run
  self.remove_oem_extras()
    File "/usr/share/ubiquity/plugininstall.py", line 1340, in remove_oem_extras
  self.do_remove(regular)
    File "/usr/share/ubiquity/plugininstall.py", line 1114, in do_remove
  if not cache.commit(fetchprogress, installprogress):
    File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
    File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
    File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 409, in run
  os.write(control_write, b'\1')
  BrokenPipeError: [Errno 32] Broken pipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1713002/+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 1741166] Re: [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device

[Timo Aaltonen]

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

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

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

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

Title:
  [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  New

Bug description:
  [Impact]
  QCA6174A XR can scan but can't pair with bt 4.0 device.

  [Fix]
  [0cf3:e010] is one of the QCA ROME family and should be listed in btusb 
driver.

  [Test Case]
  Applied the patch and can pair with bt 4.0 keyboard without any issue.

  [Regression Potential]
  Adding the device to the list won't have any regression potential.

  impacted tickets:
  LP: #1736330
  LP: #1742849

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1741166/+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 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Stefan Bader]

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Won't Fix
Status in linux source package in Zesty:
  Won't Fix
Status in systemd source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in systemd source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Won't Fix

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   

[Group.of.nepali.translators] [Bug 1703742] Re: Transparent hugepages should default to enabled=madvise

[Stefan Bader]

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

Title:
  Transparent hugepages should default to enabled=madvise

Status in linux package in Ubuntu:
  Fix Released
Status in linux-gke package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux-gke source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Released

Bug description:
  SRU Justification, Zesty, Xenial

  [Impact]

  Ubuntu kernels should default transparent_hugepages to
  enabled=madvise, not enabled=always

  (this corresponds to TRANSPARENT_HUGEPAGE_MADVISE=y in .config).

  I've blogged about this at some length here:
  https://blog.nelhage.com/post/transparent-hugepages/ but here is a
  summary:

  Transparent Hugepages are a feature that allows the kernel to attempt
  to automatically back any anonymous maps with "huge" 2MiB page tables,
  instead of the normal 4k entries. It can produce small net performance
  gains in certain benchmarks, but also has numerous downsides, in the
  form of apparent memory leaks and 30% slowdowns or worse for some
  applications. Many popular pieces of software now refuse to run with
  hugepages enabled because of known performance issues.

  Examples of problem reports:
  MongoDB: https://docs.mongodb.com/manual/tutorial/transparent-huge-pages/
  Oracle: 
https://blogs.oracle.com/linux/entry/performance_issues_with_transparent_huge
  Splunk: 
https://docs.splunk.com/Documentation/Splunk/6.5.2/ReleaseNotes/SplunkandTHP
  Go runtime: https://github.com/golang/go/issues/8832
  jemalloc: 
https://blog.digitalocean.com/transparent-huge-pages-and-alternative-memory-allocators/
  node.js: https://github.com/nodejs/node/issues/11077

  Setting `enabled=madvise` enables applications that know they benefit
  from transparent huge pages to opt-in to this feature, while
  eliminating all the problematic behavior for other applications. Note
  also that transparent hugepage settings don't affect the use of
  explicit hugepages via hugetlbfs or mmap(…, MAP_HUGETLB, …)

  [Fix]
  Enable CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y

  [Regression Potential]
  May marginally impact performance, but the benefits of madvise'd huge 
transparent hugepage over-weigh this considerably.

  This has been enabled in Artful since July (and in Bionic) and we've
  not seen any regression reports, so we are confident this has minimal
  impact.

  [Testcase]
  Kernel ADT tests and stress-ng memory tests should not show any regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703742/+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 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Timo Aaltonen]

** Changed in: scilab (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: scilab (Ubuntu Xenial)
   Status: Confirmed => Invalid

** Changed in: scilab (Ubuntu Artful)
   Status: Confirmed => Invalid

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: mesa (Ubuntu Xenial)
   Status: Confirmed => Invalid

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Invalid
Status in libjogl2-java source package in Xenial:
  Confirmed
Status in mesa source package in Xenial:
  Invalid
Status in scilab source package in Xenial:
  Invalid
Status in libjogl2-java source package in Artful:
  Fix Committed
Status in mesa source package in Artful:
  Invalid
Status in scilab source package in Artful:
  Invalid
Status in scilab package in Debian:
  Fix Released

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1742894/+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 1744295] Re: linux-hwe-edge: 4.13.0-31.34~16.04.1 -proposed tracker

[Andy Whitcroft]

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  linux-hwe-edge: 4.13.0-31.34~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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge 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: 1744294
  phase: Uploaded

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

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

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

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

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Invalid

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

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

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

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

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: New => Invalid

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

** Changed in: linux-azure-edge (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/1742725

Title:
  linux-azure-edge:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-azure-edge package in Ubuntu:
  Invalid
Status in linux-azure-edge source package in Xenial:
  Invalid

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 --
  kernel-stable-master-bug: 1744294
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1742725/+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 1744295] Re: linux-hwe-edge: 4.13.0-31.34~16.04.1 -proposed tracker

[Andy Whitcroft]

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => 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/1744295

Title:
  linux-hwe-edge: 4.13.0-31.34~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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge 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: 1744294
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1744295/+subscriptions

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

[Group.of.nepali.translators] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core

[Jesse Sung]

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

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

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

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

  System will hang on step 2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1736393/+subscriptions

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

[Group.of.nepali.translators] [Bug 1733281] Re: ubuntu/xr-usb-serial didn't get built in zesty and artful

[Jesse Sung]

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

Title:
  ubuntu/xr-usb-serial didn't get built in zesty and artful

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Committed
Status in linux-azure-edge source package in Xenial:
  Fix Released

Bug description:
  The ubuntu/xr-usb-serial is expected to be built for i386 and x86_64,
  and in ubuntu/Makefile it says:

  ifneq ($(filter $(ARCH), i386 x86_64),)
  obj-y += xr-usb-serial/
  endif

  Since ARCH is x86 for both i386 and x86_64, this condition will never
  be true thus the module will never get a chance to be built.

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