[Group.of.nepali.translators] [Bug 1616943] Re: Can't auth against U1 in g-s

2016-09-22 Thread Robert Ancell
This is currently blocked on a security review for snapd-glib.

** Description changed:

- Use case:
+ [Impact]
+ Authentication using Ubuntu One credentials to install/remove snaps always  
fails. This is due to a behaviour change in snapd (no longer accepts login 
requests from non-root users). Existing credentials continue to work.
  
- Don't be already authenticated against U1 in g-s.
- Search for nmap
- See the top result is a snap.
- Try and install it
- Get prompted to log in to U1
- Type in your credentials
- Get told "incorrect email or password" even though you are typing in the 
correct info
+ [Test Case]
+ 1. Delete any existing credentials by deleting passwords marked 
"com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse.
+ 2. Start GNOME Software
+ 3. Search for a snap (e.g. "moon-buggy")
+ 4. Install Snap
+ 5. Enter Ubuntu One credentials when prompted
+ 
+ Expected result:
+ 
+ Observed result:
+ Dialog says "Incorrect email or password".
+ 
+ Expected result:
+ Authentication completes and the snap is installed.
+ 
+ [Regression Potential]
+ The solution is to use a new D-Bus service (snapd-login-service) and new 
library (snapd-glib) to get the Macaroon from snapd. This has some risk of 
introducing new bugs. The change is minimised (other snapd code paths 
unchanged) and the alternative is login to be impossible.

** No longer affects: snapd (Ubuntu)

** No longer affects: snapd (Ubuntu Xenial)

** No longer affects: snapd (Ubuntu Yakkety)

** Changed in: gnome-software (Ubuntu Yakkety)
   Status: Triaged => In Progress

** Changed in: gnome-software (Ubuntu Yakkety)
   Importance: High => Critical

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: High => Critical

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

Title:
  Can't auth against U1 in g-s

Status in gnome-software package in Ubuntu:
  In Progress
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  In Progress

Bug description:
  [Impact]
  Authentication using Ubuntu One credentials to install/remove snaps always  
fails. This is due to a behaviour change in snapd (no longer accepts login 
requests from non-root users). Existing credentials continue to work.

  [Test Case]
  1. Delete any existing credentials by deleting passwords marked 
"com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse.
  2. Start GNOME Software
  3. Search for a snap (e.g. "moon-buggy")
  4. Install Snap
  5. Enter Ubuntu One credentials when prompted

  Expected result:

  Observed result:
  Dialog says "Incorrect email or password".

  Expected result:
  Authentication completes and the snap is installed.

  [Regression Potential]
  The solution is to use a new D-Bus service (snapd-login-service) and new 
library (snapd-glib) to get the Macaroon from snapd. This has some risk of 
introducing new bugs. The change is minimised (other snapd code paths 
unchanged) and the alternative is login to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+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 1564076] Re: Can't launch snaps

2016-09-22 Thread Robert Ancell
** Description changed:

- Clicking the "launch" button from GNOME Software has no effect for
- snaps. This is because snapd doesn't provide any mechanism to determine
- what binaries / .desktop files a snap contains.
+ [Impact]
+ No method of launching snaps from GNOME Software.
+ 
+ [Test Case]
+ 1. Open GNOME Software
+ 2. Search for a snap (e.g. "moon-buggy")
+ 3. Click on snap description
+ 4. Click install
+ 
+ Expected result:
+ Snap is installed and launch button is shown (as for .deb apps)
+ 
+ Observed result:
+ Snap is installed; no launch button shown.
+ 
+ [Regression potential]
+ Low. We now take advantage of new snapd API to make snaps launchable.

** Also affects: gnome-software (Ubuntu Yakkety)
   Importance: High
 Assignee: Robert Ancell (robert-ancell)
   Status: Fix Committed

** Also affects: snapd (Ubuntu Yakkety)
   Importance: High
   Status: Fix Released

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

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

** Changed in: snapd (Ubuntu Xenial)
   Status: New => Fix Released

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

** No longer affects: snappy

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

Title:
  Can't launch snaps

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in snapd package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  New
Status in snapd source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  No method of launching snaps from GNOME Software.

  [Test Case]
  1. Open GNOME Software
  2. Search for a snap (e.g. "moon-buggy")
  3. Click on snap description
  4. Click install

  Expected result:
  Snap is installed and launch button is shown (as for .deb apps)

  Observed result:
  Snap is installed; no launch button shown.

  [Regression potential]
  Low. We now take advantage of new snapd API to make snaps launchable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1564076/+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 1626158] Re: image won't boot after upgrading to yakkety's 4.8 kernel because efi

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.8.0-15.16

---
linux (4.8.0-15.16) yakkety; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1626239

  * image won't boot after upgrading to yakkety's 4.8 kernel because efi
(LP: #1626158)
- [Config] CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-1
- [Config] CONFIG_NLS_CODEPAGE_437=y
- [Config] CONFIG_VFAT_FS=y

  * Miscellaneous Ubuntu changes
- SAUCE: seccomp: log actions even when audit is disabled

 -- Tim Gardner   Wed, 21 Sep 2016 06:41:03
-0600

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

Title:
  image won't boot after upgrading to yakkety's 4.8 kernel because efi

Status in cloud-images:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New

Bug description:
  If I use a relatively recent yakkety daily with uvt-kvm,

  com.ubuntu.cloud.daily:server:16.10:amd64 20160918

  and upgrade the kernel to the latest kernel (which happens to be 4.8),
  my VM won't boot any more. kern.log has:

  http://paste.ubuntu.com/23211671/

  and systemd complains that,

  [FAILED] Failed to mount /boot/efi
  See 'systemctl status boot-efi.mount' for details.

  and dumps me to a recovery console. Of course, I don't have EFI since
  I'm booting this thing on KVM. The problem here (I think) is that
  /boot/efi is in /etc/fstab, and systemd fails to boot when anything in
  /etc/fstab doesn't work.

  If I comment /boot/efi out of /etc/fstab, it boots just fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1626158/+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 1449062] Re: qemu-img calls need to be restricted by ulimit (CVE-2015-5162)

2016-09-22 Thread Hemanth Makkapati
** Also affects: glance
   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/1449062

Title:
  qemu-img calls need to be restricted by ulimit (CVE-2015-5162)

Status in Cinder:
  In Progress
Status in Cinder mitaka series:
  New
Status in Cinder newton series:
  In Progress
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive liberty series:
  Fix Committed
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in Glance:
  New
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Security Advisory:
  In Progress
Status in python-oslo.concurrency package in Ubuntu:
  Fix Released
Status in python-oslo.concurrency source package in Wily:
  Fix Committed
Status in python-oslo.concurrency source package in Xenial:
  Fix Released
Status in python-oslo.concurrency source package in Yakkety:
  Fix Released

Bug description:
  Reported via private E-mail from Richard W.M. Jones.

  Turns out qemu image parser is not hardened against malicious input
  and can be abused to allocated an arbitrary amount of memory and/or
  dump a lot of information when used with "--output=json".

  The solution seems to be: limit qemu-img ressource using ulimit.

  Example of abuse:

  -- afl1.img --

  $ /usr/bin/time qemu-img info afl1.img
  image: afl1.img
  [...]
  0.13user 0.19system 0:00.36elapsed 92%CPU (0avgtext+0avgdata 
642416maxresident)k
  0inputs+0outputs (0major+156927minor)pagefaults 0swaps

  The original image is 516 bytes, but it causes qemu-img to allocate
  640 MB.

  -- afl2.img --

  $ qemu-img info --output=json afl2.img | wc -l
  589843

  This is a 200K image which causes qemu-img info to output half a
  million lines of JSON (14 MB of JSON).

  Glance runs the --output=json variant of the command.

  -- afl3.img --

  $ /usr/bin/time qemu-img info afl3.img
  image: afl3.img
  [...]
  0.09user 0.35system 0:00.47elapsed 94%CPU (0avgtext+0avgdata 
1262388maxresident)k
  0inputs+0outputs (0major+311994minor)pagefaults 0swaps

  qemu-img allocates 1.3 GB (actually, a bit more if you play with
  ulimit -v).  It appears that you could change it to allocate
  arbitrarily large amounts of RAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1449062/+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 1625328] Re: linux-snapdragon: 4.4.0-1027.30 -proposed tracker

2016-09-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

** Changed in: kernel-sru-workflow/promote-to-proposed
   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/1625328

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

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

Bug description:
  This bug is for tracking the 4.4.0-1027.30 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 --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625303
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1625328/+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 1449062] Re: qemu-img calls need to be restricted by ulimit (CVE-2015-5162)

2016-09-22 Thread Sean McGinnis
** Also affects: cinder/mitaka
   Importance: Undecided
   Status: New

** Also affects: cinder/newton
   Importance: Medium
 Assignee: Sean McGinnis (sean-mcginnis)
   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/1449062

Title:
  qemu-img calls need to be restricted by ulimit (CVE-2015-5162)

Status in Cinder:
  In Progress
Status in Cinder mitaka series:
  New
Status in Cinder newton series:
  In Progress
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive liberty series:
  Fix Committed
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Security Advisory:
  In Progress
Status in python-oslo.concurrency package in Ubuntu:
  Fix Released
Status in python-oslo.concurrency source package in Wily:
  Fix Committed
Status in python-oslo.concurrency source package in Xenial:
  Fix Released
Status in python-oslo.concurrency source package in Yakkety:
  Fix Released

Bug description:
  Reported via private E-mail from Richard W.M. Jones.

  Turns out qemu image parser is not hardened against malicious input
  and can be abused to allocated an arbitrary amount of memory and/or
  dump a lot of information when used with "--output=json".

  The solution seems to be: limit qemu-img ressource using ulimit.

  Example of abuse:

  -- afl1.img --

  $ /usr/bin/time qemu-img info afl1.img
  image: afl1.img
  [...]
  0.13user 0.19system 0:00.36elapsed 92%CPU (0avgtext+0avgdata 
642416maxresident)k
  0inputs+0outputs (0major+156927minor)pagefaults 0swaps

  The original image is 516 bytes, but it causes qemu-img to allocate
  640 MB.

  -- afl2.img --

  $ qemu-img info --output=json afl2.img | wc -l
  589843

  This is a 200K image which causes qemu-img info to output half a
  million lines of JSON (14 MB of JSON).

  Glance runs the --output=json variant of the command.

  -- afl3.img --

  $ /usr/bin/time qemu-img info afl3.img
  image: afl3.img
  [...]
  0.09user 0.35system 0:00.47elapsed 94%CPU (0avgtext+0avgdata 
1262388maxresident)k
  0inputs+0outputs (0major+311994minor)pagefaults 0swaps

  qemu-img allocates 1.3 GB (actually, a bit more if you play with
  ulimit -v).  It appears that you could change it to allocate
  arbitrarily large amounts of RAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1449062/+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 1449062] Re: qemu-img calls need to be restricted by ulimit (CVE-2015-5162)

2016-09-22 Thread Sean McGinnis
** Also affects: cinder
   Importance: Undecided
   Status: New

** Changed in: cinder
   Importance: Undecided => Medium

** Changed in: cinder
 Assignee: (unassigned) => Sean McGinnis (sean-mcginnis)

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

Title:
  qemu-img calls need to be restricted by ulimit (CVE-2015-5162)

Status in Cinder:
  New
Status in Cinder mitaka series:
  New
Status in Cinder newton series:
  New
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive liberty series:
  Fix Committed
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Security Advisory:
  In Progress
Status in python-oslo.concurrency package in Ubuntu:
  Fix Released
Status in python-oslo.concurrency source package in Wily:
  Fix Committed
Status in python-oslo.concurrency source package in Xenial:
  Fix Released
Status in python-oslo.concurrency source package in Yakkety:
  Fix Released

Bug description:
  Reported via private E-mail from Richard W.M. Jones.

  Turns out qemu image parser is not hardened against malicious input
  and can be abused to allocated an arbitrary amount of memory and/or
  dump a lot of information when used with "--output=json".

  The solution seems to be: limit qemu-img ressource using ulimit.

  Example of abuse:

  -- afl1.img --

  $ /usr/bin/time qemu-img info afl1.img
  image: afl1.img
  [...]
  0.13user 0.19system 0:00.36elapsed 92%CPU (0avgtext+0avgdata 
642416maxresident)k
  0inputs+0outputs (0major+156927minor)pagefaults 0swaps

  The original image is 516 bytes, but it causes qemu-img to allocate
  640 MB.

  -- afl2.img --

  $ qemu-img info --output=json afl2.img | wc -l
  589843

  This is a 200K image which causes qemu-img info to output half a
  million lines of JSON (14 MB of JSON).

  Glance runs the --output=json variant of the command.

  -- afl3.img --

  $ /usr/bin/time qemu-img info afl3.img
  image: afl3.img
  [...]
  0.09user 0.35system 0:00.47elapsed 94%CPU (0avgtext+0avgdata 
1262388maxresident)k
  0inputs+0outputs (0major+311994minor)pagefaults 0swaps

  qemu-img allocates 1.3 GB (actually, a bit more if you play with
  ulimit -v).  It appears that you could change it to allocate
  arbitrarily large amounts of RAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1449062/+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 1593953] Re: EC_KEY_generate_key() causes FIPS self-test failure

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 1.0.2g-1ubuntu4.4

---
openssl (1.0.2g-1ubuntu4.4) xenial-security; urgency=medium

  * SECURITY UPDATE: Pointer arithmetic undefined behaviour
- debian/patches/CVE-2016-2177.patch: avoid undefined pointer
  arithmetic in ssl/s3_srvr.c, ssl/ssl_sess.c, ssl/t1_lib.c.
- CVE-2016-2177
  * SECURITY UPDATE: Constant time flag not preserved in DSA signing
- debian/patches/CVE-2016-2178-*.patch: preserve BN_FLG_CONSTTIME in
  crypto/dsa/dsa_ossl.c.
- CVE-2016-2178
  * SECURITY UPDATE: DTLS buffered message DoS
- debian/patches/CVE-2016-2179.patch: fix queue handling in
  ssl/d1_both.c, ssl/d1_clnt.c, ssl/d1_lib.c, ssl/d1_srvr.c,
  ssl/ssl_locl.h.
- CVE-2016-2179
  * SECURITY UPDATE: OOB read in TS_OBJ_print_bio()
- debian/patches/CVE-2016-2180.patch: fix text handling in
  crypto/ts/ts_lib.c.
- CVE-2016-2180
  * SECURITY UPDATE: DTLS replay protection DoS
- debian/patches/CVE-2016-2181-1.patch: properly handle unprocessed
  records in ssl/d1_pkt.c.
- debian/patches/CVE-2016-2181-2.patch: protect against replay attacks
  in ssl/d1_pkt.c, ssl/ssl.h, ssl/ssl_err.c.
- debian/patches/CVE-2016-2181-3.patch: update error code in ssl/ssl.h.
- CVE-2016-2181
  * SECURITY UPDATE: OOB write in BN_bn2dec()
- debian/patches/CVE-2016-2182.patch: don't overflow buffer in
  crypto/bn/bn_print.c.
- CVE-2016-2182
  * SECURITY UPDATE: SWEET32 Mitigation
- debian/patches/CVE-2016-2183.patch: move DES ciphersuites from HIGH
  to MEDIUM in ssl/s3_lib.c.
- CVE-2016-2183
  * SECURITY UPDATE: Malformed SHA512 ticket DoS
- debian/patches/CVE-2016-6302.patch: sanity check ticket length in
  ssl/t1_lib.c.
- CVE-2016-6302
  * SECURITY UPDATE: OOB write in MDC2_Update()
- debian/patches/CVE-2016-6303.patch: avoid overflow in
  crypto/mdc2/mdc2dgst.c.
- CVE-2016-6303
  * SECURITY UPDATE: OCSP Status Request extension unbounded memory growth
- debian/patches/CVE-2016-6304.patch: remove OCSP_RESPIDs from previous
  handshake in ssl/t1_lib.c.
- CVE-2016-6304
  * SECURITY UPDATE: Certificate message OOB reads
- debian/patches/CVE-2016-6306-1.patch: check lengths in ssl/s3_clnt.c,
  ssl/s3_srvr.c.
- debian/patches/CVE-2016-6306-2.patch: make message buffer slightly
  larger in ssl/d1_both.c, ssl/s3_both.c.
- CVE-2016-6306

 -- Marc Deslauriers   Thu, 22 Sep 2016
08:22:22 -0400

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2177

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2178

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2179

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2180

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2181

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2182

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2183

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6302

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6303

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6304

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6306

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

Title:
  EC_KEY_generate_key() causes FIPS self-test failure

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

Bug description:
  EC_KEY_generate_key() internally calls fips_pkey_signature_test()
  which performs a pairwise check by ECDSA signing/verifying, but some
  groups don't support ECDSA.

  For example, `openssl ecparam -genkey -name Oakley-EC2N-4` fails.
  Unfortunately `openssl ecparam` doesn't give any useful information so
  I modified a bit:

  ~~~
  diff --git a/apps/ecparam.c b/apps/ecparam.c
  index 71b67f4..db89c2f 100644
  --- a/apps/ecparam.c
  +++ b/apps/ecparam.c
  @@ -585,6 +585,7 @@ int MAIN(int argc, char **argv)
   
   if (!EC_KEY_generate_key(eckey)) {
   EC_KEY_free(eckey);
  +ERR_print_errors(bio_err);
   goto end;
   }
   if (outformat == FORMAT_ASN1)
  ~~~

  And I got:

  ~~~
  $ LD_LIBRARY_PATH=$(pwd)/target/lib ./target/bin/openssl ecparam -genkey 
-name Oakley-EC2N-4
  -BEGIN EC PARAMETERS-
  BgA=
  -END EC PARAMETERS-
  140614096975512:error:0306E06C:bignum routines:BN_mod_inverse:no 
inverse:bn_gcd.c:525:
  140614096975512:error:0306E06C:bignum routines:BN_mod_inverse:no 
inverse:bn_gcd.c:525:
  140614096975512:error:2A067003:lib(42):ECDSA_sign_setup:BN 

[Group.of.nepali.translators] [Bug 1594748] Re: CRYPTO_set_mem_functions() is broken

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 1.0.2g-1ubuntu4.4

---
openssl (1.0.2g-1ubuntu4.4) xenial-security; urgency=medium

  * SECURITY UPDATE: Pointer arithmetic undefined behaviour
- debian/patches/CVE-2016-2177.patch: avoid undefined pointer
  arithmetic in ssl/s3_srvr.c, ssl/ssl_sess.c, ssl/t1_lib.c.
- CVE-2016-2177
  * SECURITY UPDATE: Constant time flag not preserved in DSA signing
- debian/patches/CVE-2016-2178-*.patch: preserve BN_FLG_CONSTTIME in
  crypto/dsa/dsa_ossl.c.
- CVE-2016-2178
  * SECURITY UPDATE: DTLS buffered message DoS
- debian/patches/CVE-2016-2179.patch: fix queue handling in
  ssl/d1_both.c, ssl/d1_clnt.c, ssl/d1_lib.c, ssl/d1_srvr.c,
  ssl/ssl_locl.h.
- CVE-2016-2179
  * SECURITY UPDATE: OOB read in TS_OBJ_print_bio()
- debian/patches/CVE-2016-2180.patch: fix text handling in
  crypto/ts/ts_lib.c.
- CVE-2016-2180
  * SECURITY UPDATE: DTLS replay protection DoS
- debian/patches/CVE-2016-2181-1.patch: properly handle unprocessed
  records in ssl/d1_pkt.c.
- debian/patches/CVE-2016-2181-2.patch: protect against replay attacks
  in ssl/d1_pkt.c, ssl/ssl.h, ssl/ssl_err.c.
- debian/patches/CVE-2016-2181-3.patch: update error code in ssl/ssl.h.
- CVE-2016-2181
  * SECURITY UPDATE: OOB write in BN_bn2dec()
- debian/patches/CVE-2016-2182.patch: don't overflow buffer in
  crypto/bn/bn_print.c.
- CVE-2016-2182
  * SECURITY UPDATE: SWEET32 Mitigation
- debian/patches/CVE-2016-2183.patch: move DES ciphersuites from HIGH
  to MEDIUM in ssl/s3_lib.c.
- CVE-2016-2183
  * SECURITY UPDATE: Malformed SHA512 ticket DoS
- debian/patches/CVE-2016-6302.patch: sanity check ticket length in
  ssl/t1_lib.c.
- CVE-2016-6302
  * SECURITY UPDATE: OOB write in MDC2_Update()
- debian/patches/CVE-2016-6303.patch: avoid overflow in
  crypto/mdc2/mdc2dgst.c.
- CVE-2016-6303
  * SECURITY UPDATE: OCSP Status Request extension unbounded memory growth
- debian/patches/CVE-2016-6304.patch: remove OCSP_RESPIDs from previous
  handshake in ssl/t1_lib.c.
- CVE-2016-6304
  * SECURITY UPDATE: Certificate message OOB reads
- debian/patches/CVE-2016-6306-1.patch: check lengths in ssl/s3_clnt.c,
  ssl/s3_srvr.c.
- debian/patches/CVE-2016-6306-2.patch: make message buffer slightly
  larger in ssl/d1_both.c, ssl/s3_both.c.
- CVE-2016-6306

 -- Marc Deslauriers   Thu, 22 Sep 2016
08:22:22 -0400

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2177

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2178

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2179

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2180

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2181

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2182

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2183

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6302

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6303

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6304

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6306

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

Title:
  CRYPTO_set_mem_functions() is broken

Status in OpenSSL:
  Unknown
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Released

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  openssl:
Installed: 1.0.2g-1ubuntu4.1
Candidate: 1.0.2g-1ubuntu4.1
Version table:
   *** 1.0.2g-1ubuntu4.1 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.2g-1ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  CRYPTO_set_mem_functions() always returns 0 because library
  initialization already calls CRYPTO_malloc() and disables it:

  #0  CRYPTO_malloc (num=num@entry=1168, file=file@entry=0x770ae02c 
"fips_drbg_lib.c",
  line=line@entry=106) at mem.c:329
  #1  0x770596df in FIPS_drbg_new (type=type@entry=0, 
flags=flags@entry=0)
  at fips_drbg_lib.c:106
  #2  0x7705aeb9 in FIPS_drbg_health_check (
  dctx=dctx@entry=0x7731c960 ) at fips_drbg_selftest.c:760
  #3  0x770595f0 in FIPS_drbg_init (dctx=dctx@entry=0x7731c960 
,
  type=, flags=) at fips_drbg_lib.c:94
  #4  0x76fe38f3 in 

[Group.of.nepali.translators] [Bug 1614210] Re: Remove incomplete fips in openssl in xenial.

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 1.0.2g-1ubuntu4.4

---
openssl (1.0.2g-1ubuntu4.4) xenial-security; urgency=medium

  * SECURITY UPDATE: Pointer arithmetic undefined behaviour
- debian/patches/CVE-2016-2177.patch: avoid undefined pointer
  arithmetic in ssl/s3_srvr.c, ssl/ssl_sess.c, ssl/t1_lib.c.
- CVE-2016-2177
  * SECURITY UPDATE: Constant time flag not preserved in DSA signing
- debian/patches/CVE-2016-2178-*.patch: preserve BN_FLG_CONSTTIME in
  crypto/dsa/dsa_ossl.c.
- CVE-2016-2178
  * SECURITY UPDATE: DTLS buffered message DoS
- debian/patches/CVE-2016-2179.patch: fix queue handling in
  ssl/d1_both.c, ssl/d1_clnt.c, ssl/d1_lib.c, ssl/d1_srvr.c,
  ssl/ssl_locl.h.
- CVE-2016-2179
  * SECURITY UPDATE: OOB read in TS_OBJ_print_bio()
- debian/patches/CVE-2016-2180.patch: fix text handling in
  crypto/ts/ts_lib.c.
- CVE-2016-2180
  * SECURITY UPDATE: DTLS replay protection DoS
- debian/patches/CVE-2016-2181-1.patch: properly handle unprocessed
  records in ssl/d1_pkt.c.
- debian/patches/CVE-2016-2181-2.patch: protect against replay attacks
  in ssl/d1_pkt.c, ssl/ssl.h, ssl/ssl_err.c.
- debian/patches/CVE-2016-2181-3.patch: update error code in ssl/ssl.h.
- CVE-2016-2181
  * SECURITY UPDATE: OOB write in BN_bn2dec()
- debian/patches/CVE-2016-2182.patch: don't overflow buffer in
  crypto/bn/bn_print.c.
- CVE-2016-2182
  * SECURITY UPDATE: SWEET32 Mitigation
- debian/patches/CVE-2016-2183.patch: move DES ciphersuites from HIGH
  to MEDIUM in ssl/s3_lib.c.
- CVE-2016-2183
  * SECURITY UPDATE: Malformed SHA512 ticket DoS
- debian/patches/CVE-2016-6302.patch: sanity check ticket length in
  ssl/t1_lib.c.
- CVE-2016-6302
  * SECURITY UPDATE: OOB write in MDC2_Update()
- debian/patches/CVE-2016-6303.patch: avoid overflow in
  crypto/mdc2/mdc2dgst.c.
- CVE-2016-6303
  * SECURITY UPDATE: OCSP Status Request extension unbounded memory growth
- debian/patches/CVE-2016-6304.patch: remove OCSP_RESPIDs from previous
  handshake in ssl/t1_lib.c.
- CVE-2016-6304
  * SECURITY UPDATE: Certificate message OOB reads
- debian/patches/CVE-2016-6306-1.patch: check lengths in ssl/s3_clnt.c,
  ssl/s3_srvr.c.
- debian/patches/CVE-2016-6306-2.patch: make message buffer slightly
  larger in ssl/d1_both.c, ssl/s3_both.c.
- CVE-2016-6306

 -- Marc Deslauriers   Thu, 22 Sep 2016
08:22:22 -0400

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2177

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2178

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2179

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2180

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2181

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2182

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2183

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6302

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6303

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6304

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6306

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

Title:
  Remove incomplete fips in openssl in xenial.

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

Bug description:
  Package: openssl-1.0.2g-1ubuntu4.1
  Distro: xenial

  The openssl contains incomplete fips patches. In light that the fips
  is incomplete and will not be completed in the main archive and they
  are impacting customers, they should be withdrawn. See lp bugs
  1593953, 1591797, 1594748, 1588524, 1613658. Removal of these fips
  patches will remove these fips-related issues.

  [Test case]
  1. Problem in 1594748
  Note: this problem was reported in upstream openssl and testcase posted there 
also.
  https://rt.openssl.org/Ticket/Display.html?id=4559

  CRYPTO_set_mem_functions() always returns 0 because library
  initialization within fips code already calls CRYPTO_malloc() and
  disables it.

  This testcase should cause openssl to abort, but instead it returns a
  context.

  #include 
  #include 
  #include 
  void * my_alloc(size_t n) { abort(); }
  void my_free(void *p) { abort(); }
  void * my_realloc(void *p, size_t n) { abort(); }
  int main(int argc, const char **argv)
  {
    const SSL_METHOD *method;
    SSL_CTX *ctx;
    CRYPTO_set_mem_functions(my_alloc, my_realloc, 

[Group.of.nepali.translators] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

2016-09-22 Thread Dan Streetman
** Changed in: ifupdown (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: ifupdown (Ubuntu Precise)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: ifupdown (Ubuntu Trusty)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

** Project changed: dhcp => ifupdown

** Changed in: ifupdown (Ubuntu Precise)
   Status: New => Invalid

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

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

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

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

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

** Changed in: ifupdown (Ubuntu Precise)
   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/1447715

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in ifupdown:
  New
Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Precise:
  Invalid
Status in ifupdown source package in Trusty:
  In Progress
Status in ifupdown source package in Xenial:
  In Progress

Bug description:
  (Original bug description follows SRU info)

  [Description]

  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:

  Can't bind to dhcp address: Cannot assign requested address

  This is because ifupdown doesn't wait, after bringing the interface
  up, for it to complete its link-local Duplicate Address Detection
  (DAD), and the dhcp client can't bind to the link-local address
  because it's still in "tentative" state (until DAD completes).

  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.

  [Test Case]

  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0
  inet6 dhcp) and reboot.  It will fail to get a dhcp address during
  boot.

  [Regression]

  None

  
  -- original bug description --

  
  After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6 
address via DHCPv6. The root cause is that dhclient is exiting with the 
following message:

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

  exiting.
  -

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are
  invoked.

  Given that a downgrade allows me to obtain an IPv6 address I think
  this might be a bug in the ISC DHCP client rather than in
  NetworkManager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ifupdown/+bug/1447715/+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 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

2016-09-22 Thread Chris Johnston
** Also affects: ifupdown (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

** Also affects: ifupdown (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/1447715

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in ifupdown:
  New
Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Precise:
  Invalid
Status in ifupdown source package in Trusty:
  In Progress
Status in ifupdown source package in Xenial:
  In Progress

Bug description:
  (Original bug description follows SRU info)

  [Description]

  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:

  Can't bind to dhcp address: Cannot assign requested address

  This is because ifupdown doesn't wait, after bringing the interface
  up, for it to complete its link-local Duplicate Address Detection
  (DAD), and the dhcp client can't bind to the link-local address
  because it's still in "tentative" state (until DAD completes).

  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.

  [Test Case]

  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0
  inet6 dhcp) and reboot.  It will fail to get a dhcp address during
  boot.

  [Regression]

  None

  
  -- original bug description --

  
  After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6 
address via DHCPv6. The root cause is that dhclient is exiting with the 
following message:

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

  exiting.
  -

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are
  invoked.

  Given that a downgrade allows me to obtain an IPv6 address I think
  this might be a bug in the ISC DHCP client rather than in
  NetworkManager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ifupdown/+bug/1447715/+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 1625303] Re: linux: 4.4.0-39.59 -proposed tracker

2016-09-22 Thread 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: In Progress => 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-39.59 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 --
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 22. September 2016 18:06 UTC

** Description changed:

  This bug is for tracking the 4.4.0-39.59 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 --
  derivative-trackers-created: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Thursday, 22. September 2016 18:06 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/1625303

Title:
  linux: 4.4.0-39.59 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-39.59 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 --
  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/1625303/+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 1624641] Re: security updates with a new dependency don't get installed

2016-09-22 Thread Brian Murray
** Also affects: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  security updates with a new dependency don't get installed

Status in unattended-upgrades package in Ubuntu:
  Triaged
Status in unattended-upgrades source package in Xenial:
  Triaged

Bug description:
  E.g. chromium-browser has an update, but U-U does not update it. I saw
  in update-manager that the security update is available before running
  U-U. Afterwards I can install the update by update-manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:13:40 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624641/+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 1575727] Re: Cloud-init incorrect openstack datasource on dpkg-reconfigure

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1575727

Title:
  Cloud-init incorrect openstack datasource on dpkg-reconfigure

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

Bug description:
   Begin SRU Template 
  [Impact] 
  When re-configuring cloud-init package by running dpkg-reconfigure, the 
OpenStack data source is incorrectly written to the configuration file 
/etc/cloud/cloud.cfg.d/90_dpkg.cfg.

  The result is that dpkg-reconfigure and selecting OpenStack results in
  non-functional openstack datasource.

  [Test Case]
  # launch a container
  $ lxc launch 

[Group.of.nepali.translators] [Bug 1605749] Re: ConfigDrive: cloud-init fails to configure bond from network_data.json

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1605749

Title:
  ConfigDrive: cloud-init fails to configure bond from network_data.json

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

Bug description:
  cloud-init fails to configure bond interfaces from network_data.json

  There is a couple of reasons:

  Bond links found in network_data.json do not have a name attribute.
  cloud-init doesn't require the name attribute to exist in links. [1]
  However cloud-init later expects the links to have a name attribute
  and crashes when it doesn't have any. [2] The name attribute is not
  part of the OpenStack 

[Group.of.nepali.translators] [Bug 1576692] Re: fully support package installation in systemd

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1576692

Title:
  fully support package installation in systemd

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

Bug description:
  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]

  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't 

[Group.of.nepali.translators] [Bug 1607810] Re: Wrong default key 'fdqn' in POST_LIST_ALL / cc_phone_home.py

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1607810

Title:
  Wrong default key 'fdqn' in POST_LIST_ALL / cc_phone_home.py

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

Bug description:
   Begin SRU Template 
  [Impact] 
  A feature of cloud-init to post its fully qualified domain name
  to a web service was broken.

  [Test Case]
  ## Recreate failure

  $ cat >user-data 

[Group.of.nepali.translators] [Bug 1609899] Re: salt minion module writes minion keys to the wrong directory

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1609899

Title:
  salt minion module writes minion keys to the wrong directory

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

Bug description:
   Begin SRU Template 
  [Impact] 
  Salt minion config module of cloud-init would not work by default
  if 'public_key' and 'private_key' were provided.

  [Test Case]
  ## Recreate failure
  $ cat >user-data  "$p" &&
  apt-get update -q && apt-get -qy install cloud-init'
  $ lxc exec x1 -- sh -c 'apt-get -qy --purge remove salt-minion && rm -Rf 
/etc/salt'
  

[Group.of.nepali.translators] [Bug 1619394] Re: base64 user-data broken in OVF datasource

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1619394

Title:
  base64 user-data broken in OVF datasource

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

Bug description:
   Begin SRU Template 
  [Impact] 
  Users of the OVF datasource can not provide user-data that is base64 encoded.

  [Test Case]
  $ rel=xenial
  $ burl="http://cloud-images.ubuntu.com/daily/server/$rel/current/;
  $ disk="$rel-server-cloudimg-amd64-disk1.img"
  $ wget "$burl/$disk" -O "$disk"

  # prepare the ovftransport.iso
  $ git clone http://git.launchpad.net/cloud-init
  $ ( cd cloud-init/doc/sources/ovf && ./make-iso 

[Group.of.nepali.translators] [Bug 1610784] Re: cloud-init openstack.py code does not recognize network type 'tap'

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1610784

Title:
  cloud-init openstack.py code does not recognize network type 'tap'

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

Bug description:
   Begin SRU Template 
  [Impact]
  Certain versions and configurations of Openstack produce a config
  drive that has network devices described as 'type: tap'.  Previously
  cloud-init would require those to be 'type: ethernet' or other.

  The fix was to allow 'tap' to be considered a "physical" type from the
  guest VM's perspective.

  [Test Case]
   * Boot a VM in the reporters environment,
   * add proposed,

[Group.of.nepali.translators] [Bug 1615745] Re: package does not include dhcp hook scripts

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1615745

Title:
  package does not include dhcp hook scripts

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

Bug description:
   Begin SRU Template 
  [Impact]
  The bug here was that some files where not collected into the cloud-init deb.
  The result was that the improved support for Azure referenced in changelog as
  'Get Azure endpoint server from DHCP client' did not work as desired.

  The fix was in packaging to make sure the files are included.

  [Test Case]
  $ lxc launch ubuntu-daily:xenial x1
  $ lxc exec x1 /bin/bash

  Failure could be seen by:
  $ dpkg -L cloud-init | grep hook- || 

[Group.of.nepali.translators] [Bug 1612313] Re: maas datasource needs support for vendor-data

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1612313

Title:
  maas datasource needs support for vendor-data

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

Bug description:
   Begin SRU Template 
  [Impact] 
  This is a new feature adding 'vendor data' support to MAAS.
  MAAS in 2.X will make use of this feature in cloud-init.

  [Test Case]
  There are unit tests to test this, actual integration test is not easily
  done outside of MAAS.

  [Regression Potential] 
  Very low chance of regression.  Cloud-init will try once to retrive
  vendor-data and if it is present use it.  If not, it will go on.

  

[Group.of.nepali.translators] [Bug 1616831] Re: cloud-init doesn't prefer new APT config format when old and new are provided

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1616831

Title:
  cloud-init doesn't prefer new APT config format when old and new are
  provided

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

Bug description:
   Begin SRU Template 
  [Impact]
  New apt configuration was enabled, but if the user provided both new
  configuration format and old configuration format, then then cloud-init
  would error.

  The fixed behavior is to allow new and old and warn if they differ.

  This allows a user to provide the same data for older releases and
  newer release.

  [Test Case]
  # Recreate failure (this would 

[Group.of.nepali.translators] [Bug 1621180] Re: specifying apt_mirror of '' renders empty entries in /etc/apt/sources.list for uri

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1621180

Title:
  specifying apt_mirror of '' renders empty entries in
  /etc/apt/sources.list for uri

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in juju-core package in Ubuntu:
  New
Status in cloud-init source package in Xenial:
  Fix Released
Status in juju-core source package in Xenial:
  New

Bug description:
   Begin SRU Template 
  [Impact]
  This is a bug that existed only in development time in cloud-init and was 
exposed during uploads to yakkety.  It has never existed in xenial, but we do 
need to make sure that the function is still present.

  The impact was that if a user (juju) started an 

[Group.of.nepali.translators] [Bug 1621336] Re: snapd.boot-ok.service hangs eternally on cloud image upgrades

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1621336

Title:
  snapd.boot-ok.service hangs eternally on cloud image upgrades

Status in cloud-init package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Triaged
Status in cloud-init source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  In Progress

Bug description:
   Begin SRU Template [cloud-init] 
  [Impact] 
  One of cloud-init's features is to upgrade the system during first boot so 
that it is fully up to date when the user code starts running.

  [Test Case]
  launch an old instance of 16.04 that will need an update to snapd with
  user-data that indicates a package upgrade should be done.

  $ lxc image show 

[Group.of.nepali.translators] [Bug 1623868] Re: cloud-final.service does not run due to dependency cycle

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.1

---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream release 0.7.8.
  * New upstream snapshot.
- systemd: put cloud-init.target After multi-user.target (LP: #1623868)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * debian/control: add Breaks of older versions of walinuxagent (LP:
#1623570)

cloud-init (0.7.7-31-g65ace7b-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/control: fix missing dependency on python3-serial,
and make SmartOS datasource work.
  * debian/cloud-init.templates fix capitalisation in template so
dpkg-reconfigure works to select OpenStack. (LP: #1575727)
  * d/README.source, d/control, d/new-upstream-snapshot, d/rules: sync
with yakkety for changes due to move to git.
  * d/rules: change PYVER=python3 to PYVER=3 to adjust to upstream change.
  * debian/rules, debian/cloud-init.install: remove install file
to ensure expected files are collected into cloud-init deb.
(LP: #1615745)
  * debian/dirs: remove obsolete / unused file.
  * upstream move from bzr to git.
  * New upstream snapshot.
- Allow link type of null in network_data.json [Jon Grimm] (LP: #1621968)
- DataSourceOVF: fix user-data as base64 with python3 (LP: #1619394)
- remove obsolete .bzrignore
- systemd: Better support package and upgrade. (LP: #1576692, #1621336)
- tests: cleanup tempdirs in apt_source tests
- apt config conversion: treat empty string as not provided. (LP: #1621180)
- Fix typo in default keys for phone_home [Roland Sommer] (LP: #1607810)
- salt minion: update default pki directory for newer salt minion.
  (LP: #1609899)
- bddeb: add --release flag to specify the release in changelog.
- apt-config: allow both old and new format to be present.
  [Christian Ehrhardt] (LP: #1616831)
- python2.6: fix dict comprehension usage in _lsb_release. [Joshua Harlow]
- Add a module that can configure spacewalk. [Joshua Harlow]
- add install option for openrc [Matthew Thode]
- Generate a dummy bond name for OpenStack (LP: #1605749)
- network: fix get_interface_mac for bond slave, read_sys_net for ENOTDIR
- azure dhclient-hook cleanups
- Minor cleanups to atomic_helper and add unit tests.
- Fix Gentoo net config generation [Matthew Thode]
- distros: fix get_primary_arch method use of os.uname [Andrew Jorgensen]
- Apt: add new apt configuration format [Christian Ehrhardt]
- Get Azure endpoint server from DHCP client [Brent Baude]
- DigitalOcean: use the v1.json endpoint [Ben Howard]
- MAAS: add vendor-data support (LP: #1612313)
- Upgrade to a configobj package new enough to work [Joshua Harlow]
- ConfigDrive: recognize 'tap' as a link type. (LP: #1610784)
- NoCloud: fix bug providing network-interfaces via meta-data.
  (LP: 1577982)
- Add distro tags on config modules that should have it [Joshua Harlow]
- ChangeLog: update changelog for previous commit.
- add ntp config module [Ryan Harper]
- SmartOS: more improvements for network configuration
- tools/read-version: update to address change in version
- make-tarball: older versions of git with --format=tar.
- read-version: do not attempt git-describe if no git.
- Newer requests have strong type validation [Joshua Harlow]
- For upstream snapshot versions do not modify git-describe output.
- adjust signal_handler for version changes.
- revert unintended change to ubuntu sources list
- drop modification of version during make-tarball, tools changes.
- adjust tools and version information.
- Update build tools to work with git [Lars Kellogg-Stedman]
- fix pep8 errors in mcollective unit tests
- mcollective: add tests, cleanups and bug fix when no config in /etc.

 -- Scott Moser   Thu, 15 Sep 2016 09:57:27 -0400

** Changed in: cloud-init (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/1623868

Title:
  cloud-final.service does not run due to dependency cycle

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

Bug description:
   Begin SRU Template 
  [Impact]
  As part of the change in bug 1576692, we made cloud-final.target
  run After multi-user.target.  That created a dependency loop between
  cloud-init.target and multi-user.target and cloud-final.target.

  Most of the time systemd would break that loop by dropping
  cloud-init.target.  But sometimes, it would break the loop by dropping
  cloud-final.target, which would mean that user scripts do not run
  and generally 

[Group.of.nepali.translators] [Bug 1586933] Re: gpu-manager's drm output detection affects boot time

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-drivers-common - 1:0.4.17.2

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

  [ Alberto Milone ]
  * gpu-manager.c:
- Fix memory leak in get_alternatives(). Make sure to always free
  alternatives->current_core and alternatives->current_egl.
- Partially drop the drm code, and get information about connectors
  from sysf. This fixes a long standing performance issue (LP: #1586933).
- Disable persistence mode before powering down the dGPU.
  If persistence mode is not disabled, gpu-manager will not be able to
  unload the nvidia module (LP: #1619306).
- Make sure to load and unload nvidia-drm. This fixes a problem that
  prevents the dGPU from being powered off in hybrid systems with
  recent nvidia drivers (LP: #1619306).

  [ Ying-Chun Liu (PaulLiu) ]
  * Quirks/quirkinfo.py:
- Catch and ignore UnicodeDecodeErrors in dmi info, as some machines
  may report board_name as 0a to mean empty, and this
  causes an error in python 3 (LP: #1320868).

 -- Alberto Milone   Mon, 06 Jun 2016
12:49:19 +0200

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

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

Title:
  gpu-manager's drm output detection affects boot time

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released

Bug description:
  SRU request:

  [Impact]
  The current drm code to probe the connected outputs is too resource 
intensive, and slow down the boot process.

  [Test Case]
  1) Boot Ubuntu and run the following command, looking for gpu-manager:
  systemd-analize blame

  This will show how long gpu-manager took. Write down the number

  2) Install the package from -proposed, and run systemd-analize blame.
  See if the number has become smaller.

  [Regression Potential]
  Low, all the changes are already included in Yakkety.

  
  _
  Rather than calling drm directly, gpu-manager should simply check the outputs 
connector status by using the sysfs filesystem (e.g. 
/sys/class/drm/card0-HDMI-A-1/status, etc.), thus relying on data that is 
already available.

  This should make gpu-manager a bit less resource intensive, especially
  on boot.

  The attached perf shows the problem in gpu-manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1586933/+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 1320868] Re: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-drivers-common - 1:0.4.17.2

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

  [ Alberto Milone ]
  * gpu-manager.c:
- Fix memory leak in get_alternatives(). Make sure to always free
  alternatives->current_core and alternatives->current_egl.
- Partially drop the drm code, and get information about connectors
  from sysf. This fixes a long standing performance issue (LP: #1586933).
- Disable persistence mode before powering down the dGPU.
  If persistence mode is not disabled, gpu-manager will not be able to
  unload the nvidia module (LP: #1619306).
- Make sure to load and unload nvidia-drm. This fixes a problem that
  prevents the dGPU from being powered off in hybrid systems with
  recent nvidia drivers (LP: #1619306).

  [ Ying-Chun Liu (PaulLiu) ]
  * Quirks/quirkinfo.py:
- Catch and ignore UnicodeDecodeErrors in dmi info, as some machines
  may report board_name as 0a to mean empty, and this
  causes an error in python 3 (LP: #1320868).

 -- Alberto Milone   Mon, 06 Jun 2016
12:49:19 +0200

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

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

Title:
  "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position
  0: invalid start byte" when removing nvidia-current package

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released

Bug description:
  $sudo apt-get remove nvidia-current
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package 'nvidia-current' is not installed, so not removed
  The following package was automatically installed and is no longer required:
linux-image-generic
  Use 'apt-get autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up nvidia-331 (331.38-0ubuntu7) ...
  INFO:Enable nvidia-331
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  Traceback (most recent call last):
File "/usr/bin/quirks-handler", line 65, in 
  operation_status = main(options)
File "/usr/bin/quirks-handler", line 44, in main
  quirks = Quirks.quirkapplier.QuirkChecker(options.package_enable, 
path=quirks_path)
File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 38, in 
__init__
  self._system_info = self.get_system_info()
File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 64, in 
get_system_info
  return quirk_info.get_dmi_info()
File "/usr/lib/python3/dist-packages/Quirks/quirkinfo.py", line 46, in 
get_dmi_info
  'class', 'dmi', 'id', item)).read().strip()
File "/usr/lib/python3.4/codecs.py", line 313, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: 
invalid start byte
  dpkg: error processing package nvidia-331 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   nvidia-331
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1320868/+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 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-drivers-common - 1:0.4.17.2

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

  [ Alberto Milone ]
  * gpu-manager.c:
- Fix memory leak in get_alternatives(). Make sure to always free
  alternatives->current_core and alternatives->current_egl.
- Partially drop the drm code, and get information about connectors
  from sysf. This fixes a long standing performance issue (LP: #1586933).
- Disable persistence mode before powering down the dGPU.
  If persistence mode is not disabled, gpu-manager will not be able to
  unload the nvidia module (LP: #1619306).
- Make sure to load and unload nvidia-drm. This fixes a problem that
  prevents the dGPU from being powered off in hybrid systems with
  recent nvidia drivers (LP: #1619306).

  [ Ying-Chun Liu (PaulLiu) ]
  * Quirks/quirkinfo.py:
- Catch and ignore UnicodeDecodeErrors in dmi info, as some machines
  may report board_name as 0a to mean empty, and this
  causes an error in python 3 (LP: #1320868).

 -- Alberto Milone   Mon, 06 Jun 2016
12:49:19 +0200

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

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

Title:
  SRU request: Include the 367 driver in Ubuntu 16.04

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-367 source package in Xenial:
  Fix Committed
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  The nvidia packages in Ubuntu 16.04 do not support recent NVIDIA GPUs.

  The new driver also requires changes in ubuntu-drivers-common, as gpu-
  manager needs to be able to unload the nvidia-drm module in order to
  power down the dGPU in hybrid systems.

  
  [Test Case]
  1) Enable the xenial-proposed repository, and install the nvidia-367 package

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

  [Regression Potential]
  Low, the packages are already in Yakkety.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+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 1625932] Re: Backlight does not change when adjust it higher than 50% after S3

2016-09-22 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/1625932

Title:
  Backlight does not change when adjust it higher than 50% after S3

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

Bug description:
  Backlight does not change when adjust it higher than 50% after S3

  Steps:
  1. Install ubuntu 16.04 and boot into OS
  2. suspend system
  3. resume system from S3
  4. Try to adjust brightness level

  Expected results: Backlight should be changed when adjust it

  Actual results: Backlight does not change when adjust it higher than
  50% after S3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1625932/+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 1572260] Re: gvfs-smb-browse hogs CPU after only opening nautilus

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package samba - 2:4.3.9+dfsg-0ubuntu0.16.04.3

---
samba (2:4.3.9+dfsg-0ubuntu0.16.04.3) xenial; urgency=medium

  * debian/patches/git_smbclient_cpu.patch:
- backport upstream patch to fix smbclient users hanging/eating cpu on
  trying to contact a machine which is not there (lp: #1572260)

 -- Sebastien Bacher   Thu, 11 Aug 2016 10:39:10
+0200

** Changed in: samba (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/1572260

Title:
  gvfs-smb-browse hogs CPU after only opening nautilus

Status in gvfs package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Xenial:
  Invalid
Status in samba source package in Xenial:
  Fix Released

Bug description:
  upgraded to 16.04 from 15.10 
  - the process in subject hogs 25% CPU after only starting nautilus, and keeps 
hogging it "forever"   - no samba browsing needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 19 20:03:12 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  InstallationDate: Installed on 2012-10-15 (1281 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121015.2)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (13 days ago)

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

2016-09-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

** Description changed:

  This bug is for tracking the 4.4.0-1027.30 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 --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625303
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Thursday, 22. September 2016 16:48 UTC

** Description changed:

  This bug is for tracking the 4.4.0-1027.30 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 --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625303
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Thursday, 22. September 2016 16:48 UTC
+ phase: Uploaded

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1027.30 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 --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625303
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1625328/+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 1620754] Re: hash(datetime.datetime(...)) fails with python3.5 on armhf (on an arm64 host) with a bus error

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package python3.4 - 3.4.3-1ubuntu1~14.04.4

---
python3.4 (3.4.3-1ubuntu1~14.04.4) trusty-proposed; urgency=medium

  * SRU: LP: #1620754: Fix invalid code in pyhash/siphash24. Issue
#28055.

 -- Matthias Klose   Sat, 10 Sep 2016 10:26:44 +0200

** Changed in: python3.4 (Ubuntu Trusty)
   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/1620754

Title:
  hash(datetime.datetime(...)) fails with python3.5 on armhf (on an
  arm64 host) with a bus error

Status in Python:
  New
Status in python-cryptography package in Ubuntu:
  Fix Released
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python3.4 source package in Trusty:
  Fix Released
Status in python3.5 source package in Xenial:
  Fix Released

Bug description:
  seen with
  https://launchpad.net/ubuntu/+source/python-cryptography/1.4-2/+build/10476934
  https://launchpad.net/ubuntu/+source/python-cryptography/1.5-1/+build/10678695

  the TestInvalidityDate.test_invalid_invalidity_date test is the first
  one to fail with a bus error. No reasonable traceback from gdb.

  Trying to build python3.5, python-cffi and python-cryptography with
  -mno-unaligned-access doesn't fix the issue (buildds running on a
  64bit kernel).

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1620754/+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 1572260] Re: gvfs-smb-browse hogs CPU after only opening nautilus

2016-09-22 Thread Amr Ibrahim
** Changed in: gvfs (Ubuntu Xenial)
   Status: Confirmed => Invalid

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

Title:
  gvfs-smb-browse hogs CPU after only opening nautilus

Status in gvfs package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Xenial:
  Invalid
Status in samba source package in Xenial:
  Fix Committed

Bug description:
  upgraded to 16.04 from 15.10 
  - the process in subject hogs 25% CPU after only starting nautilus, and keeps 
hogging it "forever"   - no samba browsing needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 19 20:03:12 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  InstallationDate: Installed on 2012-10-15 (1281 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121015.2)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1572260/+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 1608499] Re: Parallel depmod failure with dkms autoinstall

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.2

---
dkms (2.2.0.3-2ubuntu11.2) xenial; urgency=medium

  * debian/patches/Parallel-depmod-failure.patch: (LP: #1608499)
 - Backport fix from 2.3 to fix a race condition in dkms autoinstall

 -- Robert Hooker   Thu, 08 Sep 2016 15:38:21 -0400

** Changed in: dkms (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/1608499

Title:
  Parallel depmod failure with dkms autoinstall

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released

Bug description:
  Description of problem
  --

  "dkms autoinstall" installs DKMS modules in parallel, potentially executing
  several depmod instances in parallel.

  The resulting race condition causes depmod to fail and dkms install as
  well.

  This problem is critical because some DKMS modules can be left in "built"
  state after a kernel upgrade, thus the kernel modules will not be re-installed
  in /lib/modules/.

  Ubuntu release
  --
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  DKMS package version
  

  # apt-cache policy dkms
  dkms:
Installed: 2.2.0.3-2ubuntu11
Candidate: 2.2.0.3-2ubuntu11
Version table:
   *** 2.2.0.3-2ubuntu11 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  Steps to reproduce
  --

  Add 2 simple DKMS modules, mod1 and mod2 (test case in attachment) with
  "dkms add", then run "dkms autoinstall".

  # dkms add mod1 ; dkms add mod2

  Creating symlink /var/lib/dkms/mod1/1.0/source ->
   /usr/src/mod1-1.0

  DKMS: add completed.

  Creating symlink /var/lib/dkms/mod2/1.0/source ->
   /usr/src/mod2-1.0

  DKMS: add completed.

  # dkms autoinstall

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area...
  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area
  .make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod2/1.0/build S=/var/lib/dkms/mod2/1.0/build modules...
  make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod1/1.0/build S=/var/lib/dkms/mod1/1.0/build modules.

  cleaning build area...cleaning build area.

  
  DKMS: build completed.

  DKMS: build completed.

  mod2.ko:
  Running module version sanity check.

  mod1.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/

  
  depmod...depmod...(bad exit status: 1)

   Uninstall Beginning 
  Module:  mod2
  Version: 1.0
  Kernel:  4.4.0-28-generic (x86_64)
  -

  
  DKMS: install completed.

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  mod2.ko:
   - Uninstallation
 - Deleting from: /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.

  depmod

  DKMS: uninstall completed.
  Error! Problems with depmod detected.  Automatically uninstalling this module.
  DKMS: Install Failed (depmod problems).  Module rolled back to built state.

  root@ubuntu1604:~/dkms-depmod# dkms status
  mod1, 1.0, 4.4.0-28-generic, x86_64: installed
  mod2, 1.0, 4.4.0-28-generic, x86_64: built

  => mod2 should be in "installed" state as well.

  # modinfo mod1
  filename:   /lib/modules/4.4.0-28-generic/updates/dkms/mod1.ko
  author: 6WIND
  license:GPL
  srcversion: 8D30BAE7A8F4D38F20AEB57
  depends:
  vermagic:   4.4.0-28-generic SMP mod_unload modversions 

  # modinfo mod2
  modinfo: ERROR: Module mod2 not found.

  Solution
  

  The problem is fixed in dkms official repository by commit
  
https://github.com/dell-oss/dkms/commit/00114cbc0a1f8c0aa5143808205d1a7cc9e58d3b
  (also in attachment).

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

___
Mailing list: 

[Group.of.nepali.translators] [Bug 1608499] Re: Parallel depmod failure with dkms autoinstall

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package dkms - 2.2.0.3-1.1ubuntu5.14.04.8

---
dkms (2.2.0.3-1.1ubuntu5.14.04.8) trusty; urgency=medium

  * debian/patches/Parallel-depmod-failure.patch: (LP: #1608499)
- Backport fix from 2.3 to fix a race condition in dkms autoinstall

 -- Robert Hooker   Thu, 08 Sep 2016 16:47:45 -0400

** Changed in: dkms (Ubuntu Trusty)
   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/1608499

Title:
  Parallel depmod failure with dkms autoinstall

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released

Bug description:
  Description of problem
  --

  "dkms autoinstall" installs DKMS modules in parallel, potentially executing
  several depmod instances in parallel.

  The resulting race condition causes depmod to fail and dkms install as
  well.

  This problem is critical because some DKMS modules can be left in "built"
  state after a kernel upgrade, thus the kernel modules will not be re-installed
  in /lib/modules/.

  Ubuntu release
  --
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  DKMS package version
  

  # apt-cache policy dkms
  dkms:
Installed: 2.2.0.3-2ubuntu11
Candidate: 2.2.0.3-2ubuntu11
Version table:
   *** 2.2.0.3-2ubuntu11 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  Steps to reproduce
  --

  Add 2 simple DKMS modules, mod1 and mod2 (test case in attachment) with
  "dkms add", then run "dkms autoinstall".

  # dkms add mod1 ; dkms add mod2

  Creating symlink /var/lib/dkms/mod1/1.0/source ->
   /usr/src/mod1-1.0

  DKMS: add completed.

  Creating symlink /var/lib/dkms/mod2/1.0/source ->
   /usr/src/mod2-1.0

  DKMS: add completed.

  # dkms autoinstall

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area...
  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area
  .make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod2/1.0/build S=/var/lib/dkms/mod2/1.0/build modules...
  make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod1/1.0/build S=/var/lib/dkms/mod1/1.0/build modules.

  cleaning build area...cleaning build area.

  
  DKMS: build completed.

  DKMS: build completed.

  mod2.ko:
  Running module version sanity check.

  mod1.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/

  
  depmod...depmod...(bad exit status: 1)

   Uninstall Beginning 
  Module:  mod2
  Version: 1.0
  Kernel:  4.4.0-28-generic (x86_64)
  -

  
  DKMS: install completed.

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  mod2.ko:
   - Uninstallation
 - Deleting from: /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.

  depmod

  DKMS: uninstall completed.
  Error! Problems with depmod detected.  Automatically uninstalling this module.
  DKMS: Install Failed (depmod problems).  Module rolled back to built state.

  root@ubuntu1604:~/dkms-depmod# dkms status
  mod1, 1.0, 4.4.0-28-generic, x86_64: installed
  mod2, 1.0, 4.4.0-28-generic, x86_64: built

  => mod2 should be in "installed" state as well.

  # modinfo mod1
  filename:   /lib/modules/4.4.0-28-generic/updates/dkms/mod1.ko
  author: 6WIND
  license:GPL
  srcversion: 8D30BAE7A8F4D38F20AEB57
  depends:
  vermagic:   4.4.0-28-generic SMP mod_unload modversions 

  # modinfo mod2
  modinfo: ERROR: Module mod2 not found.

  Solution
  

  The problem is fixed in dkms official repository by commit
  
https://github.com/dell-oss/dkms/commit/00114cbc0a1f8c0aa5143808205d1a7cc9e58d3b
  (also in attachment).

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

___
Mailing list: 

[Group.of.nepali.translators] [Bug 1620557] Re: weather.noaa.gov was shut down

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package libgweather - 3.10.2-0ubuntu3

---
libgweather (3.10.2-0ubuntu3) trusty-proposed; urgency=medium

  * Switch to the new METAR data provider, the previous one was shut down
(update_metar_provider.patch, LP: #1620557).

 -- Dmitry Shachnev   Sat, 10 Sep 2016 17:10:21
+0300

** Changed in: libgweather (Ubuntu Trusty)
   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/1620557

Title:
  weather.noaa.gov was shut down

Status in libgweather:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Trusty:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Released

Bug description:
  The provider which libgweather was using was shut down in August.

  We need to update libgweather in Xenial to new upstream micro release,
  3.18.2, which switched to a new METAR data provider.

  Impact: this affects all libgweather-using applications, makes them
  unable to retrieve weather data.

  Test Case: make sure Weather applet in gnome-applets is able to
  display weather information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1620557/+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 1620754] Re: hash(datetime.datetime(...)) fails with python3.5 on armhf (on an arm64 host) with a bus error

2016-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package python3.5 - 3.5.2-2~16.04

---
python3.5 (3.5.2-2~16.04) xenial-proposed; urgency=medium

  * SRU: LP: #1620754: Fix invalid code in pyhash/siphash24. Issue
#28055.

 -- Matthias Klose   Sat, 10 Sep 2016 10:21:44 +0200

** Changed in: python3.5 (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/1620754

Title:
  hash(datetime.datetime(...)) fails with python3.5 on armhf (on an
  arm64 host) with a bus error

Status in Python:
  New
Status in python-cryptography package in Ubuntu:
  Fix Released
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python3.4 source package in Trusty:
  Fix Released
Status in python3.5 source package in Xenial:
  Fix Released

Bug description:
  seen with
  https://launchpad.net/ubuntu/+source/python-cryptography/1.4-2/+build/10476934
  https://launchpad.net/ubuntu/+source/python-cryptography/1.5-1/+build/10678695

  the TestInvalidityDate.test_invalid_invalidity_date test is the first
  one to fail with a bus error. No reasonable traceback from gdb.

  Trying to build python3.5, python-cffi and python-cryptography with
  -mno-unaligned-access doesn't fix the issue (buildds running on a
  64bit kernel).

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1620754/+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 1626201] Re: missing python*-dev and gcc dependencies

2016-09-22 Thread Martin Pitt
Only synced to y-proposed, will auto-close again when it lands.

** Changed in: python-virtualenv (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  missing python*-dev and gcc dependencies

Status in python-virtualenv package in Ubuntu:
  Fix Committed
Status in python-virtualenv source package in Xenial:
  Triaged

Bug description:
  http://autopkgtest.ubuntu.com/packages/python-virtualenv/yakkety/amd64
  and http://ci.debian.net/packages/p/python-virtualenv/unstable/amd64/
  recently started failing. Apparently until recently it downloaded the
  "chroot":

Downloading world-3.1.1-py2.py3-none-any.whl
  Requirement already satisfied (use --upgrade to upgrade): setuptools in 
/tmp/autopkgtest.zlm6cw/autopkgtest_tmp/p2a/lib/python2.7/site-packages (from 
world)
  Installing collected packages: world
  Successfully installed world-3.1.1
  it originates from ITALY

  but now:

Downloading world-4.0.tar.gz
  Complete output from command python setup.py egg_info:
  Python 3.4.0 or better is required

  and then it apparently tries to build it, but is missing gcc and
  python?-dev.

  So some external resource changed and broke the test, which uncovers
  that python?-virtualenv ought to Recommends: gcc, python?-dev.

  Then the test should add "Restrictions: needs-recommends"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1626201/+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 1626201] Re: missing python*-dev and gcc dependencies

2016-09-22 Thread Barry Warsaw
This bug was fixed in the package python-virtualenv - 15.0.3+ds-2

---
python-virtualenv (15.0.3+ds-2) unstable; urgency=medium

  * d/tests/smoketest-{2,3}: Pin the version of world that pip installs to
less than 4 so that no C is required.  (LP: #1626201)

 -- Barry Warsaw   Wed, 21 Sep 2016 14:01:01 -0400

** Changed in: python-virtualenv (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/1626201

Title:
  missing python*-dev and gcc dependencies

Status in python-virtualenv package in Ubuntu:
  Fix Released
Status in python-virtualenv source package in Xenial:
  Triaged

Bug description:
  http://autopkgtest.ubuntu.com/packages/python-virtualenv/yakkety/amd64
  and http://ci.debian.net/packages/p/python-virtualenv/unstable/amd64/
  recently started failing. Apparently until recently it downloaded the
  "chroot":

Downloading world-3.1.1-py2.py3-none-any.whl
  Requirement already satisfied (use --upgrade to upgrade): setuptools in 
/tmp/autopkgtest.zlm6cw/autopkgtest_tmp/p2a/lib/python2.7/site-packages (from 
world)
  Installing collected packages: world
  Successfully installed world-3.1.1
  it originates from ITALY

  but now:

Downloading world-4.0.tar.gz
  Complete output from command python setup.py egg_info:
  Python 3.4.0 or better is required

  and then it apparently tries to build it, but is missing gcc and
  python?-dev.

  So some external resource changed and broke the test, which uncovers
  that python?-virtualenv ought to Recommends: gcc, python?-dev.

  Then the test should add "Restrictions: needs-recommends"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1626201/+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 1626258] Re: [SRU] AttributeError: 'Requirement' object has no attribute 'project_name'

2016-09-22 Thread Louis Bouchard
** Also affects: python-pip (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: python-pip (Ubuntu Xenial)
 Assignee: (unassigned) => Felipe Reyes (freyes)

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

** Changed in: python-pip (Ubuntu Xenial)
   Status: New => In Progress

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

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

Title:
  [SRU] AttributeError: 'Requirement' object has no attribute
  'project_name'

Status in python-pip package in Ubuntu:
  Invalid
Status in python-pip source package in Xenial:
  In Progress

Bug description:
  [impact]

  pip 8.1.1 (xenial) tries to access properties that were dropped from
  the Requirement class and when pip's code tries to access
  Requirement.project_name fails, this was fixed in 8.1.2.

  Any user trying to install a package that triggers the
  pkg_resources.VersionConflict exception during will get the error
  "AttributeError: 'Requirement' object has no attribute 'project_name'"

  [Test Case]

  # wget 
https://pypi.python.org/packages/49/6f/183063f01aae1e025cf0130772b55848750a2f3a89bfa11b385b35d7329d/requests-2.10.0.tar.gz
  # wget 
https://pypi.python.org/packages/2e/ad/e627446492cc374c284e82381215dcd9a0a87c4f6e90e9789afefe6da0ad/requests-2.11.1.tar.gz
  # pip install requests-2.10.0.tar.gz
  # pip install requests-2.11.1.tar.gz

  Expected result:

  pip installs requests 2.11.1

  Actual result:

  pip fails with the following exception

  root@pip-x:/home/ubuntu# pip install requests-2.11.1.tar.gz
  Processing ./requests-2.11.1.tar.gz
  Exception:
  Traceback (most recent call last):
    File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 209, in 
main
  status = self.run(options, args)
    File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 328, 
in run
  wb.build(autobuilding=True)
    File "/usr/lib/python2.7/dist-packages/pip/wheel.py", line 748, in build
  self.requirement_set.prepare_files(self.finder)
    File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 360, in 
prepare_files
  ignore_dependencies=self.ignore_dependencies))
    File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 600, in 
_prepare_file
  req_to_install.check_if_exists()
    File "/usr/lib/python2.7/dist-packages/pip/req/req_install.py", line 1011, 
in check_if_exists
  self.req.project_name
  AttributeError: 'Requirement' object has no attribute 'project_name'
  You are using pip version 8.1.1, however version 8.1.2 is available.
  You should consider upgrading via the 'pip install --upgrade pip' command.

  [Regression Potential]

  * None, this change is already part of 8.1.2, and most of the change
  is already part of the ubuntu package, there is just one last place
  where the code is accessing Requirement.project_name

  [Other info]

  From 8e236dd6a09bd2f70f9d4fc886da8c354d4c58f2 Mon Sep 17 00:00:00 2001
  From: Donald Stufft 
  Date: Wed, 11 Nov 2015 18:51:46 -0500
  Subject: [PATCH] Update to use the Requirement class from packaging
  https://github.com/pypa/pip/commit/8e236dd6a09bd2f70f9d4fc886da8c354d4c58f2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1626258/+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 1046340] Re: ntp package missing logcheck exceptions file /etc/logcheck/ignore.d.server/ntp

2016-09-22 Thread ChristianEhrhardt
** Changed in: ntp (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: ntp (Ubuntu Xenial)
   Status: Triaged => Won't Fix

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

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

Title:
  ntp package missing logcheck exceptions file
  /etc/logcheck/ignore.d.server/ntp

Status in NTP:
  New
Status in ntp package in Ubuntu:
  Won't Fix
Status in ntp source package in Xenial:
  Won't Fix

Bug description:
  Hello,

  in Lucid, Package: ntp (1:4.2.4p8+dfsg-1ubuntu2) has the file
  /etc/logcheck/ignore.d.server/ntp included. This is used to configure
  logcheck to ignore ntp messages in syslog that are not error
  conditions.

  However:
  In Natty, this file is not present in the ntp package
  In Oneric, this file is not present in the ntp package
  In Precise, this file is not present in the ntp package

  When logcheck is installed, all ntp syslog messages are raised as
  alerts by logcheck because the ntp configuration file is not present.

  It would be helpful to have /etc/logcheck/ignore.d.server/ntp included
  with ntp packaging as with Lucid.

  Here are sample contents based on the Lucid version with the addition
  of "status change" tot he time sync line.

  ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: time reset 
[+-]*[0-9]{1,2}\.[0-9]{6} s$
  ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: synchronisation lost$
  ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: no servers reachable$
  ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: synchronized to 
([0-9.]{7,15}|[0-9a-fA-F:.]{4,39}), stratum [0-9]+$
  ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: synchronized to 
LOCAL\([0-9]+\), stratum [0-9]+$
  ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: kernel time sync 
(disabled|enabled|status change) [0-9]+$
  ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: precision = [0-9]+\.[0-9]+ 
usec$
  ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: peer 
([.0-9]{7,15}|[0-9a-fA-F:.]{4,39}) now (in)?valid$
  ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: adjusting local clock by 
-?[.0-9]+s$
  ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: adjust time server 
-?[.0-9]+ offset$

  Regards,
  Tim Miller Dyck

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: ntp 1:4.2.6.p3+dfsg-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Wed Sep  5 10:09:31 2012
  InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 
(20110426)
  KernLog: Sep  5 06:34:04 cmpsVMHost01 kernel: [271957.578288] SGI XFS with 
ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=linux
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ntp
  UpgradeStatus: Upgraded to precise on 2012-08-25 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ntp/+bug/1046340/+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 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.

2016-09-22 Thread Louis Bouchard
Hello,

I can confirm the issue with makedumpfile on amd64. However, the crc32c
module issue does not appear on amd64 and the module is indeed present
in the smaller initrd created for kdump (present in
/var/lib/kdump/initrd.img-4.8.0-11-generic).

I will investigate the makedumpfile issue with 4.8 kernels.

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

** Also affects: makedumpfile (Ubuntu Yakkety)
   Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
   Status: New

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

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

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

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

** Changed in: makedumpfile (Ubuntu Trusty)
 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/1626269

Title:
  Ubuntu 16.10: kdump is not working in 4.8 kernel.

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Trusty:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 ==
  ---Problem Description---

  Ubuntu 16.10: kdump is not working in 4.8 kernel.

  ---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
  6) echo "c" > /proc/sysrq-trigger

  Logs
  

  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  
  root@ubuntu:/home/ubuntu# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-11-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-11-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic 
root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:/home/ubuntu# cd
  root@ubuntu:~# echo "c" > /proc/sysrq-trigger
  [   50.733424] sysrq: SysRq : Trigger a crash
  [   50.733437] Unable to handle kernel paging request for data at address 
0x
  [   50.733441] Faulting instruction address: 0xc05af3f4
  [   50.733444] Oops: Kernel access of bad area, sig: 11 [#1]
  [   50.733446] SMP NR_CPUS=2048 NUMA pSeries
  [   50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg 
rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi 
ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic 
crc32c_vpmsum
  [   50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-11-generic 
#12-Ubuntu
  [   50.733480] task: c004f7906880 task.stack: c004f7898000
  [   50.733482] NIP: c05af3f4 LR: c05b04d8 CTR: 
c05af3c0
  [   50.733485] REGS: c004f789b990 TRAP: 0300   Not tainted  
(4.8.0-11-generic)
  [   50.733488] MSR: 80009033   CR: 28242422  
XER: 0001
  [   50.733496] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c05b04d8 c004f789bc10 c0f46700 0063 
  GPR04: c005ef78a9b8 c005ef79f7d8 c0063fe82300 5970 
  GPR08: 0007 0001  0001 
  GPR12: c05af3c0 c7b31200  2200 
  GPR16: 10170dc8 0100111c0538 10140f58 100c7570 
  GPR20:  1017dd58 10153618 1017b608 
  GPR24: 310b9624 0001 c0e9fd40 0004 
  GPR28: c0ea0100 0063 c0e528e8  
  [   50.733536] NIP [c05af3f4] sysrq_handle_crash+0x34/0x50
  [   50.733539] LR