date:20160715

[Group.of.nepali.translators] [Bug 1599491] Re: kdump-tools install script uses deprecated syntax

2016-07-15 Thread Launchpad Bug Tracker

This bug was fixed in the package makedumpfile - 1:1.6.0-2

---
makedumpfile (1:1.6.0-2) sid; urgency=medium

  * define_stampdir() : Loop on hostname -I for 5 sec to get IP address
if HOSTTAG=ip. The network stack may not be ready when kdump-config runs.
Give it some time before reverting HOSTTAG to hostname if an IP address
cannot be found. (LP: #1599561)

  * debian/rules : drop the dh_installinit override
Uses a syntax which is no longer supported and generate an error on
install. (LP: #1599491)

 -- Louis Bouchard   Fri, 15 Jul 2016
17:25:33 +0200

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

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

Title:
  kdump-tools install script uses deprecated syntax

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Triaged

Bug description:
  When installing kdump-tools, the apt-get outputs:

  Setting up kdump-tools (1:1.5.9-5) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults

  Full log:

  jayman@jayman-kubuntu:~$ sudo apt-get install kdump-tools
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
crash kexec-tools libdw1 makedumpfile
  The following NEW packages will be installed:
crash kdump-tools kexec-tools libdw1 makedumpfile
  0 upgraded, 5 newly installed, 0 to remove and 10 not upgraded.
  Need to get 0 B/2,962 kB of archives.
  After this operation, 9,379 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Preconfiguring packages ...
  Selecting previously unselected package crash.
  (Reading database ... 235512 files and directories currently installed.)
  Preparing to unpack .../crash_7.1.4-1ubuntu4_amd64.deb ...
  Unpacking crash (7.1.4-1ubuntu4) ...
  Selecting previously unselected package libdw1:amd64.
  Preparing to unpack .../libdw1_0.165-3ubuntu1_amd64.deb ...
  Unpacking libdw1:amd64 (0.165-3ubuntu1) ...
  Selecting previously unselected package makedumpfile.
  Preparing to unpack .../makedumpfile_1%3a1.5.9-5_amd64.deb ...
  Unpacking makedumpfile (1:1.5.9-5) ...
  Selecting previously unselected package kexec-tools.
  Preparing to unpack .../kexec-tools_1%3a2.0.10-1ubuntu2_amd64.deb ...
  Unpacking kexec-tools (1:2.0.10-1ubuntu2) ...
  Selecting previously unselected package kdump-tools.
  Preparing to unpack .../kdump-tools_1%3a1.5.9-5_all.deb ...
  Unpacking kdump-tools (1:1.5.9-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  Processing triggers for systemd (229-4ubuntu6) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Setting up crash (7.1.4-1ubuntu4) ...
  Setting up libdw1:amd64 (0.165-3ubuntu1) ...
  Setting up makedumpfile (1:1.5.9-5) ...
  Setting up kexec-tools (1:2.0.10-1ubuntu2) ...
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-4.4.0-28-generic
  Found initrd image: /boot/initrd.img-4.4.0-28-generic
  Found linux image: /boot/vmlinuz-4.4.0-24-generic
  Found initrd image: /boot/initrd.img-4.4.0-24-generic
  Found memtest86+ image: /boot/memtest86+.elf
  Found memtest86+ image: /boot/memtest86+.bin
  grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your 
device.map.
  Found Windows 7 (loader) on /dev/sda1
  done
  Setting up kdump-tools (1:1.5.9-5) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  jayman@jayman-kubuntu:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: kdump-tools 1:1.5.9-5
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jul  6 08:02:53 2016
  InstallationDate: Installed on 2016-06-16 (19 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: makedumpfile
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1599491/+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 1599561] Re: Ubuntu 16.04.01 kdump: IP prefix is missing in the directory name after first dump during kdump over ssh.

2016-07-15 Thread Launchpad Bug Tracker

This bug was fixed in the package makedumpfile - 1:1.6.0-2

---
makedumpfile (1:1.6.0-2) sid; urgency=medium

  * define_stampdir() : Loop on hostname -I for 5 sec to get IP address
if HOSTTAG=ip. The network stack may not be ready when kdump-config runs.
Give it some time before reverting HOSTTAG to hostname if an IP address
cannot be found. (LP: #1599561)

  * debian/rules : drop the dh_installinit override
Uses a syntax which is no longer supported and generate an error on
install. (LP: #1599491)

 -- Louis Bouchard   Fri, 15 Jul 2016
17:25:33 +0200

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

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

Title:
  Ubuntu 16.04.01 kdump: IP prefix is missing in the directory name
  after first dump during kdump over ssh.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-06-30 07:12:40 ==
  ---Problem Description---

  During kdump over ssh IP prefix will be present only in first dump,
  subsequent dumps will not have IP in directory name.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show # should show "ready to dump"
  6) ssh-keygen -t rsa
  7) Edit below parameters in /etc/default/kdump-tools
  SSH="root@"
  SSH_KEY=/root/.ssh/id_rsa
  8)  kdump-config propagate
  9)  kdump-config show
  10) reboot
  11) echo "c" > /proc/sysrq-trigger
  12) verify dump is created in ssh server.
  13) trigger the crash again.

  Logs
  =
  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.4.0-26-generic #45-Ubuntu SMP Mon Jun 20 17:27:01 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  dumps on ssh server when 3 crashes are triggered
  
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523  -201606300524
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523  -201606300524  -201606300525
  [root@ltc-fire5 crash]# cd -201606300524
  -bash: cd: -2: invalid option
  cd: usage: cd [-L|[-P [-e]]] [dir]
  [root@ltc-fire5 crash]# cd -- -201606300524
  [root@ltc-fire5 -201606300524]# ls
  dmesg.201606300524  dump.201606300524

  
  == Comment: #8 - Kevin W. Rudd - 2016-07-05 18:23:01 ==

  Canonical,

  The behavior appears to be somewhat intermittent, and it looks as if
  define_stampdir() might be getting called before the network init has
  completed.  If delaying this function is not practical, it might be
  helpful to have define_stampdir() fall back to using just "hostname"
  if "hostname -I" doesn't return any useful information for setting
  THIS_HOST.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1599561/+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 1600391] Re: No b2 executable in libboost-tools-dev

2016-07-15 Thread Jeremy Bicha

** Changed in: boost-defaults (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: boost-defaults (Ubuntu)
   Status: New => Triaged

** Package changed: boost-defaults (Ubuntu) => boost1.58 (Ubuntu)

** Also affects: boost1.60 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: boost1.60 (Ubuntu)
   Status: New => Triaged

** Changed in: boost1.60 (Ubuntu)
   Importance: Undecided => Wishlist

** Also affects: boost1.58 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: boost1.60 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: boost1.60 (Ubuntu Xenial)

** Changed in: boost1.58 (Ubuntu Xenial)
   Importance: Undecided => Wishlist

** Changed in: boost1.58 (Ubuntu Xenial)
   Status: New => Triaged

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

** Also affects: boost1.60 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831431
   Importance: Unknown
   Status: Unknown

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

Title:
  No b2 executable in libboost-tools-dev

Status in boost1.58 package in Ubuntu:
  Triaged
Status in boost1.60 package in Ubuntu:
  Triaged
Status in boost1.58 source package in Xenial:
  Triaged
Status in boost1.60 package in Debian:
  Unknown

Bug description:
  The boost build tool, b2 is important for any project that is using
  the boost build system for its own purposes.

  It is distributed in Ubuntu as part of the `libboost-tools-dev`
  package. However, it is renamed `bjam` there.

  The `bjam` name is archaic. Something like five years ago, they
  decided to rename it to `b2` since it doesn't interoperate with the
  old perforce version `bjam` which isn't developed anymore.

  http://stackoverflow.com/questions/5759434/boost-installation

  http://www.boost.org/users/history/version_1_48_0.html

  I understand that the ubuntu package still calls it `bjam` to avoid
  breakage (presumably), but can't it at least provide a symlink called
  `b2`? It seriously confused me for a long time why I couldn't get
  travis-ci to use `b2` after installing `libboost-all-dev`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.58/+bug/1600391/+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 1599068] Re: Add support for Intel 8265 Bluetooth ([8087:0A2B])

2016-07-15 Thread Kamal Mostafa

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

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

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

Title:
  Add support for Intel 8265 Bluetooth ([8087:0A2B])

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Backport supports for Intel 8265 Bluetooth from upstream

  The support is introduced in v4.7 so yakkety doesn't need this
  backport

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1599068/+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 1584192] Re: CVE-2016-4440

2016-07-15 Thread Kamal Mostafa

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

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

Title:
  CVE-2016-4440

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Invalid
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta

[Group.of.nepali.translators] [Bug 1602579] Re: the system hangs in the dma driver when reboot or shutdown on a baytrail-m laptop

2016-07-15 Thread Kamal Mostafa

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

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

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

Title:
  the system hangs in the dma driver when reboot or shutdown on a
  baytrail-m laptop

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  1. System got hang on reboot of installation phase 1;
  2. Power off system by long-press power button, then power on system again.
  3. System got hang on power off of installation phase 2.

  The hang issue blocked the installation. Can not finish the
  installation procession.

  This bug is for tracking purposes; please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1602579/+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 1602724] Re: Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

2016-07-15 Thread Leann Ogasawara

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

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

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

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

Title:
  Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

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

Bug description:
  == Comment: #0 - Heitor Ricardo Alves de Siqueira  - 
2016-07-12 12:54:27 ==
  Current nvme driver in Ubuntu 16.04 kernel does not handle error recovery; we 
are missing some patches from the upstream nvme driver.

  We would like to ask Canonical to cherry pick the following patches for the 
16.04 kernel, if possible:
  * 9396dec916c0 ("nvme: use a work item to submit async event requests")
  * 79f2b358c9ba ("nvme: don't poll the CQ from the kthread")
  * 2d55cd5f511d ("nvme: replace the kthread with a per-device watchdog 
timer")
  * 9bf2b972afea ("NVMe: Fix reset/remove race")
  * c875a7093f04 ("nvme: Avoid reset work on watchdog timer function during 
error recovery")
  * a5229050b69c ("NVMe: Always use MSI/MSI-x interrupts")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602724/+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 1603483] [NEW] [Xenial] Include Huawei PCIe SSD hio kernel driver

2016-07-15 Thread Leann Ogasawara

Public bug reported:

== SRU Justification ==
Huawei servers, including Huawei PCIe SSD's require the hio driver which is 
currently not included in our kernels.  We would like to carry this driver in 
our kernels for Xenial and newer in order to support platforms with these 
drives.

== Source ==
http://support.huawei.com/enterprisesearch/ebgSearch#sp.keyword=HUAWEI%20ES3000%20V2%20Driver%20SRC

== Testing ==
TBD

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Leann Ogasawara (leannogasawara)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Leann Ogasawara (leannogasawara)

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  [Xenial] Include Huawei PCIe SSD hio kernel driver

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  == SRU Justification ==
  Huawei servers, including Huawei PCIe SSD's require the hio driver which is 
currently not included in our kernels.  We would like to carry this driver in 
our kernels for Xenial and newer in order to support platforms with these 
drives.

  == Source ==
  
http://support.huawei.com/enterprisesearch/ebgSearch#sp.keyword=HUAWEI%20ES3000%20V2%20Driver%20SRC

  == Testing ==
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603483/+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 1599491] Re: kdump-tools install script uses deprecated syntax

2016-07-15 Thread Louis Bouchard

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

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

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

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

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

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

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

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

Title:
  kdump-tools install script uses deprecated syntax

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

Bug description:
  When installing kdump-tools, the apt-get outputs:

  Setting up kdump-tools (1:1.5.9-5) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults

  Full log:

  jayman@jayman-kubuntu:~$ sudo apt-get install kdump-tools
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
crash kexec-tools libdw1 makedumpfile
  The following NEW packages will be installed:
crash kdump-tools kexec-tools libdw1 makedumpfile
  0 upgraded, 5 newly installed, 0 to remove and 10 not upgraded.
  Need to get 0 B/2,962 kB of archives.
  After this operation, 9,379 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Preconfiguring packages ...
  Selecting previously unselected package crash.
  (Reading database ... 235512 files and directories currently installed.)
  Preparing to unpack .../crash_7.1.4-1ubuntu4_amd64.deb ...
  Unpacking crash (7.1.4-1ubuntu4) ...
  Selecting previously unselected package libdw1:amd64.
  Preparing to unpack .../libdw1_0.165-3ubuntu1_amd64.deb ...
  Unpacking libdw1:amd64 (0.165-3ubuntu1) ...
  Selecting previously unselected package makedumpfile.
  Preparing to unpack .../makedumpfile_1%3a1.5.9-5_amd64.deb ...
  Unpacking makedumpfile (1:1.5.9-5) ...
  Selecting previously unselected package kexec-tools.
  Preparing to unpack .../kexec-tools_1%3a2.0.10-1ubuntu2_amd64.deb ...
  Unpacking kexec-tools (1:2.0.10-1ubuntu2) ...
  Selecting previously unselected package kdump-tools.
  Preparing to unpack .../kdump-tools_1%3a1.5.9-5_all.deb ...
  Unpacking kdump-tools (1:1.5.9-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  Processing triggers for systemd (229-4ubuntu6) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Setting up crash (7.1.4-1ubuntu4) ...
  Setting up libdw1:amd64 (0.165-3ubuntu1) ...
  Setting up makedumpfile (1:1.5.9-5) ...
  Setting up kexec-tools (1:2.0.10-1ubuntu2) ...
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-4.4.0-28-generic
  Found initrd image: /boot/initrd.img-4.4.0-28-generic
  Found linux image: /boot/vmlinuz-4.4.0-24-generic
  Found initrd image: /boot/initrd.img-4.4.0-24-generic
  Found memtest86+ image: /boot/memtest86+.elf
  Found memtest86+ image: /boot/memtest86+.bin
  grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your 
device.map.
  Found Windows 7 (loader) on /dev/sda1
  done
  Setting up kdump-tools (1:1.5.9-5) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  jayman@jayman-kubuntu:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: kdump-tools 1:1.5.9-5
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jul  6 08:02:53 2016
  InstallationDate: Installed on 2016-06-16 (19 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: makedumpfile
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1599491/+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 1597699] Re: cc_mcollective.py fails on Ubuntu16.04

2016-07-15 Thread Scott Moser

** Description changed:

   Begin SRU Template 
  [Impact]
  mcollective usage via cloud-init is not possible.
  
  [Test Case]
  launch instance with cloud-config containing 'mcollective' entry.
  
+ $ cat >user-data <<"EOF"
+ #cloud-config
+ mcollective:
+   conf:
+ main_collective: mcollective
+ collectives: mcollective
+ libdir: /usr/share/mcollective/plugins
+ logfile: /var/log/mcollective.log
+ loglevel: debug
+ daemonize: 1
+ direct_addressing: 1
+ ttl: 4294957
+ securityprovider: psk
+ plugin.psk: unset
+ identity: 2
+ 
+ connector: rabbitmq
+ plugin.rabbitmq.vhost: mcollective
+ plugin.rabbitmq.pool.size: 1
+ plugin.rabbitmq.pool.1.host: 10.10.0.2
+ plugin.rabbitmq.pool.1.port: 61613
+ plugin.rabbitmq.pool.1.user: mcollective
+ plugin.rabbitmq.pool.1.password: ScwpVo8egrZ0OmT6sRmp9zEA
+ plugin.rabbitmq.heartbeat_interval: 30
+ 
+ factsource: yaml
+ plugin.yaml: /etc/mcollective/facts.yaml
+ EOF
+ 
+ $ keyname=brickies; image=$image;
+ $ openstack server create \
+--key-name=$keyname --flavor=m1.small \
+--image=$image --user-data=user-data mcollective-test0
+ 
+ # then ssh in and
+ a.) verifiy mcollective package is installed
+ $ dpkg-query --show mcollective
+ mcollective 2.6.0+dfsg-2.1
+ 
+ b.) verify mcollective service is running
+ $ systemctl status mcollective
+ 
+ c.) grep WARN /var/log/cloud-init.log && echo FAIL
+ 
  [Regression Potential]
  low to none.  This has been unfortunately broken since wily.
  
  [Other Info]
   End SRU Template 
- 
  
  How to reproduce:
  
  #cat /etc/issue.net
  Ubuntu 16.04 LTS
  #( cd /var/lib/cloud/ && rm -rf * )
  #cloud-init -d init
  
  #grep ^mcollective: -A25 instance/user-data.txt
  mcollective:
    conf:
  main_collective: mcollective
  collectives: mcollective
  libdir: /usr/share/mcollective/plugins
  logfile: /var/log/mcollective.log
  loglevel: debug
  daemonize: 1
  direct_addressing: 1
  ttl: 4294957
  securityprovider: psk
  plugin.psk: unset
  identity: 2
  
  connector: rabbitmq
  plugin.rabbitmq.vhost: mcollective
  plugin.rabbitmq.pool.size: 1
  plugin.rabbitmq.pool.1.host: 10.10.0.2
  plugin.rabbitmq.pool.1.port: 61613
  plugin.rabbitmq.pool.1.user: mcollective
  plugin.rabbitmq.pool.1.password: ScwpVo8egrZ0OmT6sRmp9zEA
  plugin.rabbitmq.heartbeat_interval: 30
  
  factsource: yaml
  plugin.yaml: /etc/mcollective/facts.yaml
  
  #cloud-init -d single --name mcollective
  
  The log will contain
  
  Jun 30 08:26:43 node-2 [CLOUDINIT] util.py[DEBUG]: Running module
  mcollective ()
  failed#012Traceback (most recent call last):#012  File "/usr/lib/python3
  /dist-packages/cloudinit/stages.py", line 739, in _run_modules#012
  freq=freq)#012  File "/usr/lib/python3/dist-
  packages/cloudinit/cloud.py", line 70, in run#012return
  self._runners.run(name, functor, args, freq, clear_on_fail)#012  File
  "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in
  run#012results = functor(*args)#012  File "/usr/lib/python3/dist-
  packages/cloudinit/config/cc_mcollective.py", line 83, in handle#012
  mcollective_config.write(contents)#012  File "/usr/lib/python3/dist-
  packages/configobj.py", line 2126, in write#012
  outfile.write(output_bytes)#012TypeError: string argument expected, got
  'bytes'

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

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

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

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

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

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

** Changed in: cloud-init
   Status: Confirmed => Fix Committed

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

Title:
  cc_mcollective.py fails on Ubuntu16.04

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

Bug description:
   Begin SRU Template 
  [Impact]
  mcollective usage via cloud-init is not possible.

  [Test Case]
  launch instance with cloud-config containing 'mcollective' entry.

  $ cat >user-data <<"EOF"
  #cloud-config
  mcollective:
conf:
  main_collective: mcollective
  collectives: mcollective
  libdir: /usr/share/mcollective/plugins
  logfile: /var/log/mcollective.log
  loglevel: debug
  daemonize: 1
  direct_addressing: 1
  ttl: 4294957
  securityprovider: psk
  plugin.psk: unset
  identity: 2

  connector: rabbitmq

[Group.of.nepali.translators] [Bug 1592042] Re: Unable to start guests with memballoon default.

2016-07-15 Thread 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/1592042

Title:
  Unable to start guests with memballoon default.

Status in linux:
  New
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #0 - Frank R. Lefevre  - 2016-06-13 08:49:43 
==
  ---Problem Description---
  Please include the upstream fix for virtio_balloon: fix PFN format for 
virtio-1.
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=87c9403b0d1de4676b0bd273eea68fcf6de68e68
   
  Contact Information = lefe...@us.ibm.com, mi...@us.ibm.com 
   
  ---uname output---
  root@zs93k1g112005:~# uname -a Linux zs93k1g112005 4.4.0-22-generic 
#40-Ubuntu SMP Thu May 12 22:02:55 UTC 2016 s390x s390x s390x GNU/Linux
   
  Machine Type = 2964-701 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   Include memballoon statement in xml file, guest fails to boot.
   
  *Additional Instructions for lefe...@us.ibm.com, mi...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occurring on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1592042/+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 1584393] Re: systemctl restart networking hangs reloading ssh.service

2016-07-15 Thread Martin Pitt

> --job-mode=ignore-dependencies still keeps ReloadPropagatedTo=. If
not, we need something else.

It doesn't, and indeed that would make --job-mode=ignore-dependencies a
bit pointless. So we would apply this generally, we would break e. g.
some postinst script that does "invoke-rc.d openvpn  reload", and the
reload of openvpn.service should then be propagated to all
openvpn@*.service instances.

So let's be more cautious here and limit this to openssh. Please revert
the patch to invoke-rc.d (sudo apt-get install --reinstall init-system-
helpers), and run


   sudo patch /etc/network/if-up.d/openssh-server /tmp/openssh-server.patch

instead, and verify that this helps? Thanks!

** Patch added: "proposed patch to /etc/network/if-up.d/openssh-server"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1584393/+attachment/4701238/+files/openssh-server.patch

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

** Changed in: openssh (Ubuntu Xenial)
   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/1584393

Title:
  systemctl restart networking hangs reloading ssh.service

Status in openssh package in Ubuntu:
  In Progress
Status in openssh source package in Xenial:
  Confirmed

Bug description:
  Issues "systemctl restart networking" never exits. It hangs during a
  call to "systemctl reload ssh.service":

  ● networking.service - Raise network interfaces
 Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor 
preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
 Active: activating (start) since Sat 2016-05-21 21:41:58 UTC; 18s ago
   Docs: man:interfaces(5)
Process: 1288 ExecStop=/sbin/ifdown -a --read-environment (code=exited, 
status=0/SUCCESS)
Process: 1376 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] 
&& [ -n "$(ifquery --read-environment --list --exclude=lo)" ] &
   Main PID: 1383 (ifup)
  Tasks: 7 (limit: 512)
 Memory: 1.8M
CPU: 111ms
 CGroup: /system.slice/networking.service
 ├─1383 /sbin/ifup -a --read-environment
 ├─1479 /sbin/dhclient -1 -v -pf /run/dhclient.enp0s3.pid -lf 
/var/lib/dhcp/dhclient.enp0s3.leases -I -df /var/lib/dhcp/dhclient6
 ├─1480 /bin/sh -c /bin/run-parts --exit-on-error 
/etc/network/if-up.d
 ├─1481 /bin/run-parts --exit-on-error /etc/network/if-up.d
 ├─1504 /bin/sh /etc/network/if-up.d/openssh-server
 ├─1507 /bin/sh /usr/sbin/invoke-rc.d ssh reload
 └─1527 systemctl reload ssh.service

  Then issuing the same command from another terminal causes the first
  to exit successfully (the second also exists successfully).

  On the official vagrant image, I get this problem independently of
  whether the command is issued through and ssh session. I've gotten the
  same behavior on the official xenial AMIs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May 21 21:35:08 2016
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1584393/+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 1599491] Re: kdump-tools install script uses deprecated syntax

[Group.of.nepali.translators] [Bug 1599561] Re: Ubuntu 16.04.01 kdump: IP prefix is missing in the directory name after first dump during kdump over ssh.

[Group.of.nepali.translators] [Bug 1600391] Re: No b2 executable in libboost-tools-dev

[Group.of.nepali.translators] [Bug 1599068] Re: Add support for Intel 8265 Bluetooth ([8087:0A2B])

[Group.of.nepali.translators] [Bug 1584192] Re: CVE-2016-4440

[Group.of.nepali.translators] [Bug 1602579] Re: the system hangs in the dma driver when reboot or shutdown on a baytrail-m laptop

[Group.of.nepali.translators] [Bug 1602724] Re: Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

[Group.of.nepali.translators] [Bug 1603483] [NEW] [Xenial] Include Huawei PCIe SSD hio kernel driver

[Group.of.nepali.translators] [Bug 1599491] Re: kdump-tools install script uses deprecated syntax

[Group.of.nepali.translators] [Bug 1597699] Re: cc_mcollective.py fails on Ubuntu16.04

[Group.of.nepali.translators] [Bug 1592042] Re: Unable to start guests with memballoon default.

[Group.of.nepali.translators] [Bug 1584393] Re: systemctl restart networking hangs reloading ssh.service

12 matches

Site Navigation

Mail list logo

Footer information