[Group.of.nepali.translators] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted virtualbox-hwe into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/virtualbox-
hwe/5.0.40-dfsg-0ubuntu1.16.04.1~16.04.3 in a few hours, and then in the
-proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

** Tags added: verification-needed

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

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in virtualbox-hwe package in Ubuntu:
  New
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in libinput source package in Xenial:
  Fix Committed
Status in libwacom source package in Xenial:
  Fix Committed
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in vulkan source package in Xenial:
  Fix Committed
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xfonts-utils source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+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 1701097] Re: eni rendering of ipv6 gateways fails

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.9-221-g7e41b2a7-0ubuntu1

---
cloud-init (0.7.9-221-g7e41b2a7-0ubuntu1) artful; urgency=medium

  * New upstream snapshot.
- sysconfig: use MACADDR on bonds/bridges to configure mac_address
  [Ryan Harper] (LP: #1701417)
- net: eni route rendering missed ipv6 default route config
  [Ryan Harper] (LP: #1701097)
- sysconfig: enable mtu set per subnet, including ipv6 mtu
  [Ryan Harper] (LP: #1702513)
- sysconfig: handle manual type subnets [Ryan Harper] (LP: #1687725)
- sysconfig: fix ipv6 gateway routes [Ryan Harper] (LP: #1694801)
- sysconfig: fix rendering of bond, bridge and vlan types.
  [Ryan Harper] (LP: #1695092)
- Templatize systemd unit files for cross distro deltas. [Ryan Harper]
- sysconfig: ipv6 and default gateway fixes. [Ryan Harper] (LP: #1704872)
- net: fix renaming of nics to support mac addresses written in upper case.
  (LP: #1705147)

 -- Scott Moser   Thu, 20 Jul 2017 21:37:12 -0400

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

Title:
  eni rendering of ipv6 gateways fails

Status in cloud-init:
  Confirmed
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 Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  cloud-init trunk and xenial, yakkety, zesty and artful all fail

  A network config with a ipv6 gateway route like:

  
  subnets:
- type: static
  address: 2001:4800:78ff:1b:be76:4eff:fe06:96b3
  netmask: ':::::'
  routes:
- gateway: 2001:4800:78ff:1b::1
  netmask: '::'
  network: '::'

  For eni rendering, this should create a post-up/post-down route
  command that generates a default ipv6 route entry, like this:

  post-up route add -A inet6 default gw 2001:4800:78ff:1b::1 || true
  pre-down route del -A inet6 default gw 2001:4800:78ff:1b::1 || true

  However, what is currently generated is this:

  post-up route add -net :: netmask :: gw 2001:4800:78ff:1b::1 || true
  pre-down route del -net :: netmask :: gw 2001:4800:78ff:1b::1 || true

  That does not install the route correctly as a default gateway route.

  This is fallout from commit d00da2d5b0d45db5670622a66d833d2abb907388 
  net: normalize data in network_state object

  This commit removed ipv6 route 'netmask' values, and converted them to
  prefix length values, but failed to update the eni renderer's check for
  ipv6 default gateway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701097/+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 1593907] Re: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCR

[Launchpad Bug Tracker]

This bug was fixed in the package ntp - 1:4.2.8p8+dfsg-1ubuntu2.2

---
ntp (1:4.2.8p8+dfsg-1ubuntu2.2) yakkety; urgency=medium

  * debian/ntpdate.if-up: Drop delta to stop/start service around ntpdate
updates - fixes ntp restart storms due to network changes, fixes
accidential start of ntp, avoids issues of ntpdate jumping too far while
running ntp was supposed to drift (LP: #1593907)

 -- Christian Ehrhardt   Fri, 07 Jul
2017 07:58:18 +0200

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

Title:
  ntpdate startup routine prevents ntp service from launching up on
  Ubuntu 16.04 server on system boot; manually starting ntp service
  works: [FIX in DESCRIPTION], just need to apply it and release a new
  version

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Trusty:
  Fix Committed
Status in ntp source package in Xenial:
  Fix Committed
Status in ntp source package in Yakkety:
  Fix Released
Status in ntp source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * Fixes several broken cases, those are:
   * Case 1 - ntp configured to drift time slowly, but time jumping
   - ntp is running and drifts time towards a target being way off
   - an interface comes up
   - stop ntpd
   - warp time via ntpdate-debian (static interfaces will even set -b)
   - (re-)start ntpd
   - if users relied on non-time warp they are now in trouble

   * Case 2 - ntp start/stop storms
   - ntpd comes up normally
   - the admin brings interfaces up/down rather often
   - ntp is restarted very very often due to this for no reason
   => reason for bugs like debian 823533

   * Case 3 - unintentional enablement of ntp
   - ntpd is installed but disabled (for whatever reason)
   - all is fine on any ifup/down
   - one installs ntpdate, maybe even without realizing due to a depends
   - now on the next ifup ntpd (or openntpd) will be started

   * Solution, drop the broken Delta

  [Test Case]

   * Testing Case 2/3 as it is the easiest, case 1 needs a more complex 
 setup to cause the time drift but otherwise works the same way.
 - install ntp and ntpdate
 - stop ntp
 - ifup/ifdown an interface multiple times; as simplification you can 
   also call /etc/network/if-up.d/ntpdate directly (not that this 
   spawns the change asnchronous and locks concurrency, so do that a 
   few times over the time of a minute or so)
 - the service of ntp should still be stopped and not report plenty of 
   restarts

  
  [Regression Potential] 

   * It improves a lot of cases (otherwise we wouldn't SRU), but there is 
 one regression potential I can see:

 - users that relied on starting NTP later on after other interfaces 
   got up due to that code in ntpdate which did that as a side effect. 
   But that is outweigh by Case2/3 for the majority of users. And even 
   Case1 only hits this potential regression on e.g. late network 
   intialization, but in that case please remind that the default 
   (systemd timedatectl) would handle that.

 - Since most users of ntp do not install ntpdate (which doesn't work 
   when ntp is active) we should be rather safe to assume that almost 
   no one should rely on that side effect.

 - Furthermore this is a Ubuntu Delta for very long, cause issues (see 
   the references on the git commit) but never made it into Debian - 
   in that sense another indicator it isn't an important delta to 
   have.

  [Other Info]
   
   * The original intention "what if net is available too late" fixed 
 correctly would not be part of ntpdate, but ntp and additionally 
 check if it is actually meant to be enabled - but I never seen/heard 
 of any of it since systemd is around - maybe new ordering mostly 
 avoids the original issue.


  ---

  
  I've installed ntp service on the clean ubuntu 16.04 server system. 
Configured it. Checked that it works, but, after reboot, it doesn't start 
automatically.
  When I check: 'systemctl is-enabled ntp', it shows enabled.
  If I manually start it 'systemctl start ntp' it starts just fine and woks 
correctly,
  but until I manually start it, 'systemctl status ntp' shows:

  Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
  Active: inactive (deadi)

  Installed 1.29ubuntu2 version of init-systems-helper, but it didn't
  fix the problem.

  Found a bugreport on ntpd package:

  https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596

  led to solution that involves a change to be made in file:

  /etc/network/if-up.d/ntpdate

  of ntpdate package

  

[Group.of.nepali.translators] [Bug 1693850] Re: libzen wasn't compiled with large file support

[Launchpad Bug Tracker]

This bug was fixed in the package libzen - 0.4.33-3ubuntu0.16.10.1

---
libzen (0.4.33-3ubuntu0.16.10.1) yakkety-proposed; urgency=medium

  * [57d99f9] Import large files patch (LP: #1693850)

 -- Chow Loong Jin   Tue, 30 May 2017 00:24:00
+0800

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

Title:
  libzen wasn't compiled with large file support

Status in libzen package in Ubuntu:
  Fix Released
Status in libzen source package in Xenial:
  Fix Released
Status in libzen source package in Yakkety:
  Fix Released
Status in libzen source package in Zesty:
  Fix Released
Status in libzen source package in Artful:
  Fix Released

Bug description:
  [Impact]

  The switch to cmake caused two compilation flags to be accidentally dropped:
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files on 32-bit machines. This affects the following
  reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

  [Test Case]

  Run `mediainfo $filename` where $filename is a file that is larger
  than 4.2GB. Output will be missing if this bug is present.

  [Regression Potential]

  Quite low, since the only thing that's changed here are some -D
  compilation flags that aren't even directly referenced in the
  codebase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libzen/+bug/1693850/+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 1699933] Re: ipmi-locate crash on arm64

[Launchpad Bug Tracker]

This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu4~0.16.10

---
freeipmi (1.4.11-1.1ubuntu4~0.16.10) yakkety; urgency=medium

  * Backport to yakkety
Use kernel DMI table interface, when available, instead of trolling
/dev/mem to avoid a crash on ARM. LP: #1699933.

 -- Ike Panhc   Fri, 30 Jun 2017 11:01:05 +0800

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

Title:
  ipmi-locate crash on arm64

Status in freeipmi package in Ubuntu:
  Fix Released
Status in freeipmi source package in Xenial:
  Fix Committed
Status in freeipmi source package in Yakkety:
  Fix Released
Status in freeipmi source package in Zesty:
  Fix Committed
Status in freeipmi source package in Artful:
  Fix Released
Status in freeipmi package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Read from /dev/mem and scan DMI tables is dangerous, if /dev/mem is
  not stable to read, it will cause ipmi-locate crash.

  [Test Case]

   * `sudo ipmi-locate` shall not crash

  [Regression Potential]

   * Reading from DMI tables is sysfs is more stable then reading from
  /dev/mem and if DMI tables is not available ipmi-locate will use the
  old way to search in /dev/mem. I believe its low regression risk

  
  Similiar to bug 1499838 but not 100% same.

  ipmi-locate looks into /dev/mem for DMI tables and crash when DMI
  tables are not in accessible memory region. Kernel > v4.2 provides
  /sys/firmware/DMI/tables/DMI which is a much safer place to read.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1699933/+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 1683808] Re: fail to activate the second DS8K fcp device permanently

[Launchpad Bug Tracker]

This bug was fixed in the package s390-tools - 1.36.1-0ubuntu2.2

---
s390-tools (1.36.1-0ubuntu2.2) yakkety; urgency=medium

  * chzdev: Fix ineffective zfcp-lun udev rule preventing activation of
unordered WWPNs. LP: #1683808

 -- Dimitri John Ledkov   Thu, 06 Jul 2017 14:11:42
+0100

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

Title:
  fail to activate the second DS8K fcp device permanently

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Xenial:
  Fix Released
Status in s390-tools source package in Yakkety:
  Fix Released
Status in s390-tools source package in Zesty:
  Fix Released
Status in s390-tools source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * out of order devices fail to activate

  [Test Case]

   * See steps to reproduce below

  [Regression Potential]

   * s390-tools rebuild, includes rebuilding the bootloader, thus
  failure to boot should be tested in case of a no-change rebuild
  regression. The fix for the issue in question is a pure ordering
  issue, thus ordering the ids should resolve the issue at hand without
  any other negative side-effects

  [Other Info]
   
   * Original report:

  ---Problem Description---
  Fail to active the second DS8K fcp lun permanently

  Machine Type = z13 lpar

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

  ---Steps to Reproduce---
   1. Map tow fcp luns from DS8880:
     root@ilz62u:~# lsluns
     Scanning for LUNs on adapter 0.0.1800
   at port 0x50050763070057f9:
    0x40004028
    0x40014010
     Scanning for LUNs on adapter 0.0.1900
   at port 0x50050763070b17f9:
    0x40004028
    0x40014010
  2. active the two fcp temporarily
  echo 0x40014010 > 
/sys/bus/ccw/drivers/zfcp/0.0.1800/0x50050763070057f9/unit_add
    echo 0x40014010 > 
/sys/bus/ccw/drivers/zfcp/0.0.1900/0x50050763070b17f9/unit_add

  3. active them via tool "chzdev" permanently
     root@ilz62u:~# lszdev | grep 57f9
  zfcp-lun 0.0.1800:0x50050763070057f9:0x40004028  yes  yes   sdas 
sg44
  zfcp-lun 0.0.1800:0x50050763070057f9:0x40014010  yes  yes   sdau 
sg46

  4. multipath show
  root@ilz62u:~# multipath -ll | grep 2107s
  d2ilsd2107s (36005076307ffd7f90110) dm-15 IBM,2107900
  d1ilsd2107s (36005076307ffd7f90028) dm-14 IBM,2107900

  5. reboot

  6. the secod fcp lun "0x40014010" fail to keep active any more
  root@ilz62u:/sys/bus/ccw/drivers/zfcp/0.0.1800# ls 0x50050763070057f9
  0x40004028  access_denied  failed  in_recovery  power  status  uevent 
 unit_add  unit_remove
  root@ilz62u:/sys/bus/ccw/drivers/zfcp/0.0.1900# ls 0x50050763070b17f9
  0x40004028  access_denied  failed  in_recovery  power  status  uevent 
 unit_add  unit_remove

  root@ilz62u:/sys/bus/ccw/drivers/zfcp/0.0.1900# multipath -ll | grep 2107s
  d1ilsd2107s (36005076307ffd7f90028) dm-14 IBM,2107900

  Stack trace output:
   no

  Oops output:
   no

  System Dump Info:
    The system is not configured to capture a system dump.

  == Comment: #1 - Heinz-Werner Seeck  -
  2017-04-18 03:08:54 ==

  First problem evaluation:
  Could be a chzdev problem. Seeing two jump-labels in the udev rule for port 
0x50050763070b17f9 on fcp device 0x1800 and 0x1900. The first label enables the 
LUN that is working, while the second one with the LUN number that is not 
working is likely ignored.

  Confirmed as a bug in chzdev!

  Workaround:
  Use chzdev to configure and immediately deconfigure a non-existent FCP LUN 
for the FCP devices that displays the problem.

  Example (ignore any warnings that might show up):

  For FCP device 0x1800:

  chzdev -e -p zfcp-lun 0x1800:0x:0x
  chzdev -d -p zfcp-lun 0x1800:0x:0x

  and for FCP device 0x1900:

  chzdev -e -p zfcp-lun 0x1900:0x:0x
  chzdev -d -p zfcp-lun 0x1900:0x:0x

  Solution available : Patch applied:
  Upstream patch, also applies to s390-tools v1.37.0 and v1.37.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1683808/+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 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu19

---
systemd (229-4ubuntu19) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)

systemd (229-4ubuntu18) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
is going to be started, make sure this blocks network-online.target.
(LP: #1673860)
  * networkd: cherry-pick support for setting bridge port's priority
(LP: #1668347)
  * Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
  * Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
  * resolved: fix null pointer dereference crash (LP: #1621396)
  * Cherrypick core/timer downgrade message about random time addition
(LP: #1692136)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
- CVE-2017-9445
  * Cherry-pick subset of patches to introduce infinity value in logind.conf
for UserTasksMax (LP: #1651518)

 -- Dimitri John Ledkov   Mon, 17 Jul 2017 17:00:42
+0100

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9445

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

Title:
  systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Null-pointer dereference in resolved, results in resolved crash and
  reports on launchpad and errors.

  [Test Case]

   * Unknown steps to reproduce
   * Monitor the drop off in crashes on errors.ubuntu.com:
  https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465

  [Regression Potential]

   * The behavior is similar, instead of crashing resolved it returns an
  error in the relevant function. Whilst this may not result in correct
  dns resolution for the affected dns packets, it should not result in
  resolved crashes.

  [Original Bug Report]

  This is one of background errors that happens without any active app being 
involved.
  For the records, I had open: Firefox, Slack, Franz and the Terminal

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd. This problem was most recently seen with package version 233-6ubuntu2, 
the problem page at 
https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:

  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

[Group.of.nepali.translators] [Bug 1684034] Re: Some Dell and Lenovo systems do not work after BIOS Capsule Update

[Launchpad Bug Tracker]

This bug was fixed in the package fwupdate - 0.5-2ubuntu5

---
fwupdate (0.5-2ubuntu5) xenial; urgency=medium

  [Ivan Hu]
  * Backport new version to Xenial. (LP: #1684034)
  * 4 Patches need to be updated, and modified from
https://github.com/rhboot/fwupdate/
- 0002-fwupdate-fix-memory-leaks-and-storing-update_table-t.patch: fwupdate:
  fix memory leaks and storing update_table to NULL pointer.
  commit 765bb7221af37ac56b11ef2253bf1bb3230ef589
- 0003-fwupdate.efi-use-the-reset-type-from-some-querycapsu.patch: fwupdate.
  efi: use the reset type from some querycapsuleinfo call.
  commit f1cc489783d2054e90fa6bebc3732e7ea8bb3722
- 0004-Add-a-flag-to-Allow-flashing-GUID-s-that-don-t-match.patch: Add a
  flag to Allow flashing GUID's that don't match the ESRT table.
  commit 64b4cd53baa57352fa9b2459e804c4ea50d40299
- 0005-Make-sure-our-BootNext-entry-is-always-in-BootOrder.patch: Make sure
  our BootNext entry is always in BootOrder.
  commit ba48ac4ed7329ae5beb44063dcbd3c424e11fc46

 -- Anthony Wong   Fri, 07 Jul 2017 18:50:54
+0800

** Changed in: fwupdate (Ubuntu Xenial)
   Status: Incomplete => 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/1684034

Title:
  Some Dell and Lenovo systems do not work after BIOS Capsule Update

Status in fwupdate package in Ubuntu:
  Fix Released
Status in fwupdate-signed package in Ubuntu:
  Fix Released
Status in fwupdate source package in Xenial:
  Fix Released
Status in fwupdate-signed source package in Xenial:
  Fix Released
Status in fwupdate source package in Yakkety:
  Won't Fix
Status in fwupdate-signed source package in Yakkety:
  Won't Fix
Status in fwupdate source package in Zesty:
  Fix Released
Status in fwupdate-signed source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found 
on Ubuntu 17.04 with fwupdate 9-1.

  The newer version of capsule flashing tools in Ubuntu 17.04 supports
  the reset type from some querycapsuleinfo call：

  
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722

  [Test Case]

  == fwupdate ==
  On a system with a capsule update available, perform capsule update using 
fwupdate.  Verify the system works properly after the update.

  == efivar ==
  We avoided the upgrade of efivar so we don't need to validate its 
reverse-dependencies.

  [Regression Potential]
  Any vendors that relied upon the previous functionality (hardcoded to warm 
reset rather than querying for reset types) may have problems.  This is 
actually a BIOS
  problem in those situations.

  It's unlikely that this should happen though because querying for
  reset types more closely aligns to the implementations that other OSes
  use when applying capsule updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1684034/+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 1668347] Re: Unable to set bridge_portpriority with networkd

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu19

---
systemd (229-4ubuntu19) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)

systemd (229-4ubuntu18) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
is going to be started, make sure this blocks network-online.target.
(LP: #1673860)
  * networkd: cherry-pick support for setting bridge port's priority
(LP: #1668347)
  * Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
  * Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
  * resolved: fix null pointer dereference crash (LP: #1621396)
  * Cherrypick core/timer downgrade message about random time addition
(LP: #1692136)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
- CVE-2017-9445
  * Cherry-pick subset of patches to introduce infinity value in logind.conf
for UserTasksMax (LP: #1651518)

 -- Dimitri John Ledkov   Mon, 17 Jul 2017 17:00:42
+0100

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9445

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

Title:
  Unable to set bridge_portpriority with networkd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Netplan uses systemd-netword provider to configure all sorts of networking 
settings
   * However, unlike ifupdown, released versions of systemd do not support 
setting bridgeport priority, aka
  `brctl setportprio   `
   * This prevents full migration from ifupdown to netplan/systemd-networkd for 
projects like MAAS that do need to configure equal cost; yet differential 
priority bridge ports.
   * This is proposal to cherrypick this functionality which essentially 
accepts one more key in the .network units; and send those values via netlink.

  [Test Case]

   * networkd-test.py is executed as part of autopkgtests that
  configures a bridge, and sets various valid bridge port priorities and
  verifies from sysfs that those were correctly set by systemd.

   * Alternativey create a bridge .link unit, and specify .network unit
  for a bridge port and use Priority=4 setting in the [Bridge] section
  in the said unit to modify bridge port priority.

  
  [Regression Potential] 

   * This is an upstream cherrypick of functionality that will be
  included in 234 release. However, since MAAS and netplan target stable
  releases, I would like to cherrypick this functionality all the way
  back to xenial. This almost a feature, rather than a bugfix, but it is
  so small and accompanied by regression testsuite that it is almost a
  tiny bugfix.

  [Other Info]
   
   * Original request to support this feature.

  
  1. root@ubuntu:/run/systemd/network# lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04

  2. root@ubuntu:/run/systemd/network# apt-cache policy systemd
  systemd:
    Installed: 232-18ubuntu1
    Candidate: 232-18ubuntu1
    Version table:
   *** 232-18ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  3. Using a networkd config like this:

  # cat 10-netplan-eth1.network
  [Match]
  MACAddress=52:54:00:12:34:02
  Name=eth1

  [Network]
  Bridge=br0
  LinkLocalAddressing=no
  IPv6AcceptRA=no

  [Bridge]
  Cost=50
  Priority=28

  %  cat /sys/class/net/br0/brif/eth1/priority
  28

  4. %  cat /sys/class/net/br0/brif/eth1/priority
  32

  When using ifupdown and /etc/network/interfaces to configure a bridge
  users are able to specify a bridge port priority:

  auto br0
  iface br0 inet static
    address 192.168.1.1
    bridge_ports eth1 eth2
    bridge_portprio eth1 28
    bridge_portprio eth2 14

  Which results in the bridge hook scripts running:

  brctl setportprio br0 eth1 28

  which is visible via:

  /sys/class/net/br0/brif/eth2/priority

  Note, networkd does not mention PortPriority under netdev Bridge section,
  however, PathCost is mentioned.  It appears networkd is missing an 
implementation.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  

[Group.of.nepali.translators] [Bug 1651518] Re: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu19

---
systemd (229-4ubuntu19) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)

systemd (229-4ubuntu18) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
is going to be started, make sure this blocks network-online.target.
(LP: #1673860)
  * networkd: cherry-pick support for setting bridge port's priority
(LP: #1668347)
  * Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
  * Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
  * resolved: fix null pointer dereference crash (LP: #1621396)
  * Cherrypick core/timer downgrade message about random time addition
(LP: #1692136)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
- CVE-2017-9445
  * Cherry-pick subset of patches to introduce infinity value in logind.conf
for UserTasksMax (LP: #1651518)

 -- Dimitri John Ledkov   Mon, 17 Jul 2017 17:00:42
+0100

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9445

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

Title:
  systemd/logind parsing problem: HTX exercisers stopped on error: rc
  11, errno 11 from main(): pthread_create

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  Before systemd 232, UserTasksMax=infinity is not respected in logind.conf, 
despite the documentation referring to systemd.resource-control(5) for the 
definition of this field. This limits the use of Ubuntu 16.04 and later in 
contexts where a user session should be permitted to allocate large numbers of 
processes.

  [Test case]
  1. Set UserTasksMax=infinity in /etc/systemd/logind.conf.
  2. Create a new login session.
  3. Check the ulimit for user processes with 'ulimit -u'.
  4. Verify that the limit has a numeric value.
  5. Upgrade to systemd from -proposed.
  6. Create a new login session.
  7. Check the ulimit for user processes with 'ulimit -u'.
  8. Verify that the limit is now set to 'unlimited'.

  [Regression potential]
  This is an upstream patch which is part of 232 and later without issues and 
clearly addresses the bug in question.  While the upstream commit includes code 
changes that are not strictly required in order to fix this bug, these are 
mostly cosmetic and should not carry significant additional risk.


  == Comment: #1 - Application Cdeadmin  -
  2016-12-19 04:15:10 ==

  Configuration: IBM 8001-22C (S822LC), LSI SAS adapters, SMC 4U90 disk
  drawers, HDD (180) 7.3TB

  Problem: HTX exercisers stopped on error, with HTX log showing "rc 11,
  errno 11 from main(): pthread_create"

  htxubuntu-425

  lpar: busybee.aus.stglabs.ibm.com (root/ lab passwd)

  root@busybee:~# uname -a
  Linux busybee 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:27:59 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@busybee:~# cat /tmp/htxerr

  /dev/sdh  Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdh  Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  No errors logged in syslog after starting HTX:

   State: Open by: asperez on 16 December 2016 10:28:02 
  This error recreated on the 

[Group.of.nepali.translators] [Bug 1692136] Re: Backport "core/timer: downgrade message about random time addition (#5229)".

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu19

---
systemd (229-4ubuntu19) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)

systemd (229-4ubuntu18) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
is going to be started, make sure this blocks network-online.target.
(LP: #1673860)
  * networkd: cherry-pick support for setting bridge port's priority
(LP: #1668347)
  * Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
  * Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
  * resolved: fix null pointer dereference crash (LP: #1621396)
  * Cherrypick core/timer downgrade message about random time addition
(LP: #1692136)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
- CVE-2017-9445
  * Cherry-pick subset of patches to introduce infinity value in logind.conf
for UserTasksMax (LP: #1651518)

 -- Dimitri John Ledkov   Mon, 17 Jul 2017 17:00:42
+0100

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9445

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

Title:
  Backport "core/timer: downgrade message about random time addition
  (#5229)".

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Systemd spams logs too much with pointless messages

  [Test Case]

   * Boot system and observe no pointless messages of scheduling random
  timers for things at a given offset

  [Regression Potential]

   * Low, this patch simply changes the priority of the message from
  info to debug.

  [Original bug report]

  Please backport upstream systemd v233 commit
  382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade
  message about random time addition (#5229)".
  
https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1

  This removes "random time" messages flooding dmesg.

  The spew was introduced with v229 commit "core: add new RandomSec=
  setting for time units".
  
https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07

  trusty based off v204 is not affected.

  xenial based off v229, yakkety based off v231, and zesty based off
  v232 need this fix.

  artful based off v233 has the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1692136/+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 1673860] Re: systemd-resolved unit should run Before=network-online.target

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu19

---
systemd (229-4ubuntu19) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)

systemd (229-4ubuntu18) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
is going to be started, make sure this blocks network-online.target.
(LP: #1673860)
  * networkd: cherry-pick support for setting bridge port's priority
(LP: #1668347)
  * Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
  * Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
  * resolved: fix null pointer dereference crash (LP: #1621396)
  * Cherrypick core/timer downgrade message about random time addition
(LP: #1692136)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
- CVE-2017-9445
  * Cherry-pick subset of patches to introduce infinity value in logind.conf
for UserTasksMax (LP: #1651518)

 -- Dimitri John Ledkov   Mon, 17 Jul 2017 17:00:42
+0100

** Changed in: systemd (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/1673860

Title:
  systemd-resolved unit should run Before=network-online.target

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]

  For releases using systemd-resolved (yakkety and zesty); the unit
  configuration does not require that the service be active before
  allowing systemd to reach 'network-online.target' which is a special
  target used to allow other units which require networking access to
  run.  

  In some cases, units which run After=network-online.target may
  encounter DNS failures if systemd-resolved is not yet completely
  active.

  The fix is to add Before=network-online.target to the Unit directives
  for systemd-resolved.service.

  [Test Case]

  1. lxc launch ubuntu-daily:yakkety y1
  2. lxc exec y1 -- journalctl -o short-precise \
 --unit systemd-resolved --unit network-online.target

  3. Check order of units;  If 'Reached target Network is Online' is
 listed before 'Started Network Name Resolution', then DNS may not
 be up.

  Example FAIL output:

  # apt-cache policy systemd
  systemd:
Installed: 231-9ubuntu3
Candidate: 231-9ubuntu3
Version table:
   *** 231-9ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   231-9git1 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages

  # journalctl -o short-precise -u systemd-resolved -u network-online.target 
  -- Logs begin at Thu 2017-03-23 21:22:42 UTC, end at Thu 2017-03-23 21:22:49 
UTC. --
  Mar 23 21:22:47.173454 y1 systemd[1]: Reached target Network is Online.
  Mar 23 21:22:47.197566 y1 systemd[1]: systemd-resolved.service: Failed to 
reset devices.list: Operation not permitted
  Mar 23 21:22:47.198023 y1 systemd[1]: Starting Network Name Resolution...
  Mar 23 21:22:47.207216 y1 systemd-resolved[438]: Positive Trust Anchors:
  Mar 23 21:22:47.207265 y1 systemd-resolved[438]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde3
  Mar 23 21:22:47.207319 y1 systemd-resolved[438]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-add
  Mar 23 21:22:47.216370 y1 systemd-resolved[438]: Using system hostname 'y1'.
  Mar 23 21:22:47.237441 y1 systemd-resolved[438]: Switching to system DNS 
server 10.245.119.1.
  Mar 23 21:22:47.399614 y1 systemd[1]: Started Network Name Resolution.

  
  Example PASS output:
  # journalctl -o short-precise -u systemd-resolved -u network-online.target 
  -- Logs begin at Thu 2017-03-23 21:25:08 UTC, end at Thu 2017-03-23 21:25:11 
UTC. --
  Mar 23 21:25:10.206276 y1 systemd[1]: systemd-resolved.service: Failed to 
reset devices.list: Operation not permitted
  Mar 23 21:25:10.206685 y1 systemd[1]: Starting Network Name Resolution...
  Mar 23 21:25:10.229430 y1 systemd-resolved[445]: Positive Trust Anchors:
  Mar 23 21:25:10.229449 y1 systemd-resolved[445]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde3
  Mar 23 21:25:10.229491 y1 systemd-resolved[445]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-add
  Mar 23 21:25:10.229759 y1 systemd-resolved[445]: Using system hostname 'y1'.
  Mar 23 21:25:10.231969 

[Group.of.nepali.translators] [Bug 1684034] Re: Some Dell and Lenovo systems do not work after BIOS Capsule Update

[Launchpad Bug Tracker]

This bug was fixed in the package fwupdate-signed - 1.11.1

---
fwupdate-signed (1.11.1) xenial; urgency=medium

  * Build-depend on fwupdate 0.5-2ubuntu5 (LP: #1684034)

 -- Adam Conrad   Thu, 13 Jul 2017 22:18:08 -0600

** Changed in: fwupdate-signed (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/1684034

Title:
  Some Dell and Lenovo systems do not work after BIOS Capsule Update

Status in fwupdate package in Ubuntu:
  Fix Released
Status in fwupdate-signed package in Ubuntu:
  Fix Released
Status in fwupdate source package in Xenial:
  Fix Released
Status in fwupdate-signed source package in Xenial:
  Fix Released
Status in fwupdate source package in Yakkety:
  Won't Fix
Status in fwupdate-signed source package in Yakkety:
  Won't Fix
Status in fwupdate source package in Zesty:
  Fix Released
Status in fwupdate-signed source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found 
on Ubuntu 17.04 with fwupdate 9-1.

  The newer version of capsule flashing tools in Ubuntu 17.04 supports
  the reset type from some querycapsuleinfo call：

  
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722

  [Test Case]

  == fwupdate ==
  On a system with a capsule update available, perform capsule update using 
fwupdate.  Verify the system works properly after the update.

  == efivar ==
  We avoided the upgrade of efivar so we don't need to validate its 
reverse-dependencies.

  [Regression Potential]
  Any vendors that relied upon the previous functionality (hardcoded to warm 
reset rather than querying for reset types) may have problems.  This is 
actually a BIOS
  problem in those situations.

  It's unlikely that this should happen though because querying for
  reset types more closely aligns to the implementations that other OSes
  use when applying capsule updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1684034/+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 1686361] Re: systemd does not respect nofile ulimit when running in container

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu19

---
systemd (229-4ubuntu19) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)

systemd (229-4ubuntu18) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
is going to be started, make sure this blocks network-online.target.
(LP: #1673860)
  * networkd: cherry-pick support for setting bridge port's priority
(LP: #1668347)
  * Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
  * Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
  * resolved: fix null pointer dereference crash (LP: #1621396)
  * Cherrypick core/timer downgrade message about random time addition
(LP: #1692136)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
- CVE-2017-9445
  * Cherry-pick subset of patches to introduce infinity value in logind.conf
for UserTasksMax (LP: #1651518)

 -- Dimitri John Ledkov   Mon, 17 Jul 2017 17:00:42
+0100

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9445

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

Title:
  systemd does not respect nofile ulimit when running in container

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Containers cannot use maximum RLIMIT_NOFILE, because systemd sets
  an arbitrary cap.

  [Test Case]

   * Start container with high RLIMIT_NOFILE (e.g. 100 000)
   * Check that RLIMIT_NOFILE on the container is more than 65536

  [Regression Potential]

   * This is a feature / change of behaviour. Some users may be relying
  on the lower RLIMIT_NOFILE cap, but it should not have a negative
  impact on the host (as in creating too many file descriptors/denial of
  service).

  [Original Bug Report]

  When systemd currently starts in a container that has RLIMIT_NOFILE set to 
e.g.
  10 systemd will lower it to 65536 since this value is hard-coded into 
systemd.
  I've pushed a patch to systemd upstream that will try to set
  the nofile limit to the allowed kernel maximum. If this fails, it will compute
  the minimum of the current set value (the limit that is set on the container)
  and the maximum value as soft limit and the currently set maximum value as the
  maximum value. This way it retains the limit set on the container.
  It would be great if we could backport this patch to have system adhere to
  nofile limits set for the container. This is especially important since user
  namespaces will allow you to lower the limit but not raise it back up 
afterwards.
  The upstream patch is appended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686361/+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 1695546] Re: Out of bounds write in resolved with crafted TCP responses

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu19

---
systemd (229-4ubuntu19) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)

systemd (229-4ubuntu18) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
is going to be started, make sure this blocks network-online.target.
(LP: #1673860)
  * networkd: cherry-pick support for setting bridge port's priority
(LP: #1668347)
  * Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
  * Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
  * resolved: fix null pointer dereference crash (LP: #1621396)
  * Cherrypick core/timer downgrade message about random time addition
(LP: #1692136)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
- CVE-2017-9445
  * Cherry-pick subset of patches to introduce infinity value in logind.conf
for UserTasksMax (LP: #1651518)

 -- Dimitri John Ledkov   Mon, 17 Jul 2017 17:00:42
+0100

** Changed in: systemd (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/1695546

Title:
  Out of bounds write in resolved with crafted TCP responses

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Certain sizes passed to dns_packet_new can cause it to allocate a buffer 
that's too small. A page-aligned number - sizeof(DnsPacket) + sizeof(iphdr) + 
sizeof(udphdr) will do this - so, on x86 this will be a page-aligned number - 
80. Eg, calling dns_packet_new with a size of 4016 will result in an allocation 
of 4096 bytes, but 108 bytes of this are for the DnsPacket struct.

  A malicious DNS server can exploit this by responding with a specially
  crafted TCP payload to trick systemd-resolved in to allocating a
  buffer that's too small, and subsequently write arbitrary data beyond
  the end of it.

  To demonstrate this you can run the attached python script. This is a
  mock DNS server that sends a response where the first two bytes of the
  TCP payload specify a size of 4016 (note, this size is picked to
  trigger an out of bounds write on x86 - you'll probably need to pick a
  different number for x86-64). You'll need to temporarily set your DNS
  server to 127.0.0.1.

  [Testcase]
  Launch the attached script on i386, point resolved at the started dns server, 
execute a dns query via resolved observe that it crashes.
  Upgrade systemd package and observe that resolved no longer crashes.

  [Regression Potential]
  Low, resolved is not used by default in xenial. This is a bug fix to 
resolved, in case somebody does use resolved in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1695546/+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 1686784] Re: no predictable names for platform (non-PCI) NICs

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu19

---
systemd (229-4ubuntu19) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)

systemd (229-4ubuntu18) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
is going to be started, make sure this blocks network-online.target.
(LP: #1673860)
  * networkd: cherry-pick support for setting bridge port's priority
(LP: #1668347)
  * Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
  * Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
  * resolved: fix null pointer dereference crash (LP: #1621396)
  * Cherrypick core/timer downgrade message about random time addition
(LP: #1692136)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
- CVE-2017-9445
  * Cherry-pick subset of patches to introduce infinity value in logind.conf
for UserTasksMax (LP: #1651518)

 -- Dimitri John Ledkov   Mon, 17 Jul 2017 17:00:42
+0100

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9445

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

Title:
  no predictable names for platform (non-PCI) NICs

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Systems may have NICs attached to the "platform" bus. These are NICs that are 
onboard, but not attached to a PCI(-like) bus. Rather, they are described by 
firmware directly. None of the naming policies enabled by Ubuntu by default 
matches these NICs, so they end up having unpredictable names. In the case 
where other NICs are attached (e.g. PCIe cards), the ethN enumeration race 
occurs, making it impossible to have an interface name that is persistent 
across reboots. That is, if you do a network install over "eth0", on reboot 
that NIC now maybe "eth3", which causes it to fail to start the network on boot.

  The HiSilicon D05 boards are an example of this. It has 4 onboard NICs
  that are described by ACPI directly, and may also have other PCIe NICs
  plugged in.

  [Test Case]
  Boot a system with the characteristics described above, and check to see if 
any "ethN" interfaces exist.

  [Regression Risk]
  Unless one fixed the names locally with .netlink / .rules files the interface 
names will change for the ACPI/platform bus network interfaces, from random 
ethX names to stable names named like enaVENDORMODELiX. Thus we should check 
that this update doesn't negatively break certified ARM64 platforms with: ARM, 
NVIDIA, HISILICON platform bus ethernet devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686784/+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 1704280] Re: dm-writeboost 2.1.1-1ubuntu1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2

[Launchpad Bug Tracker]

This bug was fixed in the package dm-writeboost - 2.2.6-1~16.04.1

---
dm-writeboost (2.2.6-1~16.04.1) xenial; urgency=low

  * Backport to xenial to support linux-hwe 4.10 kernels.
(LP: #1704280)

dm-writeboost (2.2.6-1) unstable; urgency=medium

  * New upstream release [September 2016].
+ fixed FTBFS with Linux 4.8 (Closes: #838547).

dm-writeboost (2.2.5-1) unstable; urgency=medium

  * New upstream release [September 2016].

dm-writeboost (2.2.4-1) unstable; urgency=medium

  * New upstream release [August 2016].

dm-writeboost (2.2.3-1) unstable; urgency=medium

  * New upstream release [August 2016].

dm-writeboost (2.2.1-1) unstable; urgency=medium

  * New upstream release [July 2016].
  * Vcs-Git URL to HTTPS.

dm-writeboost (2.2.0-1) unstable; urgency=medium

  * New upstream release [May 2016].
  * Standards-Version: 3.9.8.

dm-writeboost (2.1.2-1) unstable; urgency=medium

  * New upstream release [March 2016].
  * Standards-Version: 3.9.7.

 -- Andy Whitcroft   Fri, 14 Jul 2017 12:07:17 +0100

** Changed in: dm-writeboost (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/1704280

Title:
  dm-writeboost 2.1.1-1ubuntu1 ADT test failure with linux-hwe
  4.10.0-27.30~16.04.2

Status in dm-writeboost package in Ubuntu:
  Invalid
Status in dm-writeboost source package in Xenial:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/d/dm-writeboost/20170710_033146_b2be1@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/d/dm-writeboost/20170710_033525_b2be1@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/d/dm-writeboost/20170710_033208_b2be1@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/d/dm-writeboost/20170710_033322_b2be1@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/d/dm-writeboost/20170710_033100_b2be1@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1704280/+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 1701306] Re: linux-hwe: 4.10.0-27.30~16.04.2 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-hwe - 4.10.0-27.30~16.04.2

---
linux-hwe (4.10.0-27.30~16.04.2) xenial; urgency=low

  * Transition from linux-hwe-edge to linux-hwe:
- linux-hwe: 4.10.0-27.30~16.04.2 -proposed tracker (LP: #1701306)
- bump ABI to avoid binary file clashes with existing linux-hwe-edge
- transition linux-hwe-edge to linux-hwe for the point release
- switch up powerpc TOC. to match the version in yakkety

  * HiSilicon D05: installer doesn't appear on VGA (LP: #1698954)
   - d-i: Add hibmc-drm to kernel-image udeb

  * CVE-2017-1000364
- Revert "UBUNTU: SAUCE: mm: Only expand stack if guard area is hit"
- Revert "mm: do not collapse stack gap into THP"
- Revert "mm: enlarge stack guard gap"
- mm: larger stack guard gap, between vmas
- mm: fix new crash in unmapped_area_topdown()
- Allow stack to grow up to address space limit

 -- Andy Whitcroft   Thu, 29 Jun 2017 16:49:56 +0100

** Changed in: linux-hwe (Ubuntu Xenial)
   Status: Confirmed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000364

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

Title:
  linux-hwe: 4.10.0-27.30~16.04.2 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1701306/+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 1704283] Re: sysdig 0.8.0-1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2

[Launchpad Bug Tracker]

This bug was fixed in the package sysdig - 0.8.0-1ubuntu1

---
sysdig (0.8.0-1ubuntu1) xenial; urgency=medium

  * Fix build issues with 4.10 HWE kernel headers (LP: #1704283)
backports of upstream sysdig commits:
- [39ac26] Fix compilation issues with kernel 4.9 (#684)
- [68823f] Ifdef __access_remote_vm since the function was made
   publicly accessible (#711)
- [bf396c] Support for updated cpu hotplug API in 4.10
   kernel (#744)

 -- Colin Ian King   Mon, 17 Jul 2017 14:57:52
+0100

** Changed in: sysdig (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/1704283

Title:
  sysdig 0.8.0-1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2

Status in sysdig package in Ubuntu:
  In Progress
Status in sysdig source package in Xenial:
  Fix Released

Bug description:
  SRU REQUEST [Xenial]

  [Impact]

  With Xenial HWE 4.10 kernels we see sysdig dkms package build failures
  because we are missing compat fixes for 4.10 with the Xenial sysdig
  dkms modules.

  The fix is a minimal backport of missing compat changes to the driver,
  namely sysdig upstream commits:

  - [39ac26] Fix compilation issues with kernel 4.9 (#684)
  - [68823f] Ifdef __access_remote_vm since the function was made
 publicly accessible (#711)
  - [bf396c] Support for updated cpu hotplug API in 4.10
 kernel (#744)

  [Test Case]

  Install sysdig and sysdig-dkms.  This should build the dkms modules
  correctly without failure.  Next, one should be able to run the
  following command and gather sysdig events without problem:

  sudo sysdig

  [Regression Potential]
  This could possibly break kernel combinations that we have not tested between 
4.8 and 4.10.  I have tested this with 4.4.0-83, 4.8.0-58 and also 4.10.0-26. 
The failure to build will mean that sysdig won't work on kernels we may not 
support.

  ==

  
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/sysdig/20170710_033817_952c5@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/s/sysdig/20170710_033125_952c5@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/sysdig/20170710_033944_952c5@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysdig/+bug/1704283/+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 1704774] Re: xtables-addons 2.10-1ubuntu0.1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2

[Launchpad Bug Tracker]

This bug was fixed in the package xtables-addons - 2.12-0.1~16.04.1

---
xtables-addons (2.12-0.1~16.04.1) xenial; urgency=low

  * Backport to xenial to support linux-hwe 4.10 based kernels.
(LP: #1704774)
  * Revert changes for iptables-dev 1.6.0-3.

xtables-addons (2.12-0.1) unstable; urgency=medium

  * Non-maintainer upload.
  * New upstream release [January 2017]
+ support for Linux 4.9, 4.10 (Closes: #851576)

xtables-addons (2.11-3) unstable; urgency=medium

  * Re-build for auto-iptables transition (Closes: #845516).
  * rules: make build reproducible (Closes: #803601).
Thanks, Reiner Herrmann.

xtables-addons (2.11-2) unstable; urgency=medium

  * Re-build with correction for iptables (>= 1.6.0-3) compatibility
(Closes: #834223).
Thanks Sven Hartge, Sam Morris, Alex Volkov.
  * Depends:
= iptables-dev (>= 1.6.0-3~)

xtables-addons (2.11-1) unstable; urgency=medium

  * New upstream release [May 2016].
  * Standards-Version: 3.9.8.
  * Vcs URLs to HTTPS.
  * Updated gbp.conf.

 -- Andy Whitcroft   Mon, 17 Jul 2017 12:05:16 +0100

** Changed in: xtables-addons (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/1704774

Title:
  xtables-addons 2.10-1ubuntu0.1 ADT test failure with linux-hwe
  4.10.0-27.30~16.04.2

Status in xtables-addons package in Ubuntu:
  Invalid
Status in xtables-addons source package in Xenial:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/x/xtables-addons/20170710_033319_81aa5@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/x/xtables-addons/20170710_033556_81aa5@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/x/xtables-addons/20170710_033230_81aa5@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/x/xtables-addons/20170710_033456_81aa5@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/x/xtables-addons/20170710_033059_81aa5@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1704774/+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 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu19

---
systemd (229-4ubuntu19) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generate warnings in the journal. (LP: #1704677)

systemd (229-4ubuntu18) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
is going to be started, make sure this blocks network-online.target.
(LP: #1673860)
  * networkd: cherry-pick support for setting bridge port's priority
(LP: #1668347)
  * Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
  * Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
  * resolved: fix null pointer dereference crash (LP: #1621396)
  * Cherrypick core/timer downgrade message about random time addition
(LP: #1692136)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
- CVE-2017-9445
  * Cherry-pick subset of patches to introduce infinity value in logind.conf
for UserTasksMax (LP: #1651518)

 -- Dimitri John Ledkov   Mon, 17 Jul 2017 17:00:42
+0100

** Changed in: systemd (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/1704677

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  229-4ubuntu18 included changes irrelevant for xenial, which whilst harmless 
generates a lot of scary journal entries.

  [Fix]
  Drop the cherrypciked ExecStart|StopPost stanzas from the drop in snippet. 
Integration of the resolved stub resolver with resolvconf on xenial is not 
required, because resolved in xenial does not have stub resolver. Also xenial's 
systemd does not support '+' prefix on the Exec* lines.

  [Testcase]
  Upgrade to te new SRU, make sure testcase from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673860 still passes

  Check that there is no extra journal warnings/errors about "Executable
  path is not absolute" from systemd reading /lib/systemd/system
  /systemd-resolved.service.d/resolvconf.con

  [Original Descrption]

  
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a bug. The 
'+' prefix (see 
https://www.freedesktop.org/software/systemd/man/systemd.service.html) in 
ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  ---
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev 

[Group.of.nepali.translators] [Bug 1705137] Re: ACPI platform nics names change after install

[Launchpad Bug Tracker]

This bug was fixed in the package debian-installer -
20101020ubuntu451.13

---
debian-installer (20101020ubuntu451.13) xenial; urgency=medium

  * Rebuild with updated systemd package:
- Use predictable names for non-PCI platform NICs. LP: #1705137

 -- dann frazier   Wed, 19 Jul 2017 09:08:54 -0600

** Changed in: debian-installer (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/1705137

Title:
  ACPI platform nics names change after install

Status in debian-installer package in Ubuntu:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Released

Bug description:
  systemd in xenial-proposed has support for predictable network
  interfaces names for ACPI-described platform devices. However, the
  latest d-i in xenial-proposed was built with the previous systemd
  upload. This has a nasty side-effect that the NICs will have one name
  during install (e.g. eth1) but, after reboot, will have a different
  name (e.g. enahisic1). Further, if you used one of these NICs as your
  install interface, the network will fail to come up post-install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1705137/+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 1671019] Re: PowerNV: Restart opal-prd daemon on any kind of failure

[Launchpad Bug Tracker]

This bug was fixed in the package skiboot - 5.3.3-1ubuntu0.1

---
skiboot (5.3.3-1ubuntu0.1) yakkety; urgency=medium

  * debian/opal-prd.service: set Restart=always, which is the correct policy
for this hardware-related service in the unlikely event of crashes.
LP: #1671019.

 -- Steve Langasek   Sat, 10 Jun 2017
13:06:37 -0700

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

Title:
  PowerNV: Restart opal-prd daemon on any kind of failure

Status in The Ubuntu-power-systems project:
  Fix Released
Status in skiboot package in Ubuntu:
  Fix Released
Status in skiboot source package in Xenial:
  Fix Released
Status in skiboot source package in Yakkety:
  Fix Released
Status in skiboot source package in Zesty:
  Fix Released

Bug description:
  [SRU Justification]
  As a hardware diagnostic service, it's important that opal-prd be kept 
running even in the face of hardware unreliability.  The most effective way to 
do this is with a systemd unit policy of Restart=always, to ensure the service 
is not allowed to accidentally die.

  [Test case]
  1. Install the opal-prd package on a system that has /dev/mtd0.
  2. Verify that the service is running with 'systemctl status opal-prd'.
  3. Get the pid of the opal-prd process from systemctl and kill it with 'sudo 
kill -9 $pid'.
  4. Verify via 'systemctl status opal-prd' that the service is no longer 
running.
  5. Install opal-prd from -proposed.
  6. Verify via 'systemctl status opal-prd' that the service is running again.
  7. Kill the new process with 'sudo kill -9 $pid'.
  8. Verify via 'systemctl status opal-prd' that the service has been restarted.
  9. Install the opal-prd package from -proposed on a system that does not have 
/dev/mtd0.
  10. Verify that 'systemctl status opal-prd' shows the service is inactive, 
and has not been allowed to restart indefinitely after failure, driving up the 
system load.

  [Regression potential]
  Since the package may be installed on systems where opal-prd is useless and 
will not run, it's important to verify for each release that Restart=always 
doesn't cause systemd to go into a busy loop trying to restart the service 
under these conditions.  The uploaded change should guard against this by 
checking for the correct path before starting the job, and the test case should 
further confirm this.

  
  == Comment: #0 - VASANT HEGDE  - 2017-03-08 03:12:33 
==
  ---Problem Description---
  opal-prd package contains prd daemon (Processor Runtime Diagnostics).

  One of the requirements from a field service perspective is to be able
  to restart opal-prd when it fails for whatever reason.

  Direct systemd to restart the opal-prd service on any kind of failure.

  Ubuntu contains opal-prd package.  This bug is to restart daemon after
  failure

  Contact Information = hegdevas...@linux.vnet.ibm.com

  Machine Type = All Open Power Systems

  Userspace tool common name: opal-prd

  Userspace rpm: opal-prd

  The userspace tool has the following bit modes: 64bit

  == Comment: #3 - Ananth Narayan M G  - 2017-03-08 
03:37:46 ==
  Posted patch upstream for this -- 
https://lists.ozlabs.org/pipermail/skiboot/2017-March/006612.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1671019/+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 1693369] Re: 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu Zesty)
   Status: New => In Progress

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  5U84 - ses driver isn't binding right - cannot blink lights on 1 of
  the 2 5u84

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

Bug description:
  This is a request to add the following upstream commit to both Ubuntu
  16.04.1 and 16.04.2:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=9373eba6cfae48911b977d14323032cd5d161aae

  Without this patch, the symlink in sysfs which binds a SAS device to
  an enclosure slot does not get created. This makes disk hotplug near
  impossible on large JBOD disk drawers.

  You should be able to do:

  ls /sys/block/sdb/device/ | grep enclosure

  and see something like:

  enclosure_device:1

  If you cd to this directory, you can then access the SES controls for
  that slot to flash the LED to assist in locating the disk to replace a
  failed disk.

  Currently with 16.04.1 and 16.04.2, these symlinks are not getting
  created.

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

[Brian Murray]

Hello dann, or anyone else affected,

Accepted makedumpfile into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.5.9-5ubuntu0.5 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

** Changed in: makedumpfile (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: makedumpfile (Ubuntu Zesty)
   Status: Confirmed => Fix Released

** Changed in: makedumpfile (Ubuntu Yakkety)
   Status: Confirmed => Won't Fix

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/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 Committed
Status in linux source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Yakkety:
  In Progress
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 Committed
Status in linux source package in Zesty:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released

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.
  -

  

[Group.of.nepali.translators] [Bug 1575222] Re: Translate session action in dash

[Launchpad Bug Tracker]

This bug was fixed in the package session-shortcuts - 1.2ubuntu0.17.04.1

---
session-shortcuts (1.2ubuntu0.17.04.1) zesty; urgency=medium

  * Add X-Ubuntu-Gettext-Domain=session-shortcuts so translations are
loaded (LP: #1575222).

 -- Gunnar Hjalmarsson   Mon, 26 Jun 2017 15:05:00
+0200

** Changed in: session-shortcuts (Ubuntu Zesty)
   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/1575222

Title:
  Translate session action in dash

Status in Ubuntu Translations:
  In Progress
Status in session-shortcuts package in Ubuntu:
  Fix Released
Status in session-shortcuts source package in Xenial:
  Fix Released
Status in session-shortcuts source package in Yakkety:
  Fix Committed
Status in session-shortcuts source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  Session actions (shutdown, reboot, logout) are now available from
  Unity Dash on ubuntu 16.04 but are not translated.

  The proposed upload adds X-Ubuntu-Gettext-Domain=session-shortcuts to
  the .desktop files to make them load the translations.

  To the sponsor: A debdiff for artful has been attached. Please use the
  same for zesty and xenial, while changing the first line in the
  changelog.

  [Test Case]

  Install the updated package, start a non-English session, and find
  that the action names are now localized.

  [Regression Potential]

  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1575222/+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 1588104] Re: Update to bugfix release 3.18.6 in Xenial (fix extensive CPU usage in some cases)

[Launchpad Bug Tracker]

This bug was fixed in the package gpaste - 3.18.6-0ubuntu1

---
gpaste (3.18.6-0ubuntu1) xenial; urgency=medium

  * New upstream release (LP: #1588104)

 -- Jeremy Bicha   Tue, 27 Jun 2017 18:32:07 -0400

** Changed in: gpaste (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/1588104

Title:
  Update to bugfix release 3.18.6 in Xenial (fix extensive CPU usage in
  some cases)

Status in Ubuntu GNOME:
  Fix Released
Status in gpaste package in Ubuntu:
  Fix Released
Status in gpaste source package in Xenial:
  Fix Released

Bug description:
  IMPACT
  ---
  This is a bug-fix release which fixes extensive CPU usages in some cases, 
memory leaks and stability improvements.

  Ubuntu 16.04 LTS "Xenial" currently has gpaste 3.18.3-1.

  https://github.com/Keruspe/GPaste/commits/gpaste-3.18

  https://github.com/Keruspe/GPaste/blob/gpaste-3.18/NEWS

  NEW in 3.18.6 (17/02/2017)
  =

  - fix memory leaks in the debugging logs
  - fix some corner case in images handling
  - stability improvements

  NEW in 3.18.5 (28/06/2016)
  =

  - fix some extensive CPU usage in some cases

  NEW in 3.18.4 (22/05/2016)
  =

  - fix crash when a search goes wrong
  - fix hanging issue due to gtk+ race (?) in gtk_clipboard_store
  - fix the gnome-shell menu sometimes displaying twice
  - add debug logs to the core library

  TEST CASE
  --
  - Install gpaste from xenial-proposed and test it for at least one week to 
avoid any regressions
  - Make sure the CPU usage is fixed
  - Install the gnome-shell extension and see if it works without issues

  REGRESSION POTENTIAL
  -
  Low, as these are only bug fixes, no new features.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1588104/+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 1683808] Re: fail to activate the second DS8K fcp device permanently

[Launchpad Bug Tracker]

This bug was fixed in the package s390-tools - 1.34.0-0ubuntu8.4

---
s390-tools (1.34.0-0ubuntu8.4) xenial; urgency=medium

  * chzdev: Fix ineffective zfcp-lun udev rule preventing activation of
unordered WWPNs. LP: #1683808

 -- Dimitri John Ledkov   Thu, 06 Jul 2017 14:14:51
+0100

** Changed in: s390-tools (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/1683808

Title:
  fail to activate the second DS8K fcp device permanently

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Xenial:
  Fix Released
Status in s390-tools source package in Yakkety:
  Fix Committed
Status in s390-tools source package in Zesty:
  Fix Released
Status in s390-tools source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * out of order devices fail to activate

  [Test Case]

   * See steps to reproduce below

  [Regression Potential]

   * s390-tools rebuild, includes rebuilding the bootloader, thus
  failure to boot should be tested in case of a no-change rebuild
  regression. The fix for the issue in question is a pure ordering
  issue, thus ordering the ids should resolve the issue at hand without
  any other negative side-effects

  [Other Info]
   
   * Original report:

  ---Problem Description---
  Fail to active the second DS8K fcp lun permanently

  Machine Type = z13 lpar

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

  ---Steps to Reproduce---
   1. Map tow fcp luns from DS8880:
     root@ilz62u:~# lsluns
     Scanning for LUNs on adapter 0.0.1800
   at port 0x50050763070057f9:
    0x40004028
    0x40014010
     Scanning for LUNs on adapter 0.0.1900
   at port 0x50050763070b17f9:
    0x40004028
    0x40014010
  2. active the two fcp temporarily
  echo 0x40014010 > 
/sys/bus/ccw/drivers/zfcp/0.0.1800/0x50050763070057f9/unit_add
    echo 0x40014010 > 
/sys/bus/ccw/drivers/zfcp/0.0.1900/0x50050763070b17f9/unit_add

  3. active them via tool "chzdev" permanently
     root@ilz62u:~# lszdev | grep 57f9
  zfcp-lun 0.0.1800:0x50050763070057f9:0x40004028  yes  yes   sdas 
sg44
  zfcp-lun 0.0.1800:0x50050763070057f9:0x40014010  yes  yes   sdau 
sg46

  4. multipath show
  root@ilz62u:~# multipath -ll | grep 2107s
  d2ilsd2107s (36005076307ffd7f90110) dm-15 IBM,2107900
  d1ilsd2107s (36005076307ffd7f90028) dm-14 IBM,2107900

  5. reboot

  6. the secod fcp lun "0x40014010" fail to keep active any more
  root@ilz62u:/sys/bus/ccw/drivers/zfcp/0.0.1800# ls 0x50050763070057f9
  0x40004028  access_denied  failed  in_recovery  power  status  uevent 
 unit_add  unit_remove
  root@ilz62u:/sys/bus/ccw/drivers/zfcp/0.0.1900# ls 0x50050763070b17f9
  0x40004028  access_denied  failed  in_recovery  power  status  uevent 
 unit_add  unit_remove

  root@ilz62u:/sys/bus/ccw/drivers/zfcp/0.0.1900# multipath -ll | grep 2107s
  d1ilsd2107s (36005076307ffd7f90028) dm-14 IBM,2107900

  Stack trace output:
   no

  Oops output:
   no

  System Dump Info:
    The system is not configured to capture a system dump.

  == Comment: #1 - Heinz-Werner Seeck  -
  2017-04-18 03:08:54 ==

  First problem evaluation:
  Could be a chzdev problem. Seeing two jump-labels in the udev rule for port 
0x50050763070b17f9 on fcp device 0x1800 and 0x1900. The first label enables the 
LUN that is working, while the second one with the LUN number that is not 
working is likely ignored.

  Confirmed as a bug in chzdev!

  Workaround:
  Use chzdev to configure and immediately deconfigure a non-existent FCP LUN 
for the FCP devices that displays the problem.

  Example (ignore any warnings that might show up):

  For FCP device 0x1800:

  chzdev -e -p zfcp-lun 0x1800:0x:0x
  chzdev -d -p zfcp-lun 0x1800:0x:0x

  and for FCP device 0x1900:

  chzdev -e -p zfcp-lun 0x1900:0x:0x
  chzdev -d -p zfcp-lun 0x1900:0x:0x

  Solution available : Patch applied:
  Upstream patch, also applies to s390-tools v1.37.0 and v1.37.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1683808/+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 1683808] Re: fail to activate the second DS8K fcp device permanently

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  fail to activate the second DS8K fcp device permanently

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Xenial:
  Fix Released
Status in s390-tools source package in Yakkety:
  Fix Committed
Status in s390-tools source package in Zesty:
  Fix Released
Status in s390-tools source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * out of order devices fail to activate

  [Test Case]

   * See steps to reproduce below

  [Regression Potential]

   * s390-tools rebuild, includes rebuilding the bootloader, thus
  failure to boot should be tested in case of a no-change rebuild
  regression. The fix for the issue in question is a pure ordering
  issue, thus ordering the ids should resolve the issue at hand without
  any other negative side-effects

  [Other Info]
   
   * Original report:

  ---Problem Description---
  Fail to active the second DS8K fcp lun permanently

  Machine Type = z13 lpar

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

  ---Steps to Reproduce---
   1. Map tow fcp luns from DS8880:
     root@ilz62u:~# lsluns
     Scanning for LUNs on adapter 0.0.1800
   at port 0x50050763070057f9:
    0x40004028
    0x40014010
     Scanning for LUNs on adapter 0.0.1900
   at port 0x50050763070b17f9:
    0x40004028
    0x40014010
  2. active the two fcp temporarily
  echo 0x40014010 > 
/sys/bus/ccw/drivers/zfcp/0.0.1800/0x50050763070057f9/unit_add
    echo 0x40014010 > 
/sys/bus/ccw/drivers/zfcp/0.0.1900/0x50050763070b17f9/unit_add

  3. active them via tool "chzdev" permanently
     root@ilz62u:~# lszdev | grep 57f9
  zfcp-lun 0.0.1800:0x50050763070057f9:0x40004028  yes  yes   sdas 
sg44
  zfcp-lun 0.0.1800:0x50050763070057f9:0x40014010  yes  yes   sdau 
sg46

  4. multipath show
  root@ilz62u:~# multipath -ll | grep 2107s
  d2ilsd2107s (36005076307ffd7f90110) dm-15 IBM,2107900
  d1ilsd2107s (36005076307ffd7f90028) dm-14 IBM,2107900

  5. reboot

  6. the secod fcp lun "0x40014010" fail to keep active any more
  root@ilz62u:/sys/bus/ccw/drivers/zfcp/0.0.1800# ls 0x50050763070057f9
  0x40004028  access_denied  failed  in_recovery  power  status  uevent 
 unit_add  unit_remove
  root@ilz62u:/sys/bus/ccw/drivers/zfcp/0.0.1900# ls 0x50050763070b17f9
  0x40004028  access_denied  failed  in_recovery  power  status  uevent 
 unit_add  unit_remove

  root@ilz62u:/sys/bus/ccw/drivers/zfcp/0.0.1900# multipath -ll | grep 2107s
  d1ilsd2107s (36005076307ffd7f90028) dm-14 IBM,2107900

  Stack trace output:
   no

  Oops output:
   no

  System Dump Info:
    The system is not configured to capture a system dump.

  == Comment: #1 - Heinz-Werner Seeck  -
  2017-04-18 03:08:54 ==

  First problem evaluation:
  Could be a chzdev problem. Seeing two jump-labels in the udev rule for port 
0x50050763070b17f9 on fcp device 0x1800 and 0x1900. The first label enables the 
LUN that is working, while the second one with the LUN number that is not 
working is likely ignored.

  Confirmed as a bug in chzdev!

  Workaround:
  Use chzdev to configure and immediately deconfigure a non-existent FCP LUN 
for the FCP devices that displays the problem.

  Example (ignore any warnings that might show up):

  For FCP device 0x1800:

  chzdev -e -p zfcp-lun 0x1800:0x:0x
  chzdev -d -p zfcp-lun 0x1800:0x:0x

  and for FCP device 0x1900:

  chzdev -e -p zfcp-lun 0x1900:0x:0x
  chzdev -d -p zfcp-lun 0x1900:0x:0x

  Solution available : Patch applied:
  Upstream patch, also applies to s390-tools v1.37.0 and v1.37.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1683808/+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 1699005] Re: Update to 1.13

[Launchpad Bug Tracker]

This bug was fixed in the package snapd-glib - 1.13-0ubuntu0.17.04.1

---
snapd-glib (1.13-0ubuntu0.17.04.1) zesty; urgency=medium

  * New upstream release: (LP: #1699005)
- New API:
  - snapd_client_install2_async
  - snapd_client_install2_finish
  - snapd_client_install2_sync
  - snapd_snap_get_contact
  - snapd_system_information_get_binaries_directory
  - snapd_system_information_get_kernel_version
  - snapd_system_information_get_mount_directory
- Deprecated API:
  - snapd_client_install_async
  - snapd_client_install_finish
  - snapd_client_install_sync
- Fix calls not working inside threads.
- Fix reference counting error when calling snapd_client_get_interfaces and
  snapd_client_create_user.
  * debian/control:
- Set minimum dependency versions
- Update Vcs-Bzr
  * debian/libsnapd-glib1.symbols:
  * debian/libsnapd-qt1.symbols:
- Updated

 -- Robert Ancell   Tue, 20 Jun 2017
15:42:33 +1200

** Changed in: snapd-glib (Ubuntu Zesty)
   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/1699005

Title:
  Update to 1.13

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Xenial:
  Fix Committed
Status in snapd-glib source package in Yakkety:
  Won't Fix
Status in snapd-glib source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Older versions of Ubuntu are running older versions of snapd-glib. There have 
since been bug fixes and support for newer API that was added to snapd since 
release.

  [Test Case]
  1. Delete existing Snap credentials by deleting keys 
com.ubuntu.UbuntuOne.GnomeSoftware in Seahorse.
  2. Start GNOME Software
  3. Install a snap (e.g. moon-buggy)

  Expected result:
  User is prompted for Ubuntu credentials and is able to install snap.

  Observed result:
  Works as expected (i.e. only looking for regressions).

  [Regression Potential]
  There is a risk of breaking existing use cases. This is reduced by the 
regression tests in the package and the newer versions of snapd-glib working in 
newer releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1699005/+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 1575222] Re: Translate session action in dash

[Launchpad Bug Tracker]

This bug was fixed in the package session-shortcuts - 1.2ubuntu0.16.04.1

---
session-shortcuts (1.2ubuntu0.16.04.1) xenial; urgency=medium

  * Add X-Ubuntu-Gettext-Domain=session-shortcuts so translations are
loaded (LP: #1575222).

 -- Gunnar Hjalmarsson   Mon, 26 Jun 2017 15:05:00
+0200

** Changed in: session-shortcuts (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/1575222

Title:
  Translate session action in dash

Status in Ubuntu Translations:
  In Progress
Status in session-shortcuts package in Ubuntu:
  Fix Released
Status in session-shortcuts source package in Xenial:
  Fix Released
Status in session-shortcuts source package in Yakkety:
  Fix Committed
Status in session-shortcuts source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  Session actions (shutdown, reboot, logout) are now available from
  Unity Dash on ubuntu 16.04 but are not translated.

  The proposed upload adds X-Ubuntu-Gettext-Domain=session-shortcuts to
  the .desktop files to make them load the translations.

  To the sponsor: A debdiff for artful has been attached. Please use the
  same for zesty and xenial, while changing the first line in the
  changelog.

  [Test Case]

  Install the updated package, start a non-English session, and find
  that the action names are now localized.

  [Regression Potential]

  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1575222/+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 1683808] Re: fail to activate the second DS8K fcp device permanently

[Launchpad Bug Tracker]

This bug was fixed in the package s390-tools - 1.37.0-0ubuntu3.1

---
s390-tools (1.37.0-0ubuntu3.1) zesty; urgency=medium

  * chzdev: Fix ineffective zfcp-lun udev rule preventing activation of
unordered WWPNs. LP: #1683808

 -- Dimitri John Ledkov   Thu, 06 Jul 2017 14:08:32
+0100

** Changed in: s390-tools (Ubuntu Zesty)
   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/1683808

Title:
  fail to activate the second DS8K fcp device permanently

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Xenial:
  Fix Released
Status in s390-tools source package in Yakkety:
  Fix Committed
Status in s390-tools source package in Zesty:
  Fix Released
Status in s390-tools source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * out of order devices fail to activate

  [Test Case]

   * See steps to reproduce below

  [Regression Potential]

   * s390-tools rebuild, includes rebuilding the bootloader, thus
  failure to boot should be tested in case of a no-change rebuild
  regression. The fix for the issue in question is a pure ordering
  issue, thus ordering the ids should resolve the issue at hand without
  any other negative side-effects

  [Other Info]
   
   * Original report:

  ---Problem Description---
  Fail to active the second DS8K fcp lun permanently

  Machine Type = z13 lpar

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

  ---Steps to Reproduce---
   1. Map tow fcp luns from DS8880:
     root@ilz62u:~# lsluns
     Scanning for LUNs on adapter 0.0.1800
   at port 0x50050763070057f9:
    0x40004028
    0x40014010
     Scanning for LUNs on adapter 0.0.1900
   at port 0x50050763070b17f9:
    0x40004028
    0x40014010
  2. active the two fcp temporarily
  echo 0x40014010 > 
/sys/bus/ccw/drivers/zfcp/0.0.1800/0x50050763070057f9/unit_add
    echo 0x40014010 > 
/sys/bus/ccw/drivers/zfcp/0.0.1900/0x50050763070b17f9/unit_add

  3. active them via tool "chzdev" permanently
     root@ilz62u:~# lszdev | grep 57f9
  zfcp-lun 0.0.1800:0x50050763070057f9:0x40004028  yes  yes   sdas 
sg44
  zfcp-lun 0.0.1800:0x50050763070057f9:0x40014010  yes  yes   sdau 
sg46

  4. multipath show
  root@ilz62u:~# multipath -ll | grep 2107s
  d2ilsd2107s (36005076307ffd7f90110) dm-15 IBM,2107900
  d1ilsd2107s (36005076307ffd7f90028) dm-14 IBM,2107900

  5. reboot

  6. the secod fcp lun "0x40014010" fail to keep active any more
  root@ilz62u:/sys/bus/ccw/drivers/zfcp/0.0.1800# ls 0x50050763070057f9
  0x40004028  access_denied  failed  in_recovery  power  status  uevent 
 unit_add  unit_remove
  root@ilz62u:/sys/bus/ccw/drivers/zfcp/0.0.1900# ls 0x50050763070b17f9
  0x40004028  access_denied  failed  in_recovery  power  status  uevent 
 unit_add  unit_remove

  root@ilz62u:/sys/bus/ccw/drivers/zfcp/0.0.1900# multipath -ll | grep 2107s
  d1ilsd2107s (36005076307ffd7f90028) dm-14 IBM,2107900

  Stack trace output:
   no

  Oops output:
   no

  System Dump Info:
    The system is not configured to capture a system dump.

  == Comment: #1 - Heinz-Werner Seeck  -
  2017-04-18 03:08:54 ==

  First problem evaluation:
  Could be a chzdev problem. Seeing two jump-labels in the udev rule for port 
0x50050763070b17f9 on fcp device 0x1800 and 0x1900. The first label enables the 
LUN that is working, while the second one with the LUN number that is not 
working is likely ignored.

  Confirmed as a bug in chzdev!

  Workaround:
  Use chzdev to configure and immediately deconfigure a non-existent FCP LUN 
for the FCP devices that displays the problem.

  Example (ignore any warnings that might show up):

  For FCP device 0x1800:

  chzdev -e -p zfcp-lun 0x1800:0x:0x
  chzdev -d -p zfcp-lun 0x1800:0x:0x

  and for FCP device 0x1900:

  chzdev -e -p zfcp-lun 0x1900:0x:0x
  chzdev -d -p zfcp-lun 0x1900:0x:0x

  Solution available : Patch applied:
  Upstream patch, also applies to s390-tools v1.37.0 and v1.37.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1683808/+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 1596835] Re: libnvpair.so.1 should be in /lib/, not /usr/lib/

[Colin Ian King]

This is indeed fixed in 17.04 Zesty onwards.  I'll SRU this sometime in
the future for earlier releases

** Changed in: zfs-linux (Ubuntu Zesty)
   Status: New => Fix Released

** Changed in: zfs-linux (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: zfs-linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Artful)
   Status: New => Fix Committed

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

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

Title:
  libnvpair.so.1 should be in /lib/, not /usr/lib/

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

Bug description:
  Currently, in Ubuntu 16.04, the package libnvpair1linux puts
  libnvpair.so.1 in /usr/lib/, however, tools like zpool and zfs which
  are installed in /sbin/ need this library. According to the FHS this
  means the required libraries should be in /lib/ in order to allow the
  user to install /usr/ on a separate partition that is not immediately
  available after boot.

  This turns out to be a problem indeed. On one of my systems I had
  /usr/ on a ZFS filesystem (and /, /lib/, /sbin/, /bin/ on a separate
  ext4 partition). However, the system failed to boot: it hung while
  mounting the ZFS partitions which failed because zpool import didn't
  work as it couldn't find libnvpair.so.1.

  $ apt-cache policy libnvpair1linux 
  libnvpair1linux:
Installed: 0.6.5.6-0ubuntu9
Candidate: 0.6.5.6-0ubuntu9
Version table:
   *** 0.6.5.6-0ubuntu9 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu9
Candidate: 0.6.5.6-0ubuntu9
Version table:
   *** 0.6.5.6-0ubuntu9 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1596835/+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 1704968] Re: linux-gcp: -proposed tracker

[Stefan Bader]

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: linux-gcp (Ubuntu Xenial)
   Status: Confirmed => Invalid

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

Title:
  linux-gcp:  -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1704967

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

[Brad Figg]

** Changed in: kernel-sru-workflow/regression-testing
   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/1704982

Title:
  linux: 4.4.0-87.110 -proposed tracker

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

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

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

  backports: 1704985
  derivatives: 1704987,1704989,1704990,1704991
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1704982/+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 1705448] Re: Update google compute-image-packages to 20170718

[Launchpad Bug Tracker]

This bug was fixed in the package gce-compute-image-packages -
20170718-0ubuntu1

---
gce-compute-image-packages (20170718-0ubuntu1) artful; urgency=medium

  * Update debian/copyright
  * New upstream version 20170718 (LP: #1705448)

 -- Balint Reczey   Thu, 20 Jul 2017 14:28:58 +0200

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

Title:
  Update google compute-image-packages to 20170718

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  New
Status in gce-compute-image-packages source package in Xenial:
  New
Status in gce-compute-image-packages source package in Yakkety:
  New
Status in gce-compute-image-packages source package in Zesty:
  New

Bug description:
  [Impact]

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

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

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

  [Test Case]

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

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

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

  [Other Information]

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1705448/+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 1704982] Re: linux: 4.4.0-87.110 -proposed tracker

[Kleber Sacilotto de Souza]

HW-certification tests completed this cycle with for xenial with 
linux-image-4.4.0-84-generic==4.4.0-84.107:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-84.107/xenial-proposed.html

** Changed in: kernel-sru-workflow/certification-testing
   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/1704982

Title:
  linux: 4.4.0-87.110 -proposed tracker

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

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

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

  backports: 1704985
  derivatives: 1704987,1704989,1704990,1704991
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1704982/+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 1557751] Re: makedumpfile generates kernel version error

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1557751

Title:
  makedumpfile generates kernel version error

Status in The Ubuntu-power-systems project:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #7 - Vaishnavi Bhat  - 2016-03-15 06:16:53 ==
  The following warning is generated by makedumpfile 
  * running makedumpfile --dump-dmesg /proc/vmcore 
/mnt/201602030129/dmesg.201602030129
  The kernel version is not supported.
  The created dumpfile may be incomplete.

  The makedumpfile version on your machine is 
  # makedumpfile -v
  makedumpfile: version 1.5.5 (released on 18 Dec 2013)

  I did a #sudo apt-get source makedumpfile and checked for the sources. 
  In the makedumpfile.h ,  the LATEST_VERSION is set to
  #define OLDEST_VERSION  KERNEL_VERSION(2, 6, 15)/* linux-2.6.15 */
  #define LATEST_VERSION  KERNEL_VERSION(4, 1, 0)/* linux-4.1.0 */
  where as kernel version on the machine is 
  # uname -r
  4.2.0-27-generic

  Hence we see this mismatch and message as "The kernel version is not
  supported."

  We need canonical to change the value of LATEST_VERSION  so that we do
  not see this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1557751/+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 1705493] Re: [4.4][backport] Multiple partitions are not supported on a bcache device

[Joseph Salisbury]

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

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

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

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

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

** Tags added: kernel-da-key

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

Title:
  [4.4][backport] Multiple partitions are not supported on a bcache
  device

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

Bug description:
  Support for adding partitions on bcache devices only landed in 4.10:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b8c0d911ac5285e6be8967713271a51bdc5a936a

  Although it is a small change, it is not backported to any of the
  xenial kernels and it only exists naturally in 4.10.

  ➜ ubuntu-xenial git:(master) git tag 
--contains=b8c0d911ac5285e6be8967713271a51bdc5a936a
  Ubuntu-hwe-4.10.0-13.15_16.04.2
  Ubuntu-hwe-4.10.0-14.16_16.04.1
  Ubuntu-hwe-4.10.0-19.21_16.04.1
  Ubuntu-hwe-4.10.0-20.22_16.04.1
  Ubuntu-hwe-4.10.0-21.23_16.04.1
  Ubuntu-hwe-4.10.0-22.24_16.04.1
  Ubuntu-hwe-4.10.0-25.29_16.04.1
  Ubuntu-hwe-4.10.0-26.30_16.04.1
  Ubuntu-hwe-4.10.0-28.32_16.04.1
  Ubuntu-hwe-edge-4.10.0-9.11_16.04.2
  Ubuntu-lts-4.10.0-10.12_16.04.1
  Ubuntu-lts-4.10.0-11.13_16.04.1
  Ubuntu-lts-4.10.0-12.14_16.04.1
  Ubuntu-lts-4.10.0-13.15_16.04.1
  Ubuntu-lts-4.10.0-7.9_16.04.1
  Ubuntu-lts-4.10.0-8.10_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.2

  This will prevent usage of multiple partitions on the same device
  which is the case when data and journal are collocated.

  Also, the lack of that feature prevents dmcrypt usage as multiple
  partitions are created on a device in this case.

  
  Could that be backported to the 4.4 kernel?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705493/+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 1697501] Re: ksh segfault on job_chksave () after it receive a SIGCHLD (Signal 17)

[Launchpad Bug Tracker]

This bug was fixed in the package ksh - 93u+20120801-2ubuntu0.16.10.1

---
ksh (93u+20120801-2ubuntu0.16.10.1) yakkety; urgency=medium

  * d/p/locking.patch: Fix job locking mechanism to prevent
ksh to segfaults in job_chksave after receiving SIGCHLD. (LP: #1697501)

 -- Eric Desrochers   Tue, 04 Jul 2017
15:08:52 -0400

** Changed in: ksh (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/1697501

Title:
  ksh segfault on  job_chksave () after it receive a SIGCHLD (Signal 17)

Status in ksh package in Ubuntu:
  Fix Released
Status in ksh source package in Trusty:
  Fix Released
Status in ksh source package in Xenial:
  Fix Released
Status in ksh source package in Yakkety:
  Fix Released
Status in ksh source package in Zesty:
  Fix Released
Status in ksh source package in Artful:
  Fix Released
Status in ksh package in Debian:
  New

Bug description:
  [Impact]

   * The compiler optimization dropped parts from the ksh job
  locking mechanism from the binary code. As a consequence, ksh could terminate
  unexpectedly with a segmentation fault after it received the SIGCHLD signal.

  [Test Case]

   Unfortunately, there is no clear and easy way to reproduce the
  segfault.

   * But the original reporter of this bug can randomly reproduce the
  problem using an in-house ksh script that only works inside his
  infrastructure as follow : "ksh " and then once
  in a while ksh will segfault as follow :

  (gdb) bt
  #0  job_chksave (pid=pid@entry=19003) at 
/build/ksh-6IEHIC/ksh-93u+20120801/src/cmd/ksh93/sh/jobs.c:1948
  #1  0x004282ab in job_reap (sig=17) at 
/build/ksh-6IEHIC/ksh-93u+20120801/src/cmd/ksh93/sh/jobs.c:428
  #2  
  ...

  [Regression Potential]

  * Regression risk : low/none expected, the package has been
  highly/intensively tested by a user who run over 18M ksh scripts a day
  on each of their clusters.

  +

  * Secondly, I doubt ksh has much traction nowadays, so if a regression 
occurs... It will most likely be limited to a small amount of users IMHO.
  For instance, the bug has been reported 3 years ago for Red Hat, and we, 
Ubuntu, only heard about this same situation for the first time a few weeks ago.

  +

  * The fix has been written by RH and has been proven to work for them
  for the last 3 years.

  Note that the RH fix has never been merged upstream (ksh is a
  unmaintained project) and/or possibly never been proposed to upstream
  (to be verified).

  +

  * A test package including the RH fix has been intensively tested and 
verified (pre-SRU) by an affected user with positive feedbacks using a
  reproducer that segfault without the RH patch.

  +

  * Test package (pre-SRU) feedbacks :
  https://bugs.launchpad.net/ubuntu/xenial/+source/ksh/+bug/1697501/comments/7

  [Other Info]

   * ksh project is unmaintained nowadays [https://github.com/att/ast],
  thus no new development is made upstream nor in debian upstream.

   * Details about the RH bug :
  --
     - https://bugzilla.redhat.com/show_bug.cgi?id=1123467
     - https://bugzilla.redhat.com/show_bug.cgi?id=1112306
     - https://access.redhat.com/solutions/1253243
     - http://rhn.redhat.com/errata/RHBA-2014-1015.html

    # ksh.spec
    Fri Jul 25 2014 Michal Hlavinka  - 20120801-10.8
  - job locking mechanism did not survive compiler optimization (#1123467)

    # patch
  - ksh-20120801-locking.patch
  --

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

  [Original Description]

  # gdb
  [New LWP 3882]
  Core was generated by `/bin/ksh .ksh'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0 job_chksave (pid=pid@entry=19385) at 
/build/ksh-6IEHIC/ksh-93u+20120801/src/cmd/ksh93/sh/jobs.c:1948
  1948 if(jp->pid==pid)

  (gdb) p *jp
  Cannot access memory at address 0xb

  (gdb) p *jp->pid
  Cannot access memory at address 0x13

  (gdb) p pid
  $2 = 19385

  (gdb) p *jpold
  $1 = {next = 0xb, pid = -604008960, exitval = 11124}

  The struct is corrupted at some point looking at the next,pid and
  exitval struct members values which isn't valid data.

  # assembly code
  => 0x00427159 <+41>: cmp %edi,0x8(%rdx)

  (gdb) p $edi  ## pid variable
  $1 = 19385

  (gdb) p *($rdx + 8) ## jp->pid struct
  Cannot access memory at address 0x13
  --

  ksh is segfaulting because it can't access struct "jp" ($rdx) thus
  cannot de-reference the struct member "jp>pid" ($rdx + 8) at line :
  src/cmd/ksh93/sh/jobs.c:1948 when looking if jp->pid is equal to pid
  ($edi) variable.

  I have looked at the github project "att/ast" upstream repo and some
  patches here and there, and nothing seems to apply.

  Note that the project seems unmaintained nowadays.

To manage notifications about 

[Group.of.nepali.translators] [Bug 1697501] Re: ksh segfault on job_chksave () after it receive a SIGCHLD (Signal 17)

[Launchpad Bug Tracker]

This bug was fixed in the package ksh - 93u+20120801-2ubuntu1

---
ksh (93u+20120801-2ubuntu1) zesty; urgency=medium

  * d/p/locking.patch: Fix job locking mechanism to prevent
ksh to segfaults in job_chksave after receiving SIGCHLD. (LP: #1697501)

 -- Eric Desrochers   Tue, 04 Jul 2017
15:08:52 -0400

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

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

Title:
  ksh segfault on  job_chksave () after it receive a SIGCHLD (Signal 17)

Status in ksh package in Ubuntu:
  Fix Released
Status in ksh source package in Trusty:
  Fix Released
Status in ksh source package in Xenial:
  Fix Released
Status in ksh source package in Yakkety:
  Fix Released
Status in ksh source package in Zesty:
  Fix Released
Status in ksh source package in Artful:
  Fix Released
Status in ksh package in Debian:
  New

Bug description:
  [Impact]

   * The compiler optimization dropped parts from the ksh job
  locking mechanism from the binary code. As a consequence, ksh could terminate
  unexpectedly with a segmentation fault after it received the SIGCHLD signal.

  [Test Case]

   Unfortunately, there is no clear and easy way to reproduce the
  segfault.

   * But the original reporter of this bug can randomly reproduce the
  problem using an in-house ksh script that only works inside his
  infrastructure as follow : "ksh " and then once
  in a while ksh will segfault as follow :

  (gdb) bt
  #0  job_chksave (pid=pid@entry=19003) at 
/build/ksh-6IEHIC/ksh-93u+20120801/src/cmd/ksh93/sh/jobs.c:1948
  #1  0x004282ab in job_reap (sig=17) at 
/build/ksh-6IEHIC/ksh-93u+20120801/src/cmd/ksh93/sh/jobs.c:428
  #2  
  ...

  [Regression Potential]

  * Regression risk : low/none expected, the package has been
  highly/intensively tested by a user who run over 18M ksh scripts a day
  on each of their clusters.

  +

  * Secondly, I doubt ksh has much traction nowadays, so if a regression 
occurs... It will most likely be limited to a small amount of users IMHO.
  For instance, the bug has been reported 3 years ago for Red Hat, and we, 
Ubuntu, only heard about this same situation for the first time a few weeks ago.

  +

  * The fix has been written by RH and has been proven to work for them
  for the last 3 years.

  Note that the RH fix has never been merged upstream (ksh is a
  unmaintained project) and/or possibly never been proposed to upstream
  (to be verified).

  +

  * A test package including the RH fix has been intensively tested and 
verified (pre-SRU) by an affected user with positive feedbacks using a
  reproducer that segfault without the RH patch.

  +

  * Test package (pre-SRU) feedbacks :
  https://bugs.launchpad.net/ubuntu/xenial/+source/ksh/+bug/1697501/comments/7

  [Other Info]

   * ksh project is unmaintained nowadays [https://github.com/att/ast],
  thus no new development is made upstream nor in debian upstream.

   * Details about the RH bug :
  --
     - https://bugzilla.redhat.com/show_bug.cgi?id=1123467
     - https://bugzilla.redhat.com/show_bug.cgi?id=1112306
     - https://access.redhat.com/solutions/1253243
     - http://rhn.redhat.com/errata/RHBA-2014-1015.html

    # ksh.spec
    Fri Jul 25 2014 Michal Hlavinka  - 20120801-10.8
  - job locking mechanism did not survive compiler optimization (#1123467)

    # patch
  - ksh-20120801-locking.patch
  --

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

  [Original Description]

  # gdb
  [New LWP 3882]
  Core was generated by `/bin/ksh .ksh'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0 job_chksave (pid=pid@entry=19385) at 
/build/ksh-6IEHIC/ksh-93u+20120801/src/cmd/ksh93/sh/jobs.c:1948
  1948 if(jp->pid==pid)

  (gdb) p *jp
  Cannot access memory at address 0xb

  (gdb) p *jp->pid
  Cannot access memory at address 0x13

  (gdb) p pid
  $2 = 19385

  (gdb) p *jpold
  $1 = {next = 0xb, pid = -604008960, exitval = 11124}

  The struct is corrupted at some point looking at the next,pid and
  exitval struct members values which isn't valid data.

  # assembly code
  => 0x00427159 <+41>: cmp %edi,0x8(%rdx)

  (gdb) p $edi  ## pid variable
  $1 = 19385

  (gdb) p *($rdx + 8) ## jp->pid struct
  Cannot access memory at address 0x13
  --

  ksh is segfaulting because it can't access struct "jp" ($rdx) thus
  cannot de-reference the struct member "jp>pid" ($rdx + 8) at line :
  src/cmd/ksh93/sh/jobs.c:1948 when looking if jp->pid is equal to pid
  ($edi) variable.

  I have looked at the github project "att/ast" upstream repo and some
  patches here and there, and nothing seems to apply.

  Note that the 

[Group.of.nepali.translators] [Bug 1704774] Re: xtables-addons 2.10-1ubuntu0.1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2

[Adam Conrad]

Hello Andy, or anyone else affected,

Accepted xtables-addons into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xtables-
addons/2.12-0.1~16.04.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

** Changed in: xtables-addons (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

** Changed in: xtables-addons (Ubuntu)
   Status: New => Invalid

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

Title:
  xtables-addons 2.10-1ubuntu0.1 ADT test failure with linux-hwe
  4.10.0-27.30~16.04.2

Status in xtables-addons package in Ubuntu:
  Invalid
Status in xtables-addons source package in Xenial:
  Fix Committed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/x/xtables-addons/20170710_033319_81aa5@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/x/xtables-addons/20170710_033556_81aa5@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/x/xtables-addons/20170710_033230_81aa5@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/x/xtables-addons/20170710_033456_81aa5@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/x/xtables-addons/20170710_033059_81aa5@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1704774/+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 1704280] Re: dm-writeboost 2.1.1-1ubuntu1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2

[Adam Conrad]

Hello Andy, or anyone else affected,

Accepted dm-writeboost into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/dm-
writeboost/2.2.6-1~16.04.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

** Changed in: dm-writeboost (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

** Changed in: dm-writeboost (Ubuntu)
   Status: New => Invalid

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

Title:
  dm-writeboost 2.1.1-1ubuntu1 ADT test failure with linux-hwe
  4.10.0-27.30~16.04.2

Status in dm-writeboost package in Ubuntu:
  Invalid
Status in dm-writeboost source package in Xenial:
  Fix Committed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/d/dm-writeboost/20170710_033146_b2be1@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/d/dm-writeboost/20170710_033525_b2be1@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/d/dm-writeboost/20170710_033208_b2be1@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/d/dm-writeboost/20170710_033322_b2be1@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/d/dm-writeboost/20170710_033100_b2be1@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1704280/+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 1703532] Re: linux-hwe: 4.10.0-28.32~16.04.2 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-signed
   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/1703532

Title:
  linux-hwe: 4.10.0-28.32~16.04.2 -proposed tracker

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

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

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

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1703532/+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 1703532] Re: linux-hwe: 4.10.0-28.32~16.04.2 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   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/1703532

Title:
  linux-hwe: 4.10.0-28.32~16.04.2 -proposed tracker

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

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

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

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1703532/+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 1703532] Re: linux-hwe: 4.10.0-28.32~16.04.2 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-meta
   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/1703532

Title:
  linux-hwe: 4.10.0-28.32~16.04.2 -proposed tracker

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

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

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

  -- swm properties --
  phase: Uploaded

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

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1705272
  derivatives: 1705273,1705274,1705275,1705276
+ kernel-stable-phase-changed:Thursday, 20. July 2017 10:02 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1705272
  derivatives: 1705273,1705274,1705275,1705276
  kernel-stable-phase-changed:Thursday, 20. July 2017 10:02 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.4.0-88.111 -proposed tracker

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

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

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

  backports: 1705272
  derivatives: 1705273,1705274,1705275,1705276
  kernel-stable-phase-changed:Thursday, 20. July 2017 10:02 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1705270/+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 1703532] Re: linux-hwe: 4.10.0-28.32~16.04.2 -proposed tracker

[Andy Whitcroft]

Respinning this to include the two new CVE-2017-1000364 fixes as this
will be the point release kernel.

** Summary changed:

- linux-hwe: 4.10.0-28.32~16.04.1 -proposed tracker
+ linux-hwe: 4.10.0-28.32~16.04.2 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Juerg Haefliger (juergh) => Andy Whitcroft (apw)

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

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

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000364

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

Title:
  linux-hwe: 4.10.0-28.32~16.04.2 -proposed tracker

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

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

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

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1703532/+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 918896] Re: No data returned from MSSQL server

[Amr Ibrahim]

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

Title:
  No data returned from MSSQL server

Status in pymssql package in Ubuntu:
  Fix Released
Status in pymssql source package in Precise:
  Confirmed
Status in pymssql source package in Trusty:
  Confirmed
Status in pymssql source package in Wily:
  Confirmed
Status in pymssql source package in Xenial:
  Confirmed
Status in pymssql source package in Yakkety:
  Confirmed
Status in pymssql source package in Zesty:
  Confirmed
Status in pymssql source package in Artful:
  Fix Released
Status in pymssql package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Due to an issue with PyMSSQL 1.0.x and the version of FreeTDX in
  the repositories, PyMSSQL no longer returns any information from MSSQL
  database queries.  This means you cannot use fetchone() or fetchall()
  or similar methods to get data back from a database query.

  [Test Case]

   * Install python-pymssql to Ubuntu.
   
   * Inside a 'python' console on the Ubuntu server, use the following python 
code, replacing values accordingly for your MSSQL servers.  The "print" 
function will return 'None' in the current code base.  When fixed, you will get 
either one value, or a tuple, depending on the results (but you will NOT get 
'None'):

  import pymssql
  dbconn = pymssql.connect(host='FQDN_FOR_DBSERVER', user='DBUSER', 
password='DBPASSWORD', database='DBNAME')
  dbcur = dbconn.cursor()
  dbcur.execute('ANY_VALID_SQL_QUERY')
  dbrs = dbcur.fetchone()
  dbcur.close()
  print dbrs


  [Regression Potential]

   * The patch in the debdiffs is from pymssql upstream.  We are on a
  very old pymssql, but this patch was designed to fix the issue.

  
  [Other Info]
   
   * Test builds in 
https://launchpad.net/~teward/+archive/ubuntu/pymssql/+packages; these packages 
in that PPA are used for testing and were used to test the upstream patch.

  
  [Original Description]

  this works great in oneiric, but in precise it silently returns empty results 
from SQL server. The upstream project has relocated and provided a new release, 
I downloaded and built it and the same code I had started returning results.
  http://code.google.com/p/pymssql/downloads/list

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: python-pymssql 1.0.2+dfsg-1build1
  ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
  Uname: Linux 3.2.0-9-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 19 20:24:31 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: pymssql
  UpgradeStatus: Upgraded to precise on 2012-01-16 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pymssql/+bug/918896/+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 1696752] Re: [SRU] MAAS 2.2.0

[Launchpad Bug Tracker]

This bug was fixed in the package maas - 2.2.0+bzr6054-0ubuntu2~16.10.1

---
maas (2.2.0+bzr6054-0ubuntu2~16.10.1) yakkety-proposed; urgency=medium

  * Stable Release Update. New MAAS upstream release 2.2.0 (LP: #1696752)
- Support for Intel Rack Scale Design as a MAAS Pod.
- Support for KVM as a MAAS Pod.
- Support for Hardware Testing.
- Support for Unmanaged Subnets.
- Support for L2 Spaces.
- Support for DHCP Relay.
- Support for FB Wedge 40 & 100 switch discovery and deployment.
- Improve Windows deployment.
- Improved Commissioning environment.
- Improved UX & UI.

 -- Andres Rodriguez   Thu, 08 Jun 2017 19:42:04
-0400

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

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

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

Title:
  [SRU] MAAS 2.2.0

Status in maas package in Ubuntu:
  New
Status in maas source package in Xenial:
  Fix Released
Status in maas source package in Yakkety:
  Fix Released
Status in maas source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This is a new upstream release that addresses various issues present in 2.1 
and introduces various features that improve the robustness, and feature set of 
MAAS.

  MAAS 2.2.0 introduces the following features:

   * Intel Rack Scale Design support (via MAAS Pods).
   * Hardware Testing
   * DHCP Relay support
   * Unmanaged Subnets
   * L2 spaces
   * Improve Windows deployment support.
   * Facebook's wedge 40 & 100 discovery and deployment
   * Various UI & UX improvements
   * More robust commissioning environment

  [Test Case]
  MAAS testing has been done in various cases, partially documented 
https://wiki.ubuntu.com/MAASUpdates. This include:

  1. Manual Fresh installation of MAAS
  2. Manual upgrade from the previous Ubuntu Release.
  3. Automated (CI) testing of MAAS install and operation as per the MAAS' CI.
  4. Automated (CI) testing of MAAS install and operation against other 
Canonical's product (juju, Canonical OpenStack & Kubernetes) provided by the 
Canonical Solutions QA Team.
  5. Manual split region/rack test are performed. This is to ensure that if we 
upgrade a MAAS Region to a newer version, the MAAS rack of the older version 
remains connected and operational.

  All of this includes verifying normal operation, issues fixed, and
  ensuring that Canonical Cloud solutions can inter-operate. MAAS
  releases are also now vetted by the Solutions QA team.

  [Regression Potential]
  Minimal (For MAAS itself). MAAS is fully backwards compatible and handles 
upgrades from previous releases which result in the continuous operation of 
MAAS. Users will continue to use this new version of MAAS as they used it 
before.

  Medium (For not tested set of hardware) - A new version of Curtin has
  been SRU'd, and as such, this could impact the deployment of untested
  hardware Paths. MAAS, in itself, has not changed the way it deploys
  machines, but curtin (the one in charge of network, disk & boot-order)
  has.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1696752/+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 1696752] Re: [SRU] MAAS 2.2.0

[Launchpad Bug Tracker]

This bug was fixed in the package maas - 2.2.0+bzr6054-0ubuntu2~17.04.1

---
maas (2.2.0+bzr6054-0ubuntu2~17.04.1) zesty-proposed; urgency=medium

  * Stable Release Update. New MAAS upstream release 2.2.0 (LP: #1696752)
- Support for Intel Rack Scale Design as a MAAS Pod.
- Support for KVM as a MAAS Pod.
- Support for Hardware Testing.
- Support for Unmanaged Subnets.
- Support for L2 Spaces.
- Support for DHCP Relay.
- Support for FB Wedge 40 & 100 switch discovery and deployment.
- Improve Windows deployment.
- Improved Commissioning environment.
- Improved UX & UI.

 -- Andres Rodriguez   Thu, 08 Jun 2017 19:42:04
-0400

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

Title:
  [SRU] MAAS 2.2.0

Status in maas package in Ubuntu:
  New
Status in maas source package in Xenial:
  Fix Released
Status in maas source package in Yakkety:
  Fix Released
Status in maas source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This is a new upstream release that addresses various issues present in 2.1 
and introduces various features that improve the robustness, and feature set of 
MAAS.

  MAAS 2.2.0 introduces the following features:

   * Intel Rack Scale Design support (via MAAS Pods).
   * Hardware Testing
   * DHCP Relay support
   * Unmanaged Subnets
   * L2 spaces
   * Improve Windows deployment support.
   * Facebook's wedge 40 & 100 discovery and deployment
   * Various UI & UX improvements
   * More robust commissioning environment

  [Test Case]
  MAAS testing has been done in various cases, partially documented 
https://wiki.ubuntu.com/MAASUpdates. This include:

  1. Manual Fresh installation of MAAS
  2. Manual upgrade from the previous Ubuntu Release.
  3. Automated (CI) testing of MAAS install and operation as per the MAAS' CI.
  4. Automated (CI) testing of MAAS install and operation against other 
Canonical's product (juju, Canonical OpenStack & Kubernetes) provided by the 
Canonical Solutions QA Team.
  5. Manual split region/rack test are performed. This is to ensure that if we 
upgrade a MAAS Region to a newer version, the MAAS rack of the older version 
remains connected and operational.

  All of this includes verifying normal operation, issues fixed, and
  ensuring that Canonical Cloud solutions can inter-operate. MAAS
  releases are also now vetted by the Solutions QA team.

  [Regression Potential]
  Minimal (For MAAS itself). MAAS is fully backwards compatible and handles 
upgrades from previous releases which result in the continuous operation of 
MAAS. Users will continue to use this new version of MAAS as they used it 
before.

  Medium (For not tested set of hardware) - A new version of Curtin has
  been SRU'd, and as such, this could impact the deployment of untested
  hardware Paths. MAAS, in itself, has not changed the way it deploys
  machines, but curtin (the one in charge of network, disk & boot-order)
  has.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1696752/+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 1694733] Re: ubuntu/rsi driver has several issues as picked up by static analysis

[Stefan Bader]

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

Title:
  ubuntu/rsi driver has several issues as picked up by static analysis

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  
  ** CID 1438209:  Memory - corruptions  (OVERRUN)
  /ubuntu/rsi/rsi_91x_core.c: 352 in rsi_core_qos_processor()

  
  

  *** CID 1438209:  Memory - corruptions  (OVERRUN)
  /ubuntu/rsi/rsi_91x_core.c: 352 in rsi_core_qos_processor()
  346 
  347   if (status) {
  348   mutex_unlock(>tx_lock);
  349   break;
  350   }
  351 
  >>> CID 1438209:  Memory - corruptions  (OVERRUN)
  >>> Overrunning array "common->tx_stats.total_tx_pkt_send" of 5 4-byte 
elements at element index 5 (byte offset 20) using index "q_num" (which 
evaluates to 5).
  352   common->tx_stats.total_tx_pkt_send[q_num]++;
  353 
  354   tstamp_2 = jiffies;
  355   mutex_unlock(>tx_lock);
  356 
  357   if (tstamp_2 > tstamp_1 + (300 * HZ / 1000))

  ** CID 1438210:  Resource leaks  (RESOURCE_LEAK)
  /ubuntu/rsi/rsi_91x_hci.c: 274 in rsi_deregister_bt()

  
  

  *** CID 1438210:  Resource leaks  (RESOURCE_LEAK)
  /ubuntu/rsi/rsi_91x_hci.c: 274 in rsi_deregister_bt()
  268   cmd_frame->q_no = RSI_BT_MGMT_Q;
  269   cmd_frame->pkt_type = RSI_BT_PKT_TYPE_DEREGISTR;
  270 
  271   skb_put(skb, sizeof(struct rsi_bt_cmd_frame));
  272 
  273   //return rsi_coex_send_pkt(common, skb, RSI_BT_Q);
  >>> CID 1438210:  Resource leaks  (RESOURCE_LEAK)
  >>> Variable "skb" going out of scope leaks the storage it points to.
  274   return common->priv->host_intf_ops->write_pkt(common->priv, 
skb->data, skb->len);
  275 }
  276 EXPORT_SYMBOL_GPL(rsi_deregister_bt);
  277 
  278 int rsi_hci_recv_pkt(struct rsi_common *common, u8 *pkt)
  279 {

  ** CID 1438211:  Resource leaks  (RESOURCE_LEAK)
  /ubuntu/rsi/rsi_91x_hci.c: 249 in rsi_send_rfmode_frame()

  
  

  *** CID 1438211:  Resource leaks  (RESOURCE_LEAK)
  /ubuntu/rsi/rsi_91x_hci.c: 249 in rsi_send_rfmode_frame()
  243   cmd_frame->bt_rf_tx_power_mode = 0;
  244   cmd_frame->bt_rf_tx_power_mode = 0;
  245 
  246   skb_put(skb, sizeof(struct rsi_bt_rfmode_frame));
  247 
  248 //return rsi_coex_send_pkt(common, skb, RSI_BT_Q);
  >>> CID 1438211:  Resource leaks  (RESOURCE_LEAK)
  >>> Variable "skb" going out of scope leaks the storage it points to.
  249   return common->priv->host_intf_ops->write_pkt(common->priv, 
skb->data, skb->len);
  250 }
  251 EXPORT_SYMBOL_GPL(rsi_send_rfmode_frame);
  252 
  253 int rsi_deregister_bt(struct rsi_common *common)
  254 {

  ** CID 1438212:  Null pointer dereferences  (REVERSE_INULL)
  /ubuntu/rsi/rsi_91x_sdio.c: 1388 in rsi_freeze()

  
  

  *** CID 1438212:  Null pointer dereferences  (REVERSE_INULL)
  /ubuntu/rsi/rsi_91x_sdio.c: 1388 in rsi_freeze()
  1382  struct rsi_91x_sdiodev *sdev =
  1383  (struct rsi_91x_sdiodev *)adapter->rsi_dev;
  1384 #endif
  1385 
  1386  ven_rsi_dbg(INFO_ZONE, "SDIO Bus freeze ===>\n");
  1387 
  >>> CID 1438212:  Null pointer dereferences  (REVERSE_INULL)
  >>> Null-checking "adapter" suggests that it may be null, but it has 
already been dereferenced on all paths leading to the check.
  1388  if (!adapter) {
  1389  ven_rsi_dbg(ERR_ZONE, "Device is not ready\n");
  1390  return -ENODEV;
  1391  }
  1392 
  1393  common->suspend_in_prog = true;

  ** CID 1438213:  Control flow issues  (UNREACHABLE)
  /ubuntu/rsi/rsi_91x_usb.c: 497 in rsi_usb_check_queue_status()

  
  

  *** CID 1438213:  Control flow issues  (UNREACHABLE)
  /ubuntu/rsi/rsi_91x_usb.c: 497 in rsi_usb_check_queue_status()
  491   struct rsi_91x_usbdev *dev = (struct rsi_91x_usbdev 
*)adapter->rsi_dev;
  492   int status;
  493   u32 

[Group.of.nepali.translators] [Bug 1697829] Re: Upgrade Redpine WLAN/BT driver to ver. 1.2 (production release)

[Stefan Bader]

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

Title:
  Upgrade Redpine WLAN/BT driver to ver. 1.2 (production release)

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Upgrade the Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel to
  ver. 1.2. This version is supposed to be a production release.

  This is the latest version of the driver provided by Redpine. For now,
  this driver is enabled only on x86, x86_64 architectures. The impact
  is restricted to { SDIO_DEVICE(0x041B, 0x9330) } for SDIO based WiFi-
  BT modules and on USB bus, this driver binds only to RS9113, lets
  upstream kernel driver handle other RSI chipsets.

  Fixes since previous release(see lp: #1694607)

  Other fixes:
  - Redpine vendor driver - Switching to AP mode causes kernel panic (lp: 
#1700941)
  - ubuntu/rsi driver has several issues as picked up by static analysis (lp: 
#1694733)

  1.2 -
   WLAN Supported Features:
   
   1) Station mode
   2) 802.11bgn
   3) Secutiry modes: Open, WEP, WPA, WPA2
   4) AP mode
   5) Bgscan and roaming
   6) Legacy and UAPSD power save
   7) Regulatory support
   8) WoWLAN
   9) Management frame protection
   10) Wi-Fi direct mode

   WLAN Bug Fixes:
   ---
   1) WoWLAN from S5 fails (lp: #1686283)
   2) After wifi-ap is set, system will kernel panic  (lp: #1699753)
   3) Connect to "n" AP will cause system kernel panic (lp: #1699686)
   4) Low throughput observed in some channels for TCP downlink traffic in
   Coex mode.

   WLAN Limitations/Features NOT Supported:
   
   1) For GTK rekey, wakeup trigger send to host.

   BT Supported Features:
   --
   1) BT EDR mode
   2) BT LE mode
   3) BT Coex mode
  * WLAN STA + BT EDR
  * WLAN STA + BT LE
  * WLAN STA + BT EDR + BT LE
  * WLAN AP + BT EDR
  * WLAN AP + BT EDR + BT LE

   BT Limitations/Features NOT Supported:
   
   1) To connect multiple BT slaves, connection should be initiated
   from rsi module.
   2) In coex mode, BT file transfer fails at times with certain mobiles.

  1.2.RC16 -
   WLAN Bug Fixes:
   ---
   1. WoWLAN from S5 fails (lp: #1686283)
   2. After wifi-ap is set, system will kernel panic  (lp: #1699753)
   3. Connect to "n" AP will cause system kernel panic (lp: #1699686)

   WLAN Limitations/Features NOT Supported:
   
   1) For GTK rekey, wakeup trigger send to host.
   2) Low throughput observed for TCP downlink traffic in Coex mode

   BT Limitations/Features NOT Supported:
   
   1) To connect multiple BT slaves, connection should be initiated
   from rsi module.
   2) In coex mode, BT file transfer fails at times with certain mobiles.

  1.2.RC15 -
   WLAN Bug Fixes:
   ---
   1) Coverity scan fixes (lp: #1694733)
   2) Avoid driver reload at S4 resume

   BT Limitations/Features NOT Supported:
   
   1) To connect multiple BT slaves, connection should be initiated
   from rsi module.
   2) In coex mode, BT file transfer fails at times with certain mobiles.

  1.2.RC14 -
   WLAN Bug Fixes:
   ---
   1) Low throughput with 40MHz issue resolved.

   WLAN Limitations/Features NOT Supported:
   
   1) S5 with WoWLAN does not work.
   2) For GTK rekey, wakeup trigger send to host.
   3) Low throughput observed for TCP downlink traffic in Coex mode

   BT Limitations/Features NOT Supported:
   
   1) To connect multiple BT slaves, connection should be initiated
   from rsi module.
   2) In coex mode, BT file transfer fails at times with certain mobiles.

  1.2.RC12 -
   WLAN Bug Fixes:
   ---
   1) WoWLAN stress test cases issue resolved (when all wifi, bt, ble traffics 
run and suspend)

   WLAN Limitations/Features NOT Supported:
   
   1) S5 with WoWLAN does not work.
   2) For GTK rekey, wakeup trigger send to host.
   3) Low throughput observed for TCP downlink traffic in Coex mode

   BT Limitations/Features NOT Supported:
   
   1) To connect multiple BT slaves, connection should be initiated
   from rsi module.
   2) In coex mode, BT file transfer fails at times with certain mobiles.

  1.2.RC11 -
   WLAN New Features:
   --
   1) Module parameter for debug 

[Group.of.nepali.translators] [Bug 1700480] Re: Update snapcraft.yaml

[Stefan Bader]

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

Title:
  Update snapcraft.yaml

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Update the snapcraft.yaml we ship in Xenial to exploit some of the new
  feature present in snapcraft's 3.21.

  Among the improvements:

  1) include the linux-firmware / linux-firmware-snapdragon package in the 
final snap
  2) rename it to pc-kernel / dragonboard-kernel to match the snaps we have in 
the store
  3) dynamic versioning
  4) autogenerated config from debian.$DEBIAN/config/*
  5) generate from the same snap versions for i386, amd64, armhf, arm64, ppc64el
  and s390x (this only for -generic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700480/+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 1700941] Re: Redpine vendor driver - Switching to AP mode causes kernel panic

[Stefan Bader]

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

Title:
  Redpine vendor driver - Switching to AP mode causes kernel panic

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Switching from STA to AP mode on RS9113 Redpine Wifi-BT combo device,
  system reports a kernel panic.

  The Redpine driver (ver. 1.2 RC12) doesn't track the Linux 4.4.69 stable 
release
  which introduced following patches to mac80211 subsystem:
  - mac80211: pass RX aggregation window size to driver
  - mac80211: pass block ack session timeout to to driver
  - mac80211: RX BA support for sta max_rx_aggregation_subframes

  The Redpine driver ver. 1.2RC12 needs to be updated to handle the changes 
introduced
  in the patch:
  - mac80211: pass block ack session timeout to to driver
  (more details here: 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=U
  buntu-4.4.0-82.105=0b2141bd007213cc9c4228786f773a3c35c41c56 and 
https://bugs.launc
  hpad.net/bugs/1692900)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1700941/+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 1702541] Re: Side Button (Display Toggle) fails on Dell AIO systems

[Stefan Bader]

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

Title:
  Side Button (Display Toggle) fails on Dell AIO systems

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Some new Dell AIO systems has a third side button that should support
  Display Toggle, but it fails to work.

  It requires to add a new keycode in dell-wmi.

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