[Group.of.nepali.translators] [Bug 1290056] Re: [ati]compiz crashed with SIGSEGV in nux::GraphicsEngine::QRP_GLSL_GetBlurTexture()

[Launchpad Bug Tracker]

This bug was fixed in the package unity -
7.5.0+18.04.20180221.1-0ubuntu1

---
unity (7.5.0+18.04.20180221.1-0ubuntu1) bionic; urgency=medium

  * Unity use track_obj to safely connect to UScreen and Settings
signals (LP: #1748330) (LP: #1748330)
  * CairoBaseWindow: don't try to compute the blur of an invalid texture
(LP: #1290056)
  * Unity: use new definition of infinite CompRegion's (LP: #1749957)

 -- Marco Trevisan (Treviño)   Wed, 21 Feb 2018 15:27:45
+

** Changed in: unity (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/1290056

Title:
  [ati]compiz crashed with SIGSEGV in
  nux::GraphicsEngine::QRP_GLSL_GetBlurTexture()

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

Bug description:
  [ Impact ]

  Unity ramdomly crashes when hovering a tooltip or opening a quicklist

  [ Test case ]

  1. Hover a launcher icon
  2. Open a quicklist or wait for the tooltips
  3. Unity should never crash during such operation

  [ Possible regression ]

  The view might be opened without blurring background, but still better
  than crashing.

  --

  no further info available.

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140305-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar  9 17:35:59 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-03-09 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140308)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f0e5abf2cdf 
<_ZN3nux14GraphicsEngine23QRP_GLSL_GetBlurTextureENS_9ObjectPtrINS_18IOpenGLBaseTextureEEERNS_13TexCoordXFormERKNS_5color5ColorEfi+63>:
 mov0x88(%rcx),%edx
   PC (0x7f0e5abf2cdf) ok
   source "0x88(%rcx)" (0x0088) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: unity
  StacktraceTop:
   nux::GraphicsEngine::QRP_GLSL_GetBlurTexture(int, int, int, int, 
nux::ObjectPtr, nux::TexCoordXForm&, nux::color::Color 
const&, float, int) () from /usr/lib/x86_64-linux-gnu/libnux-graphics-4.0.so.0
   nux::GraphicsEngine::QRP_GetBlurTexture(int, int, int, int, 
nux::ObjectPtr, nux::TexCoordXForm&, nux::color::Color 
const&, float, int) () from /usr/lib/x86_64-linux-gnu/libnux-graphics-4.0.so.0
   unity::CairoBaseWindow::Draw(nux::GraphicsEngine&, bool) () from 
/usr/lib/compiz/libunityshell.so
   unity::Tooltip::Draw(nux::GraphicsEngine&, bool) () from 
/usr/lib/compiz/libunityshell.so
   nux::View::ProcessDraw(nux::GraphicsEngine&, bool) () from 
/usr/lib/x86_64-linux-gnu/libnux-4.0.so.0
  Title: compiz crashed with SIGSEGV in 
nux::GraphicsEngine::QRP_GLSL_GetBlurTexture()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1290056/+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 1665126] Re: Snaps do not show in categories

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software - 3.27.90-1ubuntu1

---
gnome-software (3.27.90-1ubuntu1) bionic; urgency=medium

  * Merge with Debian, remaining changes:
+ debian/patches/*.patch: Various Ubuntu changes from ubuntu-master
  branch - see patch headers for more information.
+ Add an "ubuntu-software" package with some branding for Ubuntu.
+ debian/gnome-software.gsettings-override.in:
  - Mark universe packages as Free.
+ debian/control.in:
  - Recommend Snap plugin
  - GNOME Software provides the PackageKit session interface.
Sessioninstaller wants to do that too - Conflict with it to get it
off user systems.
  * Upstream changes fix (LP: #1665126) and (LP: #1750030)

 -- Robert Ancell   Tue, 20 Feb 2018
11:36:59 +1300

** Changed in: gnome-software (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/1665126

Title:
  Snaps do not show in categories

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Triaged
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  1- I uploaded a snap on myapps.developer.ubuntu.com
  2- I choose Category: Games (note that I cannot choose a sub-category (Kids))
  3- Default type: ? (I choose application, but not sure what it does exactly)
  4- Opening Ubuntu Software on Ubuntu 16.04 I can find and install it when 
using the search bar
  5- BUT my application is not listed in any categories, not even in Games - All
  6- After installing the application, I can see it listed in Games - Kids 
(because the .desktop file have this entry Categories=Game;KidsGame?)

  Looks like only .deb are listed in categories within Ubuntu Software?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1665126/+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 1750619] Re: Static CompRegion destruction causes memory corruption at compiz exit

[Launchpad Bug Tracker]

This bug was fixed in the package compiz -
1:0.9.13.1+18.04.20180221.1-0ubuntu1

---
compiz (1:0.9.13.1+18.04.20180221.1-0ubuntu1) bionic; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * Region: define static const functions returning infinite and empty
regions (LP: #1749957, #1750619)

  [ Samuel Thibault ]
  * ezoom: Add option to choose between no smoothing and linear
smoothing (LP: #1736446)

 -- Marco Trevisan (Treviño)   Wed, 21 Feb 2018 17:34:08
+

** Changed in: compiz (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/1750619

Title:
  Static CompRegion destruction causes memory corruption at compiz exit

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

Bug description:
  [ Impact ]

  Unity could crash when closed with some memory corruption error

  [ Test case ]

  Run unity, loging in and out multiple times, you should get no crash
  report or /var/lib/crash file mentioning compiz.

  [ Regression potential ]

  Really none, the change could only cause compilation issues, not
  really anything for the user changed.

  
  -

  
  Valgrind is a good friend here...

  ==30842== Memcheck, a memory error detector
  ==30842== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==30842== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
  ==30842== Command: ./test-decorations-input-mixer
  ==30842==
  Gtk-Message: 12:17:20.414: Failed to load module "canberra-gtk-module"
  Gtk-Message: 12:17:20.483: Failed to load module "unity-gtk-module"
  Gtk-Message: 12:17:22.584: Failed to load module "canberra-gtk-module"
  Gtk-Message: 12:17:22.699: Failed to load module "canberra-gtk-module"
  m_GLCtx = glXCreateContext(m_X11Display, m_X11VisualInfo, 0, GL_TRUE);
  WARN  2018-02-20 12:17:37 xim.controller XIMController.cpp:103 IBus natively 
supported.
  Cleaning up window 178257923
  curThreadState = 0x15b427e0
  DispatchCurrentUnref, currents are 1
  DEstroying context 0x1f2687e0
  m_GLCtx = NULL;
  ==30842== Invalid read of size 8
  ==30842==at 0x68EA1E4: XDestroyRegion (in 
/usr/lib/x86_64-linux-gnu/libX11.so.6.3.0)
  ==30842==by 0x4130A16: CompRegion::~CompRegion() (region.cpp:113)
  ==30842==by 0x8A8F239: __cxa_finalize (cxa_finalize.c:56)
  ==30842==by 0x76D6B02: ??? (in 
/tmp/NUX_INSTALL/lib/libcompiz_core.so.0.9.13.1)
  ==30842==by 0x4011219: _dl_fini (dl-fini.c:235)
  ==30842==by 0x8A8EEBF: __run_exit_handlers (exit.c:83)
  ==30842==by 0x8A8EF19: exit (exit.c:105)
  ==30842==by 0x8A741C7: (below main) (libc-start.c:342)
  ==30842==  Address 0x15943e10 is 16 bytes inside a block of size 32 free'd
  ==30842==at 0x4C30D3B: free (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==30842==by 0x68EA1F4: XDestroyRegion (in 
/usr/lib/x86_64-linux-gnu/libX11.so.6.3.0)
  ==30842==by 0x4130A16: CompRegion::~CompRegion() (region.cpp:113)
  ==30842==by 0x8A8F239: __cxa_finalize (cxa_finalize.c:56)
  ==30842==by 0x40E5432: ??? (in /tmp/NUX_INSTALL/lib/compiz/libopengl.so)
  ==30842==by 0x4011219: _dl_fini (dl-fini.c:235)
  ==30842==by 0x8A8EEBF: __run_exit_handlers (exit.c:83)
  ==30842==by 0x8A8EF19: exit (exit.c:105)
  ==30842==by 0x8A741C7: (below main) (libc-start.c:342)
  ==30842==  Block was alloc'd at
  ==30842==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==30842==by 0x68EA03A: XCreateRegion (in 
/usr/lib/x86_64-linux-gnu/libX11.so.6.3.0)
  ==30842==by 0x4130A2A: CompRegion::init() (region.cpp:120)
  ==30842==by 0x41307CB: CompRegion::CompRegion() (region.cpp:56)
  ==30842==by 0x4131E29: __static_initialization_and_destruction_0(int, 
int) (region.cpp:43)
  ==30842==by 0x4131E73: _GLOBAL__sub_I_region.cpp (region.cpp:441)
  ==30842==by 0x4010AD9: call_init.part.0 (dl-init.c:72)
  ==30842==by 0x4010BEA: call_init (dl-init.c:30)
  ==30842==by 0x4010BEA: _dl_init (dl-init.c:120)
  ==30842==by 0x4000ED9: ??? (in /lib/x86_64-linux-gnu/ld-2.26.so)
  ==30842==
  ==30842== Invalid free() / delete / delete[] / realloc()
  ==30842==at 0x4C30D3B: free (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==30842==by 0x68EA1EC: XDestroyRegion (in 
/usr/lib/x86_64-linux-gnu/libX11.so.6.3.0)
  ==30842==by 0x4130A16: CompRegion::~CompRegion() (region.cpp:113)
  ==30842==by 0x8A8F239: __cxa_finalize (cxa_finalize.c:56)
  ==30842==by 0x76D6B02: ??? (in 
/tmp/NUX_INSTALL/lib/libcompiz_core.so.0.9.13.1)
  ==30842==by 0x4011219: _dl_fini (dl-fini.c:235)
  ==30842==by 0x8A8EEBF: __run_exit_handlers (exit.c:83)
  ==30842==by 0x8A8EF19: exit (exit.c:105)
  ==30842==by 0x8A741C7: (below main) 

[Group.of.nepali.translators] [Bug 1752711] Re: cloud-init no longer processes user data on GCE in artful

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 18.1-5-g40e77380-0ubuntu1

---
cloud-init (18.1-5-g40e77380-0ubuntu1) bionic; urgency=medium

  * New upstream snapshot.
- GCE: fix reading of user-data that is not base64 encoded. (LP: #1752711)
- doc: fix chef install from apt packages example in RTD.
- Implement puppet 4 support [Romanos Skiadas] (LP: #1446804)
- subp: Fix subp usage with non-ascii characters when no system locale.
  (LP: #1751051)
- salt: configure grains in grains file rather than in minion config.
  [Daniel Wallace]

 -- Chad Smith   Thu, 01 Mar 2018 15:47:04
-0700

** Changed in: cloud-init (Ubuntu Bionic)
   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/1752711

Title:
  cloud-init no longer processes user data on GCE in artful

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Artful:
  Confirmed
Status in cloud-init source package in Bionic:
  Fix Released

Bug description:
  If I pass in user data like so:

  $ cat cfg
  #!/bin/sh
  touch /tmp/foobar

  $ gcloud compute instances create aa-$(date +%y%m%d-%H%M) --image-family 
ubuntu-1710 --image-project ubuntu-os-cloud-devel --metadata-from-file 
user-data=cfg
  ...

  Then in the instance:

  $ ls /tmp/foobar
  $ sudo cat /var/lib/cloud/instance/user-data.txt
  $ curl 
"http://metadata.google.internal/computeMetadata/v1/instance/attributes/user-data;
 -H "Metadata-Flavor: Google"
  #/bin/sh
  touch /tmp/foobar

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1752711/+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 1720109] Re: snmpd stop on host stops snmpd on LXD containers

[Launchpad Bug Tracker]

This bug was fixed in the package net-snmp - 5.7.3+dfsg-1ubuntu4.1

---
net-snmp (5.7.3+dfsg-1ubuntu4.1) xenial; urgency=medium

  * d/snmpd.init: also match start-stop-daemon against pidfile to avoid
killing extra snmpd processes for example in container (LP: #1720109)

 -- Christian Ehrhardt   Tue, 20 Feb
2018 14:53:51 +0100

** Changed in: net-snmp (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  snmpd stop on host stops snmpd on LXD containers

Status in net-snmp package in Ubuntu:
  Fix Released
Status in net-snmp source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Stopping snmpd in Xenial can stop container processes of the same 
 binary

   * Fix by matching to the PIDFILE that is already tracked by snmpd

  [Test Case]

   * Set up a host (e.g. a VM being Xenial)
   * Set up at least one (or more) containers in it
   * Install and start snmpd in the Host
   * Install and start snmpd in the containers
   * you'll now see like:
  root@ubuntu-vm:/var/log# ps fxaw|grep snmp
  29382 ? S 0:00 \_ /usr/sbin/snmpd -Lsd -Lf /dev/null -u snmp -g snmp
  29308 ? S 0:00 /usr/sbin/snmpd -Lsd -Lf /dev/null -u snmp -g snmp 
# One of these is from the container
   * now on the host stop your service, chances are you stop your guests instead
 root@ubuntu-vm:/var/log# service snmpd stop
 root@ubuntu-vm:/var/log# ps fxaw|grep snmp
 29426 pts/0 S+ 0:00 \_ grep --color=auto snmp
 # 29382 was from a lxd container in this case

  [Regression Potential]

   * In case the pidfile stored by the snmpd daemon would be incorrect then 
 the stop/restart actions would not match the process and fail to 
 stop/restart. We didn't see that in our tests, but that is the 
 regression I could think of.

  [Other Info]
   
   * n/a

  
  

  
  If you have ubuntu 16.04 containers running snmpd and you stop the snmpd on 
the LXD host system, it will also shut down all the snmpd instances on the 
containers (but will not restart them if you restart them on the LXD host) .. 
in fact, you even need to go back into the container, stop the snmpd before you 
can start it again.

  See log below, viepovzat17 is the LXD host, viezmaaat10 is the ubuntu
  container:

    driver: lxc
    driver_version: 2.0.8
    kernel: Linux
    kernel_architecture: x86_64
    kernel_version: 4.4.0-87-generic
    server: lxd
    server_pid: 4426
    server_version: "2.16"
    storage: zfs
    storage_version: 0.6.5.6-0ubuntu16

  root@viezmaaat10:~# /etc/init.d/snmpd start
  [ ok ] Starting snmpd (via systemctl): snmpd.service.
  root@viezmaaat10:~# ps -eaf | grep snmp
  snmp  1271 1  0 10:50 ?00:00:00 /usr/sbin/snmpd -Lsd -Lf 
/dev/null -u snmp -g snmp -I -smux mteTrigger mteTriggerConf -p /run/snmpd.pid
  root  1291   757  0 10:50 ?00:00:00 grep --color=auto snmp
  root@viezmaaat10:~#
  root@viezmaaat10:~# ps -eaf | grep snmp
  snmp  1271 1  0 10:50 ?00:00:00 /usr/sbin/snmpd -Lsd -Lf 
/dev/null -u snmp -g snmp -I -smux mteTrigger mteTriggerConf -p /run/snmpd.pid
  root  1293   757  0 10:50 ?00:00:00 grep --color=auto snmp
  root@viezmaaat10:~# exit

  root@viepovzat17:~# ps -eaf | grep snmp
  snmp 22757 1  0 10:45 ?00:00:00 /usr/sbin/snmpd -Lsd -Lf 
/dev/null -u snmp -g snmp -I -smux mteTrigger mteTriggerConf -p /run/snmpd.pid
  100116   24118  5222  0 10:50 ?00:00:00 /usr/sbin/snmpd -Lsd -Lf 
/dev/null -u snmp -g snmp -I -smux mteTrigger mteTriggerConf -p /run/snmpd.pid
  root 24153 21842  0 10:50 pts/100:00:00 grep --color=auto snmp
  root@viepovzat17:~# /etc/init.d/snmpd stop
  [ ok ] Stopping snmpd (via systemctl): snmpd.service.
  root@viepovzat17:~# ps -eaf | grep snmp
  root 24286 21842  0 10:50 pts/100:00:00 grep --color=auto snmp
  root@viepovzat17:~#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1720109/+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 1737761] Re: zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu19

---
zfs-linux (0.6.5.6-0ubuntu19) xenial; urgency=medium

  * Add ZFS 0.7.0 kernel ioctl binary compat shim (LP: #1737761)
Detect ZFS kernel driver version and copy zfs ioctl command to the
newer ZFS 0.7.0 ioctl command layout.

 -- Colin Ian King   Mon, 19 Feb 2017 13:04:11
+0100

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2

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

Bug description:
  == SRU Justification, Xenial, Artful ==

  Running ZFS userspace utils with newer 0.7.x ZFS kernel drivers breaks
  ZFS send/receive because of changes in the ioctl command structure.

  == Testcase ==

  ubuntu ADT ZFS tests autotests/client/tests/ubuntu-zfs-smoke-tests
  will show a failure in ZFS SEND, with userspace zfs tools segfaulting.

  == Fix ==

  Fix is to detect if ZFS kernel driver is version 0.7.x and copy the
  0.6.5.x zfs ioctl command structure to a ZFS 0.7.x version, call the
  ioctl() and then copy the result back.

  == Regression Potential ==

  This will only affect the ZFS ioctl interface and this can be fully
  tested using the ZFS autotests with 0.7.0 and 0.6.5.x ZFS enabled
  kernels to check for the compatibility change regressions.

  --

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/z/zfs-linux/20171212_032601_d0613@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/arm64/z/zfs-linux/20171212_020008_d0613@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/ppc64el/z/zfs-linux/20171212_024359_d0613@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/z/zfs-linux/20171212_032349_d0613@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1737761/+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 1746114] Re: Move xenial to fwupd 0.8.x branch

[Launchpad Bug Tracker]

This bug was fixed in the package fwupd - 0.8.3-0ubuntu2

---
fwupd (0.8.3-0ubuntu2) xenial; urgency=medium

  * Fix systemd unit for what is actually supported in
systemd 229 in xenial (LP: #1746114)
  * This bug also fixes issues with USB devices being closed (LP: #1642812)

 -- Mario Limonciello   Wed, 14 Feb 2018
14:32:41 -0500

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

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

Title:
  Move xenial to fwupd 0.8.x branch

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

Bug description:
  [Impact]
   * Upstream has declared that 0.7.x is EOL
     - No further security updates will be performed for it.
   * Many crashers were fixed in 0.8.x.
   * Upstream can better maintain fwupd ecosystem wide if Ubuntu (the last ones 
using 0.7.x release) move to 0.8.x or newer.
   * Latest upstream release is 1.0.4 release, but moving to 0.9.x or 1.0.x is 
difficult due to many dependencies not present in Ubuntu 16.04.
   * Upstream spun this point release specifically for getting Ubuntu xenial on 
a newer maintainable version.
  https://groups.google.com/forum/#!topic/fwupd/R6UyaCtWbqo

  New Features:
   - Add --version option to fwupdmgr (Richard Hughes)

  Bugfixes:
   - Add a delay when calling update_prepare (Mario Limonciello)
   - Block owned Dell TPM updates (#339) (Mario Limonciello)
   - Catch invalid Dell dock component requests (Mario Limonciello)
   - Disable the dell plugin if libsmbios fails (Mario Limonciello)
   - Do not re-download firmware that exists in the cache (Richard Hughes)
   - Ensure the 8bitdo version is set in non-bootloader mode (Richard Hughes)
   - Fix a logic error with testing for a dell system (Mario Limonciello)
   - Fix compile with newer versions of GUdev (Richard Hughes)
   - Fix crash with dock connected but UEFI capsule off (Mario Limonciello)
   - Use new VID for 8bitdo (Richard Hughes)

  [Test Case]
   * Use fwupdmgr to check for and apply a firmware update
   * Use gnome-software to check for and apply a firmware update

  [Regression Potential]
   * This is a point release of the 0.8.x release which has been deemed stable.
   * Potential regressions would more likely exist in gnome-software which uses 
fwupd's interfaces to perform firmware updates.
   * If a regression were to occur, gnome-software may crash or not display a 
firmware update anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1746114/+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 1642812] Re: USB devices are not closed when error occurs

[Launchpad Bug Tracker]

This bug was fixed in the package fwupd - 0.8.3-0ubuntu2

---
fwupd (0.8.3-0ubuntu2) xenial; urgency=medium

  * Fix systemd unit for what is actually supported in
systemd 229 in xenial (LP: #1746114)
  * This bug also fixes issues with USB devices being closed (LP: #1642812)

 -- Mario Limonciello   Wed, 14 Feb 2018
14:32:41 -0500

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

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

Title:
  USB devices are not closed when error occurs

Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd source package in Xenial:
  Fix Released
Status in fwupd source package in Yakkety:
  Won't Fix
Status in fwupd source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * fwupd (used in Xenial) does not close USB device nodes when it fails to 
process the 
  devices.

   * The orphan (un-closed) device node will be kept until fwupd ends

   * The behavior will avoid the system to set the USB device as
  idle/suspend then the system cannot enter some power-saving mode (eg.
  S0ix)

  
  [Test Case]

   * make sure fwupd is not running by executing 'fwupdmgr get-devices'
 It will show devices information.

   * list the fds opened by fwupd
 $ sudo ls -l /proc/$(pgrep fwupd)/fd | grep usb
 If a system is not affected, it will output nothing.
 If the result shows one or more strings like /dev/bus/usb/[BUS]/[DEV]
 (BUS and DEV are numeric variables), that means the issue is existing.

  
  [Regression Potential] 

   * The fix only closes file descriptors of USB devices when errors
  happen and should not have regression there.

  
  [Original description]
In fwupd, a few of USB devices are not closed when there are some failures 
of 
operations. This issue will cause fwupd has some orphan USB nodes inside 
during fwupd is 
running. A orphan USB node might introduce memory leak and block some 
runtime power 
features as well.

I proposed a upstream PR, and also put the link here.
https://github.com/hughsie/fwupd/pull/73

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

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

[Group.of.nepali.translators] [Bug 1644662] Re: Icons missing when appearance setting is "high contrast"

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-themes-standard -
3.18.0-2ubuntu2

---
gnome-themes-standard (3.18.0-2ubuntu2) xenial; urgency=medium

  * Use HighContrast icons for the HighContrast theme. (LP: #1644662)

 -- Dariusz Gadomski   Thu, 08 Feb 2018
07:55:43 +0100

** Changed in: gnome-themes-standard (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

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

Status in gnome-themes-standard package in Ubuntu:
  Fix Released
Status in gnome-themes-standard source package in Xenial:
  Fix Released
Status in gnome-themes-standard source package in Artful:
  Fix Released

Bug description:
  [Impact]

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

  [Test Case]

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

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

  [Regression Potential]

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

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

  To reproduce this:

  Open System Settings.

  Click Appearance

  Theme: High Contrast.

  Click All Settings tab:

  Many icons are missing.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-themes-standard/+bug/1644662/+subscriptions

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

[Group.of.nepali.translators] [Bug 1747802] Re: Snapped applications launched from command line aren't properly matched

[Launchpad Bug Tracker]

This bug was fixed in the package bamf -
0.5.3~bzr0+16.04.20180209-0ubuntu1

---
bamf (0.5.3~bzr0+16.04.20180209-0ubuntu1) xenial; urgency=medium

  * bamf-window: read snap and flatpak IDs and use it to guess desktop-
id (LP: #1747802)

 -- Marco Trevisan (Treviño)   Fri, 09 Feb 2018 15:49:14
+

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

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

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

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

Bug description:
  [Impact]

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

  [Test case]

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

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

  [Regression Potential]

  Application with security profile might get a wrong desktop file.

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

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

[Group.of.nepali.translators] [Bug 1739591] Re: lttng-modules-dkms failed to build with 4.14 Azure edge kernel on Xenial

[Brian Murray]

** Changed in: lttng-modules (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  lttng-modules-dkms failed to build with 4.14 Azure edge kernel on
  Xenial

Status in lttng-modules:
  New
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in lttng-modules source package in Xenial:
  Fix Released
Status in lttng-modules source package in Artful:
  Fix Released

Bug description:
  SRU request, Xenial, Artful

  [Impact]

  lttng dkms modules fail to build against newer HWE kernels because of
  missing 4.14 compat fixes that allow it to build against newer 4.14
  kernels.

  [Fix]
  Upstream lttng 4.14 compat fixes.

  [Testcase]
  Without the fix, running the kernel team autotest lttng regression test suite 
fails because the module does not build and install.  With the fix the lttng 
smoke tests pass.

  To run the test:
  sudo autotest/client/autotest-local 
autotest/client/tests/ubuntu_lttng_smoke_test/control

  using git://kernel.ubuntu.com/ubuntu/autotest and
  git://kernel.ubuntu.com/ubuntu/autotest-client-tests

  [Regression Potential]
  lttng fails to build and work against older kernels. As the new code is 
#if'def'd compat code the 4.14 specific changes are not built into the older 
kernels, so this risk is small.

  --

  [stdout] Setting up lttng-modules-dkms (2.8.0-1ubuntu1~16.04.3) ...
   [stdout] Loading new lttng-modules-2.8.0 DKMS files...
   [stdout] First Installation: checking all kernels...
   [stdout] Building only for 4.14.0-1002-azure-edge
   [stdout] Building initial module for 4.14.0-1002-azure-edge
   [stdout] Error! Bad return status for module build on kernel: 
4.14.0-1002-azure-edge (x86_64)
   [stdout] Consult /var/lib/dkms/lttng-modules/2.8.0/build/make.log for more 
information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lttng-modules/+bug/1739591/+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 1739591] Re: lttng-modules-dkms failed to build with 4.14 Azure edge kernel on Xenial

[Launchpad Bug Tracker]

This bug was fixed in the package lttng-modules - 2.8.0-1ubuntu1~16.04.4

---
lttng-modules (2.8.0-1ubuntu1~16.04.4) xenial; urgency=medium

  * Fix builds on HWE 4.14 kernel (LP: #1739591)
Apply the following upstream commits:
 0030-Fix-update-block-instrumentation-for-4.14-kernel.patch
 0031-Fix-update-writeback-instrumentation-for-kernel-4.14.patch
 0032-Update-kvm-instrumentation-for-4.15.patch
 0033-Fix-kvm-instrumentation-for-4.15.patch
 0034-Update-kvm-instrumentation-for-3.16.52-and-3.2.97.patch
 0035-Update-kvm-instrumentation-for-debian-kernel-4.9.65-.patch
 0036-Update-kvm-instrumentation-for-4.14.14-4.9.77-4.4.11.patch

 -- Colin Ian King   Tue, 6 Feb 2018 10:38:22
+

** Changed in: lttng-modules (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  lttng-modules-dkms failed to build with 4.14 Azure edge kernel on
  Xenial

Status in lttng-modules:
  New
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in lttng-modules source package in Xenial:
  Fix Released
Status in lttng-modules source package in Artful:
  Fix Released

Bug description:
  SRU request, Xenial, Artful

  [Impact]

  lttng dkms modules fail to build against newer HWE kernels because of
  missing 4.14 compat fixes that allow it to build against newer 4.14
  kernels.

  [Fix]
  Upstream lttng 4.14 compat fixes.

  [Testcase]
  Without the fix, running the kernel team autotest lttng regression test suite 
fails because the module does not build and install.  With the fix the lttng 
smoke tests pass.

  To run the test:
  sudo autotest/client/autotest-local 
autotest/client/tests/ubuntu_lttng_smoke_test/control

  using git://kernel.ubuntu.com/ubuntu/autotest and
  git://kernel.ubuntu.com/ubuntu/autotest-client-tests

  [Regression Potential]
  lttng fails to build and work against older kernels. As the new code is 
#if'def'd compat code the 4.14 specific changes are not built into the older 
kernels, so this risk is small.

  --

  [stdout] Setting up lttng-modules-dkms (2.8.0-1ubuntu1~16.04.3) ...
   [stdout] Loading new lttng-modules-2.8.0 DKMS files...
   [stdout] First Installation: checking all kernels...
   [stdout] Building only for 4.14.0-1002-azure-edge
   [stdout] Building initial module for 4.14.0-1002-azure-edge
   [stdout] Error! Bad return status for module build on kernel: 
4.14.0-1002-azure-edge (x86_64)
   [stdout] Consult /var/lib/dkms/lttng-modules/2.8.0/build/make.log for more 
information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lttng-modules/+bug/1739591/+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 1694859] Re: arm64 kernel crashdump support

[dann frazier]

** Bug watch added: Debian Bug tracker #883899
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883899

** Also affects: makedumpfile (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883899
   Importance: Unknown
   Status: Unknown

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

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

** Changed in: makedumpfile (Ubuntu Artful)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: kexec-tools (Ubuntu Artful)
   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/1694859

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Fix Released
Status in kexec-tools source package in Yakkety:
  Won't Fix
Status in linux source package in Yakkety:
  Won't Fix
Status in makedumpfile source package in Yakkety:
  Won't Fix
Status in kexec-tools source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released
Status in kexec-tools source package in Artful:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in makedumpfile source package in Artful:
  In Progress
Status in makedumpfile package in Debian:
  Unknown

Bug description:
  Note: Updates are being staged at ppa:dannf/arm64-kdump.

  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.

  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger

  Crash dump should occur, with artifacts collected in /var/crash.

  If you want to verify that the dump is usable, install the
  corresponding linux-image--dbgsym package and run:

  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.

  crash should successfully load, placing you at a "crash>" prompt. At that 
prompt, you can issue the 'bt' command to see a backtrace.
  Note: you need crash from zesty (7.1.8-1ubuntu1) or later.

  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:

  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).

  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.

  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).

  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)

  = kexec-tools =
  == zesty ==
  For zesty, 10 patches are required to add kdump support.

  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:

  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
    The callback function only returns -1 or 0, and the return value of
    kexec_iomem_for_each_line() will never be used.
  * sh, x86
    The callback function may return (-1 for sh,) 0 or 1, but always returns
    1 once we have reached the maximum number of entries allowed.
    Even so the current kexec_iomem_for_each_line() counts them up.
    This change actually fixes this bug.
  -

  0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch:
  This generalizes a function that was duplicated by arm & x86 and makes it 
common so arm64 can use it.

  The remaining 8 of these only touch code in kexec/arch/arm64, so
  regression risk for other architectures is negligible.

  Finally, I have tested this update on both i386 and amd64 VMs. i386
  crashes do not currently work in zesty (filed LP: #1699874), and my
  test results show no change there. amd64 worked before, and continues
  to work with these changes.

  == yakkety ==
  Since yakkety is based on an older upstream, 6 additional patches are 
required:

  

[Group.of.nepali.translators] [Bug 1694859] Re: arm64 kernel crashdump support

[dann frazier]

** Also affects: kexec-tools (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

** Changed in: kexec-tools (Ubuntu Yakkety)
   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/1694859

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Fix Released
Status in kexec-tools source package in Yakkety:
  Won't Fix
Status in linux source package in Yakkety:
  Won't Fix
Status in makedumpfile source package in Yakkety:
  Won't Fix
Status in kexec-tools source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released
Status in kexec-tools source package in Artful:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in makedumpfile source package in Artful:
  In Progress
Status in makedumpfile package in Debian:
  Unknown

Bug description:
  Note: Updates are being staged at ppa:dannf/arm64-kdump.

  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.

  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger

  Crash dump should occur, with artifacts collected in /var/crash.

  If you want to verify that the dump is usable, install the
  corresponding linux-image--dbgsym package and run:

  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.

  crash should successfully load, placing you at a "crash>" prompt. At that 
prompt, you can issue the 'bt' command to see a backtrace.
  Note: you need crash from zesty (7.1.8-1ubuntu1) or later.

  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:

  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).

  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.

  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).

  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)

  = kexec-tools =
  == zesty ==
  For zesty, 10 patches are required to add kdump support.

  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:

  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
    The callback function only returns -1 or 0, and the return value of
    kexec_iomem_for_each_line() will never be used.
  * sh, x86
    The callback function may return (-1 for sh,) 0 or 1, but always returns
    1 once we have reached the maximum number of entries allowed.
    Even so the current kexec_iomem_for_each_line() counts them up.
    This change actually fixes this bug.
  -

  0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch:
  This generalizes a function that was duplicated by arm & x86 and makes it 
common so arm64 can use it.

  The remaining 8 of these only touch code in kexec/arch/arm64, so
  regression risk for other architectures is negligible.

  Finally, I have tested this update on both i386 and amd64 VMs. i386
  crashes do not currently work in zesty (filed LP: #1699874), and my
  test results show no change there. amd64 worked before, and continues
  to work with these changes.

  == yakkety ==
  Since yakkety is based on an older upstream, 6 additional patches are 
required:

  arm-fix-get_kernel_stext_sym-to-close-its-file.patch:
  This is a cleanup patch, cherry-picked because it allows later patches to 
apply w/o backporting. ARM-specific.

  kexec-add-max_size-to-memory_ranges.patch:
  Adds a new element to struct, to be used by later commits.

  

[Group.of.nepali.translators] [Bug 1752711] Re: cloud-init no longer processes user data on GCE in artful

[Scott Moser]

** Changed in: cloud-init
   Status: New => Confirmed

** Changed in: cloud-init
   Importance: Undecided => High

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => High

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Bionic)
   Importance: High
   Status: Confirmed

** Also affects: cloud-init (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Artful)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: cloud-init (Ubuntu Artful)
   Importance: Undecided => Critical

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

Title:
  cloud-init no longer processes user data on GCE in artful

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Artful:
  Confirmed
Status in cloud-init source package in Bionic:
  Confirmed

Bug description:
  If I pass in user data like so:

  $ cat cfg
  #!/bin/sh
  touch /tmp/foobar

  $ gcloud compute instances create aa-$(date +%y%m%d-%H%M) --image-family 
ubuntu-1710 --image-project ubuntu-os-cloud-devel --metadata-from-file 
user-data=cfg
  ...

  Then in the instance:

  $ ls /tmp/foobar
  $ sudo cat /var/lib/cloud/instance/user-data.txt
  $ curl 
"http://metadata.google.internal/computeMetadata/v1/instance/attributes/user-data;
 -H "Metadata-Flavor: Google"
  #/bin/sh
  touch /tmp/foobar

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1752711/+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 1746299] Re: update makedumpfile tool version to v1.6.3

[Brad Figg]

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

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: Fix Released

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

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

Title:
  update makedumpfile tool version to v1.6.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  New upstream kernel versions, as those in linux-hwe package, require a newer 
makedumpfile to be supported. Otherwise, all copies fallback to copying the 
entire memory.

  [Test case]
  kdump-tools has been installed, system rebooted, then crash trigerred and 
verified that a small dump file was present on /var/crash/. Tested on amd64 and 
ppc64le.

  [Regression potential]
  Many other bug fixes have been included in the latest version of the package. 
The changes are supposed to fix these bugs, and have been tested as well. 
However, as the total of changes is not trivial, there is impact of regression 
that has been minimized by the tests done. Regression potential of not 
supporting older kernels has been tested with the kernels shipped on xenial and 
artful as well.


  
  

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-30 
10:46:53 ==
  ---Problem Description---
  update makedumpfile to latest version v1.6.3 that officially supports
  up to kernel version 4.14.8. Since makedumpfile is inherently backward 
compatible,
  this would not break existing functionality..

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

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

  ---Steps to Reproduce---
   makedumpfile reports ""The kernel version is not supported" while generating 
vmcore
  Also, there is a possibility of bogus address translations in makedumpfile 
tool with
  missing upstream patches. Can't be so sure without an exhaustive testing. 
Instead,
  it would be a good idea to go with the version which officially supports the 
kernel
  version in question.

  Userspace tool common name: makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Hari Krishna Bathini  - 2018-01-30 
10:49:13 ==
  With kernel version updated to 4.13.0, please update makedumpfile tool
  version to 1.6.3 which officially supports up to kernel version 4.14.8 [1].

  Thanks
  Hari

  [1]
  http://lists.infradead.org/pipermail/kexec/2018-January/019853.html

  This needs to be tagged for both 16.04.4 & 18.04 releases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746299/+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 1752632] Re: The motd message is not cached

[Andreas Hasenack]

** Also affects: landscape-client (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  The motd message is not cached

Status in Landscape Client:
  New
Status in landscape-client package in Ubuntu:
  New
Status in landscape-client source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  New
Status in landscape-client source package in Artful:
  New

Bug description:
  landscape-common has an MOTD component called landscape-sysinfo.
  Historically that used update-motd to display cached information.
  update-motd has been deprecated in favor of pam_motd, but landscape-
  common was never changed accordingly.

  The situation we have now in landscape-common's debconf is:
  - "Cache sysinfo in /etc/motd": places a symlink in /etc/update-motd.d. With 
pam_motd, there is no cache, so that script is called on every login.
  - "Run sysinfo on every login": places the same symlink in /etc/profile.d, 
removes the one from /etc/update-motd.d. End result is the same as before: 
script is called on every login
  - "Do not display sysinfo on login": remove /etc/profile.d and 
/etc/update-motd.d symlinks. This is the only option that is currently working 
as advertised.

To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1752632/+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 1752381] Re: [SRU] New upstream microrelease flatpak 0.8.9

[Ken VanDine]

** No longer affects: flatpak (Ubuntu Xenial)

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

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

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

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

Title:
  [SRU] New upstream microrelease flatpak 0.8.9

Status in flatpak package in Ubuntu:
  Invalid
Status in flatpak source package in Artful:
  Triaged

Bug description:
  This is a request to SRU the latest microrelease of the 0.8 LTS series
  of flatpak into artful.

  [Impact]

  New upstream micro release of flatpak, which backports important bug
  fixes and security improvements into the 0.8 LTS series.

  Artful is currently at 0.8.7, whereas 0.8.9 is available upstream.

  The main improvements from 0.8.7 are:

* Security fixes for the dbus sandbox, debian bugs that were filed 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=42 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880451
* Allows the hosts icons to be available in sandboxed apps, so they can use 
the hosts theme.
* Give each app a persistent cache directory for fontconfig.
* Improvements to environments variables exposed to sandboxed apps.
* Results in reducing the number of patches being carried.

  [Test Case]

  The bugs being resolved are not simple to reproduce, see the test plan
  below for testing flatpak itself.

  [Regression Potential]

  Flatpak has a test suite, which is run on build across all
  architectures and passes.

  I have written a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak which can be
  used to confirm the functionality. I have checked this test plan on an
  artful machine.

  Regression potential is low, and upstream is responsive to any issues
  raised.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1752381/+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 1752381] Re: [SRU] New upstream microrelease flatpak 0.8.9

[Ken VanDine]

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

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

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

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

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

Title:
  [SRU] New upstream microrelease flatpak 0.8.9

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

Bug description:
  This is a request to SRU the latest microrelease of the 0.8 LTS series
  of flatpak into artful.

  [Impact]

  New upstream micro release of flatpak, which backports important bug
  fixes and security improvements into the 0.8 LTS series.

  Artful is currently at 0.8.7, whereas 0.8.9 is available upstream.

  The main improvements from 0.8.7 are:

* Security fixes for the dbus sandbox, debian bugs that were filed 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=42 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880451
* Allows the hosts icons to be available in sandboxed apps, so they can use 
the hosts theme.
* Give each app a persistent cache directory for fontconfig.
* Improvements to environments variables exposed to sandboxed apps.
* Results in reducing the number of patches being carried.

  [Test Case]

  The bugs being resolved are not simple to reproduce, see the test plan
  below for testing flatpak itself.

  [Regression Potential]

  Flatpak has a test suite, which is run on build across all
  architectures and passes.

  I have written a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak which can be
  used to confirm the functionality. I have checked this test plan on an
  artful machine.

  Regression potential is low, and upstream is responsive to any issues
  raised.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1752381/+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 1745261] Re: [Hyper-V] scsi: storvsc: Increase cmd_per_lun for higher speed devices

[Marcelo Cerri]

** Changed in: linux-azure (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: linux-azure (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [Hyper-V] scsi: storvsc: Increase cmd_per_lun for higher speed devices

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

Bug description:
  Increase cmd_per_lun to allow more I/Os in progress per device,
  particularly for NVMe's.  The Hyper-V host side can handle the
  higher count with no issues.

  This patch should be applied to the linux-azure kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1745261/+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 1748662] Re: [Hyper-V] Drivers: hv: vmbus: Fix ring buffer signaling

[Marcelo Cerri]

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

** Also affects: linux-azure (Ubuntu Bionic)
   Importance: Undecided
   Status: Confirmed

** Changed in: linux-azure (Ubuntu Xenial)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux-azure (Ubuntu Bionic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

Title:
  [Hyper-V] Drivers: hv: vmbus: Fix ring buffer signaling

Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Xenial:
  In Progress
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  Fix bugs in signaling the Hyper-V host when freeing space in the
  host->guest ring buffer:

  1. The interrupt_mask must not be used to determine whether to signal
 on the host->guest ring buffer
  2. The ring buffer write_index must be read (via hv_get_bytes_to_write)
 *after* pending_send_sz is read in order to avoid a race condition
  3. Comparisons with pending_send_sz must treat the "equals" case as
 not-enough-space
  4. Don't signal if the pending_send_sz feature is not present. Older
 versions of Hyper-V that don't implement this feature will poll.

  Fixes: 03bad714a161 ("vmbus: more host signalling avoidance")

  This patch is on its way upstream but has not yet been accepted into
  char-misc. It should apply to 4.4+ kernels that have taken
  03bad714a161

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1748662/+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 1699179] Re: PackageReporter kicks in during do-release-upgrade

[Andreas Hasenack]

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

Title:
  PackageReporter kicks in during do-release-upgrade

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

Bug description:
  Affected release: Ubuntu 14.04.5
  Version of package: 14.12-0ubuntu5.14.04

  Steps to reproduce:
  1. Run do-release-upgrade to upgrade to 16.04.2.
  2. Trigger the package-reporter to kick in while do-release-upgrade is 
working but not having the package database locked.
  3. Package database is locked by package-reporter, do-release-upgrade fails 
to access it and exits.

  Expected result:
  Landscape detects that there's an release upgrade in progress and will wait 
for it to finish.

  Actual result:
  PackageReporter locks the apt database, do-release-upgrade cannot access it, 
exits with an error and may leave the system in an unusable state.

  * Link to Dariusz's PR on GitHub:
  https://github.com/CanonicalLtd/landscape-client/pull/14

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

[Andreas Hasenack]

** Changed in: landscape-client
   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 Released
Status in landscape-client package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  Fix Released
Status in landscape-client source package in Xenial:
  Fix Released
Status in landscape-client source package in Artful:
  Fix Released
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]

  Scenario #1
   * 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.

  Scenario #2
   * Deploy an AWS non KVM/non C5 instance (Example : t2.medium)
   * Look sys_vendor
     $ cat /sys/class/dmi/id/sys_vendor
     Xen

   * Install landscape-client
   * Register the client to the desired landscape-server
   * Verify "VM Type" to still be "xen" 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   : 0
  cpu cores : 1
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 13
  wp 

[Group.of.nepali.translators] [Bug 1743232] Re: set vm_info to kvm for digitalocean instances

[Andreas Hasenack]

** Changed in: landscape-client
   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 Released
Status in landscape-client package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  Fix Released
Status in landscape-client source package in Xenial:
  Fix Released
Status in landscape-client source package in Artful:
  Fix Released
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 1752632] [NEW] The motd message is not cached

[Andreas Hasenack]

Public bug reported:

landscape-common has an MOTD component called landscape-sysinfo.
Historically that used update-motd to display cached information.
update-motd has been deprecated in favor of pam_motd, but landscape-
common was never changed accordingly.

The situation we have now in landscape-common's debconf is:
- "Cache sysinfo in /etc/motd": places a symlink in /etc/update-motd.d. With 
pam_motd, there is no cache, so that script is called on every login.
- "Run sysinfo on every login": places the same symlink in /etc/profile.d, 
removes the one from /etc/update-motd.d. End result is the same as before: 
script is called on every login
- "Do not display sysinfo on login": remove /etc/profile.d and 
/etc/update-motd.d symlinks. This is the only option that is currently working 
as advertised.

** Affects: landscape-client
 Importance: Undecided
 Status: New

** Affects: landscape-client (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: landscape-client (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: landscape-client (Ubuntu Artful)
 Importance: Undecided
 Status: New

** Also affects: landscape-client (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: landscape-client (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: landscape-client (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

Title:
  The motd message is not cached

Status in Landscape Client:
  New
Status in landscape-client package in Ubuntu:
  New
Status in landscape-client source package in Xenial:
  New
Status in landscape-client source package in Artful:
  New

Bug description:
  landscape-common has an MOTD component called landscape-sysinfo.
  Historically that used update-motd to display cached information.
  update-motd has been deprecated in favor of pam_motd, but landscape-
  common was never changed accordingly.

  The situation we have now in landscape-common's debconf is:
  - "Cache sysinfo in /etc/motd": places a symlink in /etc/update-motd.d. With 
pam_motd, there is no cache, so that script is called on every login.
  - "Run sysinfo on every login": places the same symlink in /etc/profile.d, 
removes the one from /etc/update-motd.d. End result is the same as before: 
script is called on every login
  - "Do not display sysinfo on login": remove /etc/profile.d and 
/etc/update-motd.d symlinks. This is the only option that is currently working 
as advertised.

To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1752632/+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 1743300] Re: libguestfs not work anymore with 4.13.0-26-generic #29~16.04.2-Ubuntu

[Launchpad Bug Tracker]

This bug was fixed in the package supermin - 5.1.14-2ubuntu1.1

---
supermin (5.1.14-2ubuntu1.1) xenial; urgency=medium

  * Backport fixes for symlink breakage, v4.13+ kernel support (LP:
#1743300)

 -- Nivedita Singhvi   Wed, 14 Feb 2018
12:45:07 -0800

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

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

Title:
  libguestfs not work anymore with 4.13.0-26-generic #29~16.04.2-Ubuntu

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

Bug description:
  [Impact]

  An update to mainline kernel v4.13 breaks the supermin v5.1.14
  package in Xenial. Supermin is a tool for preparing and building
  very specific, tiny, virtual appliances which boot very fast. It
  uses an ext2 file system disk image. Users of supermin functionality
  like guestfish, libguestfs-test-tool, etc., all break in different
  ways as a result, some catastrophic, but in each case, the tool
  and virtual appliance are not usable. This impacts the 
  libguestfs-tools package (users of supermin).

  This bug results in users not being able to upgrade their kernel,
  specifically, use a kernel that is v4.13-based or later. A 
  workaround is to ensure that an earlier kernel (e.g. v4.4-based 
  Xenial kernels) is used by supermin. This can conflict
  with user needs to use a later kernel for other reasons.

  
  [Test Case]

  1) Using the v5.1.14 supermin installed and running on a 4.13-based 
 kernel like 4.13.0-32-generic #35~16.04.1-Ubuntu:
 (Assuming you have virtualization support packages etc. already
  installed):

  $ sudo apt-get install libguestfs-tools
  $ libguestfs-test-tool

   [appliance kernel panic or qemu crash or just a silent hang]

  
  2) Using the v5.1.14 supermin version and running on a 4.13-based 
 kernel like 4.13.0-32-generic #35~16.04.1-Ubuntu:
  
 # wget 
https://cloud-images.ubuntu.com/releases/16.04/release/ubuntu-16.04-server-cloudimg-amd64-disk1.img
 -O /var/lib/libvirt/images/ubuntu-16.04-server-cloudimg-amd64-disk1.img

 # guestfish --rw -a 
/var/lib/libvirt/images/ubuntu-16.04-server-cloudimg-amd64-disk1.img
  Welcome to guestfish, the guest filesystem shell for
  editing virtual machine filesystems and disk images.

  Type: 'help' for help on commands
  'man' to read the manual
  'quit' to quit the shell

  > run
  libguestfs: error: appliance closed the connection unexpectedly.
  This usually means the libguestfs appliance crashed.

  
  [Regression Potential]

  * There might be errors in creation and management of tiny
supermin appliances via tools in the libguestfs-tools
package.

  
  [Other Info]

  * From the upstream patch description, brief explanation of
the bug:

"The ext2 filesystem on disk format has two ways to store symlinks.
For symlinks >= 60 bytes in length, they are stored as files
(so-called "slow symlinks").  For shorter symlinks the symlink is
stored in the inode ("fast symlinks").

Previously we only created slow symlinks even if they are shorter than
60 bytes.  This didn't matter until recently, when a change went into
the upstream kernel which assumes that symlinks shorter than 60 bytes
are always stored in the inode, thus breaking the filesystems that we
created before..."

Note that the real fix is to switch to use ext2fs_symlink() to create
links. 

  * A fix for this problem went into upstream supermin v5.1.18. 
Thus this bug affects supermin < v5.1.18, and kernel >= v4.13.

  * Thus this bug only affects the Ubuntu Xenial distro release:

 supermin = v5.1.14
 kernel = v4.13.*

Artful includes the v4.1.18 supermin package (which has the symlink fix)
and Bionic has a later one (v4.1.19). Thus neither is affected by
this issue. Trusty is running an older version (4.1.6-1) of supermin
but is not running the v4.13 or later kernel, and is thus not affected
either.

  * This fix has been tested successfully on Xenial and shown to fix the
reported and related breakages as listed in the Test Case section
and more.

  * A public PPA test package for Xenial is available to test with
and has been tested by at least one user who was seeing the
problem, successfully.

  * This fix backports 2 patches from upstream:

 1. ext2: Don't load whole files into memory when copying to the appliance 
(RHBZ#1113065).
 2. ext2: Create symlinks properly (RHBZ#1470157).

 Patch 1 is necessary as it supplies some dependent code 
 used by Patch 2; and Patch 2 does not compile cleanly without
 it. 

  
https://github.com/libguestfs/supermin/commit/158854e3ba4be7f6b8d81f662ddad98358ede1de

  

[Group.of.nepali.translators] [Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!

[Kleber Sacilotto de Souza]

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

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

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

** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  bnx2x_attn_int_deasserted3:4323 MC assert!

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

Bug description:
  SRU Justification
  =

  A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x
  card attached, and uses openvswitch to bridge an ibmveth interface for
  traffic from other LPARs.

  We see the following crash sometimes when running netperf:
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_attn_int_deasserted3:4323(enP24p1s0f2)]MC assert!
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_mc_assert:720(enP24p1s0f2)]XSTORM_ASSERT_LIST_INDEX 0x2
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_mc_assert:736(enP24p1s0f2)]XSTORM_ASSERT_INDEX 0x0 = 0x 
0x25e42a7e 0x00462a38 0x00010052
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_mc_assert:750(enP24p1s0f2)]Chip Revision: everest3, FW Version: 7_13_1
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_attn_int_deasserted3:4329(enP24p1s0f2)]driver assert
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_panic_dump:923(enP24p1s0f2)]begin crash dump -
  ... (dump of registers follows) ...

  Subsequent debugging reveals that the packets causing the issue come
  through the ibmveth interface - from the AIX LPAR. The veth protocol
  is 'special' - communication between LPARs on the same chassis can use
  very large (64k) frames to reduce overhead. Normal networks cannot
  handle such large packets, so traditionally, the VIOS partition would
  signal to the AIX partitions that it was 'special', and AIX would send
  regular, ethernet-sized packets to VIOS, which VIOS would then send
  out.

  This signalling between VIOS and AIX is done in a way that is not
  standards-compliant, and so was never made part of Linux. Instead, the
  Linux driver has always understood large frames and passed them up the
  network stack.

  In some cases (e.g. with TCP), multiple TCP segments are coalesced
  into one large packet. In Linux, this goes through the generic receive
  offload code, using a similar mechanism to GSO. These segments can be
  very large which presents as a very large MSS (maximum segment size)
  or gso_size.

  Normally, the large packet is simply passed to whatever network
  application on Linux is going to consume it, and everything is OK.

  However, in this case, the packets go through Open vSwitch, and are
  then passed to the bnx2x driver. The bnx2x driver/hardware supports
  TSO and GSO, but with a restriction: the maximum segment size is
  limited to around 9700 bytes. Normally this is more than adequate.
  However, if a large packet with very large (>9700 byte) TCP segments
  arrives through ibmveth, and is passed to bnx2x, the hardware will
  panic.

  [Impact]

  bnx2x card panics, requiring power cycle to restore functionality.

  The workaround is turning off TSO, which prevents the crash as the
  kernel resegments *all* packets in software, not just ones that are
  too big. This has a performance cost.

  [Fix]

  Test packet size in bnx2x feature check path and disable GSO if it is
  too large. To do this we move a function from one file to another and
  add another in the networking core.

  [Regression Potential]

  A/B/X: The changes to the network core are easily reviewed. The changes to 
behaviour are limited to the bnx2x card driver.
  The most likely failure case is a false-positive on the size check, which 
would lead to a performance regression only.

  T: This also involves a different change to the networking core to add
  the old-style GSO checking, which is more invasive. However the
  changes are simple and easily reviewed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+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 1736116] Re: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox

[LocutusOfBorg]

** Summary changed:

- Host with kernel 4.13 freezes when starting a VM with VirtualBox
+ [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox

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

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

** Also affects: virtualbox-guest-additions-iso (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: virtualbox-ext-pack (Ubuntu)
   Importance: Undecided
   Status: New

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

** No longer affects: kbuild (Ubuntu Artful)

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

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

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

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

** Changed in: virtualbox-ext-pack (Ubuntu)
   Status: New => Fix Released

** Changed in: virtualbox-ext-pack (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: virtualbox-ext-pack (Ubuntu Artful)
   Status: New => In Progress

** Changed in: virtualbox-guest-additions-iso (Ubuntu)
   Status: New => Fix Released

** Changed in: virtualbox-guest-additions-iso (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: virtualbox-guest-additions-iso (Ubuntu Artful)
   Status: New => In Progress

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

** Description changed:

- This is a spin-off of bug 1729568. With Kernel 4.13 (from linux-generic-
- hwe-16.04-edge), the host system freezes completely when starting a VM
- using VirtualBox. A black boot window pops up right before the freeze.
+ [Impact] 
+ * New kernel broke completely old and current vbox in xenial/artful, + 
security issues (meltdown,spectre)
+ * VM not able to start, 3d not working
+ [Test Case]
+ * Install 16.04 or 17.10 in a VM, Update or install the hwe stack, reboot, 
panic
+ 
+ [Regression Potential] 
+ * This is the second round of minor updates, since cherry-picking is 
impossible, and less tested by upstream/debian/me.
+ No regressions when we moved 5.0.18 to 5.0.40
+ 
+ The jump 5.0.40 -> 5.1.32 is bigger, but since 5.0.x is EOL upstream,
+ and with a lot of security issues, we should try to get the move in
+ Xenial, to make vbox continue working.
+ 
+ 5.2 can't build there, because of a lot of qtbase issues, so sticking
+ with 5.1 is the only viable solution we found over the last 4 months
+ 
+ [Other Info]
+ This is a spin-off of bug 1729568. With Kernel 4.13 (from 
linux-generic-hwe-16.04-edge), the host system freezes completely when starting 
a VM using VirtualBox. A black boot window pops up right before the freeze.

** Changed in: virtualbox-guest-additions-iso (Ubuntu Artful)
   Importance: Undecided => High

** Changed in: virtualbox-guest-additions-iso (Ubuntu Artful)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

** Changed in: virtualbox-guest-additions-iso (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: virtualbox-guest-additions-iso (Ubuntu Xenial)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

** Changed in: virtualbox-guest-additions-iso (Ubuntu)
   Importance: Undecided => High

** Changed in: virtualbox-guest-additions-iso (Ubuntu)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

** Changed in: virtualbox-ext-pack (Ubuntu Artful)
   Importance: Undecided => High

** Changed in: virtualbox-ext-pack (Ubuntu Artful)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

** Changed in: virtualbox-ext-pack (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: virtualbox-ext-pack (Ubuntu Xenial)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

** Changed in: virtualbox-ext-pack (Ubuntu)
   Importance: Undecided => High

** Changed in: virtualbox-ext-pack (Ubuntu)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

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

** Changed in: virtualbox (Ubuntu Artful)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

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

** Changed in: virtualbox (Ubuntu Xenial)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

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

** Changed in: kbuild (Ubuntu Xenial)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

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

** Changed in: kbuild (Ubuntu)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

** Changed in: virtualbox (Ubuntu)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

** Changed in: virtualbox (Ubuntu)
   Importance: Critical => High

[Group.of.nepali.translators] [Bug 1746316] Re: VirtualBox needs Security Patches

[LocutusOfBorg]

I uploaded them in unapproved queue

** Changed in: virtualbox (Ubuntu)
 Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)

** Summary changed:

- VirtualBox needs Security Patches
+ [SRU] VirtualBox needs Security Patches

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

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

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

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

Title:
  [SRU] VirtualBox needs Security Patches

Status in virtualbox package in Ubuntu:
  In Progress
Status in virtualbox source package in Xenial:
  In Progress
Status in virtualbox source package in Artful:
  In Progress

Bug description:
  VirtualBox in 16.04 LTS needs an upgraded software version to receive needed 
security patches:
  
https://www.techrepublic.com/article/10-new-vm-escape-vulnerabilities-discovered-in-virtualbox/

  Doing this will probably also fix this bug:
  https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualbox (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 30 13:01:27 2018
  InstallationDate: Installed on 2017-10-20 (102 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Group.of.nepali.translators] [Bug 1717040] Re: Please backport libzstd 1.3.1+dfsg-1 (universe) from artful

[Launchpad Bug Tracker]

This bug was fixed in the package libzstd - 1.3.1+dfsg-1ubuntu0.1

---
libzstd (1.3.1+dfsg-1ubuntu0.1) artful; urgency=medium

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

libzstd (1.3.1+dfsg-1) unstable; urgency=medium

  * Team upload
  * New upstream version
  * Exclude examples from upstream tarball
Closes: #869581
  * debhelper 10
  * cme fix dpkg-control
  * Standards-Version: 4.1.0 (no changes needed)
  * Fix copyright

libzstd (1.2.0-1) unstable; urgency=medium

  * New upstream release (Closes: #863159).

libzstd (1.1.2-1) unstable; urgency=medium

  * Team upload.
  * New upstream version 1.1.2

libzstd (1.1.1-1) unstable; urgency=medium

  * New upstream version 1.1.1 (Closes: #844248)
  * Whitespace fix to d/control
  * Ensure hardening flags pass through to compiler by appending to CPPFLAGS

libzstd (1.1.0-1) unstable; urgency=medium

  * New upstream version 1.1.0 (Closes: #839960)
  * Change uploader email
  * Build new pzstd binary, including manpage
  * Fix miscellaneous issues with d/rules and d/*.install
  * Move docs from libzstd-dev to the zstd binary

libzstd (1.0.0-1) unstable; urgency=medium

  * Imported Upstream version 1.0.0 (Closes: #836574)
  * Bump library package name to libzstd1
  * Changed project URLs, copyrights after move to facebook.
  * d/rules: hardening=+all

libzstd (0.8.0-1) unstable; urgency=medium

  [ Kevin Murray ]
  * New upstream version (Closes: #834114)

  [ Andreas Tille ]
  * hardening=+bindnow

libzstd (0.5.1-1) unstable; urgency=medium

  [ Kevin Murray ]
  * New upstream version (fixes a FTBFS)
  * Package pkgconfig file (Closes: #813854)
  * Fix path to tagged archives in d/watch
  * Add vcs URLs
  * Bump to standards version 3.9.7

  [ Mattia Rizzolo ]
  * debian/rules: Remove a lot of uneeded comments and lines

libzstd (0.4.7-1) unstable; urgency=low

  * New upstream version
  * Remove build date encoding to enable reproducible build

libzstd (0.4.5-1) unstable; urgency=low

  * Initial release (Closes: #806767)

 -- Andreas Hasenack   Tue, 16 Jan 2018 19:28:18
+

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

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

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

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

Bug description:
  [Special SRU Notes]

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

  [Impact]

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

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

   * This backport/SRU is being requested by upstream.

  [Test Case]

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

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

  a) compression tests

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

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

  Artful:
  $ zstd /usr/bin/snap -o snap.1.3.1.zst
  /usr/bin/snap: 31.03%   (11318760 => 3512707 bytes, snap.1.3.1.zst)   
 

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

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

  Artful:
  $ zstd /usr/bin/snap -o snap.1.3.1-updated.zst
  /usr/bin/snap: 31.03%   (11318760 => 3512707 bytes, 
snap.1.3.1-updated.zst) 

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

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

  Artful:
  $ zstd -d snap.1.3.1.zst -o snap.1.3.1
  snap.1.3.1.zst  : 11318760 bytes  
 
  $ zstd -d snap.1.3.1-updated.zst -o snap.1.3.1-updated
  snap.1.3.1-updated.zst: 11318760 bytes
 

   

[Group.of.nepali.translators] [Bug 1748122] Re: incorrect tools.conf template is shipped with Ubuntu

[Launchpad Bug Tracker]

This bug was fixed in the package open-vm-tools -
2:9.4.0-1280544-5ubuntu6.4

---
open-vm-tools (2:9.4.0-1280544-5ubuntu6.4) trusty; urgency=medium

  * d/local/tools.conf: Explicitly point to logfile in tools.conf
fixup for (LP 1748122).

open-vm-tools (2:9.4.0-1280544-5ubuntu6.3) trusty; urgency=medium

  * Make tools.conf template useful. (LP: #1748122)

 -- Dariusz Gadomski   Tue, 20 Feb 2018
14:01:55 +0100

** Changed in: open-vm-tools (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  incorrect tools.conf template is shipped with Ubuntu

Status in VMWare tools:
  Fix Released
Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Trusty:
  Fix Released
Status in open-vm-tools source package in Xenial:
  Fix Released
Status in open-vm-tools source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * The default tools.conf template shipped with the Ubuntu package is
  useless - it gets cleared on the first run as it contains an
  unrecognized content.

  [Test Case]

   * Install open-vm-tools.
   * Check contents of /etc/vmware-tools/tools.conf.
   * Start vmtoolsd service e.g. by systemctl start open-vm-tools.
   * Check tools.conf contents again.

  Expected result:
  Config is read an left untouched.

  Actual result:
  Config file is cleared.

  [Regression Potential]

   * If any of the parameters in the template is set to a non-default value
  the behaviour of vmtoolsd may change slightly (e.g. different log verbosity, 
log target - file vs. syslog).
 But people will get the usual conffile changed prompts, so those who 
modified it will have to consciously decide which makes it safe.

  [Other Info]

   * Original bug description:

  The tools.conf template shipped with Ubuntu (debian/local/tools.conf)
  is incorrect.

  It's current contents:
  bindir = "/usr/bin"
  do not mean anything to open-vm-tools - it's not interpreted in any way by 
vmtoolsd.

  Moreover, on the first launch this content is cleared by a piece of
  code doing a "config upgrade".

  I believe replacing it with a more meaningful content is necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/open-vm-tools/+bug/1748122/+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 1743884] Re: installed GRUB menu does not appear on term used for install

[Launchpad Bug Tracker]

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

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

  * debian/patches/mkconfig_keep_native_term_active.patch: Keep the
default EFI console active while enabling gfxterm. (LP: #1743884)

 -- dann frazier   Fri, 09 Feb 2018 11:45:07 -0700

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

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

Title:
  installed GRUB menu does not appear on term used for install

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2 source package in Artful:
  Fix Released
Status in grub2 source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  I have a UEFI-based server with both a graphical head and a serial console 
(Cavium Sabre). If I boot the netboot (d-i) installer, the install menu appears 
on both, and I'm able to interact with the installer over both the serial 
console and the graphical head. However, when booting into the *installed* 
system (w/ HIDDEN_TIMEOUT disabled), the GRUB menu only appears over the 
graphical head. I can use either serial or graphical for input - that is, if I 
monitor the graphical head I can see the changes I'm typing on the serial 
console, but the serial console remains blank until I boot into Linux.

  Note: MAAS installations are not impacted by this because curtin adds
  an /etc/default/grub.d stub that manually sets
  "GRUB_TERMINAL=console".

  [Test Case]
  Install the system using d-i over the serial console.
  Comment out the HIDDEN variables in /etc/default/grub.
  sudo update-grub
  Reboot - and watch for the GRUB menu over the serial console.

  [Regression Risk]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1743884/+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 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Kleber Sacilotto de Souza]

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

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

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

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux package in Fedora:
  Confirmed

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Timo Aaltonen]

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

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Timo Aaltonen]

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

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

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