[Group.of.nepali.translators] [Bug 1691149] Re: linux-hwe-edge: 4.10.0-22.24~16.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** 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) => Thadeu Lima de 
Souza Cascardo (cascardo)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

** Description changed:

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1691146
- phase: Packaging
- kernel-stable-phase-changed:Monday, 22. May 2017 22:33 UTC
- kernel-stable-phase:Uploaded
+ 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/1691149

Title:
  linux-hwe-edge: 4.10.0-22.24~16.04.1 -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 prepare-package-signed 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-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  New

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1691149/+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 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 233-6ubuntu3

---
systemd (233-6ubuntu3) artful; urgency=medium

  * resolved: fix null pointer dereference crash (LP: #1621396)

 -- Dimitri John Ledkov   Mon, 22 May 2017 09:29:22
+0100

** Changed in: systemd (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/1621396

Title:
  systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Yakkety:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed

Bug description:
  This is one of background errors that happens without any active app being 
involved. 
  For the records, I had open: Firefox, Slack, Franz and the Terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:
   
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1683076] Re: Swift-storage dies if rsyslog is stopped

[Corey Bryant]

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

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

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

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

Title:
  Swift-storage dies if rsyslog is stopped

Status in OpenStack swift-storage charm:
  Invalid
Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive icehouse series:
  New
Status in Ubuntu Cloud Archive kilo series:
  New
Status in Ubuntu Cloud Archive mitaka series:
  New
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in swift package in Ubuntu:
  Invalid
Status in swift source package in Trusty:
  New
Status in swift source package in Xenial:
  New

Bug description:
  Trusty, Mitaka, Juju 1.25.11

  We have a cloud where swift replicators are constantly falling over on
  2 nodes.  This occurs whenever rsyslog restarts, as in

  https://bugs.launchpad.net/swift/+bug/1094230
  https://review.openstack.org/#/c/24871
  https://bugs.python.org/issue15179

  rsyslog restarts are unfortunately frequent right now, due to
  https://bugs.launchpad.net/juju-core/+bug/1683075

  Nodes are landscape managed and up to date but still exhibit the
  failure.

  Not much from running swift in verbose.
  https://pastebin.canonical.com/185609/

  sosreports are uploading to https://private-
  fileshare.canonical.com/~jillr/sf00137831/

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-swift-storage/+bug/1683076/+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 1690388] Re: wrong hwaddr on the vlan bond with nplan and cloud-init

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.22

---
nplan (0.22) artful; urgency=medium

  * Add support for setting a custom MAC address on all device types.
(LP: #1690388)
  * Improved MAC/vlan integration tests; thanks for Dimitri John Ledkov for the
changes.

 -- Mathieu Trudel-Lapierre   Mon, 22 May 2017
11:57:39 -0400

** Changed in: nplan (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/1690388

Title:
  wrong hwaddr on the vlan bond with nplan and cloud-init

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

Bug description:
  The expected hwaddresses are as follows:

  4: bond0:  mtu 1500 qdisc noqueue 
state UP group default 
  link/ether a0:36:9f:2d:93:80 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::a236:9fff:fe2d:9380/64 scope link 
 valid_lft forever preferred_lft forever
  5: bond0.101@bond0:  mtu 1500 qdisc noqueue 
state UP group default 
  link/ether a0:36:9f:2d:93:80 brd ff:ff:ff:ff:ff:ff
  inet 104.130.20.119/24 brd 104.130.20.255 scope global bond0.101
 valid_lft forever preferred_lft forever
  inet6 fe80::a236:9fff:fe2d:9380/64 scope link 
 valid_lft forever preferred_lft forever
  6: bond0.401@bond0:  mtu 1500 qdisc noqueue 
state UP group default 
  link/ether a0:36:9f:2d:93:81 brd ff:ff:ff:ff:ff:ff
  inet 10.184.7.120/20 brd 10.184.15.255 scope global bond0.401
 valid_lft forever preferred_lft forever
  inet6 fe80::a236:9fff:fe2d:9381/64 scope link 
 valid_lft forever preferred_lft forever

  however cloud-init shows:
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: 
Net device 
info
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: 
+---+--+--+---+---+---+
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: |   Device  |  Up  |  
 Address|  Mask | Scope | Hw-Address|
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: 
+---+--+--+---+---+---+
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: |   bond0   | True |  
.   |   .   |   .   | a0:36:9f:2d:93:81 |
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: |   bond0   | True | 
fe80::a236:9fff:fe2d:9381/64 |   .   |  link | a0:36:9f:2d:93:81 |
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: | bond0.101 | True |  
  104.130.20.119| 255.255.255.0 |   .   | a0:36:9f:2d:93:81 |
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: | bond0.101 | True | 
fe80::a236:9fff:fe2d:9381/64 |   .   |  link | a0:36:9f:2d:93:81 |
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: | lo| True |  
127.0.0.1   |   255.0.0.0   |   .   | . |
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: | lo| True |  
 ::1/128|   .   |  host | . |
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: | bond0.401 | True |  
   10.184.7.120 | 255.255.240.0 |   .   | a0:36:9f:2d:93:81 |
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: | bond0.401 | True | 
fe80::a236:9fff:fe2d:9381/64 |   .   |  link | a0:36:9f:2d:93:81 |
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: |   ens9f1  | True |  
.   |   .   |   .   | a0:36:9f:2d:93:81 |
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: |   ens9f0  | True |  
.   |   .   |   .   | a0:36:9f:2d:93:81 |
  May 12 14:33:28 xnox-iad-nr5 cloud-init[1163]: ci-info: 
+---+--+--+---+---+---+

  
  Specifically
bond0   | True | fe80::a236:9fff:fe2d:9381/64 |   .   |  link | 
a0:36:9f:2d:93:81
  bond0.101 | True |104.130.20.119| 255.255.255.0 |   .   | 
a0:36:9f:2d:93:81

  Instead of expected a0:36:9f:2d:93:80

  The generated netplan.yaml does not set macaddress on the vlans at
  all.

  Where as the 

[Group.of.nepali.translators] [Bug 1677990] Re: xl2tpd crash when tearing down L2TP/IPSec VPN connection

[Launchpad Bug Tracker]

This bug was fixed in the package xl2tpd - 1.3.6+dfsg-4ubuntu1

---
xl2tpd (1.3.6+dfsg-4ubuntu1) yakkety; urgency=medium

  * d/p/xl2tpd-call-c-nullptr-dereference.patch (LP: #1677990)
Backport fix for NULL-pointer dereference. (Closes: #760602)

 -- Frode Nordahl   Wed, 10 May 2017
14:16:17 +

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

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

Title:
  xl2tpd crash when tearing down L2TP/IPSec VPN connection

Status in Linux Mint:
  New
Status in xl2tpd package in Ubuntu:
  Fix Released
Status in xl2tpd source package in Xenial:
  Fix Released
Status in xl2tpd source package in Yakkety:
  Fix Released
Status in xl2tpd package in Debian:
  Fix Released

Bug description:
  [Impact]

   * xl2tpd crash with segmentation fault when disconnecting from
  L2TP/IPSec VPN

   * pppd processes never reaped, user will have to manually intervene
  to clean up

   * this will be a major annoyance for our users and I suggest we add
  this update to the stable release.

   * the proposed debdiff fixes this problem by patching a NULL-pointer
  de-reference in the upstream code.

  [Test Case]

   * Set up L2TP/IPSec VPN server
     1. create a VM on your computer and install Ubuntu Xenial on it (must be 
VM, IPSec won't work in LXC)
     2. sudo apt install xl2tpd libssl-dev
     3. get and run this script: 
https://github.com/philpl/setup-strong-strongswan

   * Set up L2TP/IPSec VPN client
     1. sudo add-apt-repository ppa:nm-l2tp/network-manager-l2tp
     sudo apt update
     sudo apt install network-manager-l2tp
     2. sudo service xl2tpd stop 
(https://github.com/nm-l2tp/network-manager-l2tp/issues/38)
     3. Configure L2TP/IPSec VPN using Network Manager GUI and point it to the 
IP of your VM
     4. Connect
     5. Disconnect
     6. Observe that you see xl2tpd SIGSEGV in dmesg and that pppd is still 
running.

  [Regression Potential]

   * The patch contains a check for NULL before de-referencing a pointer
  during cleanup. The same code has been tested for quite some time in
  the upstream 1.3.8 release that is available in Z and AA.

   * Patch already in Debian upstream for quite some time as well :
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760602

  [Original bug description]

  Ubuntu Xenial

  xl2tpd[20221]: segfault at 188 ip 0040bd08 sp 7ffd8b6546b0
  error 4 in xl2tpd[40+1b000]

  Core was generated by `/usr/sbin/xl2tpd -D -c /var/run/nm-xl2tpd.conf.20135 
-C /var/run/nm-xl2tpd_l2tp'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x0040bd08 in destroy_call (c=0x171d110) at call.c:420
  420   call.c: No such file or directory.
  (gdb) bt
  #0  0x0040bd08 in destroy_call (c=0x171d110) at call.c:420
  #1  0x0040bf90 in call_close (c=) at call.c:358
  #2  0x0040c155 in call_close (c=0x171cb40) at call.c:335
  #3  0x004023d6 in death_handler (signal=signal@entry=15)
  at xl2tpd.c:294
  #4  0x004024bf in process_signal () at xl2tpd.c:338
  #5  0x0040d016 in network_thread () at network.c:455
  #6  0x00401b96 in main (argc=, argv=)
  at xl2tpd.c:1557
  (gdb) print *c
  $1 = {lbit = 0, seq_reqd = 0, tx_pkts = 0, rx_pkts = 0, tx_bytes = 0,
    rx_bytes = 0, zlb_xmit = 0x0, prx = 0, state = 12, frame = 1, next = 0x0,
    debug = 0, msgtype = -1, ourcid = 106, cid = 10304, qcid = -1, bearer = -1,
    serno = 1, addr = 0, txspeed = 0, rxspeed = 0, ppd = 0, physchan = -1,
    dialed = '\000' , dialing = '\000' ,
    subaddy = '\000' , needclose = 0, closing = -1,
    container = 0x171c6a0, fd = -1, oldptyconf = 0x171d460, die = 0, nego = 0,
    pppd = 20222, result = -1, error = -1, fbit = 0, ourfbit = 0, cnu = 0,
    pnu = 0, errormsg = '\000' , lastsent = {tv_sec = 0,
  tv_usec = 0}, data_seq_num = 0, data_rec_seq_num = 0, closeSs = 0,
    pLr = -1, lns = 0x0, lac = 0x171d4d0, dial_no = '\000' }
  (gdb) print c->lns
  $2 = (struct lns *) 0x0
  (gdb)

  This is a NULL pointer de-reference and is fixed in this commit:
  
https://github.com/xelerance/xl2tpd/commit/a193e02c741168a9b9072b523f2d6faf14a049da

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1677990/+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 1677990] Re: xl2tpd crash when tearing down L2TP/IPSec VPN connection

[Launchpad Bug Tracker]

This bug was fixed in the package xl2tpd - 1.3.6+dfsg-4ubuntu0.16.04.1

---
xl2tpd (1.3.6+dfsg-4ubuntu0.16.04.1) xenial; urgency=medium

  * d/p/xl2tpd-call-c-nullptr-dereference.patch (LP: #1677990)
Backport fix for NULL-pointer dereference. (Closes: #760602)

 -- Frode Nordahl   Wed, 10 May 2017
14:16:17 +

** Changed in: xl2tpd (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/1677990

Title:
  xl2tpd crash when tearing down L2TP/IPSec VPN connection

Status in Linux Mint:
  New
Status in xl2tpd package in Ubuntu:
  Fix Released
Status in xl2tpd source package in Xenial:
  Fix Released
Status in xl2tpd source package in Yakkety:
  Fix Released
Status in xl2tpd package in Debian:
  Fix Released

Bug description:
  [Impact]

   * xl2tpd crash with segmentation fault when disconnecting from
  L2TP/IPSec VPN

   * pppd processes never reaped, user will have to manually intervene
  to clean up

   * this will be a major annoyance for our users and I suggest we add
  this update to the stable release.

   * the proposed debdiff fixes this problem by patching a NULL-pointer
  de-reference in the upstream code.

  [Test Case]

   * Set up L2TP/IPSec VPN server
     1. create a VM on your computer and install Ubuntu Xenial on it (must be 
VM, IPSec won't work in LXC)
     2. sudo apt install xl2tpd libssl-dev
     3. get and run this script: 
https://github.com/philpl/setup-strong-strongswan

   * Set up L2TP/IPSec VPN client
     1. sudo add-apt-repository ppa:nm-l2tp/network-manager-l2tp
     sudo apt update
     sudo apt install network-manager-l2tp
     2. sudo service xl2tpd stop 
(https://github.com/nm-l2tp/network-manager-l2tp/issues/38)
     3. Configure L2TP/IPSec VPN using Network Manager GUI and point it to the 
IP of your VM
     4. Connect
     5. Disconnect
     6. Observe that you see xl2tpd SIGSEGV in dmesg and that pppd is still 
running.

  [Regression Potential]

   * The patch contains a check for NULL before de-referencing a pointer
  during cleanup. The same code has been tested for quite some time in
  the upstream 1.3.8 release that is available in Z and AA.

   * Patch already in Debian upstream for quite some time as well :
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760602

  [Original bug description]

  Ubuntu Xenial

  xl2tpd[20221]: segfault at 188 ip 0040bd08 sp 7ffd8b6546b0
  error 4 in xl2tpd[40+1b000]

  Core was generated by `/usr/sbin/xl2tpd -D -c /var/run/nm-xl2tpd.conf.20135 
-C /var/run/nm-xl2tpd_l2tp'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x0040bd08 in destroy_call (c=0x171d110) at call.c:420
  420   call.c: No such file or directory.
  (gdb) bt
  #0  0x0040bd08 in destroy_call (c=0x171d110) at call.c:420
  #1  0x0040bf90 in call_close (c=) at call.c:358
  #2  0x0040c155 in call_close (c=0x171cb40) at call.c:335
  #3  0x004023d6 in death_handler (signal=signal@entry=15)
  at xl2tpd.c:294
  #4  0x004024bf in process_signal () at xl2tpd.c:338
  #5  0x0040d016 in network_thread () at network.c:455
  #6  0x00401b96 in main (argc=, argv=)
  at xl2tpd.c:1557
  (gdb) print *c
  $1 = {lbit = 0, seq_reqd = 0, tx_pkts = 0, rx_pkts = 0, tx_bytes = 0,
    rx_bytes = 0, zlb_xmit = 0x0, prx = 0, state = 12, frame = 1, next = 0x0,
    debug = 0, msgtype = -1, ourcid = 106, cid = 10304, qcid = -1, bearer = -1,
    serno = 1, addr = 0, txspeed = 0, rxspeed = 0, ppd = 0, physchan = -1,
    dialed = '\000' , dialing = '\000' ,
    subaddy = '\000' , needclose = 0, closing = -1,
    container = 0x171c6a0, fd = -1, oldptyconf = 0x171d460, die = 0, nego = 0,
    pppd = 20222, result = -1, error = -1, fbit = 0, ourfbit = 0, cnu = 0,
    pnu = 0, errormsg = '\000' , lastsent = {tv_sec = 0,
  tv_usec = 0}, data_seq_num = 0, data_rec_seq_num = 0, closeSs = 0,
    pLr = -1, lns = 0x0, lac = 0x171d4d0, dial_no = '\000' }
  (gdb) print c->lns
  $2 = (struct lns *) 0x0
  (gdb)

  This is a NULL pointer de-reference and is fixed in this commit:
  
https://github.com/xelerance/xl2tpd/commit/a193e02c741168a9b9072b523f2d6faf14a049da

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1677990/+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 1688606] Re: SRU cloud-initramfs-rooturl to archive

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-initramfs-tools - 0.27ubuntu1.4

---
cloud-initramfs-tools (0.27ubuntu1.4) xenial; urgency=medium

  * Add cloud-initramfs-rooturl package (LP: #1688606).

 -- Scott Moser   Thu, 11 May 2017 16:29:13 -0400

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

** Changed in: cloud-initramfs-tools (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/1688606

Title:
  SRU cloud-initramfs-rooturl to archive

Status in maas-images:
  Triaged
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in cloud-initramfs-tools source package in Trusty:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released
Status in cloud-initramfs-tools source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  MAAS has an interest in booting entirely ephemerally without iscsi root.
  The package cloud-initramfs-rooturl supports booting with root coming
  from a url.
    root=http:///squashfs

  This function will be used to pxe boot into a RAM only system with no
  dependency on the network.

  [Test Case]
  See the attached prepare-1688606.sh.  That script automates
  everything here making this much easier to test.

  1. make sure squashfs module is in the initramfs
     squashfs module is not automatically added to initramfs in precise.
     Just ensure that it is there.

     $ [ "$(lsb_release -sc)" = "precise" ] &&
    echo "manual_add_modules squashfs" |
   sudo tee /etc/initramfs-tools/hooks/squashfs

  2. install cloud-initramfs-rooturl
     sudo apt-get update
     sudo apt-get install cloud-initramfs-rooturl

  3. collect the kernel and newly generated initramfs

     sudo cat /boot/vmlinu?-$(uname -r) > kernel
     cp /boot/initrd.img-$(uname -r) initrd

  4. Download a squashfs image or a .tar.xz image

     rel="xenial"
     burl="http://cloud-images.ubuntu.com/daily/server;
     file="$rel-server-cloudimg-amd64-root.tar.xz"
     file="$rel-server-cloudimg-amd64.squashfs"
     wget "$burl/$rel/current/$file" -O "$file"

  5. run a web server
     python -m SimpleHTTPServer  &

  6. create a seed disk for cloud-init.

     $ cat > my-user-data < my-meta-data
     $ cloud-localds seed.img my-user-data my-meta-data

  7. Boot a vm using the kernel, initrd and url.

     cmdline="root=http://10.0.2.2:/$file console=ttyS0 -v "
     cmdline="${cmdline} overlayroot=tmpfs"

     qemu-system-x86_64 -enable-kvm \
    -device virtio-net-pci,netdev=net00 \
    -netdev type=user,id=net00 \
    -drive if=virtio,file=seed.img \
    -m 1G -nographic \
    -kernel kernel -initrd initrd \
    -append "root=$cmdline"

  [Regression Potential]
  Low.  This is adding a package previously not present.

  [Other Info]
  Related bugs:
   * bug 1689557: replace iscsi usage in ephemeral image with rooturl
   * bug 1689642: cloud-initramfs-rooturl should manual_add_modules squashfs 

  === End SRU Template ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1688606/+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 1688606] Re: SRU cloud-initramfs-rooturl to archive

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-initramfs-tools - 0.30ubuntu1.2

---
cloud-initramfs-tools (0.30ubuntu1.2) yakkety; urgency=medium

  * Add cloud-initramfs-rooturl package (LP: #1688606).

 -- Scott Moser   Thu, 11 May 2017 16:11:05 -0400

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

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

Title:
  SRU cloud-initramfs-rooturl to archive

Status in maas-images:
  Triaged
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in cloud-initramfs-tools source package in Trusty:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released
Status in cloud-initramfs-tools source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  MAAS has an interest in booting entirely ephemerally without iscsi root.
  The package cloud-initramfs-rooturl supports booting with root coming
  from a url.
    root=http:///squashfs

  This function will be used to pxe boot into a RAM only system with no
  dependency on the network.

  [Test Case]
  See the attached prepare-1688606.sh.  That script automates
  everything here making this much easier to test.

  1. make sure squashfs module is in the initramfs
     squashfs module is not automatically added to initramfs in precise.
     Just ensure that it is there.

     $ [ "$(lsb_release -sc)" = "precise" ] &&
    echo "manual_add_modules squashfs" |
   sudo tee /etc/initramfs-tools/hooks/squashfs

  2. install cloud-initramfs-rooturl
     sudo apt-get update
     sudo apt-get install cloud-initramfs-rooturl

  3. collect the kernel and newly generated initramfs

     sudo cat /boot/vmlinu?-$(uname -r) > kernel
     cp /boot/initrd.img-$(uname -r) initrd

  4. Download a squashfs image or a .tar.xz image

     rel="xenial"
     burl="http://cloud-images.ubuntu.com/daily/server;
     file="$rel-server-cloudimg-amd64-root.tar.xz"
     file="$rel-server-cloudimg-amd64.squashfs"
     wget "$burl/$rel/current/$file" -O "$file"

  5. run a web server
     python -m SimpleHTTPServer  &

  6. create a seed disk for cloud-init.

     $ cat > my-user-data < my-meta-data
     $ cloud-localds seed.img my-user-data my-meta-data

  7. Boot a vm using the kernel, initrd and url.

     cmdline="root=http://10.0.2.2:/$file console=ttyS0 -v "
     cmdline="${cmdline} overlayroot=tmpfs"

     qemu-system-x86_64 -enable-kvm \
    -device virtio-net-pci,netdev=net00 \
    -netdev type=user,id=net00 \
    -drive if=virtio,file=seed.img \
    -m 1G -nographic \
    -kernel kernel -initrd initrd \
    -append "root=$cmdline"

  [Regression Potential]
  Low.  This is adding a package previously not present.

  [Other Info]
  Related bugs:
   * bug 1689557: replace iscsi usage in ephemeral image with rooturl
   * bug 1689642: cloud-initramfs-rooturl should manual_add_modules squashfs 

  === End SRU Template ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1688606/+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 1673557] Re: /proc/cpuinfo should be collected

[Launchpad Bug Tracker]

This bug was fixed in the package whoopsie - 0.2.52.3

---
whoopsie (0.2.52.3) xenial-proposed; urgency=medium

  * src/whoopsie.c: Add ProcCpuinfoMinimal which can be larger than 1KB to the
list of accepted fields. (LP: #1673557)

 -- Brian Murray   Fri, 12 May 2017 10:21:20 -0700

** Changed in: whoopsie (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/1673557

Title:
  /proc/cpuinfo should be collected

Status in apport package in Ubuntu:
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in whoopsie source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in whoopsie source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  Fix Released
Status in whoopsie source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  While some apport reports contain ProcCpuinfo not all of them do and it would 
be useful to determine how many users can only run the i386 version of Ubuntu. 
Additionally, the existing implementation gathers information about every 
processor which is quite lengthy - something smaller would be better.

  [Test Case]
  1. Run ubuntu-bug 2vcard
  2. Observe there is no report key ProcCpuinfoMinimal

  With the version of apport from -proposed you will have
  ProcCpuinfoMinimal which will contain information about your
  processor.

  To verify the whoopsie change you'll want to do the following:
  1) sudo service whoopsie stop
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) kill -11 a process (but not the whoopsie one!)
  4) confirm sending the report
  5) Find the OOPS ID in the whoopsie output
  6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID
  7) Verify ProcCpuinfoMinimal appears in the OOPS


  [Regression Potential]
  This exists in Zesty, and Artful and there have been no issues collecting the 
information. Even if there are errors in the general ubuntu hook, which was 
modified for this SRU, apport will continue collecting information for the 
report and just add a traceback to the report about the hook error.

  The general Ubuntu hook, possibly add_kernel_info() could be used,
  should be modified such that the contents of /proc/cpuinfo are
  gathered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1651623] Re: adt tests fail on zesty for apport

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.3-0ubuntu8.3

---
apport (2.20.3-0ubuntu8.3) yakkety; urgency=medium

  * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues
with apt key ring. Thanks to Dimitri John Ledkov for the patch.
(LP: #1651623)
  * Disable report.test_add_gdb_info_abort_glib test case for now, as the
glib assertion message is broken under current Ubuntu (LP: #1689344)
  * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in
every report. (LP: #1673557)

 -- Brian Murray   Wed, 10 May 2017 18:10:32 -0700

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

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

Title:
  adt tests fail on zesty for apport

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Invalid
Status in apport source package in Yakkety:
  Fix Released
Status in apport source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Apport autopkgtests are failing with GPG errors e.g.:
  SystemError: W:GPG error: http://archive.ubuntu.com/ubuntu trusty Release: 
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32, E:The 
repository 'http://archive.ubuntu.com/ubuntu trusty Release' is not signed.

  [Test Case]
  Run the autopkgtests and observe failures regarding GPG.
  With the test fixed there should be no failures.

  [Regression Potential]
  While not a regression its possible fixing these tests will reveal other 
failures.

  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz

  fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+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 1673557] Re: /proc/cpuinfo should be collected

[Launchpad Bug Tracker]

This bug was fixed in the package whoopsie - 0.2.24.6ubuntu4

---
whoopsie (0.2.24.6ubuntu4) trusty-proposed; urgency=medium

  * src/whoopsie.c: Add ProcCpuinfoMinimal which can be larger than 1KB to the
list of accepted fields. (LP: #1673557)

 -- Brian Murray   Fri, 12 May 2017 10:25:00 -0700

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

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

Title:
  /proc/cpuinfo should be collected

Status in apport package in Ubuntu:
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in whoopsie source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in whoopsie source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  Fix Released
Status in whoopsie source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  While some apport reports contain ProcCpuinfo not all of them do and it would 
be useful to determine how many users can only run the i386 version of Ubuntu. 
Additionally, the existing implementation gathers information about every 
processor which is quite lengthy - something smaller would be better.

  [Test Case]
  1. Run ubuntu-bug 2vcard
  2. Observe there is no report key ProcCpuinfoMinimal

  With the version of apport from -proposed you will have
  ProcCpuinfoMinimal which will contain information about your
  processor.

  To verify the whoopsie change you'll want to do the following:
  1) sudo service whoopsie stop
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) kill -11 a process (but not the whoopsie one!)
  4) confirm sending the report
  5) Find the OOPS ID in the whoopsie output
  6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID
  7) Verify ProcCpuinfoMinimal appears in the OOPS


  [Regression Potential]
  This exists in Zesty, and Artful and there have been no issues collecting the 
information. Even if there are errors in the general ubuntu hook, which was 
modified for this SRU, apport will continue collecting information for the 
report and just add a traceback to the report about the hook error.

  The general Ubuntu hook, possibly add_kernel_info() could be used,
  should be modified such that the contents of /proc/cpuinfo are
  gathered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1673557] Re: /proc/cpuinfo should be collected

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.1-0ubuntu2.6

---
apport (2.20.1-0ubuntu2.6) xenial; urgency=medium

  * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in
every report. (LP: #1673557)
  * data/general/ubuntu-gnome.py: The GNOME3 PPAs are no longer supported for
14.04 or 16.04 so set an UnreportableReason in those reports.
(LP: #1689093)
  * test_backend_apt_dpkg.py: Move tests from Ubuntu 15.10 "wily" (which is
EoL now) to 16.04 LTS "xenial". (LP: #1690437)

 -- Brian Murray   Fri, 12 May 2017 11:39:04 -0700

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

** Changed in: apport (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/1673557

Title:
  /proc/cpuinfo should be collected

Status in apport package in Ubuntu:
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in whoopsie source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in whoopsie source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  Fix Released
Status in whoopsie source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  While some apport reports contain ProcCpuinfo not all of them do and it would 
be useful to determine how many users can only run the i386 version of Ubuntu. 
Additionally, the existing implementation gathers information about every 
processor which is quite lengthy - something smaller would be better.

  [Test Case]
  1. Run ubuntu-bug 2vcard
  2. Observe there is no report key ProcCpuinfoMinimal

  With the version of apport from -proposed you will have
  ProcCpuinfoMinimal which will contain information about your
  processor.

  To verify the whoopsie change you'll want to do the following:
  1) sudo service whoopsie stop
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) kill -11 a process (but not the whoopsie one!)
  4) confirm sending the report
  5) Find the OOPS ID in the whoopsie output
  6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID
  7) Verify ProcCpuinfoMinimal appears in the OOPS


  [Regression Potential]
  This exists in Zesty, and Artful and there have been no issues collecting the 
information. Even if there are errors in the general ubuntu hook, which was 
modified for this SRU, apport will continue collecting information for the 
report and just add a traceback to the report about the hook error.

  The general Ubuntu hook, possibly add_kernel_info() could be used,
  should be modified such that the contents of /proc/cpuinfo are
  gathered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1673557] Re: /proc/cpuinfo should be collected

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.14.1-0ubuntu3.24

---
apport (2.14.1-0ubuntu3.24) trusty; urgency=medium

  * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in
every report. (LP: #1673557)
  * data/general/ubuntu-gnome.py: The GNOME3 PPAs are no longer supported for
14.04 or 16.04 so set an UnreportableReason in those reports.
(LP: #1689093)

 -- Brian Murray   Fri, 12 May 2017 12:29:08 -0700

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

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

Title:
  /proc/cpuinfo should be collected

Status in apport package in Ubuntu:
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in whoopsie source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in whoopsie source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  Fix Released
Status in whoopsie source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  While some apport reports contain ProcCpuinfo not all of them do and it would 
be useful to determine how many users can only run the i386 version of Ubuntu. 
Additionally, the existing implementation gathers information about every 
processor which is quite lengthy - something smaller would be better.

  [Test Case]
  1. Run ubuntu-bug 2vcard
  2. Observe there is no report key ProcCpuinfoMinimal

  With the version of apport from -proposed you will have
  ProcCpuinfoMinimal which will contain information about your
  processor.

  To verify the whoopsie change you'll want to do the following:
  1) sudo service whoopsie stop
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) kill -11 a process (but not the whoopsie one!)
  4) confirm sending the report
  5) Find the OOPS ID in the whoopsie output
  6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID
  7) Verify ProcCpuinfoMinimal appears in the OOPS


  [Regression Potential]
  This exists in Zesty, and Artful and there have been no issues collecting the 
information. Even if there are errors in the general ubuntu hook, which was 
modified for this SRU, apport will continue collecting information for the 
report and just add a traceback to the report about the hook error.

  The general Ubuntu hook, possibly add_kernel_info() could be used,
  should be modified such that the contents of /proc/cpuinfo are
  gathered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1679784] Re: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.92.37.8

---
software-properties (0.92.37.8) trusty; urgency=medium

  * software-properties-gtk:
- fix the backend code to set the gnome debconf frontend, without which
  libgtk2-perl goes unused.
- depend on libgtk2-perl to ensure it's available, since it was not seeded
  on the desktop at release time.  This is only a Recommends: in zesty,
  but we need to ensure this isn't ignored on upgrade.
LP: #1679784.

 -- Steve Langasek   Thu, 27 Apr 2017
16:28:45 -0700

** Changed in: software-properties (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/1679784

Title:
  Changing from Xorg video driver to NVIDIA driver using Software &
  Updates does not display debconf prompt

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  Fix Released
Status in software-properties source package in Xenial:
  Fix Released
Status in software-properties source package in Yakkety:
  Fix Released

Bug description:
  [SRU Justification]
  software-properties does not display debconf prompts. while most debconf 
prompts have default answers and this is fine, for installing dkms modules on a 
SecureBoot-capable system we specifically have a critical debconf prompt with 
no possible default answer that users need to step through in order for their 
dkms modules to be usable.

  [Test case]
  1. sudo apt-add-repository ppa:vorlon/debconf-tests
  2. sudo apt update
  3. Launch Settings -> Software & Updates -> Additional Drivers
  4. Confirm that you are offered the option of using the 'noisy-fake-driver' 
package.
  5. Select this driver and apply changes.
  6. Confirm that no debconf prompt is shown, and the driver package fails to 
install ('dpkg -l noisy-fake-driver' shows 'iF').
  7. Reset the package state by removing the driver again.
  8. Enable -proposed.
  9. Run update-manager and verify that the new software-properties package is 
successfully installed from -proposed, pulling in libgtk2-perl in the process.
  10. Close Software & Updates and re-launch it.
  11. Select the 'noisy-fake-driver' package again.
  12. Confirm that you are shown a debconf prompt, and the driver package 
installs successfully.

  [Regression potential]
  The actual code change is small and self-contained, but the fix also requires 
pulling in new package dependencies which will also need to be promoted from 
universe to main in the process.  We need to take extra care to ensure the 
upgrade path is correct.  This SRU should also be done serially one release at 
a time to gather feedback at each stage.

  [Original bug description]
  I've encountered this repeatedly.

  In the first installation -- on updating via Software Updater, this
  crashed on upgrading the shim-signed package.

  On suggestions from here:

  I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work,
  however when I now try to swap the display driver, from xorg -->
  nvidia. This now triggered the same issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Apr  4 18:21:32 2017
  DuplicateSignature:
   package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
   Processing triggers for shim-signed 
(1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
   Running in non-interactive mode, doing nothing.
   dpkg: error processing package shim-signed (--configure):
    subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: shim-signed
  Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1679784/+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 1651623] Re: adt tests fail on zesty for apport

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.4-0ubuntu4.1

---
apport (2.20.4-0ubuntu4.1) zesty; urgency=medium

  * Disable report.test_add_gdb_info_abort_glib test case for now, as the
glib assertion message is broken under current Ubuntu (LP: #1689344)
  * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues
with apt key ring. Thanks to Dimitri John Ledkov for the patch.
(LP: #1651623)

 -- Brian Murray   Wed, 10 May 2017 17:05:11 -0700

** Changed in: apport (Ubuntu Zesty)
   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/1651623

Title:
  adt tests fail on zesty for apport

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Invalid
Status in apport source package in Yakkety:
  Fix Released
Status in apport source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Apport autopkgtests are failing with GPG errors e.g.:
  SystemError: W:GPG error: http://archive.ubuntu.com/ubuntu trusty Release: 
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32, E:The 
repository 'http://archive.ubuntu.com/ubuntu trusty Release' is not signed.

  [Test Case]
  Run the autopkgtests and observe failures regarding GPG.
  With the test fixed there should be no failures.

  [Regression Potential]
  While not a regression its possible fixing these tests will reveal other 
failures.

  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz

  fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+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 1689093] Re: modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.1-0ubuntu2.6

---
apport (2.20.1-0ubuntu2.6) xenial; urgency=medium

  * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in
every report. (LP: #1673557)
  * data/general/ubuntu-gnome.py: The GNOME3 PPAs are no longer supported for
14.04 or 16.04 so set an UnreportableReason in those reports.
(LP: #1689093)
  * test_backend_apt_dpkg.py: Move tests from Ubuntu 15.10 "wily" (which is
EoL now) to 16.04 LTS "xenial". (LP: #1690437)

 -- Brian Murray   Fri, 12 May 2017 11:39:04 -0700

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

** Changed in: apport (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/1689093

Title:
  modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04

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

Bug description:
  Impact
  --
  As announced, the GNOME3 PPAs for Ubuntu 16.04 LTS are no longer being 
maintained as of April 2017. Therefore, the Ubuntu GNOME project would like to 
stop receiving bugs from packages installed from those PPAs for that version, 
or for 14.04 LTS which is no longer supported by Ubuntu GNOME.

  See https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3

  Test Case
  -
  sudo add-apt-repository ppa:gnome3-team/gnome3
  sudo apt update
  sudo apt upgrade

  Ubuntu 14.04:
  ubuntu-bug gnome-system-monitor

  Ubuntu 16.04:
  ubuntu-bug nautilus

  What should happen:
  After several moments, you should see a popup with
  The GNOME3 PPA you are using is no longer supported for this Ubuntu release. 
Please run "ppa-purge ppa:gnome3-team/gnome3".

  Clean up:
  sudo apt install ppa-purge
  sudo ppa-purge ppa:gnome3-team/gnome3

  Other Info
  --
  Ubuntu GNOME has always installed ppa-purge by default.

  Regression Potential
  
  People will be unable to report bugs with PPA packages like they used to but 
they'll be told why. The message unfortunately likely won't be translated right 
away, but since it will land in the development release, it should eventually 
be translated for future Ubuntu releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689093/+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 1690437] Re: xenial autopkgtest fails because its using an End of Life release

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.1-0ubuntu2.6

---
apport (2.20.1-0ubuntu2.6) xenial; urgency=medium

  * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in
every report. (LP: #1673557)
  * data/general/ubuntu-gnome.py: The GNOME3 PPAs are no longer supported for
14.04 or 16.04 so set an UnreportableReason in those reports.
(LP: #1689093)
  * test_backend_apt_dpkg.py: Move tests from Ubuntu 15.10 "wily" (which is
EoL now) to 16.04 LTS "xenial". (LP: #1690437)

 -- Brian Murray   Fri, 12 May 2017 11:39:04 -0700

** Changed in: apport (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/1690437

Title:
  xenial autopkgtest fails because its using an End of Life release

Status in apport package in Ubuntu:
  Invalid
Status in apport source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  A xenial autopackagetest, test_backend_apt_dpkg.py, for apport is failing 
because they try and get data from ddebs.ubuntu.com for an End of Life release.

  [Test Case]
  1) Observe the autopkgtest failure
  "SystemError: W:The repository 'http://ddebs.ubuntu.com wily Release' does 
not have a Release file., W:Data from such a repository can't be authenticated 
and is therefore potentially dangerous to use., W:See apt-secure(8) manpage for 
repository creation and user configuration details., E:Failed to fetch 
http://ddebs.ubuntu.com/dists/wily/main/binary-armhf/Packages  404  Not Found, 
E:Some index files failed to download. They have been ignored, or old ones used 
instead."

  With the version of apport in -proposed their will not be an
  autopkgtest failure.

  [Regression Potential]
  We are switching to the version of the autopkgtest which is currently working 
in apport and has been working since yakkety's development.  Additionally, its 
just a test change so there should be no regressions.

  Here's a link to a failure:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  xenial/xenial/amd64/a/apport/20170426_142511_fd07d@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1690437/+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 1687752] Re: ubuntu-cpc: Exit on first failure for extra hooks

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.435.3

---
livecd-rootfs (2.435.3) yakkety; urgency=medium

  * live-build/ubuntu-cpc/hooks/999-extras.binary: Exit on first failure.
(LP: #1687752)

 -- Robert C Jennings   Tue, 09 May 2017
13:49:48 -0700

** Changed in: livecd-rootfs (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: livecd-rootfs (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/1687752

Title:
  ubuntu-cpc: Exit on first failure for extra hooks

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * When running extra binary hooks for the ubuntu-cpc project, exit on
  first failure rather than running all hooks.

   * This allows ubuntu-cpc to fail fast and find errors more easily.
  This change has been made in devel and proves very useful.

  [Test Case]

   * Add binary hooks to the extra directory where one hook exits non-
  zero. Ensure build returns an error at that point rather than run-
  parts continuing after the initial failure

  [Regression Potential]

   * Low risk, any non-zero exit will fail the build with or without
  this patch.  Now we'll fail optimally for the first failure.

   Original description 

  This was fixed(improved?) in devel with r1464.1.2.  I have opened this
  bug to back-port these to zesty, yakkety, and xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1687752/+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 1687752] Re: ubuntu-cpc: Exit on first failure for extra hooks

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.441.3

---
livecd-rootfs (2.441.3) zesty; urgency=medium

  * live-build/ubuntu-cpc/hooks/999-extras.binary: Exit on first failure.
(LP: #1687752)

 -- Robert C Jennings   Tue, 09 May 2017
13:46:01 -0700

** Changed in: livecd-rootfs (Ubuntu Zesty)
   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/1687752

Title:
  ubuntu-cpc: Exit on first failure for extra hooks

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Yakkety:
  Fix Released
Status in livecd-rootfs source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * When running extra binary hooks for the ubuntu-cpc project, exit on
  first failure rather than running all hooks.

   * This allows ubuntu-cpc to fail fast and find errors more easily.
  This change has been made in devel and proves very useful.

  [Test Case]

   * Add binary hooks to the extra directory where one hook exits non-
  zero. Ensure build returns an error at that point rather than run-
  parts continuing after the initial failure

  [Regression Potential]

   * Low risk, any non-zero exit will fail the build with or without
  this patch.  Now we'll fail optimally for the first failure.

   Original description 

  This was fixed(improved?) in devel with r1464.1.2.  I have opened this
  bug to back-port these to zesty, yakkety, and xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1687752/+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 1680384] Re: libvirt-qemu apparmor profiles misses several important entries

[Launchpad Bug Tracker]

This bug was fixed in the package libvirt - 2.5.0-3ubuntu5.1

---
libvirt (2.5.0-3ubuntu5.1) zesty; urgency=medium

  * Add missing apparmor profile entries (LP: #1680384)
- debian/patches/ubuntu/apparmor-vfio.patch: apparmor: add /dev/vfio
  for vf (hot) attach
- debian/patches/ubuntu/apparmor-ppcwrapper.patch: apparmor: allow
  extra tools executed by kvm.powerpc
- debian/patches/ubuntu/apparmor-shutdown.patch: apparmor: allow to
  parse cmdline of the pid that send the shutdown signal

 -- Christian Ehrhardt   Wed, 26 Apr
2017 13:47:27 +0200

** Changed in: libvirt (Ubuntu Zesty)
   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/1680384

Title:
  libvirt-qemu apparmor profiles misses several important entries

Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Trusty:
  Incomplete
Status in libvirt source package in Xenial:
  Fix Committed
Status in libvirt source package in Yakkety:
  Fix Released
Status in libvirt source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Attaching of virtual functions (SR-IOV) not possible without manually
     modification of apparmor rules
   * libvirt/qemu guest logfiles can not state the program that sent the
     shutdown signal
   * on ppc64el when starting on SMT enabled it failes (expected) but does
     not present the hint about SMT being the reasons that was added in
     >=zesty
   * various apparmor denials in the log hide other issues
   * Fix by opening up apparmor rules as needed for these use-cases

  [Test Case]

   * The rules covere a set of use cases, outlining them all here. Some only
     apply to >=Zesty, so I mark each subtest with release names.
   * All start with "Spawn a kvm guest e.g. via uvtool-libvirt"
   * A) >=Xenial - shutdown message
     - A1 - start the guest
     - A2 - stop the guest
     - A3 - check the log in /var/log/libvirt/qemu/.log
     - A-check: without the fix the log ends with 
    With the fix it shall contain the name of the process
    stopping it instead of. So libvirt shutdown will show
    libvirtd, kill from bash shows bash, ...)
   * B) >=Xenial
     - B1 - prepare a hotplug xml and a SR-IOV device - that depends on your
   system, one example is outlined here:
    # Prep VFs and attach
    $ echo 4 | sudo tee /sys/bus/pci/devices/0005\:01\:00.0/sriov_numvfs
    $ sudo modprobe vfio-pci
    $ lspci -n -s 0005:01:01.3
  0005:01:01.3 0200: 10df:e228 (rev 10)
    $ cat VF-5.1.1.3.xml
  
    
  
    
  
  - B2 until bug 1679704 is fixed you need to manually increase the
    locked memory limit of the qemu process before going on
  - B3 attach the device
    $ virsh attach-device z-test VF-5.1.1.3.xml
  - B-check: without the fix it will fail for a set of apparmor denials
     with the fix the attaching will succeed
   * C) >=Zesty
     - C1 - on a ppc64el system start and stop a guest
     - C-check: without the fix apparmor will hold many denies for ppc64_cpu
    and/or accessing /sys/devices/system/cpu/...
    With the fix not only the denies are gone, but also if you
    run on a system with SMT enabled (kvm will fail there) it
    will report to you in the log about "Error: You must disable
    SMT ..."

  [Regression Potential]

   * We are only further "opening up" the current apparmor profiles. So we
     should not end up affecting existing use cases by new blocks.
   * There is a very slight chance that due to accesses being allowed follow
     on actions are triggered which people are not used to like "the VF hot
     attach actually working". So if one relied on it not working it will be
     different for them.
   * Further I made some brainstorming on the potential effects but the only
     other one that came to my mind being a regression of some sort is that
     it now correctly states what send the shutdown signal. So when qemu did
     not end by itself (guest stops) but is stopped (shutdown) the old
     message was:
   terminating on signal 15 from pid 22938 ()
     And now will be like:
   terminating on signal 15 from pid 7714 (/usr/sbin/libvirtd)
     For the hopefully super unlikely case that someone e.g. grepped for
     unknown here it might be a regression.
     And making that message more useful (along with getting rid of the
     associated aa deny is part of the intended fix).

  [Other Info]

   * Tested manually and via regression tests in advance on bileto tickets.
     So all are green there now, there were two unrelated in some dep8 tests 
 due to 

[Group.of.nepali.translators] [Bug 1680384] Re: libvirt-qemu apparmor profiles misses several important entries

[Launchpad Bug Tracker]

This bug was fixed in the package libvirt - 2.1.0-1ubuntu9.5

---
libvirt (2.1.0-1ubuntu9.5) yakkety; urgency=medium

  * Add missing apparmor profile entries (LP: #1680384)
- debian/patches/ubuntu/apparmor-vfio.patch: apparmor: add /dev/vfio
  for vf (hot) attach
- debian/patches/ubuntu/apparmor-shutdown.patch: apparmor: allow to
  parse cmdline of the pid that send the shutdown signal

 -- Christian Ehrhardt   Wed, 26 Apr
2017 13:46:42 +0200

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

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

Title:
  libvirt-qemu apparmor profiles misses several important entries

Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Trusty:
  Incomplete
Status in libvirt source package in Xenial:
  Fix Committed
Status in libvirt source package in Yakkety:
  Fix Released
Status in libvirt source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * Attaching of virtual functions (SR-IOV) not possible without manually
     modification of apparmor rules
   * libvirt/qemu guest logfiles can not state the program that sent the
     shutdown signal
   * on ppc64el when starting on SMT enabled it failes (expected) but does
     not present the hint about SMT being the reasons that was added in
     >=zesty
   * various apparmor denials in the log hide other issues
   * Fix by opening up apparmor rules as needed for these use-cases

  [Test Case]

   * The rules covere a set of use cases, outlining them all here. Some only
     apply to >=Zesty, so I mark each subtest with release names.
   * All start with "Spawn a kvm guest e.g. via uvtool-libvirt"
   * A) >=Xenial - shutdown message
     - A1 - start the guest
     - A2 - stop the guest
     - A3 - check the log in /var/log/libvirt/qemu/.log
     - A-check: without the fix the log ends with 
    With the fix it shall contain the name of the process
    stopping it instead of. So libvirt shutdown will show
    libvirtd, kill from bash shows bash, ...)
   * B) >=Xenial
     - B1 - prepare a hotplug xml and a SR-IOV device - that depends on your
   system, one example is outlined here:
    # Prep VFs and attach
    $ echo 4 | sudo tee /sys/bus/pci/devices/0005\:01\:00.0/sriov_numvfs
    $ sudo modprobe vfio-pci
    $ lspci -n -s 0005:01:01.3
  0005:01:01.3 0200: 10df:e228 (rev 10)
    $ cat VF-5.1.1.3.xml
  
    
  
    
  
  - B2 until bug 1679704 is fixed you need to manually increase the
    locked memory limit of the qemu process before going on
  - B3 attach the device
    $ virsh attach-device z-test VF-5.1.1.3.xml
  - B-check: without the fix it will fail for a set of apparmor denials
     with the fix the attaching will succeed
   * C) >=Zesty
     - C1 - on a ppc64el system start and stop a guest
     - C-check: without the fix apparmor will hold many denies for ppc64_cpu
    and/or accessing /sys/devices/system/cpu/...
    With the fix not only the denies are gone, but also if you
    run on a system with SMT enabled (kvm will fail there) it
    will report to you in the log about "Error: You must disable
    SMT ..."

  [Regression Potential]

   * We are only further "opening up" the current apparmor profiles. So we
     should not end up affecting existing use cases by new blocks.
   * There is a very slight chance that due to accesses being allowed follow
     on actions are triggered which people are not used to like "the VF hot
     attach actually working". So if one relied on it not working it will be
     different for them.
   * Further I made some brainstorming on the potential effects but the only
     other one that came to my mind being a regression of some sort is that
     it now correctly states what send the shutdown signal. So when qemu did
     not end by itself (guest stops) but is stopped (shutdown) the old
     message was:
   terminating on signal 15 from pid 22938 ()
     And now will be like:
   terminating on signal 15 from pid 7714 (/usr/sbin/libvirtd)
     For the hopefully super unlikely case that someone e.g. grepped for
     unknown here it might be a regression.
     And making that message more useful (along with getting rid of the
     associated aa deny is part of the intended fix).

  [Other Info]

   * Tested manually and via regression tests in advance on bileto tickets.
     So all are green there now, there were two unrelated in some dep8 tests 
 due to what seems transient network timeouts (worked on retry) - if 
 showing up in proposed as well we will 

[Group.of.nepali.translators] [Bug 1669712] Re: Newline characters (\n) must be sanitized before LDAP requests take place.

[Andy Whitcroft]

Hello Victor, or anyone else affected,

Accepted sssd into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sssd/1.11.8-0ubuntu0.6
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

Title:
  Newline characters (\n) must be sanitized before LDAP requests take
  place.

Status in sssd package in Ubuntu:
  Triaged
Status in sssd source package in Trusty:
  Fix Committed
Status in sssd source package in Xenial:
  Fix Released
Status in sssd source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * When a username with a trailing newline or carriage return
  character is used for authentication, the malformed LDAP query will
  return that the username does not exist and then the username will be
  erased from the LDB cache.

  [Test Case]

   1. While the provider is online, request a valid user and confirm
  it's cached:

  ubuntu@ubuntu:~⟫ sudo sss_cache -E; getent passwd 'ad1'
  ad1:*:1500:1500:ad1:/home/ad:/bin/bash

  ubuntu@ubuntu:~⟫ sudo ldbsearch -H /var/lib/sss/db/cache_UBUNTU.TEST.ldb -b 
name=ad1,cn=users,cn=UBUNTU.TEST,cn=sysdb | grep entries
  asq: Unable to register control with rootdse!
  # 1 entries

   2. Request an invalid username:
  ubuntu@ubuntu:~⟫ sudo sss_cache -E; getent passwd 'ad1
  '

   3. Confirm the cache entry has disappeared:
  ubuntu@ubuntu:~⟫ sudo ldbsearch -H /var/lib/sss/db/cache_UBUNTU.TEST.ldb -b 
name=ad1,cn=users,cn=UBUNTU.TEST,cn=sysdb | grep entries
  asq: Unable to register control with rootdse!
  # 0 entries

  [Regression Potential]

   * None, the sanitizer code is just extended for these two characters

  [Other Info]

   * Upstream bug: https://pagure.io/SSSD/sssd/issue/3317
   * Fix has been merged upstream 


  [Original Description]

  Introducing valid usernames with trailing newline characters triggers
  the removal of valid LDB cache entries

  Reproducer:

  1. Request a valid user and confirm it's cached:
  ubuntu@ubuntu:~⟫ sudo sss_cache -E; getent passwd 'ad1'
  ad1:*:1500:1500:ad1:/home/ad:/bin/bash

  ubuntu@ubuntu:~⟫ sudo ldbsearch -H /var/lib/sss/db/cache_UBUNTU.TEST.ldb -b 
name=ad1,cn=users,cn=UBUNTU.TEST,cn=sysdb | grep entries
  asq: Unable to register control with rootdse!
  # 1 entries

  2. Request an invalid username:
  ubuntu@ubuntu:~⟫ sudo sss_cache -E; getent passwd 'ad1
  '

  3. Confirm the cache entry has disappeared:
  ubuntu@ubuntu:~⟫ sudo ldbsearch -H /var/lib/sss/db/cache_UBUNTU.TEST.ldb -b 
name=ad1,cn=users,cn=UBUNTU.TEST,cn=sysdb | grep entries
  asq: Unable to register control with rootdse!
  # 0 entries

  This is an excerpt from the logs of the request with the newline char:

  (Tue Feb 28 16:07:40 2017) [sssd[be[UBUNTU.TEST]]] [be_get_account_info] 
(0x0200): Got request for [0x1001][FAST BE_REQ_USER][1][name=ad1
  ]

  (Tue Feb 28 16:08:33 2017) [sssd[be[UBUNTU.TEST]]] 
[sdap_get_generic_ext_step] (0x0400): calling ldap_search_ext with 
[(&(sAMAccountName=ad1
  
)(objectclass=user)(sAMAccountName=*)(&(uidNumber=*)(!(uidNumber=0][CN=Users,DC=ubuntu,DC=test].
  (Tue Feb 28 16:08:33 2017) [sssd[be[UBUNTU.TEST]]] [sdap_get_users_done] 
(0x0040): Failed to retrieve users
  (Tue Feb 28 16:08:33 2017) [sssd[nss]] [sss_ncache_set_str] (0x0400): Adding 
[NCE/USER/UBUNTU.TEST/ad1
  ] to negative cache
  (Tue Feb 28 16:08:33 2017) [sssd[nss]] [nss_cmd_getpwnam_search] (0x0040): No 
results for getpwnam call

  At this point, the ldb entry removal request for ad1 (without \n)
  takes place via sysdb_delete_user.

  Adding '\n' to the character list in sss_filter_sanitize_ex() seems to
  fix this issue.

  Upstream bug: https://pagure.io/SSSD/sssd/issue/3317

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

___
Mailing list: 

[Group.of.nepali.translators] [Bug 1618463] Re: udev race condition with qeth device and bridge_role

[Dimitri John Ledkov]

@admcleod

Based on feedback from IBM i'm going to withdraw this update. The
ordering of the flags is correct, as long as one activates the flag
needed to have bridge_role attribute available before onlining the
device.

Specifically one should use:

in-target chzdev --no-root-update -pVe c003 layer2=1
bridge_role=primary;

meaning... enable layer2 networking, which creates a bunch of attributes
specific to layer2 mode, including the bridge_role. Then set
bridge_role. Then online the device.

Testing this out here locally results in race free boots, without any
changes to the code.

Could you please try out above command in your preseeds without using
packages from proposed?

Regards,

Dimitri.

** Tags removed: verification-needed
** Tags added: verification-failed

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

** Changed in: s390-tools (Ubuntu Yakkety)
   Status: Fix Committed => Incomplete

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

** Changed in: s390-tools (Ubuntu Zesty)
   Status: Fix Released => 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/1618463

Title:
  udev race condition with qeth device and bridge_role

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in s390-tools package in Ubuntu:
  Confirmed
Status in s390-tools source package in Xenial:
  Incomplete
Status in s390-tools source package in Yakkety:
  Incomplete
Status in s390-tools source package in Zesty:
  Confirmed

Bug description:
  [Impact]

   * bridge_role property setting is racy on boot

   * This results in incorrect bridge mode set on the devices,
  sometimes, which leads to lack of desired connectivity (e.g. bridging
  internet to containers)

   * The fix for this issue is to set bridge_role, only after the device
  is online

   * Unfortunately the udev rules are not regenerated, therefore
  affected systemd must manually remove and recreate chzdev rules

  [Test Case]

   * Remove qeth udev rules from /etc/udev/rules.d/
   * Enable qeth device using chzdev with a non-default bridge_role setting, 
e.g.:
 chzdev --no-root-update -pVe c003 bridge_role=primary;
   * Reboot and check that bridge_role setting is correctly set in the sysfs, 
e.g.:
 /sys/devices/qeth/0.0.c003/bridge_role

  [Regression Potential]

   * Minimal, the generated udev rules remain the same; the only
  difference in the generated udev rules is the ordering in setting the
  bridge_role attribute

  [Other Info]
   
   * Original bug report:

  Attempting to set bridge_role = primary with the following command in
  preseed:

  in-target chzdev --no-root-update -pVe c003 bridge_role=primary;

  ...works, and generates the following udev rule for this device:

  https://pastebin.canonical.com/164271/

  However, after reboot:

  systemd-udevd[2634]: error opening
  ATTR{/sys/devices/qeth/0.0.c003/bridge_role} for writing: Permission
  denied

  More logging:

  https://pastebin.canonical.com/164272/

  after the system has booted, we are able to write to the file and set
  bridge_role to primary:

  root@10-13-3-10:/var/log# cat /sys/devices/qeth/0.0.c003/bridge_role
  none
  root@10-13-3-10:/var/log# echo primary > 
/sys/devices/qeth/0.0.c003/bridge_role
  root@10-13-3-10:/var/log# cat /sys/devices/qeth/0.0.c003/bridge_role
  primary

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1618463/+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 1691186] Re: linux-gke: 4.4.0-1014.14 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux-gke: 4.4.0-1014.14 -proposed tracker

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

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

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

[Brad Figg]

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

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

Title:
  linux-azure: 4.10.0-1005.5 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1686645
  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/1691247/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Dimitri John Ledkov]

Remove zesty task; added xenial task.

** Changed in: systemd (Ubuntu)
Milestone: ubuntu-17.04 => ubuntu-17.06

** Changed in: systemd (Ubuntu Zesty)
Milestone: ubuntu-17.04 => zesty-updates

** Also affects: landscape-client (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** No longer affects: systemd (Ubuntu Zesty)

** Changed in: systemd (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.3

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

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

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

** No longer affects: landscape-client (Ubuntu Zesty)

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in landscape-client source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed

Bug description:
  Used Landscape (Paid Canonical Subscription) to upgrade one of my
  machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Sebastian Unger]

This is still an issue in the current linux-raspi2 version. Where those
changes ported to that kernel?

** Also affects: linux-raspi2 (Ubuntu)
   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/1655842

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

Status in linux package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Released
Status in linux-raspi2 source package in Xenial:
  New

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+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 1690730] Re: New upstream microreleases 9.3.17, 9.5.7 and 9.6.3

[ChristianEhrhardt]

** Also affects: postgresql-9.3 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: postgresql-9.3 (Ubuntu Trusty)
   Status: New => Fix Committed

** No longer affects: postgresql-9.3 (Ubuntu Xenial)

** No longer affects: postgresql-9.3 (Ubuntu Yakkety)

** No longer affects: postgresql-9.3 (Ubuntu Zesty)

** No longer affects: postgresql-9.5 (Ubuntu Trusty)

** No longer affects: postgresql-9.5 (Ubuntu Zesty)

** No longer affects: postgresql-9.6 (Ubuntu Yakkety)

** No longer affects: postgresql-9.6 (Ubuntu Trusty)

** No longer affects: postgresql-9.6 (Ubuntu Xenial)

** Changed in: postgresql-9.6 (Ubuntu)
   Status: New => Triaged

** Changed in: postgresql-9.3 (Ubuntu)
   Status: New => Triaged

** Changed in: postgresql-9.3 (Ubuntu)
   Importance: Undecided => High

** Changed in: postgresql-9.3 (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: postgresql-9.6 (Ubuntu)
   Importance: Undecided => High

** Changed in: postgresql-9.6 (Ubuntu Zesty)
   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/1690730

Title:
  New upstream microreleases 9.3.17, 9.5.7 and 9.6.3

Status in postgresql-9.3 package in Ubuntu:
  Triaged
Status in postgresql-9.5 package in Ubuntu:
  Triaged
Status in postgresql-9.6 package in Ubuntu:
  Triaged
Status in postgresql-9.3 source package in Trusty:
  Fix Committed
Status in postgresql-9.5 source package in Xenial:
  Fix Committed
Status in postgresql-9.5 source package in Yakkety:
  Fix Committed
Status in postgresql-9.6 source package in Zesty:
  Fix Committed

Bug description:
  https://www.postgresql.org/about/news/1746/

  As per the standing micro-release exception these should land in
  stable Ubuntu releases.

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