date:20180321

[Group.of.nepali.translators] [Bug 1582181] Re: AArch64: slow cpuinfo due to redundant loop

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package lshw - 02.18-0.1ubuntu6

---
lshw (02.18-0.1ubuntu6) bionic; urgency=medium

  * AArch64: cpuinfo: Remove redundant cpu caps loop (LP: #1582181)
(Merged into EZix upstream commit [20cda772])

 -- Ike Panhc   Wed, 21 Mar 2018 14:42:13 +0800

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

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

Title:
  AArch64: slow cpuinfo due to redundant loop

Status in lshw package in Ubuntu:
  Fix Released
Status in lshw source package in Xenial:
  New
Status in lshw source package in Artful:
  New
Status in lshw source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  lshw takes too long time on parsing /proc/cpuinfo on aarch64 system
  It takes minutes on 96cores and almost 10min on 224cores system.

  [Test Case]
  `time sudo lshw` and it shall be less then 15sec

  [Regression Potential]
  This patch only modifies codes for aarch64. Lowest regression rick on other 
arch and has been tested on aarch64

  [Other Info]
  Patch has been merged into upstream branch.
  https://github.com/lyonel/lshw/commit/20cda77239e8604e798b87a0441e694edb0214d1

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

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

[Group.of.nepali.translators] [Bug 1748247] Re: [CVE] Arbitrary command execution in the removable device notifier

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package plasma-workspace - 4:5.10.5-0ubuntu1.1

---
plasma-workspace (4:5.10.5-0ubuntu1.1) artful-security; urgency=high

  * SECURITY UPDATE: Arbitrary command execution in the removable device
notifier (LP: #1748247):
- fix-CVE-2018-6791.patch
- CVE-2018-6791

 -- Simon Quigley   Fri, 16 Mar 2018 23:02:49 -0500

** Changed in: plasma-workspace (Ubuntu Artful)
   Status: In Progress => Fix Released

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

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

Status in Kubuntu PPA:
  Fix Released
Status in Kubuntu PPA artful series:
  Fix Released
Status in Kubuntu PPA xenial series:
  Fix Released
Status in plasma-workspace package in Ubuntu:
  Fix Released
Status in plasma-workspace source package in Xenial:
  Fix Released
Status in plasma-workspace source package in Artful:
  Fix Released
Status in plasma-workspace source package in Bionic:
  Fix Released

Bug description:
  KDE Project Security Advisory
  =

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1748247/+subscriptions

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

[Group.of.nepali.translators] [Bug 1757481] Re: Only enable APM on disks that advertise it

2018-03-21 Thread dann frazier

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

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

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

Title:
  Only enable APM on disks that advertise it

Status in hdparm package in Ubuntu:
  Fix Released
Status in hdparm source package in Xenial:
  In Progress
Status in hdparm source package in Artful:
  In Progress
Status in hdparm source package in Bionic:
  Fix Released
Status in hdparm package in Debian:
  Unknown

Bug description:
  [Impact]
  hdparm can cause certain systems to occasionally fail to boot. hdparm tries 
to enable APM on every (non-USB/non-firewire) disk in the system without first 
checking if APM is supported. This *should*
  be OK, since hdparm fails gracefully in this case. However, sending APM 
commands to disks that don't support it can have side-effects. I received a 
report that this was causing bus resets on a Cavium Sabre system with the disk 
below that would sometimes escalate to a boot failure.

  [Test Case]
  Boot a system with a non-USB/non-firewire disk that does not support APM and 
verify that there are no kernel messages like:

  SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 40 fe 21 04
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   APM_level = not supported

  
  [Regression Risk]
  This change entered Debian and Ubuntu 1 month ago, and no regressions have 
been reported. One source of regressions might be that configuring APM on a 
disk that claims not to support it did have some positive side-effect that 
would no longer occur.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/1757481/+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 1582181] Re: AArch64: slow cpuinfo due to redundant loop

2018-03-21 Thread dann frazier

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

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

** Also affects: lshw (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Ike Panhc (ikepanhc)
   Status: In Progress

** Description changed:

- lshw on AArch64 hardware is painfully slow.
- This affects both lshw in current Ubuntu releases and vanilla upstream.
- 
- For a 48 core node, cpuinfo parsing added up to 30 seconds (8 lines
- per core in /proc/cpuinfo add up to 384 lines to parse).
- 
- For a 96 core node, parsing took up to 5 minutes (!).
- 
- I think the problem was introduced by [1], and can be summarized as:
- - CPU capabilities should be added only to the current CPU core,
-   and NOT to all previous CPU cores parsed.
- 
- My suggestion is dropping the loop in [1], thus calling the 
- and  only for currentcpu.
- 
- I put together a small patch (basically removing the for loop in question)
- at [2] (or see attachement), which should be applied on top of version
- "02.16-2ubuntu1.3" from Ubuntu Trusty 14.04.
- 
- After applying the patch at [2], parsing for the above system (48 cores)
- takes less than 1 second (instead of 30s), with the exact same results ...
- 
- [1]
- https://github.com/lyonel/lshw/commit/beb89de5a3c10449fe73f1c77b2486d868e5bc9a
- #diff-f4010714738fa4cdd5999499579da2b3R217
- 
- [2] http://paste.ubuntu.com/16456620/
- 
- # lsb_release -rd
- Description:Ubuntu 14.04.4 LTS
- Release:14.04
- 
- BR,
- Alex
- 
  [Impact]
  lshw takes too long time on parsing /proc/cpuinfo on aarch64 system
  It takes minutes on 96cores and almost 10min on 224cores system.
  
  [Test Case]
  `time sudo lshw` and it shall be less then 15sec
  
  [Regression Potential]
  This patch only modifies codes for aarch64. Lowest regression rick on other 
arch and has been tested on aarch64
  
  [Other Info]
  Patch has been merged into upstream branch.
  https://github.com/lyonel/lshw/commit/20cda77239e8604e798b87a0441e694edb0214d1

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

Title:
  AArch64: slow cpuinfo due to redundant loop

Status in lshw package in Ubuntu:
  In Progress
Status in lshw source package in Xenial:
  New
Status in lshw source package in Artful:
  New
Status in lshw source package in Bionic:
  In Progress

Bug description:
  [Impact]
  lshw takes too long time on parsing /proc/cpuinfo on aarch64 system
  It takes minutes on 96cores and almost 10min on 224cores system.

  [Test Case]
  `time sudo lshw` and it shall be less then 15sec

  [Regression Potential]
  This patch only modifies codes for aarch64. Lowest regression rick on other 
arch and has been tested on aarch64

  [Other Info]
  Patch has been merged into upstream branch.
  https://github.com/lyonel/lshw/commit/20cda77239e8604e798b87a0441e694edb0214d1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1582181/+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 1437353] Re: UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit SFI/SFP+

2018-03-21 Thread Steve Langasek

** Changed in: grub2 (Ubuntu Yakkety)
   Status: New => Won't Fix

** Changed in: grub2-signed (Ubuntu Yakkety)
   Status: New => Won't Fix

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

Title:
  UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit
  SFI/SFP+

Status in MAAS:
  Invalid
Status in maas-images:
  Triaged
Status in python-tx-tftp:
  Invalid
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  New
Status in grub2 source package in Trusty:
  New
Status in grub2-signed source package in Trusty:
  New
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in grub2 source package in Yakkety:
  Won't Fix
Status in grub2-signed source package in Yakkety:
  Won't Fix

Bug description:
  [Impact]
  MAAS commissioning may fail when deploying Xenial images or using grubx64.efi 
from Xenial due to hardware particularities of some Intel 82599-based network 
cards. Other network manufacturers may be affected as well. The main failure 
mode appears to be an infinite re-send of some packets because of an unexpected 
response from the network hardware.

  [Test case]
  Attempt to netboot on a system with a "82599ES 10-Gigabit SFI/SFP+" network 
adapter.

  [Regression potential]
  As this affects network in EFI mode; any failure to netboot using EFI should 
be considered a possible regression. Systems may fail to receive data from the 
network boot server and terminate the process with a timeout. Another possible 
failure scenario is to fail to receive complete data over the network, or data 
corruption.

  

  I am using MAAS to commission and install machines. When I attempt to 
commission a machine with a "82599ES 10-Gigabit SFI/SFP+" network adapter the 
following happens:
  1) TFTP Request — bootx64.efi
  2) TFTP Request — /grubx64.efi
  3) Console hangs at grub prompt

  If I go into bios and force the adapter above into legacy mode then the 
machine is able to network boot and run through the commission process.
  1) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-initrd
  2) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-kernel
  3) TFTP Request — ifcpu64.c32
  4) PXE Request — power off
  5) TFTP Request — pxelinux.cfg/01-90-e2-ba-52-23-78
  6) TFTP Request — pxelinux.cfg/71e3f102-bd8b-11e4-b634-3c18a001c80a
  7) TFTP Request — pxelinux.0

  Also, if I disconnect the cable to the adapter above and connect a
  cable to the integrated "I210 Gigabit" adapter which is configured for
  UEFI mode. The machine is able to network boot grubx64.efi and run
  through the commission process.

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

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

___
Mailing list:

[Group.of.nepali.translators] [Bug 1755208] Re: linux: 4.4.0-117.141 -proposed tracker

2018-03-21 Thread Brad Figg

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

Title:
  linux: 4.4.0-117.141 -proposed tracker

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

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

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

  backports: bug 1755209 (linux-lts-xenial), bug 1755210 (linux-aws)
  derivatives: bug 1755212 (linux-euclid), bug 1755213 (linux-raspi2), bug 
1755215 (linux-snapdragon), bug 1755216 (linux-gke), bug 1755217 (linux-aws), 
bug 1755219 (linux-kvm)
  -- 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/1755208/+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 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial

2018-03-21 Thread Łukasz Zemczak

Let me reach out to xnox to see if he's planning another systemd SRU
after the current one migrates into -updates. If yes, maybe we can have
him bundle up this change. If not, we can just release this one fix
then.

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

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

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

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

Title:
  need backport the new scancode of dell-wmi for Microphone mute hotkey
  to xenial

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New
Status in udev source package in Xenial:
  New

Bug description:
  [Impact]
  dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 
0x100150, so need to add a new mapping for it.

  related commit:
  https://github.com/systemd/systemd/pull/5012

  [Test Case]
  1. install the udev package which applied patch.
  2. check if Microphone mute hotkey works.
  3. if it not works, please provide the log of evtest.

  [Regression Potential]
  low regression potential, because it just add one more mapping.

  also affect:
  LP: #1736352
  LP: #1740080
  LP: #1734609

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1738153/+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 1722481] Re: systemd should sync disks, before killing all processes on shutdown

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

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

Title:
  systemd should sync disks, before killing all processes on shutdown

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

Bug description:
  [Impact]

   * systemd-shutdown binary is executed to complete system shutdown. In
  xenial, it calls sync() after killing all processes, and not before
  killing them. This means that processes are racing the SIGKILL/TERM
  timeouts to sync all IO to disk. To mitigate this race condition, and
  make the shutdown process more reliable the sync() should also happen
  before process killing spree starts.

  [Fix]
  Backport upstream commit 
https://github.com/systemd/systemd/commit/2e79d1828a8da9b3af1b052297e3617905ec94f3

  
  [Test Case]

   * Make sure systems still shuts down, including e.g. root on raid.

  [Regression Potential]

   * Shutdowns may appear to be slower due to two sync() calls instead of one
   * However total shutdown time should not be impacted much, as there really 
should not be much additional IO caused by killing all processes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1722481/+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 1734409] Re: systemd-sysctl: exit gracefully on EPERM/EACCESS

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

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

Title:
  systemd-sysctl: exit gracefully on EPERM/EACCESS

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

Bug description:
  [Impact]

   * systemd-sysctl service fails in containers, due to read-only sysfs,
  which is normal.

  [Test Case]

   * Ensure systemd-sysctl is successful in containers, e.g. lxc & lxd

  [Regression Potential]

   * The application of sysctls fails anyway, but at least in this case
  false-errors are not reported and the container doesn't enter
  "degraded" state without a good reason.

  [Other Info]
   
   * Original bug report

  Hi everyone,

  systemd-sysctl in systemd versions prior to 232 will exit with FAILED
  when not being able to apply kernel variables. In containers it should
  simply move on and exit with SUCCESS. Upstream systemd carries
  appropriate patches for this already. The relevant commits are:

  411e869f497c7c7bd0688f1e3500f9043bc56e48
  39540de8abe24886693ca29a9caeea85c88089aa

  these should be backported to xenial's systemd.

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734409/+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 696435] Re: wait-for-root fails to detect nbd root

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

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

Title:
  wait-for-root fails to detect nbd root

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

Bug description:
  [Impact]
  Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.

  [Fix]
  Generate change uevent when size of /dev/nbd0 changes

  [Testcase]
  * Start udevadm monitor
  * modprobe nbd
  * use ndb-client to connect something to /dev/nbd0
  * observe that there are change udev events generated on /dev/nbd0 itself

  [Regression Potential]
  There is no change to existing uevents, or their ordering.
  There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions

  [Original Bug Report]

  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
   while [ -z "${FSTYPE}" ]; do
    FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

    # Run failure hooks, hoping one of them can fix up the system
    # and we can restart the wait loop.  If they all fail, abort
    # and move on to the panic handler and shell.
    if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
     break
    fi
   done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+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 1755213] Re: linux-raspi2: 4.4.0-1086.94 -proposed tracker

2018-03-21 Thread Taihsiang Ho

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.4.0-1086.94/raspi2-4.4-proposed-published.html

** Tags added: certification-testing-passed

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1755208
  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/1755213/+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 1734410] Re: systemd: handle undelegated cgroup2 hierarchy

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

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

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

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

Title:
  systemd: handle undelegated cgroup2 hierarchy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * When a container is presented with a unified cgroup hierarchy,
  which is not properly delegated, systemd should not attempt (and fail)
  to use. This improves compatibility of xenial containers running on
  unified cgroup hierarchy hosts.

  [Test Case]

   * Xenial containers should boot, with non-writable unified cgroup
  hierarchy hosts.

  [Regression Potential]

   * unified cgroup hierarchy is not in use by default on xenial hosts,
  thus this is forward compatibility improvment with e.g. bionic hosts
  running xenial containers.

  [Other Info]
   
   * Original bug report

  Hey everyone,

  Current systemd versions all fail when the unified cgroup hierarchy is
  not-writable. This is especially problematic in containers where the
  systemd administrator might decide to not delegate the unified
  hierarchy or when running with a liblxc driver that doesn't yet know
  how to handle the unified cgroup hierarchy. I've pushed patches to
  systemd upstream that let systemd ingnore the non-delegated unified
  hierarchy. The relevant commits are:

  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0

  These patches will be in 236 but should be backported from xenial
  upwards.

  Christian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734410/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

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

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

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

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with

[Group.of.nepali.translators] [Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

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

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

Title:
  Systemd - Bypassing MemoryDenyWriteExecution policy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * MemoryDenyWritePolicy can be bypassed by using a slightly different
  syscall.

  [Test Case]

   * Check that MemoryDenyWritePolicy, blocks pkey_mprotect as well as
  mprotect.

  [Regression Potential]

   * Upstream fix cherrypick, security vulnerability.

  [Other Info]
   
   * Original report

  Hello,

  We would like to report to you a vulnerability about systemd which
  allows to bypass the MemoryDenyWriteExecution policy on Linux 4.9+.

  The vulnerability is described in the attached PDF file.

  Sincerely,
  Thomas IMBERT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725348/+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 1737570] Re: Add support for RequiredForOnline in networkd

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 234-2ubuntu12.3

---
systemd (234-2ubuntu12.3) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Fix test-functions failing with Ubuntu units. LP: #1750608
  * tests: switch to using ext4 by default, instead of ext3. LP: #1750608
  * Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
  * systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
  * netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
  * resolved.service: set DefaultDependencies=no (LP: #1734167)
  * systemd.postinst: enable persistent journal. (LP: #1618188)
  * core: add support for non-writable unified cgroup hierarchy for container 
support.
Rebase and de-fuzz. (LP: #1734410)
  * Prevent MemoryDenyWriteExecution policy bypass, by disallowing 
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
  * networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)

  [ Kleber Sacilotto de Souza ]
  * systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We 
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)

 -- Dimitri John Ledkov   Tue, 20 Feb 2018 16:11:58
+

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

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

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

Title:
  Add support for RequiredForOnline in networkd

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

Bug description:
  [Impact]

   * netplan & networkd based systems typically await networking to be
  up on boot, without any ability to specify that an interface should be
  configured, but might not be online at boot. This is a backport of the
  RequiredForOnline= feature to match optional=true in netplan.

  [Test Case]

   * Configure a netowkring interface using .link/.network file and specify 
RequiredForOnline=False
   * Bring the interface down / offline it
   * execute systemd-networkd-wait-online, which should exit immediately since 
no interfaces are required to be online

  [Regression Potential]

   * This adds a support for an additional stanza in the network files.
  This stanza is not used by default. if the stanza is used, but older
  networkd is in use, networkd will ignore this unknown stanza. Thus
  this change is backward and forward compatible. The difference is that
  boot is not blocked awaiting systemd-networkd-wait-online to timeout.

  [Other Info]
   
   * Original bug report

  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737570/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

[ Dimitri John Ledkov ]
* udev: Mark ndb devices as inactive until connected. (LP: #696435)
* networkd: in dhcp, change UseMTU default to true, to accept DHCP provided
MTU by default.
(LP: #1717471)
* sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
* networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
* shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
* sysctl: do not fail, when cannot apply sysctl changes due to read-only
sysfs in containers.
(LP: #1734409)
* networkd,wait-online: add RequiredForOnline to mark mandatory/optional
links for boot.
(LP: #1737570)

[ David Glasser ]
* journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

-- Dimitri John Ledkov Wed, 21 Feb 2018 13:46:37
+

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

Title:
Networkd fail to set ip address between leases if ip address changes
on UbuntuCore

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

Bug description:
[Impact]

* networkd fails to renew a lease, specifically it fails to change IPv4
address via DHCP renew/rebind.
* networkd relies on a kernel feature to promote secondary IPv4 address to
primary, upon primary address lease expiry.
* this sysctl tunable was not enabled by default in systemd.

[Test Case]

Add a device, and assign two IPv4 addresses. First one, with a short
lease time. Second one, with a different ip and a longer lease time.
Second one should be treated as secondary ip address, and upon expiry
of the first one, should be promoted and become primary ip address.
The below scripted instructions simulate this:

sudo ip link add name testleases type dummy

sudo ip address add 192.0.2.10/27 dev testleases \
valid_lft 5 preferred_lft 5

sudo ip address add 192.0.2.11/27 dev testleases \
valid_lft 11 preferred_lft 11

ip address list dev testleases | \
grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
&& echo ok || echo not ok

ip address list dev testleases | \
grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
&& echo ok || echo not ok

sleep 6

ip address list dev testleases | \
grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
&& echo ok || echo not ok

sudo ip link del dev testleases

[Regression Potential]

* This changes the default kernel behaviour, previously upon expiry
of the primary address, secondary addresses were removed as well.
Which is imho silly.

* comparing networkd renewal with isc-dhcp renewal the semantics are
quite different. Upon acquiring new ip address, isc-dhcp would
instantly flush existing ip address, and add a new one. Networkd add
the new address as secondary, and waits for old one to expire first
before promoting / switching to using the new ip address. IMHO kernel
should have an API to promote secondary ip address to a primary one.

* This update also applies other safe-looking options, which are
currently also already applied via sysctls shipped in other packages

# Source route verification
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1

# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.all.accept_source_route = 0

# Enable hard and soft link protection
fs.protected_hardlinks = 1
fs.protected_symlinks = 1

* This update also applies the following upstream/bufferbloat.net
recommended setting

# Fair Queue CoDel packet scheduler to fight bufferbloat
net.core.default_qdisc = fq_codel

* [~racb] There are complex network setups out there, such as HA with
corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
fix were SRU'd, will all of these things in the wild cope with this
sysctl change?

[Other Info]

* Original bug report

Hi there,
we found a replicable issue that involves the Ubuntu Core networking and
causes complete loss of connectivity.
We run a custom board with ubuntu core: the architecure is amrhf.
We replicated this issue with an official Ubuntu Core image on a Raspberry
Pi: other platform was been tested.
It shows that it is a snap core problem which interests networkd: we use the
default network stack based on networkd + netplan.

Below steps to replicate the

[Group.of.nepali.translators] [Bug 1717471] Re: networkd does not accept / set advertised mtu

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

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

Title:
  networkd does not accept / set advertised mtu

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in nplan source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Hosts may require a specific MTU to be set as passed by DHCP options. We 
should honor these settings to ensure proper communication of the host with the 
rest of the network.

  [Test case]
  1) Run netplan on a system that should receive MTU settings from DHCP.
  2) Validate that the MTU configuration provided by DHCP is applied to the 
right interface.

  [Regression Potential]
  If DHCP settings specify an invalid MTU setting which is currently being 
ignored and letting the systems communicate correctly with the network, then 
these systems would regress.

  ---

   Right, so as far as I can tell the neutron-api on lcy01 is
  configured to advertise an instance interface MTU of 1400, though
  that's lower than it has to be, and the new DHCP setup with networkd
  just doesn't respect that DHCP option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+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 1718444] Re: systemd-sysctl in Xenial is not obeying the order of the sysctls

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

[ David Glasser ]
* journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

-- Dimitri John Ledkov Wed, 21 Feb 2018 13:46:37
+

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

Title:
systemd-sysctl in Xenial is not obeying the order of the sysctls

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

Bug description:
[Impact]

* sysctls are applied out of order

[Test Case]

* Monitor that sysctls are applied in-order, instead of out of order
/ random order.

[Regression Potential]

* Cherrypick of an upstream patch which is present in v232+ and in
use in Ubuntu in later releases. The code changes are minimal,
updating s/Hashmap/OrderedHashmap/ which is implemented and available
in xenial's systemd.

https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6

[Other Info]

* Original bug report.

systemd-sysctl in Xenial forces itself over procps by shipping a link
for procps.service to systemd-sysctl.service. However, it does not
obey the order both of the files and also of the sysctls within the
files. Instead it uses a simple hashmap. As it turns out that's fixed
upstream and systemd master uses an ordered hashmap because of this,
which at least preserves order within single files. Traditionally
files in sysctl.d have been prefixed with numbers to ensure an order
and that's now completely non-deterministic on Xenial.

Relevant upstream commit:

https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6

Note that conf_files_list_nulstr in master sorts the configuration
files using strcmp, so even order of configuration files should be
obeyed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718444/+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 1737570] Re: Add support for RequiredForOnline in networkd

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 229-4ubuntu21.2

---
systemd (229-4ubuntu21.2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * udev: Mark ndb devices as inactive until connected. (LP: #696435)
  * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided 
MTU by default.
(LP: #1717471)
  * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
  * networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
  * shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
  * sysctl: do not fail, when cannot apply sysctl changes due to read-only 
sysfs in containers.
(LP: #1734409)
  * networkd,wait-online: add RequiredForOnline to mark mandatory/optional 
links for boot.
(LP: #1737570)

  [ David Glasser ]
  * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 13:46:37
+

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

Title:
  Add support for RequiredForOnline in networkd

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

Bug description:
  [Impact]

   * netplan & networkd based systems typically await networking to be
  up on boot, without any ability to specify that an interface should be
  configured, but might not be online at boot. This is a backport of the
  RequiredForOnline= feature to match optional=true in netplan.

  [Test Case]

   * Configure a netowkring interface using .link/.network file and specify 
RequiredForOnline=False
   * Bring the interface down / offline it
   * execute systemd-networkd-wait-online, which should exit immediately since 
no interfaces are required to be online

  [Regression Potential]

   * This adds a support for an additional stanza in the network files.
  This stanza is not used by default. if the stanza is used, but older
  networkd is in use, networkd will ignore this unknown stanza. Thus
  this change is backward and forward compatible. The difference is that
  boot is not blocked awaiting systemd-networkd-wait-online to timeout.

  [Other Info]
   
   * Original bug report

  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737570/+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 1746066] Re: linux-azure-edge: 4.14.0-1004.4 -proposed tracker

2018-03-21 Thread Marcelo Cerri

*** This bug is a duplicate of bug 1755769 ***
https://bugs.launchpad.net/bugs/1755769

** This bug has been marked a duplicate of bug 1755769
   linux-azure-edge: 4.15.0-1003.3 -proposed tracker

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

Title:
  linux-azure-edge: 4.14.0-1004.4 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.14.0-1004.4 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/1746066/+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 1755771] Re: linux-gcp: 4.13.0-1012.16 -proposed tracker

2018-03-21 Thread Taihsiang Ho

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

Title:
  linux-gcp: 4.13.0-1012.16 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1755762
  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/1755771/+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 1734225] Re: Invalid service name defined in /etc/ctdb/events.d/50.samba

2018-03-21 Thread David Britton

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

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

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

Title:
  Invalid service name defined in /etc/ctdb/events.d/50.samba

Status in samba package in Ubuntu:
  Fix Released
Status in samba source package in Trusty:
  Triaged
Status in samba source package in Xenial:
  Triaged

Bug description:
  The CTDB deployed /etc/ctdb/events.d/50.samba script contain the following 
code to detect the smbd/nmbd service name:
  ---
  case $CTDB_INIT_STYLE in
  suse)
  CTDB_SERVICE_SMB=${CTDB_SERVICE_SMB:-smb}
  CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-nmb}
  ;;
  debian)
  CTDB_SERVICE_SMB=${CTDB_SERVICE_SMB:-samba}
  CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-""}
  ;;
  *)
  # Use redhat style as default:
  CTDB_SERVICE_SMB=${CTDB_SERVICE_SMB:-smb}
  CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-""}
  ;;
  esac
  ---

  It detects Ubuntu as Debian (/etc/ctdb/functions) and so define that
  the smb service is named "samba" and the nmb service does not exists.

  That could be OK since Samba deploy an "samba" init script as well as
  smbd and nmbd. Except, this init script does not really work to start
  smbd and nmbd.

  To make CTDB happy, the previous code must be modified:
  --- 50.samba.orig 2017-11-23 23:34:35.146314429 +
  +++ 50.samba  2017-11-23 23:35:08.161814684 +
  @@ -14,8 +14,8 @@
CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-nmb}
;;
debian)
  - CTDB_SERVICE_SMB=${CTDB_SERVICE_SMB:-samba}
  - CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-""}
  + CTDB_SERVICE_SMB=smbd
  + CTDB_SERVICE_NMB=nmbd
;;
*)
# Use redhat style as default:

  
  I reproduced this issue on both Ubuntu 16.04 and 14.04. But it does not 
exists on Debian Stretch (the 50.samba has been updated).

  
  An easier workaround to avoid updating the 50.samba script is to set those 2 
service name in the /etc/default/ctdb:

  CTDB_SERVICE_SMB=smbd
  CTDB_SERVICE_NMB=nmbd

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

2018-03-21 Thread Taihsiang Ho

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/snapdragon/4.4.0-1088.93/snapdragon-4.4-proposed-published.html

** Tags added: certification-testing-passed

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

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

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

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

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

2018-03-21 Thread Taihsiang Ho

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

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

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

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

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

2018-03-21 Thread 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

** Description changed:

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

** Description changed:

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

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

Title:
  linux-azure-edge: 4.15.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-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-azure-edge package in Ubuntu:
  Invalid
Status in linux-azure-edge source package in Xenial:
  Confirmed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755769/+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 1721749] Re: Security Fix - CVE-2017-12617

2018-03-21 Thread Matthias Klose

fixed with 8.5.29-1 in bionic

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

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

** Also affects: tomcat8 (Ubuntu Bionic)
   Importance: Undecided
   Status: Triaged

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

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

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

Title:
  Security Fix - CVE-2017-12617

Status in tomcat8 package in Ubuntu:
  Fix Released
Status in tomcat8 source package in Trusty:
  New
Status in tomcat8 source package in Xenial:
  New
Status in tomcat8 source package in Artful:
  New
Status in tomcat8 source package in Bionic:
  Fix Released

Bug description:
  Tomcat Versions earlier than 7.0.82, 8.0.47, 8.5.23 or 9.0.1 (beta) are 
containing the vulnerability
  http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12617 (Severity: 
Important)

  The tomcat8 package in ubuntu xenial wasn't updated in the last
  month's so I don't think there was a  backport of the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1721749/+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 1756987] Re: chrony install does not stop systemd-timesyncd

2018-03-21 Thread ChristianEhrhardt

The way the newer versions solve this is to have a native systemd
service and in there there is:

Conflicts=systemd-timesyncd.service openntpd.service

That ensures only one of these can be started.

Xenial has no systemd service at all, it has sysV and uses the systemd 
generator.
So there is no "just add the line" fix available.

Xenial as-is
$ timedatectl status
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no
systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
   └─disable-with-time-daemon.conf
   Active: active (running) since Wed 2018-03-21 16:00:19 UTC; 1min 30s ago

This isn't even fully protected if you install ntp (not chrony) as it
was the ntp server back in Xenial. (Right after install it still runs).

What stops it there for NTPd is that this uses a config dir which pulls in:
  /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

So any further starts will be blocked:
# don't run timesyncd if we have another NTP daemon installed
ConditionFileIsExecutable=!/usr/sbin/ntpd
ConditionFileIsExecutable=!/usr/sbin/openntpd
ConditionFileIsExecutable=!/usr/sbin/chronyd
ConditionFileIsExecutable=!/usr/sbin/VBoxService

You see that if you check systemd-timesyncd.service:
$ systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
   └─disable-with-time-daemon.conf
   Active: inactive (dead)
Condition: start condition failed at Wed 2018-03-21 16:06:42 UTC; 44s ago
   ConditionFileIsExecutable=!/usr/sbin/ntpd was not met

After installing Chrony this is the same:

Condition: start condition failed at Wed 2018-03-21 16:11:37 UTC; 1s ago
   ConditionFileIsExecutable=!/usr/sbin/chronyd was not met

That is good (no special issue to chrony) and bad (actually all
timeservers "collide" right after install).

A reboot or restart will pick that up.
OTOH it is discouraged to start/stop/restart other packages services form a 
postinst - as the first thought would be to do refresh for that condition after 
installing any of these.

Given that there was not a single complaint about it in 2 years of
Xenial other than us now looking for it in detail I'd rate it low, but
it is a valid issue.

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

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

** Changed in: ntp (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: ntp (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: chrony (Ubuntu Bionic)
   Importance: Undecided => Low

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

Title:
  chrony install does not stop systemd-timesyncd

Status in chrony package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in chrony source package in Xenial:
  New
Status in ntp source package in Xenial:
  Confirmed
Status in openntpd source package in Xenial:
  New
Status in chrony source package in Artful:
  New
Status in ntp source package in Artful:
  New
Status in openntpd source package in Artful:
  New
Status in chrony source package in Bionic:
  Fix Released
Status in ntp source package in Bionic:
  New
Status in openntpd source package in Bionic:
  New

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  2. 
  root@ubuntu:~# apt-cache policy systemd
  systemd:
Installed: 229-4ubuntu21.1
Candidate: 229-4ubuntu21.1
Version table:
   *** 229-4ubuntu21.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  root@ubuntu:~# apt-cache policy chrony
  chrony:
Installed: 2.1.1-1
Candidate: 2.1.1-1
Version table:
   *** 2.1.1-1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  3. installing chrony should stop systemd-timesyncd so they both don't
  try to adjust time

  4. after chrony is installed both systemd-timesyncd and chronyd are
  running.

  root@ubuntu:~# ps aux | egrep

[Group.of.nepali.translators] [Bug 1688508] Re: libvirt-guests.sh fails to shutdown guests in parallel

2018-03-21 Thread Launchpad Bug Tracker

This bug was fixed in the package libvirt - 4.0.0-1ubuntu6

---
libvirt (4.0.0-1ubuntu6) bionic; urgency=medium

  * Backport from recent upstream to stabilize libvirt (LP: #1756915)
- d/p/stable/0033-qemu-Fix-comparison-assignment-in-qemuDomainUpdateDe.patch
- d/p/stable/0034-qemu-Fix-memory-leak-in-qemuConnectGetAllDomainStats.patch
- d/p/stable/0035-libvirtd-fix-potential-deadlock-when-reloading.patch
- d/p/stable/0036-qemu-Use-correct-bus-type-for-input-devices.patch
- d/p/stable/0037-qemu-hostdev-Fix-the-error-on-VM-start-with-an-mdev-.patch
- d/p/stable/0038-conf-Fix-crash-in-virDomainDefCompatibleDevice.patch
  * d/p/ubuntu/lp1688508-tools-fix-variable-scope-in-in-check_guests_shutdown:
avoid issues shutting down more guests than configured for parallel
shutdown (LP: #1688508)
  * d/p/ubuntu-aa/lp1756394-virt-aa-helper-resolve-file-symlinks.patch: fix
using devices that are symlinks (LP: #1756394)

 -- Christian Ehrhardt   Mon, 19 Mar
2018 14:57:08 +0100

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

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

Title:
  libvirt-guests.sh fails to shutdown guests in parallel

Status in libvirt:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Triaged
Status in libvirt source package in Zesty:
  Won't Fix
Status in libvirt source package in Artful:
  Triaged

Bug description:
  [Environment]

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  [Impact]

  There is a bug/race condition on libvirt-guests.service, that prevents
  the shutdown of guests to happen in parallel.

  The critical chain for this service is:

  libvirt-guests.service +20ms
  └─libvirt-bin.service @2.784s +140ms
    └─remote-fs.target @2.777s
  └─remote-fs-pre.target @2.775s
    └─open-iscsi.service @2.554s +116ms
  └─iscsid.service @2.525s +18ms
    └─network-online.target @2.502s
  └─network.target @1.955s
    └─networking.service @1.625s +299ms
  └─network-pre.target @1.601s
    └─cloud-init-local.service @405ms +1.072s
  └─systemd-remount-fs.service @232ms +64ms
    └─systemd-journald.socket @178ms
  └─-.slice @117ms

  As an example, I have the following kvm host with 42 virtual
  machines.

  ubuntu@xenial-base:~$ virsh list --all
   IdName   State
  
   12locked-trusty-2running
   13locked-trusty-3running
  [...]
   41locked-trusty-42   running

  After rebooting the machine:

  [  250.999516] libvirt-guests.sh[4215]: Running guests on default URI: 
locked-trusty-2, locked-trusty-4, locked-trusty-12, locked-trusty-3, 
locked-trusty-5, locked-trusty-11, locked-trusty-10, locked-trusty-8, 
locked-trusty-9, locked-trusty-7, locked-trusty-6, locked-trusty-13, 
locked-trusty-14, locked-trusty-15, locked-trusty-16, locked-trusty-17, 
locked-trusty-18, locked-trusty-19, locked-trusty-20, locked-trusty-21, 
locked-trusty-22, locked-trusty-23, locked-trusty-24, locked-trusty-25, 
locked-trusty-26, locked-trusty-27, locked-trusty-28, locked-trusty-29, 
locked-trusty-30, locked-trusty-31, locked-trusty-32, locked-trusty-33, 
locked-trusty-34, locked-trusty-35, locked-trusty-36, locked-trusty-37, 
locked-trusty-38, locked-trusty-39, locked-trusty-40, locked-trusty-41, 
locked-trusty-42
  [  251.011367] libvirt-guests.sh[4215]: Shutting down guests on default URI...
  [  251.027072] libvirt-guests.sh[4215]: Starting shutdown on guest: 
locked-trusty-2
  [...]
  [  391.949941] libvirt-guests.sh[4215]: Waiting for 28 guests to shut down, 
10 seconds left
  [  398.074405] libvirt-guests.sh[4215]: Waiting for 28 guests to shut down, 5 
seconds left
  [  403.020479] libvirt-guests.sh[4215]: Timeout expired while shutting down 
domains
  [  OK  ] Stopped Suspend Active Libvirt Guests.
  [  OK  ] Stopped target System Time Synchronized.

  [Test Case]

   * Make sure the following variables are set in /etc/default/libvirt-
  guests (which are all default options):

  ON_SHUTDOWN=shutdown
  PARALLEL_SHUTDOWN=10
  SHUTDOWN_TIMEOUT=120

   * Create over 20 virtual machines (in my case, using uvt-kvm).

  $  for f in $(seq 0 40); do uvt-kvm create --memory 2000 --cpu 1
  locked-trusty-$f release=xenial arch=amd64 ; done

   * Reboot the machine and monitor the systemd service stop sequence
  or console output.

  (With systemd: systemctl start debug-shell and jumpt to ctrl+alt+f9)

  * Error message "Timeout

[Group.of.nepali.translators] [Bug 1757435] Re: Redpine: WiFi scan stopping issue observed with BLE

2018-03-21 Thread Joseph Salisbury

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

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

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

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

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

Title:
  Redpine: WiFi scan stopping issue observed with BLE

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

Bug description:
  Below is the procedure to reproduce this issue

     1)  Any PC (Ubuntu Desktop): setup iBeacon advertiser
     2)  Caracalla 3003 (Ubuntu Server/Core) run:
  ./scan.sh
   By default WiFi supplicant will run on Caracalla
   You can check the WiFi scan results by using below command
  iw dev wlan0 scan

   After 24hrs successful regression, we are unable to get the
  WiFi scan results by giving the above command

  Attached are BLE scripts.

  This bug is for tracking purposes only, please don't triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757435/+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 1757422] Re: Fix Runtime PM for r8169

2018-03-21 Thread Joseph Salisbury

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  Fix Runtime PM for r8169

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

Bug description:
  ===SRU Justification===
  [Impact]
  r8169 stays in D0 even when no ethernet cable is plugged in. This drains
  lots of power (~3W). The tested laptop uses 5.5W when r8169 is in D0,
  1.8W when r8169 is in D3. The power saved is substantial.

  [Fix]
  Improved rumtime PM logic to let the device gets suspended (D3) when the
  port is not in used and the link is down.

  [Test Case]
  The chip version is 8168h/8111h.
  Test when no ethernet gets plugged.

  Powertop shows power consumption is roughly 5.5W.
  lspci shows the device is in D0.

  With the patch,
  The power consumption is reduced to 1.8W.
  lspci shows the device is in D3, PME# is correctly enabled.
  Plug ethernet cable can corretly wake up the device.
  Unplug the cable, the device gets suspended to D3 correctly.

  [Regression Potential]
  Medium.
  - r8169 is so ubiquitous, with lots of different chip versions. It's
hard to test all of them.
  - PCI D3 needs system firmware (ACPI) support, this might hit some
plaform bugs.
  - the code is still in v4.16-rc*, so it's not well tested by end users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1757422/+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 1757443] Re: Redpine: BLE radio lost issue

2018-03-21 Thread Joseph Salisbury

** Also affects: linux (Ubuntu Bionic)
   Importance: Critical
   Status: Confirmed

** Also affects: linux-firmware (Ubuntu Bionic)
   Importance: Critical
   Status: Confirmed

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

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

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

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

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

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Confirmed => Triaged

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

** Changed in: linux-firmware (Ubuntu Xenial)
   Importance: Undecided => Critical

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

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux-firmware source package in Xenial:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux-firmware source package in Bionic:
  Triaged

Bug description:
  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757443/+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 1757481] [NEW] Only enable APM on disks that advertise it

2018-03-21 Thread dann frazier

Public bug reported:

[Impact]
hdparm can cause certain systems to occasionally fail to boot. hdparm tries to 
enable APM on every (non-USB/non-firewire) disk in the system without first 
checking if APM is supported. This *should*
be OK, since hdparm fails gracefully in this case. However, sending APM 
commands to disks that don't support it can have side-effects. I received a 
report that this was causing bus resets on a Cavium Sabre system with the disk 
below that would sometimes escalate to a boot failure.

[Test Case]
Boot a system with a non-USB/non-firewire disk that does not support APM and 
verify that there are no kernel messages like:

SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 40 fe 21 04
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 APM_level = not supported


[Regression Risk]
This change entered Debian and Ubuntu 1 month ago, and no regressions have been 
reported. One source of regressions might be that configuring APM on a disk 
that claims not to support it did have some positive side-effect that would no 
longer occur.

** Affects: hdparm (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: hdparm (Ubuntu Xenial)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: hdparm (Ubuntu Artful)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: hdparm (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Released

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

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

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

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

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

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

** Changed in: hdparm (Ubuntu Xenial)
 Assignee: (unassigned) => dann frazier (dannf)

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

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

Title:
  Only enable APM on disks that advertise it

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

Bug description:
  [Impact]
  hdparm can cause certain systems to occasionally fail to boot. hdparm tries 
to enable APM on every (non-USB/non-firewire) disk in the system without first 
checking if APM is supported. This *should*
  be OK, since hdparm fails gracefully in this case. However, sending APM 
commands to disks that don't support it can have side-effects. I received a 
report that this was causing bus resets on a Cavium Sabre system with the disk 
below that would sometimes escalate to a boot failure.

  [Test Case]
  Boot a system with a non-USB/non-firewire disk that does not support APM and 
verify that there are no kernel messages like:

  SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 40 fe 21 04
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   APM_level = not supported

  
  [Regression Risk]
  This change entered Debian and Ubuntu 1 month ago, and no regressions have 
been reported. One source of regressions might be that configuring APM on a 
disk that claims not to support it did have some positive side-effect that 
would no longer occur.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/1757481/+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 1582181] Re: AArch64: slow cpuinfo due to redundant loop

[Group.of.nepali.translators] [Bug 1748247] Re: [CVE] Arbitrary command execution in the removable device notifier

[Group.of.nepali.translators] [Bug 1757481] Re: Only enable APM on disks that advertise it

[Group.of.nepali.translators] [Bug 1582181] Re: AArch64: slow cpuinfo due to redundant loop

[Group.of.nepali.translators] [Bug 1437353] Re: UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit SFI/SFP+

[Group.of.nepali.translators] [Bug 1755208] Re: linux: 4.4.0-117.141 -proposed tracker

[Group.of.nepali.translators] [Bug 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial

[Group.of.nepali.translators] [Bug 1722481] Re: systemd should sync disks, before killing all processes on shutdown

[Group.of.nepali.translators] [Bug 1734409] Re: systemd-sysctl: exit gracefully on EPERM/EACCESS

[Group.of.nepali.translators] [Bug 696435] Re: wait-for-root fails to detect nbd root

[Group.of.nepali.translators] [Bug 1755213] Re: linux-raspi2: 4.4.0-1086.94 -proposed tracker

[Group.of.nepali.translators] [Bug 1734410] Re: systemd: handle undelegated cgroup2 hierarchy

[Group.of.nepali.translators] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

[Group.of.nepali.translators] [Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

[Group.of.nepali.translators] [Bug 1737570] Re: Add support for RequiredForOnline in networkd

[Group.of.nepali.translators] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

[Group.of.nepali.translators] [Bug 1717471] Re: networkd does not accept / set advertised mtu

[Group.of.nepali.translators] [Bug 1718444] Re: systemd-sysctl in Xenial is not obeying the order of the sysctls

[Group.of.nepali.translators] [Bug 1737570] Re: Add support for RequiredForOnline in networkd

[Group.of.nepali.translators] [Bug 1746066] Re: linux-azure-edge: 4.14.0-1004.4 -proposed tracker

[Group.of.nepali.translators] [Bug 1755771] Re: linux-gcp: 4.13.0-1012.16 -proposed tracker

[Group.of.nepali.translators] [Bug 1734225] Re: Invalid service name defined in /etc/ctdb/events.d/50.samba

[Group.of.nepali.translators] [Bug 1755215] Re: linux-snapdragon: 4.4.0-1088.93 -proposed tracker

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

[Group.of.nepali.translators] [Bug 1755769] Re: linux-azure-edge: 4.15.0-1003.3 -proposed tracker

[Group.of.nepali.translators] [Bug 1721749] Re: Security Fix - CVE-2017-12617

[Group.of.nepali.translators] [Bug 1756987] Re: chrony install does not stop systemd-timesyncd

[Group.of.nepali.translators] [Bug 1688508] Re: libvirt-guests.sh fails to shutdown guests in parallel

[Group.of.nepali.translators] [Bug 1757435] Re: Redpine: WiFi scan stopping issue observed with BLE

[Group.of.nepali.translators] [Bug 1757422] Re: Fix Runtime PM for r8169

[Group.of.nepali.translators] [Bug 1757443] Re: Redpine: BLE radio lost issue

[Group.of.nepali.translators] [Bug 1757481] [NEW] Only enable APM on disks that advertise it

32 matches

Site Navigation

Mail list logo

Footer information