[Group.of.nepali.translators] [Bug 1742364] Re: Updated microcode for Spectre fix

2018-02-23 Thread Leann Ogasawara 
** Changed in: intel
   Status: New => Incomplete

** Changed in: intel
   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/1742364

Title:
  Updated microcode for Spectre fix

Status in intel:
  Fix Released
Status in intel-microcode package in Ubuntu:
  Fix Released
Status in intel-microcode source package in Trusty:
  Fix Released
Status in intel-microcode source package in Xenial:
  Fix Released
Status in intel-microcode source package in Zesty:
  Fix Released
Status in intel-microcode source package in Artful:
  Fix Released
Status in intel-microcode source package in Bionic:
  Fix Released

Bug description:
  Intel have finally released the updated microcode for the Spectre bug.

  See https://downloadcenter.intel.com/download/27431/Linux-Processor-
  Microcode-Data-File?v=t

  From the release note:
  Intel Processor Microcode Package for Linux
  20180108 Release

  -- Updates upon 20171117 release --
  IVT C0(06-3e-04:ed) 428->42a
  SKL-U/Y D0(06-4e-03:c0) ba->c2
  BDW-U/Y E/F   (06-3d-04:c0) 25->28
  HSW-ULT Cx/Dx (06-45-01:72) 20->21
  Crystalwell Cx(06-46-01:32) 17->18
  BDW-H E/G (06-47-01:22) 17->1b
  HSX-EX E0 (06-3f-04:80) 0f->10
  SKL-H/S R0(06-5e-03:36) ba->c2
  HSW Cx/Dx (06-3c-03:32) 22->23
  HSX C0(06-3f-02:6f) 3a->3b
  BDX-DE V0/V1  (06-56-02:10) 0f->14
  BDX-DE V2 (06-56-03:10) 70d->711
  KBL-U/Y H0(06-8e-09:c0) 62->80
  KBL Y0 / CFL D0   (06-8e-0a:c0) 70->80
  KBL-H/S B0(06-9e-09:2a) 5e->80
  CFL U0(06-9e-0a:22) 70->80
  CFL B0(06-9e-0b:02) 72->80
  SKX H0(06-55-04:b7) 235->23c
  GLK B0(06-7a-01:01) 1e->22

  These should be released ASAP since they will be needed for the
  upcoming Spectre fixes in the Kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1742364/+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 1728762] Re: Update iwlwifi firmware for 3160, 3168, 7260, 7265 and 7265D

2018-02-23 Thread Leann Ogasawara 
** Changed in: intel
   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/1728762

Title:
  Update iwlwifi firmware for 3160, 3168, 7260, 7265 and 7265D

Status in intel:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Trusty:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Zesty:
  Fix Released
Status in linux-firmware source package in Artful:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  SRU Justification

  Impact: Intel wireless firmware WoWLAN functionality is vulnerable to
  some CVEs from the KRACK attack vulnerabilities, CVE-2017-13080 and
  CVE-2017-13081.

  Fix: Updated firmware from Intel containing fixes for these
  vulnerabilities.

  Test Case: Difficult to test; we are reliant on testing done by Intel.

  Regression Potential: There is always some possibility for regressions
  with firmware updates, but as these are bug fix updates the regression
  potential is minimal. I have been using the 7260 firmware for over a
  week now without issue.

  ---

  There are two parts of WIFI firmware update. Please double check if
  Ubuntu release has include them.

  A new firmware version for 8260 and 8265 WiFi devices.
  This our Core31 release (-34.ucode).
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=348d2b53326bcef4c260037cc7a6006fc80ca5bb

  A new firmware version  for 3160, 3168, 7260, 7265 and 7265D
  Note: This firmware version hasn't been pulled into mainline yet.
  This includes a security fix.
  The patch in iwlwifi/linux-firmware.git is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=11e310f97470f91e26e6f3408b09871fd6cd3c5c

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1728762/+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 1617535] Re: geoip.ubuntu.com does not utilize HTTPS

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package ubuntu-geoip -
1.0.2+18.04.20180223-0ubuntu1

---
ubuntu-geoip (1.0.2+18.04.20180223-0ubuntu1) bionic; urgency=medium

  * Use https for geoip.ubuntu.com (LP: #1617535)

 -- Jeremy Bicha   Fri, 23 Feb 2018 17:23:36 +

** Changed in: ubuntu-geoip (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  geoip.ubuntu.com does not utilize HTTPS

Status in ubuntu-geoip package in Ubuntu:
  Fix Released
Status in ubuntu-geoip source package in Trusty:
  Triaged
Status in ubuntu-geoip source package in Xenial:
  Triaged
Status in ubuntu-geoip source package in Artful:
  Triaged

Bug description:
  Impact
  --
  It's better to use https where we can. There were concerns about location 
leakage for users using a proxy (such as Tor).

  Test Case
  -

  Regression Potential
  
  As long as Canonical maintains https://geoip.ubuntu.com, things should be 
fine here. Minimal fix.

  
  Original Bug Report
  ---
  geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This 
can potentially be utilized by nation state adversaries to compromise user 
privacy. This service is called multiple times per day by the OS in order to 
track users.

  $ nc -zv geoip.ubuntu.com 80
  Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded!

  $ nc -zv -w 3 geoip.ubuntu.com 443
  nc: connect to geoip.ubuntu.com port 443 (tcp) timed out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+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 1749095] Re: linux-euclid: 4.4.0-9025.27 -proposed tracker

2018-02-23 Thread Brad Figg 
The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Friday, 23. February 2018 20:00 UTC
+ kernel-stable-phase: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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1749089
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Friday, 23. February 2018 20:00 UTC
- kernel-stable-phase:Released

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

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

Title:
  linux-euclid: 4.4.0-9025.27 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
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:
  Fix Released
Status in linux-euclid package in Ubuntu:
  Invalid
Status in linux-euclid source package in Xenial:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1749089
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749095/+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 1745492] Re: Backport of Debian bug #785714 for Xenial to avoid unclean reboots

2018-02-23 Thread dann frazier 
** Also affects: kexec-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** No longer affects: kexec-tools (Ubuntu Artful)

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

Title:
  Backport of Debian bug #785714 for Xenial to avoid unclean reboots

Status in kexec-tools package in Ubuntu:
  New
Status in kexec-tools source package in Xenial:
  New
Status in kexec-tools package in Debian:
  Fix Released

Bug description:
  Debian bug #785714 is a fairly substantial one, as it causes unclean
  shutdowns.  In our case, KVM hosts with many guests will begin to
  partially shutdown a couple before kexec jumps the gun and reboots the
  machine.  Without this fix, kexec is of only minimal use on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1745492/+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 1749095] Re: linux-euclid: 4.4.0-9025.27 -proposed tracker

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux-euclid - 4.4.0-9025.27

---
linux-euclid (4.4.0-9025.27) xenial; urgency=medium

  * linux-euclid: 4.4.0-9025.27 -proposed tracker (LP: #1749095)

  * BUG: unable to handle kernel NULL pointer dereference at 0009
(LP: #1748671)
- SAUCE: net: ipv4: fix for a race condition in raw_sendmsg -- fix backport

  * CVE-2017-5715 (Spectre v2 Intel)
- SAUCE: drop lingering gmb() macro
- x86/feature: Enable the x86 feature to control Speculation
- x86/feature: Report presence of IBPB and IBRS control
- x86/enter: MACROS to set/clear IBRS and set IBPB
- x86/enter: Use IBRS on syscall and interrupts
- x86/idle: Disable IBRS entering idle and enable it on wakeup
- x86/idle: Disable IBRS when offlining cpu and re-enable on wakeup
- x86/mm: Set IBPB upon context switch
- x86/mm: Only set IBPB when the new thread cannot ptrace current thread
- x86/kvm: add MSR_IA32_SPEC_CTRL and MSR_IA32_PRED_CMD to kvm
- x86/kvm: Set IBPB when switching VM
- x86/kvm: Toggle IBRS on VM entry and exit
- x86/spec_ctrl: Add sysctl knobs to enable/disable SPEC_CTRL feature
- x86/spec_ctrl: Add lock to serialize changes to ibrs and ibpb control
- x86/cpu/amd, kvm: Satisfy guest kernel reads of IC_CFG MSR
- x86/cpu/AMD: Add speculative control support for AMD
- x86/microcode: Extend post microcode reload to support IBPB feature
- KVM: SVM: Do not intercept new speculative control MSRs
- x86/svm: Set IBRS value on VM entry and exit
- x86/svm: Set IBPB when running a different VCPU
- KVM: x86: Add speculative control CPUID support for guests
- SAUCE: Fix spec_ctrl support in KVM
- SAUCE: turn off IBRS when full retpoline is present
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files
- [Packaging] sort retpoline file from previous ABI

linux-euclid (4.4.0-9024.25) xenial; urgency=low

  * linux-euclid: 4.4.0-9024.25 -proposed tracker (LP: #1746939)

  * CVE-2017-5715 (Spectre v2 retpoline)
- x86/cpuid: Provide get_scattered_cpuid_leaf()
- x86/cpu: Factor out application of forced CPU caps
- x86/cpufeatures: Make CPU bugs sticky
- x86/cpufeatures: Add X86_BUG_CPU_INSECURE
- x86/cpu, x86/pti: Do not enable PTI on AMD processors
- x86/pti: Rename BUG_CPU_INSECURE to BUG_CPU_MELTDOWN
- x86/cpufeatures: Add X86_BUG_SPECTRE_V[12]
- x86/cpu: Merge bugs.c and bugs_64.c
- sysfs/cpu: Add vulnerability folder
- x86/cpu: Implement CPU vulnerabilites sysfs functions
- x86/alternatives: Add missing '\n' at end of ALTERNATIVE inline asm
- x86/mm/32: Move setup_clear_cpu_cap(X86_FEATURE_PCID) earlier
- x86/asm: Use register variable to get stack pointer value
- x86/kbuild: enable modversions for symbols exported from asm
- x86/asm: Make asm/alternative.h safe from assembly
- EXPORT_SYMBOL() for asm
- kconfig.h: use __is_defined() to check if MODULE is defined
- x86/retpoline: Add initial retpoline support
- x86/spectre: Add boot time option to select Spectre v2 mitigation
- x86/retpoline/crypto: Convert crypto assembler indirect jumps
- x86/retpoline/entry: Convert entry assembler indirect jumps
- x86/retpoline/ftrace: Convert ftrace assembler indirect jumps
- x86/retpoline/hyperv: Convert assembler indirect jumps
- x86/retpoline/xen: Convert Xen hypercall indirect jumps
- x86/retpoline/checksum32: Convert assembler indirect jumps
- x86/retpoline/irq32: Convert assembler indirect jumps
- x86/retpoline: Fill return stack buffer on vmexit
- x86/retpoline: Remove compile time warning
- x86/retpoline: Add LFENCE to the retpoline/RSB filling RSB macros
- module: Add retpoline tag to VERMAGIC
- x86/mce: Make machine check speculation protected
- retpoline: Introduce start/end markers of indirect thunk
- kprobes/x86: Blacklist indirect thunk functions for kprobes
- kprobes/x86: Disable optimizing on the function jumps to indirect thunk
- x86/retpoline: Optimize inline assembler for vmexit_fill_RSB
- [Config] CONFIG_RETPOLINE=y
- [Packaging] retpoline -- add call site validation
- [Config] disable retpoline checks for first upload
- [Config] updateconfigs for retpoline support

  * CVE-2017-5753 (Spectre v1 Intel)
- x86/cpu/AMD: Make the LFENCE instruction serialized
- x86/cpu/AMD: Remove now unused definition of MFENCE_RDTSC feature
- SAUCE: reinstate MFENCE_RDTSC feature definition
- locking/barriers: introduce new observable speculation barrier
- bpf: prevent speculative execution in eBPF interpreter
- x86, bpf, jit: prevent speculative execution when JIT is enabled
- SAUCE: FIX: x86, bpf, jit: prevent speculative execution when JIT is 
enabled
- carl9170: prevent speculative execution
- qla2xxx: prevent speculative execution
- Thermal/int340x: prevent speculative

[Group.of.nepali.translators] [Bug 1746939] Re: linux-euclid: 4.4.0-9024.25 -proposed tracker

2018-02-23 Thread Launchpad Bug Tracker 
*** This bug is a duplicate of bug 1749095 ***
https://bugs.launchpad.net/bugs/1749095

This bug was fixed in the package linux-euclid - 4.4.0-9025.27

---
linux-euclid (4.4.0-9025.27) xenial; urgency=medium

  * linux-euclid: 4.4.0-9025.27 -proposed tracker (LP: #1749095)

  * BUG: unable to handle kernel NULL pointer dereference at 0009
(LP: #1748671)
- SAUCE: net: ipv4: fix for a race condition in raw_sendmsg -- fix backport

  * CVE-2017-5715 (Spectre v2 Intel)
- SAUCE: drop lingering gmb() macro
- x86/feature: Enable the x86 feature to control Speculation
- x86/feature: Report presence of IBPB and IBRS control
- x86/enter: MACROS to set/clear IBRS and set IBPB
- x86/enter: Use IBRS on syscall and interrupts
- x86/idle: Disable IBRS entering idle and enable it on wakeup
- x86/idle: Disable IBRS when offlining cpu and re-enable on wakeup
- x86/mm: Set IBPB upon context switch
- x86/mm: Only set IBPB when the new thread cannot ptrace current thread
- x86/kvm: add MSR_IA32_SPEC_CTRL and MSR_IA32_PRED_CMD to kvm
- x86/kvm: Set IBPB when switching VM
- x86/kvm: Toggle IBRS on VM entry and exit
- x86/spec_ctrl: Add sysctl knobs to enable/disable SPEC_CTRL feature
- x86/spec_ctrl: Add lock to serialize changes to ibrs and ibpb control
- x86/cpu/amd, kvm: Satisfy guest kernel reads of IC_CFG MSR
- x86/cpu/AMD: Add speculative control support for AMD
- x86/microcode: Extend post microcode reload to support IBPB feature
- KVM: SVM: Do not intercept new speculative control MSRs
- x86/svm: Set IBRS value on VM entry and exit
- x86/svm: Set IBPB when running a different VCPU
- KVM: x86: Add speculative control CPUID support for guests
- SAUCE: Fix spec_ctrl support in KVM
- SAUCE: turn off IBRS when full retpoline is present
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files
- [Packaging] sort retpoline file from previous ABI

linux-euclid (4.4.0-9024.25) xenial; urgency=low

  * linux-euclid: 4.4.0-9024.25 -proposed tracker (LP: #1746939)

  * CVE-2017-5715 (Spectre v2 retpoline)
- x86/cpuid: Provide get_scattered_cpuid_leaf()
- x86/cpu: Factor out application of forced CPU caps
- x86/cpufeatures: Make CPU bugs sticky
- x86/cpufeatures: Add X86_BUG_CPU_INSECURE
- x86/cpu, x86/pti: Do not enable PTI on AMD processors
- x86/pti: Rename BUG_CPU_INSECURE to BUG_CPU_MELTDOWN
- x86/cpufeatures: Add X86_BUG_SPECTRE_V[12]
- x86/cpu: Merge bugs.c and bugs_64.c
- sysfs/cpu: Add vulnerability folder
- x86/cpu: Implement CPU vulnerabilites sysfs functions
- x86/alternatives: Add missing '\n' at end of ALTERNATIVE inline asm
- x86/mm/32: Move setup_clear_cpu_cap(X86_FEATURE_PCID) earlier
- x86/asm: Use register variable to get stack pointer value
- x86/kbuild: enable modversions for symbols exported from asm
- x86/asm: Make asm/alternative.h safe from assembly
- EXPORT_SYMBOL() for asm
- kconfig.h: use __is_defined() to check if MODULE is defined
- x86/retpoline: Add initial retpoline support
- x86/spectre: Add boot time option to select Spectre v2 mitigation
- x86/retpoline/crypto: Convert crypto assembler indirect jumps
- x86/retpoline/entry: Convert entry assembler indirect jumps
- x86/retpoline/ftrace: Convert ftrace assembler indirect jumps
- x86/retpoline/hyperv: Convert assembler indirect jumps
- x86/retpoline/xen: Convert Xen hypercall indirect jumps
- x86/retpoline/checksum32: Convert assembler indirect jumps
- x86/retpoline/irq32: Convert assembler indirect jumps
- x86/retpoline: Fill return stack buffer on vmexit
- x86/retpoline: Remove compile time warning
- x86/retpoline: Add LFENCE to the retpoline/RSB filling RSB macros
- module: Add retpoline tag to VERMAGIC
- x86/mce: Make machine check speculation protected
- retpoline: Introduce start/end markers of indirect thunk
- kprobes/x86: Blacklist indirect thunk functions for kprobes
- kprobes/x86: Disable optimizing on the function jumps to indirect thunk
- x86/retpoline: Optimize inline assembler for vmexit_fill_RSB
- [Config] CONFIG_RETPOLINE=y
- [Packaging] retpoline -- add call site validation
- [Config] disable retpoline checks for first upload
- [Config] updateconfigs for retpoline support

  * CVE-2017-5753 (Spectre v1 Intel)
- x86/cpu/AMD: Make the LFENCE instruction serialized
- x86/cpu/AMD: Remove now unused definition of MFENCE_RDTSC feature
- SAUCE: reinstate MFENCE_RDTSC feature definition
- locking/barriers: introduce new observable speculation barrier
- bpf: prevent speculative execution in eBPF interpreter
- x86, bpf, jit: prevent speculative execution when JIT is enabled
- SAUCE: FIX: x86, bpf, jit: prevent speculative execution when JIT is 
enabled
- carl9170: prevent speculative execution

[Group.of.nepali.translators] [Bug 1718568] Re: dhclient-script fails to wait for link-local address

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package isc-dhcp - 4.3.5-3ubuntu4

---
isc-dhcp (4.3.5-3ubuntu4) bionic; urgency=medium

  * dhclient-script.linux: handle empty case also when waiting for ipv6 link
local DAD. (LP: #1718568)

 -- Dan Streetman   Thu, 12 Oct 2017
08:48:06 -0400

** Changed in: isc-dhcp (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/1718568

Title:
  dhclient-script fails to wait for link-local address

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress
Status in isc-dhcp source package in Zesty:
  Won't Fix
Status in isc-dhcp source package in Artful:
  In Progress
Status in isc-dhcp source package in Bionic:
  Fix Released
Status in isc-dhcp package in Debian:
  New

Bug description:
  [impact]

  bug 1633479 made a change to isc-dhcp to wait for an interface's link-local 
ipv6 address to switch from 'tentative' to normal, because all link-local 
addresses briefly go through a 'tentative' state while the kernel is performing 
ipv6 link-local 'duplicate address detection' (DAD).  While in the 'tentative' 
state, dhclient can't take over the interface and send out
  dhcpv6 requests; it must wait until DAD completes.

  However, the change made in that bug does not account for the case
  where the 'tentative' check is done before the interface has even set
  up a link-local address; its case statement assumes if there is no
  'tentative' or 'dadfailed' string in the output, the link-local
  address is ready to use.  When the address check finds no address at
  all, this will return as successful, even though it shouldn't, and
  dhclient will fail to get the dhcpv6 address.

  [test case]

  on a system that is configured for dhcpv6 on one or more of its
  interfaces, repeatedly try to get the dhcpv6 address.  For interfaces
  that are slower to actually set up their initial tentative link-local
  address, they will occasionally fail, since the current code is a race
  between the kernel adding the tentative link-local address, and the
  dhclient-script.linux code checking the interface for a tentative
  address.

  with the patch to correct this, even interfaces slow to add their
  tentative link-local address should correctly wait for the address to
  get added, and then transition from tentative to normal, and then
  begin the dhcpv6 process.

  [regression potential]

  errors in this function can cause dhclient to fail to get a ipv6
  address for an interface; regression would happen if this patch makes
  it fail more than it already is failing, but would not cause other
  failures or problems after getting an ipv6 address; this patch will
  affect only startup-time.

  [other info]

  related bug 1633479

  
  [original description]

  
  Summary:
  

  If a interface does not yet have a link-local address (as it may have
  just been brought up), dhclient -6  will fail. The built-in
  "wait for link-local address" loop does not function properly, causing
  DHCP failure.

  Discussion:
  ===

  In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on
  Ubuntu 17.04, I was finding that on boot I was getting failures with
  the logged message "no link-local IPv6 address for "

  I found that it took several seconds for the link-local address to be
  assigned when the interface came up (in this case, the ISP/modem-
  facing interface), and worked around it with a script that looks at

    /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20'

  and loops for a fixed number of times for that to be successful.

  On looking at /sbin/dhclient-script it appears that it *tries* to do
  the same thing in

    # set the link up and wait for ipv6 link local dad to finish
    ipv6_link_up_and_dad()

  this code sets

    out=$(ip -6 -o address show dev "$dev" scope link)

  then checks it with a case statement inside of a loop for

  case " $out " in
  *\ dadfailed\ *)
  error "$dev: ipv6 dad failed."
  return 1;;
  *\ tentative\ *) :;;
  *) return 0;;
  esac

  If there is no link-local address, $out will be empty. The default
  case is taken, and the loop exits immediately:

  $ echo "'$out'" ; case " $out " in
  > *\ dadfailed\ *)
  > echo "dadfailed"
  > ;;
  > *\ tentative\ *)
  > echo "tentative"
  > ;;
  > *)
  > echo "default"
  > esac
  ''
  default

  As a result, there is no "wait for link-local address" and when there
  is no link-local address, dhclient fails later on.

  Possible Fix:
  =

  Adding "the missing case" for "no address" case that

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

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package libvirt - 4.0.0-1ubuntu4

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

  * d/p/ubuntu/lp1688508-tools-avoid-text-spilling-into-variables.patch:
avoid hanging on shutdown (LP: #1688508)

 -- Christian Ehrhardt   Fri, 23 Feb
2018 16:43:19 +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:
  In Progress
Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  In Progress
Status in libvirt source package in Zesty:
  In Progress
Status in libvirt source package in Artful:
  In Progress

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 expired while shutting down domains" should
  be displayed.

  [Regression Potential]

  * None identified.

  [Other Info]

  * There is a proposed patch in upstream already that has been already
  linked to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1450141

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1688508/+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 1351267] Re: partman-auto prefers to give disk to swap, leaving root too small

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package partman-auto - 134ubuntu8

---
partman-auto (134ubuntu8) bionic; urgency=medium

  * Introduce partman-auto/cap-ram, to allow capping RAM size as used for
swap partition calculations. This allows us to effectively cap the
swap partitions size to maximum of 2*CAP. Default is set to 1024, thus
capping swap partitions to 2GB maximum. LP: #1351267

 -- Dimitri John Ledkov   Fri, 23 Feb 2018 13:53:15
+

** Changed in: partman-auto (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  partman-auto prefers to give disk to swap, leaving root too small

Status in partman-auto package in Ubuntu:
  Fix Released
Status in partman-auto source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Impossible to perform guided LVM installation, with an all-in-one
  configuration out of the box, on high-memory systems. High-memory
  systems are systems that have RAM on par, or more than, disk space.
  E.g. 8GB RAM with 8GB disk space, or 1TB RAM with 256GB hard drive.

  [Test Case]

   * Start d-i installer
   * Select Use entire disk & setup LVM
   * Select drive to use, which is on par, or less then total RAM on the system
   * Select all in one / atomic partition recipe
   * Install should succeed, with no more than 2GB of swap partition / volume

  [Regression Potential]

   * SWAP partition or LVM volume is typically calculated as a
  percentage of RAM - between 100% and 200% of RAM. Yet, this assumes
  that RAM is significantly less than total disk space, and thus on
  high-memory systems results in badly setup systems with too small
  rootfs, and too much swap.

  [Other Info]
   
   * Original bug report

  
  I was trying to install Ubuntu 14.04.1 LTS on an Oracle VirtualBox VM with 
6.5GB of RAM and 8GB (default for a new Virtual HDD on VirtualBox) of disk 
space.

  I selected the option "Erase disk and install Ubuntu" (and post crash
  "Erase Ubuntu 14.04.1 LTS and reinstall") and let it use the defaults.

  The installer gives the error:

   "Some of the partitions you created are too small. Please make the
  following partitions at least this large:

   / 3.4 GB

   If you do not go back to the partitioner and increase the size of
  these partitions, the installation may fail."

  The message is very confusing to a new user who did not specify any
  partition sizes themselves.

  The installer created a 6GB Swap partition on the 8GB drive. The
  installer then could not install to the root partition and failed
  midway:

  "The installer encountered an error copying files to the hard disk:

  [Errno 28] No space left on device

  This is due to there being insufficient disk space for the install to
  complete on the target partition. Please run the installer again and
  select a larger partition to install into."

  ..then a box appears stating that the installer has crashed:

  "Installer crashed

  We're sorry; the installer crashed. After you close this window, we'll
  allow you to file a bug report using the integrated bug reporting
  tool. This will gather information about your system and your
  installation process. The details will be sent to our bug tracker and
  a developer will attend to the problem as soon as possible."

  The box cannot be closed. No bug reporting tool launches. The computer
  requires restarting to become usable again.

  Please let me know if you need any more information as this is my
  first bug report.

  Thanks for your time,
  Matthew

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1351267/+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 1670696] Re: Typo in error msg when no crashkernel memory reservation is set

2018-02-23 Thread Thadeu Lima de Souza Cascardo 
** Changed in: makedumpfile (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/1670696

Title:
  Typo in error msg when no crashkernel memory reservation is set

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Zesty:
  Won't Fix
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  [Impact]

   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial/Zesty, Debian and makedumpfile upstream.

  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!"

  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"

  The typo is located here in src code :

  # filename : makedumpfile.c
  -
  int show_mem_usage(void)
   {
   uint64_t vmcoreinfo_addr, vmcoreinfo_len;
   struct cycle cycle = {0};

   if (!is_crashkernel_mem_reserved()) {
     ==>  ERRMSG("No memory is reserved for crashkenrel!\n");
   return FALSE;
   }
  -

  [Test Case]

   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore

   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!

  [Regression Potential]

   * No regression, it is a trivial change with no behavioural change.

  [Other Info]

  * Upstream:
  Patch has been submitted upstream (ML :ke...@lists.infradead.org) 
  - AFAIK, there is no upstream bug database, so no URL available, ML only.
  - Patch will be merge in upstream version 1.6.2 # See comment #4

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1670696/+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 1351267] Re: partman-auto prefers to give disk to swap, leaving root too small

2018-02-23 Thread Łukasz Zemczak 
This has been accepted and needs verification (the script failed while
writing the bug info).

** Changed in: partman-auto (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

** Changed in: partman-auto (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: partman-auto (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  partman-auto prefers to give disk to swap, leaving root too small

Status in partman-auto package in Ubuntu:
  Fix Committed
Status in partman-auto source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Impossible to perform guided LVM installation, with an all-in-one
  configuration out of the box, on high-memory systems. High-memory
  systems are systems that have RAM on par, or more than, disk space.
  E.g. 8GB RAM with 8GB disk space, or 1TB RAM with 256GB hard drive.

  [Test Case]

   * Start d-i installer
   * Select Use entire disk & setup LVM
   * Select drive to use, which is on par, or less then total RAM on the system
   * Select all in one / atomic partition recipe
   * Install should succeed, with no more than 2GB of swap partition / volume

  [Regression Potential]

   * SWAP partition or LVM volume is typically calculated as a
  percentage of RAM - between 100% and 200% of RAM. Yet, this assumes
  that RAM is significantly less than total disk space, and thus on
  high-memory systems results in badly setup systems with too small
  rootfs, and too much swap.

  [Other Info]
   
   * Original bug report

  
  I was trying to install Ubuntu 14.04.1 LTS on an Oracle VirtualBox VM with 
6.5GB of RAM and 8GB (default for a new Virtual HDD on VirtualBox) of disk 
space.

  I selected the option "Erase disk and install Ubuntu" (and post crash
  "Erase Ubuntu 14.04.1 LTS and reinstall") and let it use the defaults.

  The installer gives the error:

   "Some of the partitions you created are too small. Please make the
  following partitions at least this large:

   / 3.4 GB

   If you do not go back to the partitioner and increase the size of
  these partitions, the installation may fail."

  The message is very confusing to a new user who did not specify any
  partition sizes themselves.

  The installer created a 6GB Swap partition on the 8GB drive. The
  installer then could not install to the root partition and failed
  midway:

  "The installer encountered an error copying files to the hard disk:

  [Errno 28] No space left on device

  This is due to there being insufficient disk space for the install to
  complete on the target partition. Please run the installer again and
  select a larger partition to install into."

  ..then a box appears stating that the installer has crashed:

  "Installer crashed

  We're sorry; the installer crashed. After you close this window, we'll
  allow you to file a bug report using the integrated bug reporting
  tool. This will gather information about your system and your
  installation process. The details will be sent to our bug tracker and
  a developer will attend to the problem as soon as possible."

  The box cannot be closed. No bug reporting tool launches. The computer
  requires restarting to become usable again.

  Please let me know if you need any more information as this is my
  first bug report.

  Thanks for your time,
  Matthew

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1351267/+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 1749095] Re: linux-euclid: 4.4.0-9025.27 -proposed tracker

2018-02-23 Thread Stefan Bader 
** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-euclid: 4.4.0-9025.27 -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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Invalid
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:
  Fix Released
Status in linux-euclid package in Ubuntu:
  Invalid
Status in linux-euclid 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: 1749089
  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/1749095/+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 1736954] Re: ppc64el: Do not call ibm, os-term on panic

2018-02-23 Thread Thadeu Lima de Souza Cascardo 
** Changed in: linux (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/1736954

Title:
  ppc64el: Do not call ibm,os-term on panic

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

Bug description:
  [Impact]
  When panic_timeout is set, the user would expect the system to reboot. 
However, it is shutdown, possibly requiring user intervention to power on the 
system again. This may impact availability. This happens under certain versions 
of qemu (2.10+) emulating pseries.

  [Test Case]
  Built kernels (trusty, xenial, zesty, artful) have been tested and they 
reboot after the fix, when running under an affected qemu.

  [Regression Potential]
  fadump might require that RTAS ibm,os-term be called. The fix should still 
allow it to be called when fadump is registered.

  
  ---

  When panic_timeout is set, the user would expect that the system would
  reboot after some timeout after a panic.

  However, on powerpc architecture, a panic notifier may not ever return
  and even shutdown the system. The main example that impacts platforms
  we support is pseries calling RTAS ibm,os-term.

  That panic notifier and calling RTAS ibm,os-term is useful for fadump,
  so this should not be impacted.

  The Linux code has changed back and forth on considering the
  panic_timeout setting and checking whether ibm,extended-os-term was
  available. Unfortunately, recent changes on qemu led to the guest
  being shut down when calling ibm,os-term even when ibm,extended-os-
  term was available.

  Luckily, upstream Linux already has the change that does not call ibm
  ,os-term on panic, but only during fadump. So, we can use that commit
  for fixing this. Changing qemu itself is harder as: 1) qemu community
  already decided some qemu settings should override PAPR; 2) updating
  deployed hypervisor is harder than updating our guest kernels.

  Cascardo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736954/+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 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package ubuntu-drivers-common - 1:0.4.17.6

---
ubuntu-drivers-common (1:0.4.17.6) xenial-proposed; urgency=medium

  * tests/ubuntu_drivers.py:
- Skip test_system_modaliases_system on s390x.
  Fixes FTBFS (LP: #1728547).

ubuntu-drivers-common (1:0.4.17.5) xenial-proposed; urgency=medium

  [ Alberto Milone ]
  * gpu-manager.{c|py}:
- Drop the amdgpu-pro code introduced in the previous upload,
  as it will be dealt with in a different upload.

  [ Alex Tu ]
  * gpu-manager.c:
- Skip bbswitch, and make sure to unload the nvidia driver when
  the force-dgpu-on option is enabled (LP: #1728547).

 -- Alberto Milone   Mon, 22 Jan 2018
12:48:54 +0100

** Changed in: ubuntu-drivers-common (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/1728547

Title:
  SRU: Add support for keeping the dGPU on in power saving mode

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed
Status in ubuntu-drivers-common source package in Artful:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Some systems don't play well when the dGPU is disabled. It should still be 
possible to use the Intel iGPU without disabling the dGPU.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Install the mesa-utils package:
  sudo apt install mesa-utils

  5) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  
  [Regression Potential]
  Low, as the feature is disabled by default. This is only for hardware 
specific workarounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728547/+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 1731873] Re: Backport amdgpu-pro support

2018-02-23 Thread Łukasz Zemczak 
As mentioned before, this change has been reverted from -proposed.

** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
   Status: Fix Released => Triaged

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

Title:
  Backport amdgpu-pro support

Status in OEM Priority Project:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Triaged
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Support for the amdgpu-pro driver has been available in Artful since May 
2017. We need to backport the code to the other stable releases.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the amdgpu-pro packages are installed (if not, install
  them, and restart your system).

  3) Check that power saving mode is supported:

  amdgpu-pro-px --ispx

  If it returns true, then it is supported by the hardware.

  4) Set power saving mode:

  sudo amdgpu-pro-px --mode powersaving

  5) Restart your computer and check that the "Enabling power saving
  mode for amdgpu-pro" line is in your /var/log/gpu-manager.log.

  6) Install the mesa-utils package:
  sudo apt install mesa-utils

  7) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  [Regression Potential]
  Low, as the feature is disabled by default, unless users set power saving 
manually.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1731873/+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 1731873] Re: Backport amdgpu-pro support

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package ubuntu-drivers-common - 1:0.4.17.6

---
ubuntu-drivers-common (1:0.4.17.6) xenial-proposed; urgency=medium

  * tests/ubuntu_drivers.py:
- Skip test_system_modaliases_system on s390x.
  Fixes FTBFS (LP: #1728547).

ubuntu-drivers-common (1:0.4.17.5) xenial-proposed; urgency=medium

  [ Alberto Milone ]
  * gpu-manager.{c|py}:
- Drop the amdgpu-pro code introduced in the previous upload,
  as it will be dealt with in a different upload.

  [ Alex Tu ]
  * gpu-manager.c:
- Skip bbswitch, and make sure to unload the nvidia driver when
  the force-dgpu-on option is enabled (LP: #1728547).

 -- Alberto Milone   Mon, 22 Jan 2018
12:48:54 +0100

** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
   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/1731873

Title:
  Backport amdgpu-pro support

Status in OEM Priority Project:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Triaged
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Support for the amdgpu-pro driver has been available in Artful since May 
2017. We need to backport the code to the other stable releases.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the amdgpu-pro packages are installed (if not, install
  them, and restart your system).

  3) Check that power saving mode is supported:

  amdgpu-pro-px --ispx

  If it returns true, then it is supported by the hardware.

  4) Set power saving mode:

  sudo amdgpu-pro-px --mode powersaving

  5) Restart your computer and check that the "Enabling power saving
  mode for amdgpu-pro" line is in your /var/log/gpu-manager.log.

  6) Install the mesa-utils package:
  sudo apt install mesa-utils

  7) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  [Regression Potential]
  Low, as the feature is disabled by default, unless users set power saving 
manually.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1731873/+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 1555904] Re: opal-prd not installed by default on ppc64el systems

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package hw-detect - 1.117ubuntu2.3

---
hw-detect (1.117ubuntu2.3) xenial; urgency=medium

  * hw-detect.sh: install opal-prd on OpenPOWER machines. LP: #1555904
  * Drop hw-detect.pre-pkgsel.d/20install-hwpackages, as it installs
universe package, which is probably in itself not useful on
Ubuntu. LP: #1577833

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 15:36:54
+

** Changed in: hw-detect (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/1555904

Title:
  opal-prd not installed by default on ppc64el systems

Status in The Ubuntu-power-systems project:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  In Progress
Status in hw-detect source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * opal-prd should be installed on OpenPOWER systems

  [Test Case]

   * install power system

   * check that /sys/firmware/devicetree/base/ibm,opal/diagnostics
  exists

   * if above is true, check that opal-prd package is installed

  [Regression Potential]

   * Additional package installation is performed, thus the install
  process may take longer, and additional disk space will be used.
  However the new code path is non-fatal, and all errors are ignored,
  thus all installation should still proceed past this point. For
  systems without relevant diagnostics exposed, this code path is a no-
  op.

  [Other Info]
   
   * Original bug report

  Just tried an install with current 16.04 network media, using standard
  server package selections, and it looks like opal-prd isn't installed
  by default:

   [jk@fstn ~]$ dpkg -l opal-prd
   dpkg-query: no packages found matching opal-prd

  This is required for RAS-type functions on OpenPOWER machines; and has
  a similar role to something like acpid, on x86.

  I'm not sure whether filing this against the skiboot package is best,
  or whether this should be moved to something installer-related. Happy
  to shift if necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1555904/+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 1577833] Re: Support statement for packages within Ubuntu 16.04 LTS should have the 5 Y statement

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package hw-detect - 1.117ubuntu2.3

---
hw-detect (1.117ubuntu2.3) xenial; urgency=medium

  * hw-detect.sh: install opal-prd on OpenPOWER machines. LP: #1555904
  * Drop hw-detect.pre-pkgsel.d/20install-hwpackages, as it installs
universe package, which is probably in itself not useful on
Ubuntu. LP: #1577833

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 15:36:54
+

** Changed in: hw-detect (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/1577833

Title:
  Support statement for packages within Ubuntu 16.04 LTS should have the
  5 Y statement

Status in Ubuntu Seeds:
  Fix Committed
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in hw-detect source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Default install of Ubuntu server, should not install universe
  packages, specifically discover

  [Test Case]

   * Use d-i installer, to perform a server-like install

   * Check that there are no universe packages installed by default

   * Specifically check that discover package is not installed

  [Regression Potential]

   * discover appears to be a useless package which does not enable any
  extra hardware at either install, or post-boot time. Less disk space
  is used, as well as less time, and non-supported package is not
  installed unconditionally onto the target systems.

  [Other Info]
   
   * Original bug report

  We detected following information

  Manuell Installation in Standard-Mode (not Expert Mode)with following
  selection: standard system utilities, OpenSSH server, Basic Ubuntu
  server for s390-tools:

  Following information are provided by the ubuntu-support-status tool.

  Supported until January 2017 (9m):
  libpfm4 s390-tools sysconfig-hardware

  Supported until April 2019 (3y):
  discover discover-data libdiscover2

  The assumption is, the 16.04 LTS will have 5 year support for each
  package within release/main

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1577833/+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 1608927] Re: fix postinst in s390-tools in xenial

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package s390-tools - 1.34.0-0ubuntu8.5

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

  * Correct postinst, which cleans up erroneous directory from
1.34.0-0ubuntu8 upload and earlier. LP: #1608927

 -- Dimitri John Ledkov   Wed, 21 Feb 2018 16:44:02
+

** Changed in: s390-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  fix postinst in s390-tools in xenial

Status in s390-tools package in Ubuntu:
  Invalid
Status in s390-tools source package in Xenial:
  Fix Released

Bug description:
  
  [Impact] 

   * On each upgrade there is an attempt to remove bogus directory which
  has been gone since 1.34.0-0ubuntu8.1, thus the guard to remove the
  directory should use the correct version number for xenial, i.e.
  1.34.0-0ubuntu8.1 not 1.34.0-0ubuntu10.

   * as per infinity, the version check is wrong firing on every
  upgrade.

  [Test Case]

   * install s390-tools from updates
   * upgrade to this new version from proposed
   * during this upgrade one should not see error message from rmdir

  Setting up s390-tools (1.34.0-0ubuntu8.5) ...
  rmdir: failed to remove '/3770': No such file or directory

  [Regression Potential]

   * This is a fixup of a typo in version check, it is a cosmetic change
  to make sure pointless warnings are not shown. There is little harm in
  trying to remove the bogus/gone directory. And even less harm in
  stopping to try to remove it going further.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1608927/+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 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.17

---
grub2 (2.02~beta2-36ubuntu3.17) xenial; urgency=medium

  * Signal to zpool that it should emit full names of constituent devices.
(LP: #1527727)

 -- Scott Moser   Wed, 24 Jan 2018 16:21:35 -0500

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

** Changed in: grub2-signed (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1527727/+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 1743638] Re: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package debian-installer -
20101020ubuntu451.22

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

  [ dann frazier ]
  * arm64-efi/netboot: Improvements to mini.iso generation:
- Add an EFI System Partition to fix booting from USB stick on
  same platforms LP: #1692876.
- Remove no-op arguments -boot-load-size and -boot-info-table.
- Use simpler "-e" instead of "--efi-boot" since we only have 1
  el torito image.
- Add -partition_offset 16 so that the output of commands like
  'isosize' is correct.
  * netboot/arm64: Include nic-firmware. LP: #1743638.

  [ Łukasz 'sil2100' Zemczak ]
  * Bump FLOPPY_SIZE on amd64, i386, and powerpc for kernel growth.

 -- Łukasz 'sil2100' Zemczak   Wed, 21 Feb
2018 10:43:54 +0100

** Changed in: debian-installer (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Committed
Status in debian-installer source package in Artful:
  Fix Committed
Status in linux source package in Artful:
  Fix Released
Status in linux-firmware source package in Artful:
  Fix Committed
Status in linux-hwe source package in Artful:
  Invalid
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-hwe source package in Bionic:
  Invalid
Status in linux-hwe-edge source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Network installs over a QLogic QED 25/40/100Gb Ethernet NIC will not work.

  [Test Case]
  Attempt to use the netinst installer to install a system over this NIC.

  [Regression Risk]
  The fix is just add to add additional kernel modules and firmware to the 
installer to support this NIC. The biggest risk I see there is that it 
increases the size of the installer, which could potentially grow to bit for 
some smaller systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1743638/+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 1692876] Re: ubuntu-server ARM64 ISOs lack partition table with EFI System Partition

2018-02-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package debian-installer -
20101020ubuntu451.22

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

  [ dann frazier ]
  * arm64-efi/netboot: Improvements to mini.iso generation:
- Add an EFI System Partition to fix booting from USB stick on
  same platforms LP: #1692876.
- Remove no-op arguments -boot-load-size and -boot-info-table.
- Use simpler "-e" instead of "--efi-boot" since we only have 1
  el torito image.
- Add -partition_offset 16 so that the output of commands like
  'isosize' is correct.
  * netboot/arm64: Include nic-firmware. LP: #1743638.

  [ Łukasz 'sil2100' Zemczak ]
  * Bump FLOPPY_SIZE on amd64, i386, and powerpc for kernel growth.

 -- Łukasz 'sil2100' Zemczak   Wed, 21 Feb
2018 10:43:54 +0100

** Changed in: debian-installer (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu-server ARM64 ISOs lack partition table with EFI System
  Partition

Status in Ubuntu CD Images:
  Fix Committed
Status in debian-installer package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  On some arm64/efi platforms, the firmware will not be able to boot from an 
ISO dd'd to a USB stick.

  [Test Case]
  My test is to attach the ISO as an "HD/USB Image" to a Cavium CRB1S w/ AMI 
UEFI firmware using the BMC's Virtual Media. Note that the BMC requires that 
the file be renamed with a ".img" suffix.

  [Regression Risk]
  For d-i, this is aligning the xorriso boot options with the same ones now 
used to build the server ISO. Regression risk has been mitigated by testing on 
real hardware connected as both CD and disk images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1692876/+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 1751280] Re: Backport fix for url from upstream

2018-02-23 Thread Ken VanDine 
** Also affects: fwupd (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/1751280

Title:
  Backport fix for url from upstream

Status in fwupd package in Ubuntu:
  New
Status in fwupd source package in Xenial:
  New

Bug description:
  Upstream has updated the url for downloads to be more future proof.

  Please backport this fix for 16.04:

  
https://github.com/hughsie/fwupd/commit/cbb228c7c34c99cfe98caf13f4699731535c65e5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1751280/+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 1751225] Re: apt update hangs when repository url is redirect url

2018-02-23 Thread Julian Andres Klode 
OK, so:

xenial: affected
artful, bionic: NOT affected

So I might just want to revert this commit in an apt 1.2.26 release and
look at it again later.

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

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

Title:
  apt update hangs when repository url is redirect url

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Artful:
  Invalid

Bug description:
  [Impact]

  When using redirect url on /etc/apt/sources.list

  apt update command hangs

  this is affected with commit
  
https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1

  In my test, moving below[1] code after[2]

  [1]
  ###
  if (ContentLength == 0)
  return true;
  ###
  [2]
  if (Encoding == Closes)
  Encoding = Stream;

  ###

  it worked fine.

  [Test Case]

  echo "deb http://packages.cloudfoundry.org/debian stable main" >
  /etc/apt/sources.list.d/cloudfoundry-cli.list

  apt update

  [Regression]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1751225/+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 1751225] Re: apt update hangs when repository url is redirect url

2018-02-23 Thread Julian Andres Klode 
OK, so I need to dig a bit further into this. I think if I move the if I
break things elsewhere. IIRC, I added the if that early because, when
apt received a redirect with Content-Length: 0, it started hanging, and
that fixed it. But maybe it breaks some other stuff now.

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

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

Title:
  apt update hangs when repository url is redirect url

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  Triaged
Status in apt source package in Artful:
  New

Bug description:
  [Impact]

  When using redirect url on /etc/apt/sources.list

  apt update command hangs

  this is affected with commit
  
https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1

  In my test, moving below[1] code after[2]

  [1]
  ###
  if (ContentLength == 0)
  return true;
  ###
  [2]
  if (Encoding == Closes)
  Encoding = Stream;

  ###

  it worked fine.

  [Test Case]

  echo "deb http://packages.cloudfoundry.org/debian stable main" >
  /etc/apt/sources.list.d/cloudfoundry-cli.list

  apt update

  [Regression]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1751225/+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 1751225] Re: apt update hangs when repository url is redirect url

2018-02-23 Thread Julian Andres Klode 
Ack, that seems to make sense. Strange.

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

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

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

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

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

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

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

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

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Changed in: apt (Ubuntu Xenial)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Changed in: apt (Ubuntu Artful)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  apt update hangs when repository url is redirect url

Status in apt package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Triaged
Status in apt source package in Artful:
  Triaged

Bug description:
  [Impact]

  When using redirect url on /etc/apt/sources.list

  apt update command hangs

  this is affected with commit
  
https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1

  In my test, moving below[1] code after[2]

  [1]
  ###
  if (ContentLength == 0)
  return true;
  ###
  [2]
  if (Encoding == Closes)
  Encoding = Stream;

  ###

  it worked fine.

  [Test Case]

  echo "deb http://packages.cloudfoundry.org/debian stable main" >
  /etc/apt/sources.list.d/cloudfoundry-cli.list

  apt update

  [Regression]
  TBD

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