[Group.of.nepali.translators] [Bug 1657909] Re: SSH service should be hidden from Startup Applications too

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-keyring - 3.20.0-3ubuntu1

---
gnome-keyring (3.20.0-3ubuntu1) zesty; urgency=medium

  * Merge with Debian. Remaining changes:
- debian/control.in:
  + Add Vcs-Bzr for Ubuntu.
- debian/control, debian/*.install, debian/rules:
  + Install pkcs11 in its own binary.
- debian/gnome-keyring.ubiquity, debian/rules:
  + Apply capabilities at the end of the ubiquity process to make sure new
installs have gnome-keyring-daemon with cap_ipc_lock+ep.
- debian/gnome-keyring.conf, debian/gnome-keyring-ssh.conf:
  + Provide upstart user session jobs.
- debian/user/*, debian/*.override, debian/rules:
  + Install units to start gnome-keyring with systemd if the session
is using it.
  + Disable XDG autostart when we're using upstart.
- 04_nodisplay_autostart.patch:
  + Mark autostart files as NoDisplay=true.
- 0001-Look-for-both-dlopen-and-dlsym-when-configuring.patch:
  + Fix finding dlopen and dlsym in the build, fixing FTBFS.
- 0002-pam-Pass-the-correct-argc-to-gkr_pam_client_run_oper.patch:
  + Fix null pointer dereference when no password is supplied, e.g. in
lightdm --test-mode.
- 0001-Die-if-the-XDG-session-we-were-started-under-goes-aw.patch:
  + Cherry-pick upstream patch to track our login session and exit if
that ends. This means that gnome-keyring gets cleaned up properly
on logout under dbus-user-session.
  * Update 04_nodisplay_autostart.patch to hide SSH service too
(LP: #1657909)

gnome-keyring (3.20.0-3) unstable; urgency=medium

  [ Jeremy Bicha ]
  * Enable parallel building and all hardening flags
  * Add debian/patches/05_skip-known-test-failures.patch:
- Skip a few failing tests that have already been reported upstream.
  Before the switch from cdbs to dh, these tests still failed but did
  not fail the build and therefore were mostly unnoticed.
  * Explicitly Build-Depend on python for tests (Closes: #832852)

  [ Dmitry Shachnev ]
  * Depend on default-dbus-session-bus | dbus-session-bus instead of
dbus-x11 (closes: #835885).

 -- Jeremy Bicha   Thu, 19 Jan 2017 20:04:08 -0500

** Changed in: gnome-keyring (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/1657909

Title:
  SSH service should be hidden from Startup Applications too

Status in gnome-keyring package in Ubuntu:
  Fix Released
Status in gnome-keyring source package in Trusty:
  Triaged
Status in gnome-keyring source package in Xenial:
  In Progress
Status in gnome-keyring source package in Yakkety:
  In Progress

Bug description:
  SRU Team
  
  Wait to accept this. Showing the SSH service was apparently intentional and 
not just an oversight.
  https://launchpad.net/ubuntu/+source/gnome-keyring/3.10.1-1ubuntu4.2

  Impact
  ==
  Ubuntu has for several years set NoDisplay=true for various services that use 
/etc/xdg/autostart so that users don't open Startup Applications and turn off a 
service that isn't really meant to be disabled that way

  gnome-keyring has a patch to do this, but one service "SSH Key Agent"
  needs to be added to the patch.

  Test Case
  =
  Install the updated gnome-keyring package.
  Open Startup Applications in Ubuntu (Unity) or Ubuntu GNOME
  "SSH Key Agent" should not show up in the list.

  Regression Potential
  
  Low. If someone *did* uncheck the box next to SSH in Startup Applications, it 
will now be a bit more tricky to re-enable that service.

  rm ~/.local/share/autostart/gnome-keyring-ssh.desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1657909/+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 1657433] Re: linux-snapdragon: 4.4.0-1046.50 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1657433

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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 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-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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1657430
  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/1657433/+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 1657432] Re: linux-raspi2: 4.4.0-1042.49 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1657432

Title:
  linux-raspi2: 4.4.0-1042.49 -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:
  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-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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1657430
  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/1657432/+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 1657430] Re: linux: 4.4.0-62.83 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1657430

Title:
  linux: 4.4.0-62.83 -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:
  Confirmed
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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+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 1637223] Re: Update to newer version of docker-compose >= 1.6

[Michael Hudson-Doyle]

Ugh, it seems that a new version of python-websocket is required too,
and that has some non-trivial reverse dependencies. Maybe they'll be
fine but it requires a bit of investigation that I'm afraid I don't have
time for any more this week :(

** Also affects: python-docker (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: docker-compose (Ubuntu Yakkety)
   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/1637223

Title:
  Update to newer version of docker-compose >= 1.6

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in docker-compose package in Ubuntu:
  Invalid
Status in python-docker package in Ubuntu:
  Invalid
Status in docker-compose source package in Xenial:
  Confirmed
Status in python-docker source package in Xenial:
  Confirmed
Status in docker-compose source package in Yakkety:
  New
Status in python-docker source package in Yakkety:
  New

Bug description:
  Ubuntu 16.04.1 does not contain latest docker-compose release needed
  to handle v2 yml files. As minimum level 1.6 has to be integrated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1637223/+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 1657909] [NEW] SSH service should be hidden from Startup Applications too

[Jeremy Bicha]

Public bug reported:

Impact
==
Ubuntu has for several years set NoDisplay=true for various services that use 
/etc/xdg/autostart so that users don't open Startup Applications and turn off a 
service that isn't really meant to be disabled that way

gnome-keyring has a patch to do this, but one service "SSH Key Agent"
needs to be added to the patch.

Test Case
=
Install the updated gnome-keyring package.
Open Startup Applications in Ubuntu (Unity) or Ubuntu GNOME
"SSH Key Agent" should not show up in the list.

Regression Potential

Low. If someone *did* uncheck the box next to SSH in Startup Applications, it 
will now be a bit more tricky to re-enable that service.

rm ~/.local/share/autostart/gnome-keyring-ssh.desktop

** Affects: gnome-keyring (Ubuntu)
 Importance: Low
 Status: Fix Committed

** Affects: gnome-keyring (Ubuntu Trusty)
 Importance: Low
 Status: Triaged

** Affects: gnome-keyring (Ubuntu Xenial)
 Importance: Low
 Status: In Progress

** Affects: gnome-keyring (Ubuntu Yakkety)
 Importance: Low
 Status: In Progress


** Tags: xenial yakkety

** Also affects: gnome-keyring (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: gnome-keyring (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: gnome-keyring (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: gnome-keyring (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: gnome-keyring (Ubuntu Yakkety)
   Importance: Undecided => Low

** Changed in: gnome-keyring (Ubuntu Yakkety)
   Status: New => In Progress

** Also affects: gnome-keyring (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: gnome-keyring (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: gnome-keyring (Ubuntu Trusty)
   Status: New => Triaged

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

Title:
  SSH service should be hidden from Startup Applications too

Status in gnome-keyring package in Ubuntu:
  Fix Committed
Status in gnome-keyring source package in Trusty:
  Triaged
Status in gnome-keyring source package in Xenial:
  In Progress
Status in gnome-keyring source package in Yakkety:
  In Progress

Bug description:
  Impact
  ==
  Ubuntu has for several years set NoDisplay=true for various services that use 
/etc/xdg/autostart so that users don't open Startup Applications and turn off a 
service that isn't really meant to be disabled that way

  gnome-keyring has a patch to do this, but one service "SSH Key Agent"
  needs to be added to the patch.

  Test Case
  =
  Install the updated gnome-keyring package.
  Open Startup Applications in Ubuntu (Unity) or Ubuntu GNOME
  "SSH Key Agent" should not show up in the list.

  Regression Potential
  
  Low. If someone *did* uncheck the box next to SSH in Startup Applications, it 
will now be a bit more tricky to re-enable that service.

  rm ~/.local/share/autostart/gnome-keyring-ssh.desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1657909/+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 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel

[Joseph Salisbury]

I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.

Can you test the following kernels and report back? We are looking for
the first kernel version that exhibits this bug:

3.13 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/
3.16 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-utopic/
4.0 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/
4.2 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-wily/
4.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/


You don't have to test every kernel, just up until the kernel that first has 
this bug.

Thanks in advance!

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

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

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

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

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

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

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

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

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

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

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

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

** Tags removed: kernel-da-key
** Tags added: kernel-key

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

Title:
  System won't boot after upgrade to 16.04 with 4.4.0 kernel

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

Bug description:
  I have a Dell PowerEdge 1800 with Dell CERC 1.5/6ch RAID controller in
  it. Everything worked fine under Ubuntu 14.04.1. When I upgraded to
  16.04.1 the system won't boot. It can't find the root filesystem. I
  see errors about host adapter dead on the screen many times. This is
  with kernel 4.4.0-57 and with 4.8.0-32. When I switch back to kernel
  3.13.0-105 the system boots just fine.

  I have mptbios 5.06.04.
  The CERC card says bios version 4.1-0 [Build 7403]

  When booting into the ercovery kernel I'm getting error messages about host 
adapter dead.
  Eventually I get a message:
  "aacraid: aac_fib_send: first asynchronous command timed out.
  Usually a result of a PCI interrupt routing problem
  update moher board BIOS or consider utilizing one of
  the SAFE mode kernel options (acpi, apic etc)"

  
  Using kernel parameter "intel_iommu=on" doesn't help. This was suggested on a 
post that I saw about these errors.

  Booting with "noapic" didn't help.
  Booting with "noapic noacpi" didn't help.

  
  I've also tried the dkms modules from Adaptec and that doesn't seem to help 
either.

  
  I can't figure out how to upgrade the firmware or BIOS on the system from 
Ubuntu either.

  
  This may be related to this bug: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551?comments=all
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=beec17b5-eac8-4e94-ac99-65b63c428b77
  InstallationDate: Installed on 2014-02-24 (1039 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  IwConfig:
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Computer Corporation PowerEdge 1800
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic 
root=UUID=83e1b87e-adb9-4798-a6e0-18d401c91a4a ro nosplash noplymouth
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   

[Group.of.nepali.translators] [Bug 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10

[Joseph Salisbury]

I see commit 59107e2f4 in mainline:
59107e2f4883 x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic

However, I don't see 56ef6718a as of yet.  Do you have a patch
available?

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

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

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

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

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

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

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

Title:
  Kdump through NMI SMP and single core not working on Ubuntu16.10

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  During some tests I've encountered an issue with kdump through NMI SMP
  and single core. After kdump configuration, when I trigger the crash
  through an NMI call from the host, the VM will panic, however it will
  not write the vmcore dump files and neither reboot.

  REPRO STEPS:

  1. configure kdump
   - crashkernel=512M-:384M  /boot/grub/grub.cfg
   - USE_KDUMP=1 /etc/default/kdump-tools

  2. after configuration reboot the VM

  3. check kdump status
   - cat /sys/kernel/kexec_*
   - service kdump-tools status

  4. configure NMI
   - sysctl -w kernel.unknown_nmi_panic=1

  5. trigger a crash from host
   - Debug-VM -Name $vmName -InjectNonMaskableInterrupt -ComputerName $hvServer 
-Force

  This case also applies to:
  -Ubuntu 16.10 generation 2(kernel version: 4.8.0-17-generic)
  -Ubuntu 16.04.1(kernel: 4.4.0-38-generic)
  -Ubuntu 14.04.5(kernel: 3.19.0-69-generic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630924/+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 1643585] Re: Backporting gce-compute-image-packages

[Launchpad Bug Tracker]

This bug was fixed in the package gce-compute-image-packages -
20160930-0ubuntu3~16.04.0

---
gce-compute-image-packages (20160930-0ubuntu3~16.04.0) xenial; urgency=medium

  * Backport gce-compute-image-packages to xenial (LP: #1643585)

 -- Phil Roche   Thu, 25 Nov 2016 14:01:00
+

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

Title:
  Backporting gce-compute-image-packages

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

Bug description:
  [Impact]

   * GCE no longer wish to use gce-utils and instead want to use the new
  gce-compute-image-packages package

   * All supported versions of Ubuntu on GCE should have gce-compute-
  image-packages installed to avail of any new features on GCE

  [Test Case]

   * There are no bugs to reproduce as this is a new package.

   * There are numerous tests:
 * ntp conf
 * expected packages are installed
 * expected services are running
 * SSH access
 * Kernel Config
 * Hosts file is as expected

  These run as part of Ubuntu cloud image for GCE creation. These tests
  have been updated to test any changes introduced by gce-compute-image-
  packages. All of these tests pass.

   * The simplest way to test this package is to launch a GCE instance
  with this package installed [2] and test that it is reachable via SSH
  using the keys specified when launching. Also check that any startup
  scripts specified are run and that NTP has set the time correctly.

  [Regression Potential]

   * Most harmful regression potential is GCE instance becoming
  unreachable. This was the case with gce-utils too though.

  [Other Info]

   * This change has been requested by GCE and is a requirement for any
  future Ubuntu cloud images for GCE. They are very eager to get this
  backported.

  [1] https://launchpad.net/ubuntu/+source/gce-utils
  [2] "/ubuntu-os-cloud-devel/daily-ubuntu-testing-1610-yakkety-v20161110"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585/+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 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update

[Joseph Salisbury]

Does this bug go away if you boot back into the prior kernel version?


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

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

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

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

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

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

Title:
  Laptop stick and touchpad problems after linux 4.4 update

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

Bug description:
  Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have 
behaved erratically on my Dell Precision 7510:
  * The trackpoint moves WAY too fast and there don't seem to be any parameters 
I can change in xinput to fix this. It is essentially unusable.
  * The touchpad starts with parameters set incorrectly.
  * Touchpad tap to click is now turned on again and is very sensitive. This I 
can change through xinput but the change is still odd.
  * The two finger scrolling is set incorrectly to be highly sensitive. This I 
can also change through xinput.
  * Two finger scrolling still activates often during normal use of the 
trackpad. To the extent that I had to turn off two finger scrolling to stop 
inadvertent scrolling.

  All of the above behavior is new going from 4.4.0-47 to -53.
  Previously this all worked perfectly on this machine.

  Seems to be symptoms noted by these other users on askubuntu here as
  well: http://askubuntu.com/questions/862527/laptop-stick-mouse-
  problems-after-linux-4-4-update-on-14-04

  The touchpad symptoms I seem to be able to work around my changing
  xinput parameters, but the trackpoint I have not been able to fix at
  all (which is sad since that is my primary mouse device normally).
  Would appreciate any suggestions as to how to revert the old behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpeverill   2813 F pulseaudio
   /dev/snd/controlC0:  jpeverill   2813 F pulseaudio
  Date: Wed Jan 18 10:21:55 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-17 (916 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
  dmi.bios.date: 01/24/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657553/+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 1655934] Re: update-grub-legacy-ec2 should detect -aws kernels as appropriate for EC2

[Scott Moser]

** Description changed:

  [Impact]
  PV images built with AWS custom kernels currently won't boot because their 
kernels aren't detected.
  
  [Test Case]
  * Launch an HVM instance
  * Run update-grub-legacy-ec2 and see an error message like "Ignoring non-Xen 
Kernel on Xen domU host: vmlinuz-4.4.0-1001-aws"
  * Install the new package
  * Run update-grub-legacy-ec2 again and see success like:
  Found kernel: /boot/vmlinuz-4.4.0-1001-aws
  Found kernel: /boot/vmlinuz-4.4.0-1001-aws
  Updating /boot/grub/menu.lst ... done
  
  [Regression Potential]
  This is a single line change to a case statement; regression potential is 
minimal.
  
  [Original Report]
  Currently, it will detect -ec2 kernels, but we also need it to detect -aws 
kernels.
+ 
+ Related bugs:
+  * bug 1379080: update-grub-legacy-ec2 fails to detect xen kernel

** No longer affects: cloud-init (Ubuntu Trusty)

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

Title:
  update-grub-legacy-ec2 should detect -aws kernels as appropriate for
  EC2

Status in cloud-init package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  PV images built with AWS custom kernels currently won't boot because their 
kernels aren't detected.

  [Test Case]
  * Launch an HVM instance
  * Run update-grub-legacy-ec2 and see an error message like "Ignoring non-Xen 
Kernel on Xen domU host: vmlinuz-4.4.0-1001-aws"
  * Install the new package
  * Run update-grub-legacy-ec2 again and see success like:
  Found kernel: /boot/vmlinuz-4.4.0-1001-aws
  Found kernel: /boot/vmlinuz-4.4.0-1001-aws
  Updating /boot/grub/menu.lst ... done

  [Regression Potential]
  This is a single line change to a case statement; regression potential is 
minimal.

  [Original Report]
  Currently, it will detect -ec2 kernels, but we also need it to detect -aws 
kernels.

  Related bugs:
   * bug 1379080: update-grub-legacy-ec2 fails to detect xen kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1655934/+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 1626972] Re: QEMU memfd_create fallback mechanism change for security drivers

[Launchpad Bug Tracker]

This bug was fixed in the package qemu - 1:2.6.1+dfsg-0ubuntu5.2

---
qemu (1:2.6.1+dfsg-0ubuntu5.2) yakkety; urgency=medium

  [ Rafael David Tinoco ]
  * Fixed wrong migration blocker when vhost is used (LP: #1626972)
- d/p/vhost_migration-blocker-only-if-shared-log-is-used.patch

 -- Christian Ehrhardt   Tue, 22 Nov
2016 13:45:46 +0100

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

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

Title:
  QEMU memfd_create fallback mechanism change for security drivers

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in QEMU:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Fix Committed
Status in qemu source package in Yakkety:
  Fix Released
Status in qemu source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Updated QEMU (from UCA) live migration doesn't work with 3.13 kernels.
   * QEMU code checks if it can create /tmp/memfd-XXX files wrongly.
   * Apparmor will block access to /tmp/ and QEMU will fail migrating.

  [Test Case]

   * Install 2 Ubuntu Trusty (3.13) + UCA Mitaka + apparmor rules.
   * Try to live-migration from one to another. 
   * Apparmor will block creation of /tmp/memfd-XXX files.

  [Regression Potential]

   Pros:
   * Exhaustively tested this.
   * Worked with upstream on this fix. 
   * I'm implementing new vhost log mechanism for upstream.
   * One line change to a blocker that is already broken.

   Cons:
   * To break live migration in other circumstances. 

  [Other Info]

   * Christian Ehrhardt has been following this.

  ORIGINAL DESCRIPTION:

  When libvirt starts using apparmor, and creating apparmor profiles for
  every virtual machine created in the compute nodes, mitaka qemu (2.5 -
  and upstream also) uses a fallback mechanism for creating shared
  memory for live-migrations. This fall back mechanism, on kernels 3.13
  - that don't have memfd_create() system-call, try to create files on
  /tmp/ directory and fails.. causing live-migration not to work.

  Trusty with kernel 3.13 + Mitaka with qemu 2.5 + apparmor capability =
  can't live migrate.

  From qemu 2.5, logic is on :

  void *qemu_memfd_alloc(const char *name, size_t size, unsigned int seals, int 
*fd)
  {
  if (memfd_create)... ### only works with HWE kernels

  else ### 3.13 kernels, gets blocked by apparmor
     tmpdir = g_get_tmp_dir
     ...
     mfd = mkstemp(fname)
  }

  And you can see the errors:

  From the host trying to send the virtual machine:

  2016-08-15 16:36:26.160 1974 ERROR nova.virt.libvirt.driver 
[req-0cac612b-8d53-4610-b773-d07ad6bacb91 691a581cfa7046278380ce82b1c38ddd 
133ebc3585c041aebaead8c062cd6511 - - -] [instance: 
2afa1131-bc8c-43d2-9c4a-962c1bf7723e] Migration operation has aborted
  2016-08-15 16:36:26.248 1974 ERROR nova.virt.libvirt.driver 
[req-0cac612b-8d53-4610-b773-d07ad6bacb91 691a581cfa7046278380ce82b1c38ddd 
133ebc3585c041aebaead8c062cd6511 - - -] [instance: 
2afa1131-bc8c-43d2-9c4a-962c1bf7723e] Live Migration failure: internal error: 
unable to execute QEMU command 'migrate': Migration disabled: failed to 
allocate shared memory

  From the host trying to receive the virtual machine:

  Aug 15 16:36:19 tkcompute01 kernel: [ 1194.356794] type=1400 
audit(1471289779.791:72): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="libvirt-2afa1131-bc8c-43d2-9c4a-962c1bf7723e" 
pid=12565 comm="apparmor_parser"
  Aug 15 16:36:19 tkcompute01 kernel: [ 1194.357048] type=1400 
audit(1471289779.791:73): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="qemu_bridge_helper" pid=12565 comm="apparmor_parser"
  Aug 15 16:36:20 tkcompute01 kernel: [ 1194.877027] type=1400 
audit(1471289780.311:74): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="libvirt-2afa1131-bc8c-43d2-9c4a-962c1bf7723e" 
pid=12613 comm="apparmor_parser"
  Aug 15 16:36:20 tkcompute01 kernel: [ 1194.904407] type=1400 
audit(1471289780.343:75): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="qemu_bridge_helper" pid=12613 comm="apparmor_parser"
  Aug 15 16:36:20 tkcompute01 kernel: [ 1194.973064] type=1400 
audit(1471289780.407:76): apparmor="DENIED" operation="mknod" 
profile="libvirt-2afa1131-bc8c-43d2-9c4a-962c1bf7723e" name="/tmp/memfd-tNpKSj" 
pid=12625 comm="qemu-system-x86" requested_mask="c" denied_mask="c" fsuid=107 
ouid=107
  Aug 15 16:36:20 tkcompute01 kernel: [ 1194.979871] type=1400 
audit(1471289780.411:77): apparmor="DENIED" operation="open" 
profile="libvirt-2afa1131-bc8c-43d2-9c4a-962c1bf7723e" name="/tmp/" pid=12625 
comm="qemu-system-x86" requested_mask="r" 

[Group.of.nepali.translators] [Bug 1653278] Re: Update gss-ntlmssp to 0.7.0 to correct sequence numbering mismatch

[Timo Aaltonen]

fixed in zesty, I'll prep sru for xenial & yakkety

** Also affects: gss-ntlmssp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gss-ntlmssp (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: gss-ntlmssp (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: gss-ntlmssp (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Update gss-ntlmssp to 0.7.0 to correct sequence numbering mismatch

Status in gss-ntlmssp package in Ubuntu:
  Fix Released
Status in gss-ntlmssp source package in Xenial:
  New
Status in gss-ntlmssp source package in Yakkety:
  New

Bug description:
  gss-ntlmmssp sequence numbers are incorrect in 0.6.0. In 0.7.0 the
  following patch (which is most of the difference between the two
  versions) fixes sequence numbers. We discovered this testing OMI from
  Linux to Windows, but don't have a simpler test case we can provide.

  ./ntlm_crypto.c
  564a565,592
  > int ntlm_reset_rc4_state(uint32_t flags, bool recv,
  >  struct ntlm_key *session_key,
  >  struct ntlm_signseal_state *state)
  > {
  > struct ntlm_buffer rc4_key;
  > int ret;
  >
  > if (!(flags & NTLMSSP_NEGOTIATE_EXTENDED_SESSIONSECURITY)) {
  > return no_ext_sec_handle(flags, session_key,
  >  >send.seal_handle);
  > }
  >
  > if (recv) {
  > RC4_FREE(>recv.seal_handle);
  > rc4_key.data = state->recv.seal_key.data;
  > rc4_key.length = state->recv.seal_key.length;
  > ret = RC4_INIT(_key, NTLM_CIPHER_DECRYPT,
  >>recv.seal_handle);
  > } else {
  > RC4_FREE(>send.seal_handle);
  > rc4_key.data = state->send.seal_key.data;
  > rc4_key.length = state->send.seal_key.length;
  > ret = RC4_INIT(_key, NTLM_CIPHER_ENCRYPT,
  >>send.seal_handle);
  > }
  > return ret;
  > }./gss_sec_ctx.c
  432a433
  > if (actual_mech_type) *actual_mech_type = 
discard_const(_oid);
  992a994
  > if (mech_type) *mech_type = discard_const(_oid);
  1093a1096,1153
  > uint32_t gssntlm_set_seq_num(uint32_t *minor_status,
  >  struct gssntlm_ctx *ctx,
  >  const gss_buffer_t value)
  > {
  > uint32_t retmin;
  > uint32_t retmaj;
  >
  > if (ctx->gss_flags & GSS_C_DATAGRAM_FLAG) {
  > if (value->length != 4) {
  > return GSSERRS(ERR_BADARG, GSS_S_FAILURE);
  > }
  > memcpy(>crypto_state.recv.seq_num,
  >value->value, value->length);
  > ctx->crypto_state.send.seq_num = ctx->crypto_state.recv.seq_num;
  > } else {
  > return GSSERRS(ERR_WRONGCTX, GSS_S_FAILURE);
  > }
  >
  > return GSSERRS(0, GSS_S_COMPLETE);
  > }
  >
  > gss_OID_desc reset_crypto_oid = {
  > GSS_NTLMSSP_RESET_CRYPTO_OID_LENGTH,
  > discard_const(GSS_NTLMSSP_RESET_CRYPTO_OID_STRING)
  > };
  >
  > uint32_t gssntlm_reset_crypto(uint32_t *minor_status,
  >   struct gssntlm_ctx *ctx,
  >   const gss_buffer_t value)
  > {
  > uint32_t retmin;
  > uint32_t retmaj;
  >
  > if (value->length != 4) {
  > return GSSERRS(ERR_BADARG, GSS_S_FAILURE);
  > }
  >
  > /* reset crypto state */
  > if (ctx->neg_flags & (NTLMSSP_NEGOTIATE_SIGN |
  > NTLMSSP_NEGOTIATE_SEAL)) {
  > uint32_t val;
  >
  > memcpy(, value->value, value->length);
  >
  > /* A val of 1 means we want to reset the verifier handle,
  >  * which is the receive handle for NTLM, otherwise we reset
  >  * the send handle. */
  > retmin = ntlm_reset_rc4_state(ctx->neg_flags, (val == 1),
  >   >exported_session_key,

  >   >crypto_state);
  > if (retmin) {
  > return GSSERRS(retmin, GSS_S_FAILURE);
  > }
  > }
  >
  > return GSSERRS(0, GSS_S_COMPLETE);
  > }
  >
  1114,1129c1174,1176
  < if (ctx->gss_flags & GSS_C_DATAGRAM_FLAG) {
  <
  < if (value->length != 4) {
  < set_GSSERR(ERR_BADARG);
  < goto done;
  < }
  <
  < memcpy(>crypto_state.recv.seq_num,
  value, value->length);
  < ctx->crypto_state.send.seq_num = ctx->crypto_state.recv.seq_num;
  < set_GSSERRS(0, GSS_S_COMPLETE);
  < goto done;
  < } else {
  < set_GSSERRS(ERR_WRONGCTX, GSS_S_FAILURE);
  < goto done;
  < }
  ---
  > return 

[Group.of.nepali.translators] [Bug 1577460] Re: mkinitramfs --help > Core dumped

[Frank Heimes]

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

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in glibc source package in Xenial:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in glibc source package in Yakkety:
  Fix Released
Status in util-linux source package in Yakkety:
  Fix Committed

Bug description:
  [Testcase]
  * $ LC_ALL=fo_FOO.UTF-8 getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- 
--help
  Expected result:
/usr/sbin/mkinitramfs: unrecognized option '--help'
 --
Exit code 1
  Current result:
Segmentation fault
Exit code 139.

  There are two bugs in play here. glibc bug was fixed, and util-linux
  bug needs an upload still.

  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d ,
  s1@entry=0x2e6575634a500a6a ,
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, argv=0x40,
  optstring=0x20030 , longopts=,
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=,
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=,
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1577460/+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 1596968] Re: fail to activate fcp device for installation

[Frank Heimes]

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

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

Title:
  fail to activate fcp device for installation

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in s390-zfcp package in Ubuntu:
  Fix Released
Status in s390-zfcp source package in Xenial:
  Fix Released

Bug description:
  [Test case]
  * Start installation with many zfcp devices >>100
  * It should be able to complete zfcp device activation

  == Comment: #0 - XIANG ZHANG  - 2016-06-20 09:28:02 ==
  ---Problem Description---
  Can not activate FCP devices for installation

  ---uname output---
  Linux ilablnx3 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:26:02 UTC 2016 
s390x s390x s390x GNU/Linux

  Machine Type = z13 lpar

  ---boot type---
  Network boot

  ---Install repository type---
  Local repository

  ---Install repository Location---
  9.11.56.168:/OS_IMAGE/ISO/ubuntu/s390

  ---Point of failure---
  Other failure during installation (stage 1)

  I am installing a sanboot s390 ubuntu server via ftp server on a
  native lpar.  But I am not able to activate fcp device for
  installation. However I am able active the fcp device and attach san
  boot lun via shell.

  echo  1 > /sys/bus/ccw/driver/zfcp/0.0.1800/online
  echo 0x > 
/sys/bus/ccw/driver/zfcp/0.0.1800/0x5005076802401ee8/unit_add

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1596968/+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 1637223] Re: Update to newer version of docker-compose >= 1.6

[Dimitri John Ledkov]

** Also affects: docker-compose (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: docker-compose (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: docker-compose (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: docker-compose (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: docker-compose (Ubuntu Xenial)
Milestone: None => xenial-updates

** Changed in: docker-compose (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: docker-compose (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Dimitri John 
Ledkov (xnox)

** Also affects: python-docker (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: python-docker (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: python-docker (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: python-docker (Ubuntu)
   Status: New => Invalid

** Changed in: python-docker (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: python-docker (Ubuntu Xenial)
Milestone: None => xenial-updates

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

Title:
  Update to newer version of docker-compose >= 1.6

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in docker-compose package in Ubuntu:
  Invalid
Status in python-docker package in Ubuntu:
  Invalid
Status in docker-compose source package in Xenial:
  Confirmed
Status in python-docker source package in Xenial:
  Confirmed

Bug description:
  Ubuntu 16.04.1 does not contain latest docker-compose release needed
  to handle v2 yml files. As minimum level 1.6 has to be integrated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1637223/+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 1577460] Re: mkinitramfs --help > Core dumped

[Launchpad Bug Tracker]

This bug was fixed in the package util-linux - 2.27.1-6ubuntu3.2

---
util-linux (2.27.1-6ubuntu3.2) xenial; urgency=medium

  * Cherrypick upstream fix to prevent segfaults in getopt by ensuring
that options array is correctly terminated. LP: #1577460

 -- Dimitri John Ledkov   Fri, 16 Dec 2016 14:49:06
+

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

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in glibc source package in Xenial:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in glibc source package in Yakkety:
  Fix Released
Status in util-linux source package in Yakkety:
  Fix Committed

Bug description:
  [Testcase]
  * $ LC_ALL=fo_FOO.UTF-8 getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- 
--help
  Expected result:
/usr/sbin/mkinitramfs: unrecognized option '--help'
 --
Exit code 1
  Current result:
Segmentation fault
Exit code 139.

  There are two bugs in play here. glibc bug was fixed, and util-linux
  bug needs an upload still.

  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d ,
  s1@entry=0x2e6575634a500a6a ,
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, argv=0x40,
  optstring=0x20030 , longopts=,
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=,
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=,
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1577460/+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 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package

[Launchpad Bug Tracker]

This bug was fixed in the package glib2.0 - 2.50.2-2ubuntu1

---
glib2.0 (2.50.2-2ubuntu1) yakkety; urgency=medium

  * No-change backport of this stable release from unstable to 16.04 (LP:
#1644320)
  * Should fix trashing of files in symlinked directories (LP: #1638245)
  * Should fix display of trash on external drives (LP: #1633824)

glib2.0 (2.50.2-2) unstable; urgency=medium

  * debian/rules: disable libmount on !linux (Closes: #844052)
  * debian/patches/0001-Fix-trashing-on-overlayfs.patch: Update with new
version from the upsstream report to hopefully fix trashing of files in
directories which are symlinks to different devices. (Closes: #800047)

glib2.0 (2.50.2-1) unstable; urgency=medium

  * New upstream release.
  * Track stable releases in debian/watch.

glib2.0 (2.50.1-1) unstable; urgency=medium

  [ Jason Crain ]
  * libglib2.0-bin: includes a new 'gio' commandline tool (Closes: #840164)

  [ Andreas Henriksson ]
  * New upstream release.

glib2.0 (2.50.0-2) unstable; urgency=medium

  [ Simon McVittie ]
  * Build-depend on tzdata, which is no longer transitively Essential.
One test needs it. (Closes: #839487)

  [ Michael Biebl ]
  * Fix Vcs-* to point to unstable.
  * Mark dependencies which are required to run the test-suite with
.
  * Add explicit Build-Depends on xsltproc, docbook-xml and docbook-xsl.
Besides libxml2-utils, those are needed for building the man pages.
  * Drop Build-Depends on dbus-x11. The test-suite uses a mock version of
dbus-launch nowadays, so this dependency is no longer needed.
(Closes: #835884)
  * Use dh-exec to substitute ${DEB_HOST_MULTIARCH} in .install, .links and
.dirs files.

 -- Iain Lane   Wed, 23 Nov 2016 17:44:33 +

** Changed in: glib2.0 (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  Files in the root of a folder on another partition symlinked to user's
  home cannot be moved to trash because of a patch in this package

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Committed
Status in glib2.0 source package in Yakkety:
  Fix Released

Bug description:
  [ Description ]

  Can't trash files if the directory they are in is a symlink to another
  device

  [ QA ]

  Steps:
  1. Install system and partition disk into root and data partitions
  2. create ~/Data folder, and mount data partition on it
  3. create symlinks for ~/whatever/ to ~/Data/something/
  4. delete files directly inside ~/whatever/

  What happen:
  Then Nautilus says: "File can't be put in the trash. Do you want to delete it 
immediately?".

  What should happen:
  The files moved into Trash.

  [ Regression potential ]

  The proposed fix uses g_stat instead of g_stat to follow symlinks, so
  we know where to place the trash (you can't rename() across
  filesystems). If that is wrong, then it could regress trashing other
  kinds of files.

  [ Original ]

  I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1.

  I've reported this bug (or marked as "it affects me") in a couple of
  other places before I've finally discovered that this is the package
  that's causing this problem, which unfortunately has been around for a
  couple of years now.

  This bug has been reported upstream as well, but it's just taking very
  very long to arrive at a decision and take action it seems.

  Apparently one of the patches
  (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix-
  trashing-on-overlayfs.patch/) which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz)
  to the original package which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz)
  is the root cause of this annoying problem.

  As I prefer keeping one patition for the root filesystem (/), one
  partition for user settings (/home) and one partition for user data
  (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which
  are simply symlinked to my home folder for ease of use, I cannot move
  any file to the trash in the root of these folders when I access them
  from my home folder or nautilus sidebar.

  This problem doesn't affect folders at all, nor any other files in
  subfolders, etc.

  So I was wondering if Ubuntu devs can leave out that particular patch
  when building this package for Ubuntu - if it doesn't cause more harm,
  which I doubt.

  Otherwise, I would appreciate if I could learn how to do it myself:
  how can I (as an end-user) compile the contents of
  "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in
  "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on-
  overlayfs.patch"?

To manage notifications about this bug 

[Group.of.nepali.translators] [Bug 1596968] Re: fail to activate fcp device for installation

[Launchpad Bug Tracker]

This bug was fixed in the package s390-zfcp - 1.0.2ubuntu1.1

---
s390-zfcp (1.0.2ubuntu1.1) xenial; urgency=medium

  [ Hendrik Brueckner ]
  * Improve displaying numereous detected FCP devices by replacing the
hard-coded limit with a dynamically allocated solution LP: #1596968

 -- Dimitri John Ledkov   Wed, 14 Dec 2016 14:03:20
+

** Changed in: s390-zfcp (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/1596968

Title:
  fail to activate fcp device for installation

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in s390-zfcp package in Ubuntu:
  Fix Released
Status in s390-zfcp source package in Xenial:
  Fix Released

Bug description:
  [Test case]
  * Start installation with many zfcp devices >>100
  * It should be able to complete zfcp device activation

  == Comment: #0 - XIANG ZHANG  - 2016-06-20 09:28:02 ==
  ---Problem Description---
  Can not activate FCP devices for installation

  ---uname output---
  Linux ilablnx3 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:26:02 UTC 2016 
s390x s390x s390x GNU/Linux

  Machine Type = z13 lpar

  ---boot type---
  Network boot

  ---Install repository type---
  Local repository

  ---Install repository Location---
  9.11.56.168:/OS_IMAGE/ISO/ubuntu/s390

  ---Point of failure---
  Other failure during installation (stage 1)

  I am installing a sanboot s390 ubuntu server via ftp server on a
  native lpar.  But I am not able to activate fcp device for
  installation. However I am able active the fcp device and attach san
  boot lun via shell.

  echo  1 > /sys/bus/ccw/driver/zfcp/0.0.1800/online
  echo 0x > 
/sys/bus/ccw/driver/zfcp/0.0.1800/0x5005076802401ee8/unit_add

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1596968/+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 1644071] Re: [SRU] MAAS 2.1.3

[Launchpad Bug Tracker]

This bug was fixed in the package maas - 2.1.3+bzr5573-0ubuntu1~16.10.1

---
maas (2.1.3+bzr5573-0ubuntu1~16.10.1) yakkety-proposed; urgency=medium

  * Stable Release Update. New MAAS upstream bugfix release 2.1.3 (LP: #1644071)
- MAAS 2.1.3 is a new upstream bugfix release that fixes several bugs
  present on MAAS 2.1.0. This is solely a bugfix release. To see what
  issues this release fixes, please refer to the CHANGELOG.

 -- Andres Rodriguez   Thu, 22 Dec 2016 08:22:55
-0500

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

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

Title:
  [SRU] MAAS 2.1.3

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

Bug description:
  [Impact]

  MAAS 2.1.3 is a new upstream bugfix release that includes various
  fixes that Ubuntu version of MAAS would benefit of. See the CHANGELOG
  for a complete list of bugs fixed.

  [Test Case]
  1. Install MAAS 2.0.0 or Ubuntu 2.1.0
  2. Upgrade to MAAS 2.1.3
  3. MAAS will continue to function as originally designed.

  [Regression Potential]
  Minimal. MAAS 2.1.3 has been CI'd and manually tested:

   - We perform new install package testing to ensure that the package is rock 
solid on fresh installations.
   - We perform upgrade testing from previous MAAS and Ubuntu Releases. At the 
moment we perform upgrade testing covering upgrades from MAAS 2.0. The upgrade 
ensures that MAAS after the upgrade is up and running with no issues.
   - We have performed CI testing to ensure there are no regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1644071/+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 1633678] Re: Compability issue with adobe-flashplugin

[Launchpad Bug Tracker]

This bug was fixed in the package freshplayerplugin - 0.3.4-3ubuntu0.1

---
freshplayerplugin (0.3.4-3ubuntu0.1) xenial; urgency=medium

  * d/*.postinst, d/*.preinst, d/*.prerm:
- Use the same alternative as the adobe-flashplugin package to
  prevent confusion with the NPAPI plugin installed by
  adobe-flashplugin (LP: #1633678).
  Thanks to Alin Andrei for the solution!
  * d/control:
- Drop the pepperflashplugin-nonfree recommend.
- Recommend adobe-flashplugin.
- Maintainer: Ubuntu Developers.
  * d/rules:
- Run tests with LC_ALL=C to prevent the build failure reported in
  LP bug 1578252.

 -- Gunnar Hjalmarsson   Fri, 28 Oct 2016 23:00:00
+0200

** Changed in: freshplayerplugin (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/1633678

Title:
  Compability issue with adobe-flashplugin

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

Bug description:
  [Impact]

  Since google no longer bundles its pepperflash plugin with chrome's
  debs (bug #1632870) the recommended way to get the plugin is by
  installing adobe-flashplugin from the partner repository. However,
  since it also includes the outdated NPAPI-plugin this will result in
  two flash-plugins being installed to Firefox' plugin directory, due to
  the fact that browser-plugin-freshplayer-pepperflash and adobe-
  flashplugin doesn't use the same alternative link, which they should.

  In /usr/lib/mozilla/plugins there's currently two links:
  flash-mozilla.so -> /etc/alternatives/flash-mozilla.so (installed by 
browser-plugin-freshplayer-pepperflash)
  flashplugin-alternative.so -> /etc/alternatives/mozilla-flashplugin 
(installed by adobe-flashplugin)

  browser-plugin-freshplayer-pepperflash should use the same
  alternatives-link as the official package but with an higher priority,
  which would eliminate the compability issue.

  Also the recommend of pepperflashplugin-nonfree should be removed and
  solely recommend adobe-flashplugin instead.

  Proposed changes to achieve this are available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/freshplayerplugin

  [Test Case]

  1. Install adobe-flashplugin from Canonical Partner.
  2. Install the current version of
 browser-plugin-freshplayer-pepperflash.
  3. Restart Firefox and find that two version of "Shockwave Flash" are
 shown under Tools -> Add-ons -> Plugins.
  4. Install the proposed browser-plugin-freshplayer-pepperflash.
  5. Restart Firefox and find only adobe-flashplugin's PPAPI plugin under
 Plugins.

  [Regression Potential]

  Low. This proposal is a natural step for Ubuntu to deal with the
  pepperflashplugin-nonfree breakage caused by Google. As an extra
  bonus, since adobe-flashplugin actually installs the PPAPI plugin and
  not just downloads it from an external source at install, users will
  have the (almost) latest plugin version installed through the package
  updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freshplayerplugin/+bug/1633678/+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 1642383] Re: Unable to configure swap space on ephemeral disk in Azure

[Scott Moser]

This is tested as working on 0.7.8-49-g9e904bb-0ubuntu1~16.04.3 in xenial  in 
azure
$ cat /etc/cloud/build.info 
build_name: server
serial: 20170117
$ cat /proc/swaps 
FilenameTypeSizeUsedPriority
/dev/sdb2   partition   178247640  
-1
$ df -h /mnt2
 df -h /mnt2
Filesystem  Size  Used Avail Use% Mounted on
/dev/sdb133G   48M   31G   1% /mnt2
smoser@smoser0119x:~$ 


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

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

Title:
  Unable to configure swap space on ephemeral disk in Azure

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Fix Released

Bug description:
  I'm following the instructions to send cloud-config and repartition
  the ephemeral disk in Azure:
  https://wiki.ubuntu.com/AzureSwapPartitions.  These instructions fail
  on Ubuntu 14.04 and 16.04 (did not test 12.04 yet).

  Repro:

  1) Add the following content to a file such as customdata.txt:

   #cloud-config
   disk_setup:
   ephemeral0:
   table_type: mbr
   layout: [66, [33, 82]]
   overwrite: True
   fs_setup:
   - device: ephemeral0.1
     filesystem: ext4
   - device: ephemeral0.2
     filesystem: swap
   mounts:
   - ["ephemeral0.1", "/mnt2"]
   - ["ephemeral0.2", "none", "swap", "sw", "0", "0"]

  2) Create a VM in Azure with this cloud-config:

   $ azure group create ubtest 'east us'

   $ azure vm create ubtest ubtest-1604 Linux --image-urn
  canonical:UbuntuServer:16.04.0-LTS:latest --admin-username azureuser
  --admin-password '' --nic-name ubtest-1604 --location "East
  US" --vnet-name "ubtest" --vnet-address-prefix "10.0.0.0/24" --vnet-
  subnet-name "ubtest" --vnet-subnet-address-prefix "10.0.0.0/24"
  --public-ip-name "ubtest" --public-ip-domain-name "ubtest" --custom-
  data ./customdata.txt

  Expected Result:

   - /dev/disk/cloud/azure_resource should have two partitions; one ext4 and a 
second swap
   - /dev/disk/cloud/azure_resource-part1 should be mounted on /mnt2
   - /dev/disk/cloud/azure_resource-part2 should be active swap space
   - /etc/fstab should be configured correctly

  Actual Results:

   - /dev/disk/cloud/azure_resource-part1 is properly mounted on /mnt2.
   - On Ubuntu 14.04, /dev/disk/cloud/azure_resource is re-partitioned as 
expected.
   - On Ubuntu 16.04, /dev/disk/cloud/azure_resource is *not* re-partitioned. 
There is only a single partition (no swap space).
   - On Ubuntu 14.04 and 16.04, /etc/fstab includes an incorrect entry for the 
swap space:

     ephemeral0.2noneswapsw,comment=cloudconfig  0   0

  This clearly won't work, it should resolve to "/dev/disk/cloud
  /azure_resource-part2".  I do notice that on Ubuntu 14.04, the
  ephemeral disk is re-partitioned correctly, but there is no symlink in
  /dev/disk/azure/ to the second partition. These symlinks are created
  by /lib/udev/rules.d/66-azure-ephemeral.rules. Perhaps cloud-init
  needs to re-trigger this udev rule after repartitioning the disk.

  FYI, I also tested with the latest cloud-init that is currently in
  xenial-proposed (0.7.8-47-gb6561a1-0ubuntu1~16.04.1) with the same
  results.

  Related bugs:
   * bug 1460715: MBR disk setup fails because sfdisk no longer accepts M as a 
valid unit
   * bug 1647708: azure ephemeral disk not mounted at boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1642383/+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 1650596] Re: [ppc64-diag] package update for Marvell SATA HDD LEDs support

[Launchpad Bug Tracker]

This bug was fixed in the package ppc64-diag - 2.7.1-5ubuntu1~16.10

---
ppc64-diag (2.7.1-5ubuntu1~16.10) yakkety; urgency=medium

  [ Mauricio Faria de Oliveira ]
  * Add upstream patches to support Marvell HDD LEDs on S822LC for HPC
(LP: #1650596)
- debian/patches/marvell-leds-0001-add-support.patch
- debian/patches/marvell-leds-0002-handle-non-unique-loc.patch
- debian/patches/marvell-leds-0003-do-not-exit-early-sys-class-led.patch
- 
debian/patches/marvell-leds-0004-opal-call-all-get_indices-in-opal_get_indicator.patch
- debian/patches/marvell-leds-0005-validate-get-indicator-for-loc.patch
- debian/patches/marvell-leds-0006-remove-warning.patch
- debian/patches/marvell-leds-0007-check-for-dt-property.patch
- debian/patches/marvell-leds-0008-fix-test-case.patch
- debian/patches/marvell-leds-0009-volatile.patch

 -- Steve Langasek   Wed, 11 Jan 2017
16:21:54 +0200

** Changed in: ppc64-diag (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  [ppc64-diag] package update for Marvell SATA HDD LEDs support

Status in ppc64-diag package in Ubuntu:
  Fix Released
Status in ppc64-diag source package in Xenial:
  Fix Committed
Status in ppc64-diag source package in Yakkety:
  Fix Released
Status in ppc64-diag source package in Zesty:
  Fix Released

Bug description:
  [SRU Justification]
  Hardware enablement

  [Regression potential]
  Low; the code changes are limited to the LED detection, to enable LED support 
on a different class of system.

  [Test case]
  1. Install ppc64-diag on an existing supported ppc64el system.
  2. Run 'usysident' and capture output.
  3. Install ppc64-diag from proposed.
  4. Run 'usysident' and capture output.
  5. Compare the output from the two runs and confirm that it is the same.
  6. Install ppc64-diag on a system with Marvell SATA LEDs.
  7. Run 'usysident' and confirm that the output includes reporting of the SATA 
HDD LEDs.

  == Comment: #0 - Mauricio Faria De Oliveira - 2016-12-16 05:10:23 ==
  Hi Canonical,

  Can you please update ppc64-diag with the patches
  to support the Marvell HDD LEDs in the 'IBM Power
  System S822LC for HPC' server?

  The main target is 16.04.x. I realize that SRUs
  are not suited for features, only bugs, however
  since this is related to hardware support, and
  16.04 is LTS, it seems we can ask/talk about it.

  The commits apply cleanly, attached debdiffs for
  Zesty and Xenial.

  commit id/summary
  (most-recent first; git-log style; ordered in debian/patches/series)

  cf718b32bcbd lpd: marvell: mark the indirect-access registers as volatile
  727c17f75033 lpd/test: Fix test case
  22e8e4edd4c2 lpd: Check for device tree property
  d88b88735bd7 lpd: Remove redundant warning message
  82a6a8c966b9 lpd: Validate get_indicator_for_loc_code() return value
  53f12274da2c lpd: opal: call all get_indices() in opal_get_indicator_list()
  d56f7f1367bd lpd: marvell: do not exit early on empty /sys/class/leds dir 
(OPAL)
  627287130fab lpd: marvell: handle non-unique/duplicate location codes
  efb9a4df3f88 lpd: Add support for Marvell HDD LEDs on S822LC for HPC

  ---Additional Hardware Info---
  0009:04:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 
PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11) (prog-if 01 
[AHCI 1.0])
   Subsystem: IBM 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1014:0612]

  Machine Type = IBM Power System S822LC for HPC

  == Comment: #5 - Mauricio Faria De Oliveira - 2016-12-16 05:18:12 ==
  @taco-screen-team

  For assignee suggestions, the recent uploaders of Ubuntu local
  versions were @cyphermox and @vorlon.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppc64-diag/+bug/1650596/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

[Launchpad Bug Tracker]

This bug was fixed in the package ido - 13.10.0+16.04.20161028-0ubuntu1

---
ido (13.10.0+16.04.20161028-0ubuntu1) xenial; urgency=medium

  * IdoCalendarMenuItem: disconnect from parent signals on item
destruction (LP: #1506427)

 -- Marco Trevisan (Treviño)   Fri, 28 Oct 2016 22:43:02
+

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

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

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Xenial:
  Fix Committed
Status in ido source package in Yakkety:
  Fix Released

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Launchpad Bug Tracker]

This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu15.2

---
isc-dhcp (4.3.3-5ubuntu15.2) yakkety; urgency=medium

  * debian/initramfs/lib/etc/dhcp/dhclient-enter-hooks.d/config: fix script to
not write to /run/net-$iface.conf when dealing with IPv6; which should only
write to a /run/net6-$iface.conf file. (LP: #1621507)
  * debian/README.Debian: document what this config script is and why a hook is
shipped for the initramfs.

isc-dhcp (4.3.3-5ubuntu15.1) yakkety; urgency=medium

  * ipv6: wait for duplicate address detection to finish (LP: #1633479).

 -- Mathieu Trudel-Lapierre   Fri, 21 Oct 2016
12:46:20 -0400

** Changed in: isc-dhcp (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: initramfs-tools (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Released
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

  Bugs related to uploads for this specific SRU:

  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU

  ifupdown:
  bug 1629972: networking.service takes down lo on stop

  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)

  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD

  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  [Stable Fix]

  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.

  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

  [Tests for verification]

  Whoever checks the last one off, please mark verification done.

  MAAS test cases:
   X / Y
  [+]/[+] MAAS on IPv6-only network
  [+]/[+] MAAS on IPv4-only network
  [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)

  Non-MAAS test cases:
   X / Y
  [+]/[+] ip="" and ip6 not present
  [+]/[+] ip=:eth0:dhcp and ip6 not present
  [+]/[+] d-i install with iSCSI remote root should complete normally
  [+]/[+] Validate normal boot without remote root
  

[Group.of.nepali.translators] [Bug 1644071] Re: [SRU] MAAS 2.1.3

[Launchpad Bug Tracker]

This bug was fixed in the package maas - 2.1.3+bzr5573-0ubuntu1~16.04.1

---
maas (2.1.3+bzr5573-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * Stable Release Update. New MAAS upstream bugfix release 2.1.3 (LP: #1644071)
- MAAS 2.1.3 is a new upstream bugfix release that fixes several bugs
  present on MAAS 2.1.0. This is solely a bugfix release. To see what
  issues this release fixes, please refer to the CHANGELOG.

 -- Andres Rodriguez   Thu, 22 Dec 2016 08:22:55
-0500

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

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

Title:
  [SRU] MAAS 2.1.3

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

Bug description:
  [Impact]

  MAAS 2.1.3 is a new upstream bugfix release that includes various
  fixes that Ubuntu version of MAAS would benefit of. See the CHANGELOG
  for a complete list of bugs fixed.

  [Test Case]
  1. Install MAAS 2.0.0 or Ubuntu 2.1.0
  2. Upgrade to MAAS 2.1.3
  3. MAAS will continue to function as originally designed.

  [Regression Potential]
  Minimal. MAAS 2.1.3 has been CI'd and manually tested:

   - We perform new install package testing to ensure that the package is rock 
solid on fresh installations.
   - We perform upgrade testing from previous MAAS and Ubuntu Releases. At the 
moment we perform upgrade testing covering upgrades from MAAS 2.0. The upgrade 
ensures that MAAS after the upgrade is up and running with no issues.
   - We have performed CI testing to ensure there are no regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1644071/+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 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

[Launchpad Bug Tracker]

This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu15.2

---
isc-dhcp (4.3.3-5ubuntu15.2) yakkety; urgency=medium

  * debian/initramfs/lib/etc/dhcp/dhclient-enter-hooks.d/config: fix script to
not write to /run/net-$iface.conf when dealing with IPv6; which should only
write to a /run/net6-$iface.conf file. (LP: #1621507)
  * debian/README.Debian: document what this config script is and why a hook is
shipped for the initramfs.

isc-dhcp (4.3.3-5ubuntu15.1) yakkety; urgency=medium

  * ipv6: wait for duplicate address detection to finish (LP: #1633479).

 -- Mathieu Trudel-Lapierre   Fri, 21 Oct 2016
12:46:20 -0400

** Changed in: isc-dhcp (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Precise:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:

   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/

   Can't bind to dhcp address: Cannot assign requested address
   Please make sure there is no other dhcp server
   running and that there's no entry for dhcp or
   bootp in /etc/inetd.conf.   Also make sure you
   are not running HP JetAdmin software, which
   includes a bootp server.

   If you think you have received this message due to a bug rather
   than a configuration issue please read the section on submitting
   bugs on either our web page at www.isc.org or in the README file
   before submitting a bug.  These pages explain the proper
   process and the information we find helpful for debugging..
   $ echo $?
   1

  Related bugs:
   * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address
   * bug 1633562: 'dhclient -6 -S' does not bring interface up 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.125ubuntu6.3

---
initramfs-tools (0.125ubuntu6.3) yakkety; urgency=medium

  * Do not rely on debug variables from dhclient.

initramfs-tools (0.125ubuntu6.2) yakkety; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * scripts/functions: for configure_networking:
- split out IPv6 options in its own cmdline parameter: ip6= ; always use
  dhclient in this case if the value set is anything other than 'off' or
  'none'. Furthermore, parse anything other than 'on', 'dhcp' or 'any' as
  the name of an interface. (LP: #1621507)
- rework the stop conditions so that we properly handle the ROUNDTTT loop,
  timing out after a short period of time and trying again after a short
  sleep.
- add a 'done' parameter for both ip= and ip6= so that we can properly
  exit the ROUNDTTT loop once we know that either there is no work to do,
  or that we've achieved what we wanted (that is, to bring up IPv4, IPv6,
  or possibly both).
- return ip=dhcp to the ipconfig use case; if set, then ipconfig will be
  run using any interface available, or the BOOTIF if it was set.

  [ LaMont Jones ]
  * Only source ipv4 config in configure_networking() if it exists.

initramfs-tools (0.125ubuntu6.1) yakkety; urgency=medium

  * scripts/functions: Revert configure_networking changes to the state at
0.125ubuntu3. (LP: #1631474)

initramfs-tools (0.125ubuntu6) yakkety; urgency=medium

  * Fix case where ip=dhcp and ip=:eth0 and other ip= instances exists on
the kernel command line (LP: #1631474)
  * Also fixed an error discovered by the shellcheck static code analyzer
where "$DEVICES" would be processed as a single device where-as removing
the quotes allows the list to be correctly processed by the for loop.

 -- LaMont Jones   Wed, 30 Nov 2016 08:30:14 -0700

** Changed in: initramfs-tools (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  Fix Released
Status in initramfs-tools source package in Zesty:
  In Progress

Bug description:
  [Impact]
   * initramfs-tools SRUs introduced regressions in ip= syntax, which cause 
unexpected behavior

  [Test Case]
   * Create a machine that boots using an nfsroot.
   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.
   * Discover that the device never comes up because, networking is not 
configured correctly.

  [Regression Potential]
  Should be back to original behavior before ipv6 support was introduced in the 
past 2 or 3 SRUs.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
     - The ?*:?*:?*:?*: use case falls through to the default case, and likely 
breaks there.  As such static assignment via ip= appears broken
     -
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  This bug is a regression of changes made under bug 1628306.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1655934] Re: update-grub-legacy-ec2 should detect -aws kernels as appropriate for EC2

[Scott Moser]

** Changed in: cloud-init (Ubuntu)
   Status: Fix Released => Fix Committed

** Also affects: cloud-init (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Dan Watkins (daniel-thewatkins)
   Status: Fix Committed

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

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

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

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

Title:
  update-grub-legacy-ec2 should detect -aws kernels as appropriate for
  EC2

Status in cloud-init package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Trusty:
  New
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  PV images built with AWS custom kernels currently won't boot because their 
kernels aren't detected.

  [Test Case]
  * Launch an HVM instance
  * Run update-grub-legacy-ec2 and see an error message like "Ignoring non-Xen 
Kernel on Xen domU host: vmlinuz-4.4.0-1001-aws"
  * Install the new package
  * Run update-grub-legacy-ec2 again and see success like:
  Found kernel: /boot/vmlinuz-4.4.0-1001-aws
  Found kernel: /boot/vmlinuz-4.4.0-1001-aws
  Updating /boot/grub/menu.lst ... done

  [Regression Potential]
  This is a single line change to a case statement; regression potential is 
minimal.

  [Original Report]
  Currently, it will detect -ec2 kernels, but we also need it to detect -aws 
kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1655934/+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 1657430] Re: linux: 4.4.0-62.83 -proposed tracker

[Brad Figg]

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

Title:
  linux: 4.4.0-62.83 -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:
  Confirmed
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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+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 1657430] Re: linux: 4.4.0-62.83 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the 4.4.0-62.83 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
  
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 19. January 2017 11:05 UTC

** Description changed:

  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: true
- phase: Packaging
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Thursday, 19. January 2017 11:05 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+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 1657432] Re: linux-raspi2: 4.4.0-1042.49 -proposed tracker

[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-1042.49/raspi2-xenial-proposed-frozen.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/1657432

Title:
  linux-raspi2: 4.4.0-1042.49 -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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1657430
  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/1657432/+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 1657594] Re: Recent MySQL vulnerabilities partially applies to MariaDB too

[Otto Kekäläinen]

Zesty should be fixed by importing latest mariadb-10.1 10.1.21 from
Debian unstable once available.

** Also affects: mariadb-10.0 (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: mariadb-10.0 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: mariadb-10.0 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: mariadb-10.0 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: mariadb-5.5 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mariadb-10.1 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: mariadb-10.0 (Ubuntu Trusty)

** No longer affects: mariadb-10.1 (Ubuntu Trusty)

** No longer affects: mariadb-10.1 (Ubuntu Xenial)

** No longer affects: mariadb-10.1 (Ubuntu Yakkety)

** No longer affects: mariadb-5.5 (Ubuntu Zesty)

** No longer affects: mariadb-5.5 (Ubuntu Yakkety)

** No longer affects: mariadb-5.5 (Ubuntu Xenial)

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

Title:
  Recent MySQL vulnerabilities partially applies to MariaDB too

Status in mariadb-10.0 package in Ubuntu:
  New
Status in mariadb-10.1 package in Ubuntu:
  New
Status in mariadb-5.5 package in Ubuntu:
  New
Status in mariadb-5.5 source package in Trusty:
  New
Status in mariadb-10.0 source package in Xenial:
  New
Status in mariadb-10.0 source package in Yakkety:
  New
Status in mariadb-10.0 source package in Zesty:
  New
Status in mariadb-10.1 source package in Zesty:
  New

Bug description:
  A USN-identifier has not been created after the latest Oracle CPU
  affecting MySQL. I'll update the title later when there is one.

  The security notice also affect MariaDB and the latest release
  includes fixes.

  I will produce a security release soon and attach more information to this 
bug report for:
   - mariadb.5.5 in Trusty
   - mariadb-10.0 in Xenial and Yakkety (zesty can sync from Debian)

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