[Group.of.nepali.translators] [Bug 1642679] Re: The OpenStack network_config.json implementation fails on Hyper-V compute nodes

[Scott Moser]

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

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

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

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

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

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

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

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

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

** Changed in: cloud-init (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

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

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

Title:
  The OpenStack network_config.json implementation fails on Hyper-V
  compute nodes

Status in cloud-init:
  Confirmed
Status in OpenStack Compute (nova):
  In Progress
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  We have discovered an issue when booting Xenial instances on OpenStack
  environments (Liberty or newer) and Hyper-V compute nodes using config
  drive as metadata source.

  When applying the network_config.json, cloud-init fails with this error:
  http://paste.openstack.org/show/RvHZJqn48JBb0TO9QznL/

  The fix would be to add 'hyperv' as a link type here:
  /usr/lib/python3/dist-packages/cloudinit/sources/helpers/openstack.py, line 
587

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1642679/+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 1643901] Re: flxdec security update tracking bug

[Mathew Hodson]

** No longer affects: gst-plugins-good0.10 (Ubuntu)

** Changed in: gst-plugins-good1.0 (Ubuntu Zesty)
   Importance: Undecided => Medium

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

Title:
  flxdec security update tracking bug

Status in gst-plugins-good1.0 package in Ubuntu:
  Confirmed
Status in gst-plugins-good0.10 source package in Precise:
  Fix Released
Status in gst-plugins-good0.10 source package in Trusty:
  Fix Released
Status in gst-plugins-good1.0 source package in Trusty:
  Fix Released
Status in gst-plugins-good0.10 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Yakkety:
  Fix Released
Status in gst-plugins-good1.0 source package in Zesty:
  Confirmed

Bug description:
  This bug is to track the security update to fix the flxdec out-of-
  bounds write.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1643901/+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 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"

[Mathew Hodson]

There is a fix for the warning message in bug #1644498.

You can follow the instructions in that bug to test the fix. You can
also follow the progress in that bug and wait for the fix to be released
for Xenial.

** No longer affects: appstream (Ubuntu)

** Project changed: ubuntu-gnome => ubuntu-translations

** No longer affects: ubuntu-translations

** Project changed: appstream => ubuntu-translations

** No longer affects: ubuntu-translations

** Summary changed:

- "AppStream cache update completed, but some metadata was ignored due to 
errors." on "sudo apt-get update"
+ fwupd: Error message due to invalid AppStream file

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

Title:
  fwupd: Error message due to invalid AppStream file

Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd source package in Xenial:
  Fix Released
Status in fwupd package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Checks for apt updates using apt or apt-get also update the
  appstream cache.  Some of the appstream metadata installed locally
  isn't strictly valid as it's missing two fields.

  [Test Case]

   * fwupdmgr refresh
   * apt update
   * check for errors about metadata being ignored

  [Regression Potential]

   * This is just changing the XML metadata locally, I don't see any
  regression potential.

  [Other Info]
   
   * This fix has been applied upstream: 
https://github.com/hughsie/fwupd/commit/f4e0e88f7cba833a4badc1a3d62f1a08dd1bfd96

  [Original report]

  I have found that when there are new packages available which my
  machine doesn't know about yet, if I run "sudo apt-get update" this is
  the output:

  Get:1 http://gb.archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
  Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Get:3 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease [82.2 
kB]
  Get:4 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages [28 B]
  Get:5 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease 
[82.2 kB]
  Get:6 http://security.ubuntu.com/ubuntu xenial-security/restricted i386 
Packages [28 B]
  Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe i386 
Packages [28 B]
  Get:8 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 
Packages [28 B]
  Get:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 
Packages [28 B]
  Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse 
Translation-en [28 B]
  Get:11 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 
[1,201 kB]
  Get:12 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages 
[1,196 kB]
  Get:13 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en_GB 
[426 kB]
  Get:14 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en 
[568 kB]
  Get:15 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 
Metadata [733 kB]
  Get:16 http://gb.archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons 
[409 kB]
  Get:17 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages [8,344 B]
  Get:18 http://gb.archive.ubuntu.com/ubuntu xenial/restricted i386 
Packages [8,684 B]
  Get:19 http://gb.archive.ubuntu.com/ubuntu xenial/restricted 
Translation-en_GB [2,556 B]
  Get:20 http://gb.archive.ubuntu.com/ubuntu xenial/restricted 
Translation-en [2,908 B]
  Get:21 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 DEP-11 
Metadata [186 B]
  Get:22 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 
[7,532 kB]
  Get:23 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 
[7,512 kB]
  Get:24 http://gb.archive.ubuntu.com/ubuntu xenial/universe 
Translation-en_GB [3,040 kB]
  Get:25 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en 
[4,354 kB]
  Get:26 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 DEP-11 
Metadata [3,410 kB]
  Get:27 http://gb.archive.ubuntu.com/ubuntu xenial/universe DEP-11 64x64 
Icons [7,448 kB]
  Get:28 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages [144 kB]
  Get:29 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages [140 kB]
  Get:30 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse 
Translation-en_GB [88.1 kB]
  Get:31 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse 
Translation-en [106 kB]
  Get:32 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 DEP-11 
Metadata [63.8 kB]
  Get:33 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse DEP-11 64x64 
Icons [230 kB]
  Get:34 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages [28 B]
  Get:35 http://gb.archive.ubuntu.com/ubuntu 

[Group.of.nepali.translators] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

[Mathew Hodson]

** No longer affects: debian

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

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

Title:
  apt-get update returns "AppStream cache update completed, but some
  metadata was ignored due to errors." periodically

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The recent update of the Ubuntu asgen instance yielded it to
  generate modern metadata. While we could tell asgen to generate old-
  style metadata, fixing appstream is the better idea, since we already
  applied similar patches to appstream-glib (and having this package
  hold back updates is a bad idea). Currently, the unknown metadata is
  considered to be broken by appstream and it displays a warning about
  that issue during an `apt update`

   * The attached patch includes a second change to make AppStream more
  robust against broken YAML data, ensuring LP #1579712 can not be
  triggered on purpose or due to broken disks creating damaged YAML
  structure.

  [Test Case 1]

   * apt update
   * Check for errors about metadata being ignored

  [Test Case 2]

   * appstreamcli refresh --force
   * Check for errors about metadata being ignored
   * Check if we ignored data that should be present
 (search for it via `appstreamcli search `)
   * Run `appstreamcli status` and see if we still have information on the same 
amount of components as prior to the update.

  [Regression Potential]

   * Medium; The works case would be KDE Discover and GNOME Software
  loosing information on available software, but this risk is very low
  and the patch to fix this bug is very simple and has almost no
  regression potential. The YAML parser fix patch is a bit more complex,
  but should have no sideeffects.

  [Original report]

  Periodically I get emails from a machine with the subject:

  Cron  if [ -x /etc/munin/plugins/apt_all ]; then
  /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
  /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
  >/dev/null; fi

  And a body of:

  AppStream cache update completed, but some metadata was ignored due to
  errors.

  I have a machine monitored by Munin.  One of the plugins used on that
  machine is /etc/munin/plugins/apt which periodically counts the number
  of packets that can be upgraded.  This is achieved by a crontab entry
  installed from the package which looks like this:

  #
  # cron-jobs for munin-node
  #

  MAILTO=root

  # If the APT plugin is enabled, update packages databases approx. once
  # an hour (12 invokations an hour, 1 in 12 chance that the update will
  # happen), but ensure that there will never be more than two hour (7200
  # seconds) interval between updates..
  */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then 
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x 
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 
>/dev/null; fi

  For many months everything has been running smoothly.  On the 23rd
  November 2016 I started getting the "AppStream cache update completed,
  but some metadata was ignored due to errors." messages at a rate of
  about ten a day.

  I did a quick Google search which turned up a handful of bugs from earlier 
this year, such as
  Bug1575248.  That is marked as Fixed Released though, so I am raising this 
new bug.

  If there are any further diagnostic details I can provide, please let
  me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 09:57:18 2016
  InstallationDate: Installed on 2013-05-08 (1295 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
  JournalErrors:
   -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 
GMT. --
   Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
  SourcePackage: appstream
  UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago)

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

[Group.of.nepali.translators] [Bug 1460164] Re: restart of openvswitch-switch causes instance network down when l2population enabled

[Corey Bryant]

Marking Juno as "Won't fix" for the Ubuntu Cloud Archive since it is
EOL.

** Changed in: cloud-archive/juno
   Status: New => Won't Fix

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

Title:
  restart of openvswitch-switch causes instance network down when
  l2population enabled

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive icehouse series:
  Fix Released
Status in Ubuntu Cloud Archive juno series:
  Won't Fix
Status in Ubuntu Cloud Archive kilo series:
  Fix Released
Status in neutron:
  Fix Released
Status in neutron kilo series:
  New
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Trusty:
  Fix Released
Status in neutron source package in Wily:
  Fix Released
Status in neutron source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Restarts of openvswitch (typically on upgrade) result in loss of tunnel 
connectivity when the l2population driver is in use.  This results in loss of 
access to all instances on the effected compute hosts

  [Test Case]
  Deploy cloud with ml2/ovs/l2population enabled
  boot instances
  restart ovs; instance connectivity will be lost until the 
neutron-openvswitch-agent is restarted on the compute hosts.

  [Regression Potential]
  Minimal - in multiple stable branches upstream.

  [Original Bug Report]
  On 2015-05-28, our Landscape auto-upgraded packages on two of our
  OpenStack clouds.  On both clouds, but only on some compute nodes, the
  upgrade of openvswitch-switch and corresponding downtime of
  ovs-vswitchd appears to have triggered some sort of race condition
  within neutron-plugin-openvswitch-agent leaving it in a broken state;
  any new instances come up with non-functional network but pre-existing
  instances appear unaffected.  Restarting n-p-ovs-agent on the affected
  compute nodes is sufficient to work around the problem.

  The packages Landscape upgraded (from /var/log/apt/history.log):

  Start-Date: 2015-05-28  14:23:07
  Upgrade: nova-compute-libvirt:amd64 (2014.1.4-0ubuntu2, 2014.1.4-0ubuntu2.1), 
libsystemd-login0:amd64 (204-5ubuntu20.11, 204-5ubuntu20.12), 
nova-compute-kvm:amd64 (2014.1.4-0ubuntu2, 2014.1.4-0ubuntu2.1), 
systemd-services:amd64 (204-5ubuntu20.11, 204-5ubuntu20.12), 
isc-dhcp-common:amd64 (4.2.4-7ubuntu12.1, 4.2.4-7ubuntu12.2), nova-common:amd64 
(2014.1.4-0ubuntu2, 2014.1.4-0ubuntu2.1), python-nova:amd64 (2014.1.4-0ubuntu2, 
2014.1.4-0ubuntu2.1), libsystemd-daemon0:amd64 (204-5ubuntu20.11, 
204-5ubuntu20.12), grub-common:amd64 (2.02~beta2-9ubuntu1.1, 
2.02~beta2-9ubuntu1.2), libpam-systemd:amd64 (204-5ubuntu20.11, 
204-5ubuntu20.12), udev:amd64 (204-5ubuntu20.11, 204-5ubuntu20.12), 
grub2-common:amd64 (2.02~beta2-9ubuntu1.1, 2.02~beta2-9ubuntu1.2), 
openvswitch-switch:amd64 (2.0.2-0ubuntu0.14.04.1, 2.0.2-0ubuntu0.14.04.2), 
libudev1:amd64 (204-5ubuntu20.11, 204-5ubuntu20.12), isc-dhcp-client:amd64 
(4.2.4-7ubuntu12.1, 4.2.4-7ubuntu12.2), python-eventlet:amd64 (0.13.0-1ubuntu2, 
0.13.0-1ubuntu2.1), python-novaclient:amd64 (2.17.0-0ubuntu1.1, 
2.17.0-0ubuntu1.2), grub-pc-bin:amd64 (2.02~beta2-9ubuntu1.1, 
2.02~beta2-9ubuntu1.2), grub-pc:amd64 (2.02~beta2-9ubuntu1.1, 
2.02~beta2-9ubuntu1.2), nova-compute:amd64 (2014.1.4-0ubuntu2, 
2014.1.4-0ubuntu2.1), openvswitch-common:amd64 (2.0.2-0ubuntu0.14.04.1, 
2.0.2-0ubuntu0.14.04.2)
  End-Date: 2015-05-28  14:24:47

  From /var/log/neutron/openvswitch-agent.log:

  2015-05-28 14:24:18.336 47866 ERROR neutron.agent.linux.ovsdb_monitor
  [-] Error received from ovsdb monitor: ovsdb-client:
  unix:/var/run/openvswitch/db.sock: receive failed (End of file)

  Looking at a stuck instances, all the right tunnels and bridges and
  what not appear to be there:

  root@vector:~# ip l l | grep c-3b
  460002: qbr7ed8b59c-3b:  mtu 1500 qdisc 
noqueue state UP mode DEFAULT group default
  460003: qvo7ed8b59c-3b:  mtu 1500 
qdisc pfifo_fast master ovs-system state UP mode DEFAULT group default qlen 1000
  460004: qvb7ed8b59c-3b:  mtu 1500 
qdisc pfifo_fast master qbr7ed8b59c-3b state UP mode DEFAULT group default qlen 
1000
  460005: tap7ed8b59c-3b:  mtu 1500 qdisc 
pfifo_fast master qbr7ed8b59c-3b state UNKNOWN mode DEFAULT group default qlen 
500
  root@vector:~# ovs-vsctl list-ports br-int | grep c-3b
  qvo7ed8b59c-3b
  root@vector:~#

  But I can't ping the unit from within the qrouter-${id} namespace on
  the neutron gateway.  If I tcpdump the {q,t}*c-3b interfaces, I don't
  see any traffic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1460164/+subscriptions

___
Mailing list: 

[Group.of.nepali.translators] [Bug 1582278] Re: [SR-IOV][CPU Pinning] nova compute can try to boot VM with CPUs from one NUMA node and PCI device from another NUMA node.

[Corey Bryant]

Marking as fix released for xenial/mitaka since 13.1.2 is now in xenial-
updates and mitaka-updates.

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/mitaka
   Importance: Undecided
   Status: New

** Changed in: cloud-archive
   Status: New => Invalid

** Changed in: nova (Ubuntu Xenial)
   Status: Triaged => Fix Released

** Changed in: cloud-archive/mitaka
   Status: New => 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/1582278

Title:
  [SR-IOV][CPU Pinning] nova compute can try to boot VM with CPUs from
  one NUMA node and PCI device from another NUMA node.

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Fix Released
Status in nova source package in Yakkety:
  Fix Released

Bug description:
  Environment:
  Two NUMA nodes on compute host (node-0 and node-1).
  One SR-IOV PCI device associated with NUMA node-1.

  Steps to reproduce:

  Steps to reproduce:
   1) Deploy env with SR-IOV and CPU pinning enable
   2) Create new flavor with cpu pinning:
  nova flavor-show m1.small.performance
  
++---+
  | Property | Value |
  
++---+
  | OS-FLV-DISABLED:disabled | False |
  | OS-FLV-EXT-DATA:ephemeral | 0 |
  | disk | 20 |
  | extra_specs | {"hw:cpu_policy": "dedicated", "hw:numa_nodes": "1"} |
  | id | 7b0e5ee0-0bf7-4a46-9653-9279a947c650 |
  | name | m1.small.performance |
  | os-flavor-access:is_public | True |
  | ram | 2048 |
  | rxtx_factor | 1.0 |
  | swap | |
  | vcpus | 1 |
  
++
   3) download ubuntu image
   4) create sr-iov port and boot vm on this port with m1.small.performance 
flavor:
  NODE_1='node-4.test.domain.local'
  NODE_2='node-5.test.domain.local'
  NET_ID_1=$(neutron net-list | grep net_EW_2 | awk '{print$2}')
  neutron port-create $NET_ID_1 --binding:vnic-type direct --device_owner 
nova-compute --name sriov_23
  port_id=$(neutron port-list | grep 'sriov_23' | awk '{print$2}')
  nova boot vm23 --flavor m1.small.performance --image ubuntu_image 
--availability-zone nova:$NODE_1 --nic port-id=$port_id --key-name vm_key

  Expected results:
   VM is an ACTIVE state
  Actual result:
   In most cases the state is ERROR with following logs:

  2016-05-13 08:25:56.598 29097 ERROR nova.pci.stats 
[req-26138c0b-fa55-4ff8-8f3a-aad980e3c815 d864c4308b104454b7b46fb652f4f377 
9322dead0b5d440986b12596d9cbff5b - - -] Failed to allocate PCI devices for 
instance. Unassigning devices back to pools. This should not happen, since the 
scheduler should have accurate information, and allocation during claims is 
controlled via a hold on the compute node semaphore
  2016-05-13 08:25:57.502 29097 INFO nova.virt.libvirt.driver 
[req-26138c0b-fa55-4ff8-8f3a-aad980e3c815 d864c4308b104454b7b46fb652f4f377 
9322dead0b5d440986b12596d9cbff5b - - -] [instance: 
4e691469-893d-4b24-a0a8-00bbee0fa566] Creating image
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager 
[req-26138c0b-fa55-4ff8-8f3a-aad980e3c815 d864c4308b104454b7b46fb652f4f377 
9322dead0b5d440986b12596d9cbff5b - - -] Instance failed network setup after 1 
attempt(s)
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager Traceback (most 
recent call last):
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1570, in 
_allocate_network_async
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager 
bind_host_id=bind_host_id)
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 666, in 
allocate_for_instance
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager 
self._delete_ports(neutron, instance, created_port_ids)
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager 
self.force_reraise()
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager 
six.reraise(self.type_, self.value, self.tb)
  2016-05-13 08:25:57.664 29097 ERROR nova.compute.manager   File 

[Group.of.nepali.translators] [Bug 1608934] Re: ephemeral/swap disk creation fails for local storage with image type raw/lvm

[Corey Bryant]

Marking as fix released for xenial/mitaka since 13.1.2 is now in xenial-
updates and mitaka-updates.

** Changed in: cloud-archive/mitaka
   Status: Fix Committed => Fix Released

** Changed in: nova/mitaka
   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/1608934

Title:
  ephemeral/swap disk creation fails for local storage with image type
  raw/lvm

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive liberty series:
  Fix Committed
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) mitaka series:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Fix Released

Bug description:
  Description
  ===
  I am currently trying to launch an instance in my mitaka cluster with a 
flavor with ephemeral and root storage. Whenever i am trying to start the 
instance i am running into an "DiskNotFound" Error (see trace below). Starting 
instances without ephemeral works perfectly fine and the root disk is created 
as expected in /var/lib/nova/instance/$INSTANCEID/disk .

  Steps to reproduce
  ==
  1. Create a flavor with ephemeral and root storage.
  2. Start an instance with that flavor.

  Expected result
  ===
  Instance starts and ephemeral disk is created in 
/var/lib/nova/instances/$INSTANCEID/disk.eph0 or disk.local ? (Not sure where 
the switchase for the naming is)

  Actual result
  =
  Instance does not start, ephemeral disk seems to be created at 
/var/lib/nova/instances/$INSTANCEID/disk.eph0, but nova checks 
/var/lib/nova/instances/_base/ephemeral_* for disk_size

  TRACE: http://pastebin.com/raw/TwtiNLY2

  Environment
  ===
  I am running OpenStack mitaka on Ubuntu 16.04 in the latest version with 
Libvirt + KVM as hypervisor (also latest stable in xenial).

  Config
  ==

  nova.conf:

  ...
  [libvirt]
  images_type = raw
  rbd_secret_uuid = XXX
  virt_type = kvm
  inject_key = true
  snapshot_image_format = raw
  disk_cachemodes = "network=writeback"
  rng_dev_path = /dev/random
  rbd_user = cinder
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1608934/+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 1642538] Re: swift-ring-builder rebalance - endless loop

[Corey Bryant]

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

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

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

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

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

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

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

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

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

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/newton
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/mitaka
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/ocata
   Importance: Undecided
   Status: New

** Changed in: cloud-archive/mitaka
   Status: New => Triaged

** Changed in: cloud-archive/newton
   Status: New => Triaged

** Changed in: cloud-archive/ocata
   Status: New => Triaged

** Changed in: cloud-archive/ocata
   Importance: Undecided => High

** Changed in: cloud-archive/newton
   Importance: Undecided => High

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

** Changed in: cloud-archive/mitaka
   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/1642538

Title:
  swift-ring-builder rebalance - endless loop

Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive newton series:
  Triaged
Status in Ubuntu Cloud Archive ocata series:
  Triaged
Status in OpenStack Object Storage (swift):
  Fix Released
Status in swift package in Ubuntu:
  Triaged
Status in swift source package in Xenial:
  Triaged
Status in swift source package in Yakkety:
  Triaged
Status in swift source package in Zesty:
  Triaged

Bug description:
  There is an issue with swift-ring-builder and rebalancing under
  certain conditions beginning in Mitaka.

  Steps to reproduce:
  Create a ring with part power of 12. 3 servers with 11 devices each, BUT 2 
servers in zone 1 and one server in zone 2. After adding all devices as 
described above, swift-ring-builder .builder rebalance does not return 
and seems to run into an endless loop.

  The weirdness starts with the 11th device, 10 devices still work. It
  does not matter whether you add each 10 devices from the 3 servers and
  rebalance, and than add the 11th device from each server afterwards or
  do it all at once.

  This behaviour does not exists in Liberty and starts with Mitaka.

  For connivence I am adding the statements to reproduce:


  swift-ring-builder account.builder create 12 3 1

  swift-ring-builder account.builder add --region 1 --zone 1 --ip 10.46.15.60 
--port 6002 --replication-ip 10.46.15.60 --replication-port 6002 --device 
swift-01 --weight 100.00
  swift-ring-builder account.builder add --region 1 --zone 1 --ip 10.46.15.60 
--port 6002 --replication-ip 10.46.15.60 --replication-port 6002 --device 
swift-02 --weight 100.00
  swift-ring-builder account.builder add --region 1 --zone 1 --ip 10.46.15.60 
--port 6002 --replication-ip 10.46.15.60 --replication-port 6002 --device 
swift-03 --weight 100.00
  swift-ring-builder account.builder add --region 1 --zone 1 --ip 10.46.15.60 
--port 6002 --replication-ip 10.46.15.60 --replication-port 6002 --device 
swift-04 --weight 100.00
  swift-ring-builder account.builder add --region 1 --zone 1 --ip 10.46.15.60 
--port 6002 --replication-ip 10.46.15.60 --replication-port 6002 --device 
swift-05 --weight 100.00
  swift-ring-builder account.builder add --region 1 --zone 1 --ip 10.46.15.60 
--port 6002 --replication-ip 10.46.15.60 --replication-port 6002 --device 
swift-06 --weight 100.00
  swift-ring-builder account.builder add --region 1 --zone 1 --ip 10.46.15.60 
--port 6002 --replication-ip 10.46.15.60 --replication-port 6002 --device 
swift-07 --weight 100.00
  swift-ring-builder account.builder add --region 1 --zone 1 --ip 10.46.15.60 
--port 6002 --replication-ip 10.46.15.60 --replication-port 6002 --device 
swift-08 --weight 100.00
  swift-ring-builder account.builder add --region 1 --zone 1 --ip 10.46.15.60 
--port 6002 --replication-ip 10.46.15.60 --replication-port 6002 --device 
swift-09 --weight 100.00
  swift-ring-builder account.builder add --region 1 --zone 1 --ip 10.46.15.60 
--port 6002 --replication-ip 10.46.15.60 --replication-port 6002 --device 
swift-10 --weight 100.00
  swift-ring-builder account.builder add --region 1 --zone 1 --ip 10.46.15.60 
--port 6002 --replication-ip 10.46.15.60 --replication-port 6002 --device 
swift-11 

[Group.of.nepali.translators] [Bug 1644377] Re: SRU of LXD 2.0.8 (upstream bugfix release)

[Launchpad Bug Tracker]

This bug was fixed in the package lxd - 2.0.8-0ubuntu1~ubuntu16.04.1

---
lxd (2.0.8-0ubuntu1~ubuntu16.04.1) xenial; urgency=medium

  * New upstream bugfix release (2.0.8) (LP: #1644377)
- Don't grab addresses from public remotes

lxd (2.0.7-0ubuntu1~ubuntu16.04.1) xenial; urgency=medium

  * New upstream bugfix release (2.0.7) (LP: #1644377)
- extra/bash: Better parse containers list
- lxc/copy: Make container copy more robust
- lxd/containers: Don't assign idmaps to privileged containers
- lxd/containers: Don't break when parsing old containers
- lxd/containers: Don't double apply templates
- lxd/containers: Fix concurrent map iteration+modification
- lxd/containers: Fix idmap handling of pre-idmap containers
- tests: Add tests for file templating

lxd (2.0.6-0ubuntu1~ubuntu16.04.1) xenial; urgency=medium

  * New upstream bugfix release (2.0.6) (LP: #1644377)
- Support for container specific uid/gid maps (see userns-idmap.md)
- appveyor: Add config to git
- appveyor: Cleanup appveyor.yml before modifications
- appveyor: Create archive with platform specifier in its name
- appveyor: Do verbose testing for test names and timings
- appveyor: Publish compiled binaries for download
- client: Rework progress handling
- doc: Add hacking guide (debugging.md)
- doc: Add official Windows support in README
- doc: Bump liblxc version required in README
- doc: Sort API endpoints in rest-api.md
- doc: Update README to specify docker installation details
- doc: Update requirements, we actually require 2.0.0 or higher
- doc: Use consistent method ordering in rest-api.md
- extra/bash: Allow dash in parameters to lxc-client bash-completion
- extra/bash: Fix _lxd_profiles in lxc-client bash-completion
- extra/lxc-to-lxd: Better output with no container
- extra/lxc-to-lxd: Check that source path exists (disk)
- extra/lxc-to-lxd: Consistent logging
- extra/lxc-to-lxd: Don't fail dry-run with running containers
- extra/lxc-to-lxd: Drop dependency on pylxd
- extra/lxc-to-lxd: Fix lxdpath handling
- extra/lxc-to-lxd: Formatting
- extra/lxc-to-lxd: Migrate lxc.aa_profile if set
- extra/lxc-to-lxd: Print summary and proper exit code
- lxc/copy: Don't use the operation as a marker of success
- lxc/copy: Wait on the source operation too
- lxc/delete: update help text
- lxc/exec: Set term to "dumb" on windows
- lxc/finger: update help text
- lxc: Fix tests on Windows/Mac
- lxc/list: Fix typo in help message
- lxc/remote: Fix remote add with Go tip
- lxc/restore: update help text
- lxc: Use .yaml as the yaml extension in examples
- lxd/certificates: Export all documented certificate fields
- lxd/containers: Add /snap/bin to PATH even if only /snap exists
- lxd/containers: Also clean up apparmor stuff on failure in OnStart
- lxd/containers: Attach to userns on file operations
- lxd/containers: Be more verbose on mkdir failure
- lxd/containers: Better handle concurent stop/shutdown
- lxd/containers: Catch and return more errors in OnStop
- lxd/containers: Clarify container delete failure error
- lxd/containers: Don't destroy ephemeral container on restart
- lxd/containers: Don't double delete ephemeral containers
- lxd/containers: Don't show invalid logs
- lxd/containers: Fix forkmount to work with 4.8 and higher
- lxd/containers: Fix invalid filename of metadata on export
- lxd/containers: Improve config validation on update
- lxd/containers: Improve container error handling
- lxd/containers: Improve container locking mechanism
- lxd/containers: log OnStart/OnStop hook errors
- lxd/containers: More reliable container autostart
- lxd/containers: Only load kernel modules if not loaded
- lxd/containers: Properly validate CPU allowance
- lxd/containers: Properly validate memory limits
- lxd/containers: Record the err from go-lxc
- lxd/containers: Remove legacy code from OnStop
- lxd/containers: Remove unused code
- lxd/containers: Save properties on publish
- lxd/containers: Set LXC loglevel to match daemon
- lxd/containers: Skip leading whitespace in raw.lxc
- lxd/containers: Start storage when necessary in stateful start
- lxd/containers: Timeout container freeze on stop
- lxd/images: Detect out of disk space unpack errors
- lxd/images: Don't make unnecessary image copies
- lxd/images: Don't update images at all if interval is 0
- lxd/images: Store the simplestreams cache to disk
- lxd/init: Detect zfs kernel support
- lxd/init: Ignore ZFS if in a container
- lxd/main: Immediately exit when no DB in activateifneeded
- lxd/migration: Fix a race for collecting logs
- lxd/migration: Remove debugging by file creation
- lxd/migration: Start migration storage at the right time
- lxd/storage: Fix 

[Group.of.nepali.translators] [Bug 1628285] Re: apparmor should be allowed to start in containers

[Tyler Hicks]

This bug will not be fixed in 14.04, meaning that AppArmor policy will
not be loaded inside of 14.04 LXD containers and snaps will not work
inside of 14.04 LXD containers. 16.04 LXD containers should be used in
such use cases.

** Changed in: apparmor (Ubuntu Trusty)
   Status: Incomplete => Won't Fix

** Changed in: upstart (Ubuntu Trusty)
   Status: Incomplete => Won't Fix

** Changed in: upstart (Ubuntu Trusty)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

** Changed in: apparmor (Ubuntu Trusty)
 Assignee: Tyler Hicks (tyhicks) => (unassigned)

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

Title:
  apparmor should be allowed to start in containers

Status in apparmor package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Invalid
Status in apparmor source package in Trusty:
  Won't Fix
Status in upstart source package in Trusty:
  Won't Fix
Status in apparmor source package in Xenial:
  Fix Released

Bug description:
  =apparmor and upstart 14.04 SRU=
  [Impact]
  A recent 16.04 kernel (4.4.0-46.67) and the lxd 
(2.0.5-0ubuntu1~ubuntu16.04.1) allows us to enable stacked/namespaced AppArmor 
policy for 14.04 lxd containers. This means that the container can have an 
overall confinement profile while still allowing individual processes inside of 
the container to have individual confinement profiles. This bug is for the 
apparmor and upstart userspace changes needed to allow the container init to 
load apparmor profiles during the container boot procedure.

  [Test Case]
  Install the latest Xenial kernel and lxd. Reboot into the new kernel and set 
up a new 14.04 lxd container (MUST be an unprivileged container):

   $ lxc launch ubuntu-daily:14.04 t

  Install apparmor from trusty-proposed (2.10.95-0ubuntu2.5~14.04.1) and
  upstart from trusty-proposed (1.12.1-0ubuntu4.3) inside of the
  container and reboot the container.

  Verify that the container's dhclient is confined inside of an AppArmor
  namespace with a stacked profile that was loaded inside of the
  container:

  $ ps auxZ | grep 
'^lxd-t_//&:lxd-t_:///sbin/dhclient'
  lxd-t_//&:lxd-t_:///sbin/dhclient (enforce) 165536 
3889 0.0  0.0 16120 860 ? Ss 03:55   0:00 /sbin/dhclient -1 -v -pf 
/run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -I -df 
/var/lib/dhcp/dhclient6.eth0.leases eth0

  Verify that aa-status works inside of the container:

  $ lxc exec t -- aa-status
  apparmor module is loaded.
  4 profiles are loaded.
  4 profiles are in enforce mode.
     /sbin/dhclient
     /usr/lib/NetworkManager/nm-dhcp-client.action
     /usr/lib/connman/scripts/dhclient-script
     /usr/sbin/tcpdump
  0 profiles are in complain mode.
  1 processes have profiles defined.
  1 processes are in enforce mode.
     /sbin/dhclient (518)
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  Now, examine the output of aa-status to verify that the
  /usr/sbin/tcpdump profile is loaded.

  To validate the upstart change, use apparmor-profile-load to load a
  profile:

  $ echo "profile lp1628285-test {} " | lxc exec t -- tee 
/etc/apparmor.d/lp1628285-test
  $ lxc exec t -- /lib/init/apparmor-profile-load lp1628285-test
  $ lxc exec t -- aa-status
  apparmor module is loaded.
  5 profiles are loaded.
  5 profiles are in enforce mode.
     /sbin/dhclient
     /usr/lib/NetworkManager/nm-dhcp-client.action
     /usr/lib/connman/scripts/dhclient-script
     /usr/sbin/tcpdump
     lp1628285-test
  0 profiles are in complain mode.
  1 processes have profiles defined.
  1 processes are in enforce mode.
     /sbin/dhclient (518)
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.
  $ lxc exec t -- ls /etc/apparmor.d/cache/lp1628285-test
  /etc/apparmor.d/cache/lp1628285-test

  Now, reboot and then run aa-status again to verify that the output is
  the same (except for the process ID numbers).

  It is also a good test to install ntp and cups-daemon, use aa-status
  to verify that their profiles are in enforce mode and that their
  processes are confined. Then reboot and use aa-status to verify the
  same thing.

  [Regression Potential]
  The regression potential is relatively high because processes inside of 
Ubuntu containers can be confined with an additional profile that is loaded 
inside of the container. This feature was released in Ubuntu 16.10 and 16.04 
with no known serious issues so far.

  IMPORTANT: There is a known regression that may be seen by users of
  `lxc exec`. See bug #1641236 for details. Bug #1640868 is pre-
  existing, doesn't seem to have any negative side-effects, and is not
  caused by this SRU.

  =apparmor 16.04 SRU=
  [Impact]
  The kernel in xenial-proposed (4.4.0-46.67) and the lxd that has recently 
migrated from xenial-proposed 

[Group.of.nepali.translators] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04

[Mario Limonciello]

** Package changed: fwupdate-signed (Ubuntu) => fwupd (Ubuntu)

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

Title:
  USB audio device is not recognized after startup in 16.04

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

Bug description:
  [Impact]
  High end USB audio devices don't work properly after fwupd is started from 
gnome-software.

  [Test case]
  Login to Ubuntu session and try to use a USB audio device.  See if it works 
properly.

  If you are applying this upgrade and testing a regression it's important that 
the device isn't in a bad state to start.  To guarantee this doesn't happen:
  1) Apply the update
  2) Power off your machine
  3) Unplug device
  4) Plug in device
  5) Power on machine
  6) Check if it works.

  [Regression Potential]
  This affects the DFU provider in Ubuntu.  The fix is only made to that part 
of the fwupd stack.
  No firmware for DFU has been published to the LVFS yet, so this shouldn't 
have any regression risk to Ubuntu.

  [Original bug]
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1574079/+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 1603610] Re: Snaps have no screenshots

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software - 3.20.1+git20161013.0
.d77d6cf-0ubuntu2~xenial1

---
gnome-software (3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1) xenial; 
urgency=medium

  * New upstream snapshot from the wip/ubuntu branch at
git://git.gnome.org/gnome-software.
- Use snapd-glib to perform snapd login. This fixes non-root access being
  removed in snapd. (LP: #1616943)
- Show screenshots for snaps (requires snapd 2.15.2) (LP: #1603610)
- Set snap summary from snapd response (LP: #1629456)
- Don't show terminal for graphical apps (LP: #1595023)
  * debian/control:
- Build-depend on libsnapd-glib-dev
  * debian/rules:
- Build with --enable-snap

 -- Robert Ancell   Wed, 23 Nov 2016
21:31:03 +1300

** Changed in: gnome-software (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/1603610

Title:
  Snaps have no screenshots

Status in snapd-glib:
  Fix Released
Status in Snappy:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Fix Released

Bug description:
  Snaps have no screenshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd-glib/+bug/1603610/+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 1595023] Re: Need to determine if snap apps require terminal or not

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software - 3.20.1+git20161013.0
.d77d6cf-0ubuntu2~xenial1

---
gnome-software (3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1) xenial; 
urgency=medium

  * New upstream snapshot from the wip/ubuntu branch at
git://git.gnome.org/gnome-software.
- Use snapd-glib to perform snapd login. This fixes non-root access being
  removed in snapd. (LP: #1616943)
- Show screenshots for snaps (requires snapd 2.15.2) (LP: #1603610)
- Set snap summary from snapd response (LP: #1629456)
- Don't show terminal for graphical apps (LP: #1595023)
  * debian/control:
- Build-depend on libsnapd-glib-dev
  * debian/rules:
- Build with --enable-snap

 -- Robert Ancell   Wed, 23 Nov 2016
21:31:03 +1300

** Changed in: gnome-software (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/1595023

Title:
  Need to determine if snap apps require terminal or not

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

Bug description:
  snapd returns a list of apps a snap contains, i.e:

  "apps": [{"name": "moon-buggy"}]

  However, we can't tell if this is a terminal app (like moon buggy) or
  a graphical app (like Ubuntu calculator).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1595023/+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 1616943] Re: Can't auth against U1 in g-s

[Launchpad Bug Tracker]

This bug was fixed in the package snapd-glib - 1.2-0ubuntu1.1~xenial

---
snapd-glib (1.2-0ubuntu1.1~xenial) xenial; urgency=medium

  * Backport to xenial (LP: #1616943)

 -- Robert Ancell   Wed, 16 Nov 2016
14:58:58 +1300

** Changed in: snapd-glib (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: gnome-software (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/1616943

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

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

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

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

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

  Expected result:
  Authentication completes and the snap is installed.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

[Launchpad Bug Tracker]

This bug was fixed in the package ifupdown - 0.8.13ubuntu3

---
ifupdown (0.8.13ubuntu3) yakkety-proposed; urgency=medium

  * networking.service: exclude loopback device lo in ExecStop (LP:
#1629972)

 -- Scott Moser   Fri, 14 Oct 2016 13:53:32 -0400

** Changed in: ifupdown (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/1629972

Title:
  networking stop incorrectly disconnects from (network) root filesystem

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  In Progress
Status in ifupdown source package in Yakkety:
  Fix Released
Status in ifupdown package in Debian:
  New

Bug description:
  === Begin SRU Template ===
  [Impact]
  The systemd networking.service unit will bring down the loopback device (lo)
  when it is stopped.  This behavior differs from the behavior in other
  Ubuntu releases (upstart's networking.conf), where 'lo' is not taken down.

  The problem that was seen was that iscsi root over ipv6 would hang on
  shutdown.  

  [Test Case]
  Test is fairly simple and can be demonstrated in lxc container.
  The key is really that the lo device should not have its link set down
  after stopping networking.service.  So, below:
out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty

  should not show 'empty', but should have LOOPBACK,UP,LOWER in its
  output.

  $ release=yakkety; name=y1
  $ lxc launch ubuntu-daily:$release $name
  $ sleep 10
  $ lxc exec $name /bin/bash

  ## show only things that are up (note output has LOOPBACK,UP,LOWER_UP)
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  % ip address show dev lo up
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever

  ## Stop the service and show lo link is down (no 'UP' or 'LOWER_UP').
  % systemctl stop networking.service
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state DOWN mode DEFAULT group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
  empty

  ## Now enable proposed, install update, reboot and show.
  % rel=$(lsb_release -sc)
  % echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
  sudo tee /etc/apt/sources.list.d/proposed.list
  % sudo apt update -qy && sudo apt install -qy ifupdown  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % ip address show dev lo up
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  % systemctl stop networking.service
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever

  
  [Regression Potential]
  Should be pretty low.  zesty and  yakkety-proposed have this.
  Taking down 'lo' is often cause of problems, and never the solution to
  problems as far as I'm aware.

  [Other Info]

  === End SRU Template ===

  With the switch to systemd, all support for iscsi root (and other)
  filesystems disappeared, since shutdown yanks the rug out from under
  us.

  Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
  creates..), the DEV check should be expanded to include iscsi devices,
  and networking.service ExecStop should honor those checks.

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1621507: ipv6 network boot does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1629972/+subscriptions

[Group.of.nepali.translators] [Bug 1629456] Re: Summary isn't shown for snaps

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software - 3.20.1+git20161013.0
.d77d6cf-0ubuntu2~xenial1

---
gnome-software (3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1) xenial; 
urgency=medium

  * New upstream snapshot from the wip/ubuntu branch at
git://git.gnome.org/gnome-software.
- Use snapd-glib to perform snapd login. This fixes non-root access being
  removed in snapd. (LP: #1616943)
- Show screenshots for snaps (requires snapd 2.15.2) (LP: #1603610)
- Set snap summary from snapd response (LP: #1629456)
- Don't show terminal for graphical apps (LP: #1595023)
  * debian/control:
- Build-depend on libsnapd-glib-dev
  * debian/rules:
- Build with --enable-snap

 -- Robert Ancell   Wed, 23 Nov 2016
21:31:03 +1300

** Changed in: gnome-software (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/1629456

Title:
  Summary isn't shown for snaps

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

Bug description:
  Ubuntu packages are shown in gnome-software with the name, followed by
  the summary, followed by install buttons, and finally followed by a
  more detailed description. In contrast, snaps are shown with the name,
  detailed summary, followed by install buttons. The summary isn't
  present, and the experience isn't consistent with normal packages.

  I suggest we maintain consistency: show the snap name, followed by the
  snap summary, followed by install buttons, and finally followed by the
  more detailed description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1629456/+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 1482938] Re: im-config gcin qt5

[Launchpad Bug Tracker]

This bug was fixed in the package im-config - 0.29-1ubuntu12.3

---
im-config (0.29-1ubuntu12.3) xenial-proposed; urgency=medium

  * debian/patches/fix-uim-qt5.patch:
- Fix uim Qt5 immodule path (LP: #1642001).
  * debian/patches/gcin-qt5.patch:
- Add gcin Qt5 immodule (LP: #1482938).

 -- Gunnar Hjalmarsson   Wed, 16 Nov 2016 11:14:00
+0100

** Changed in: im-config (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/1482938

Title:
  im-config gcin qt5

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in im-config package in Debian:
  Fix Released

Bug description:
  [Impact]

  missing

  QT_IM_MODULE=gcin

  in /usr/share/im-config/data/26_gcin.rc

  QT5 needs this.

  Fix uploaded to yakkety queue; xenial patch attached to bug #1642001.

  [Test Case]

  After the change, this command:

  grep -A3 QT_IM_MODULE /usr/share/im-config/data/26_gcin.rc

  should output:

  QT_IM_MODULE=xim
  # use immodule when available for Qt5
  for IM_CONFIG_MARKER in 
/usr/lib/*/qt5/plugins/platforminputcontexts/libgcinplatforminputcontextplugin.so
 ; do
  if [ -e $IM_CONFIG_MARKER ]; then
  QT_IM_MODULE=gcin
  break
  fi
  done

  [Regression Potential]

  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1482938/+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 1642001] Re: uim-qt5 check is broken

[Launchpad Bug Tracker]

This bug was fixed in the package im-config - 0.29-1ubuntu12.3

---
im-config (0.29-1ubuntu12.3) xenial-proposed; urgency=medium

  * debian/patches/fix-uim-qt5.patch:
- Fix uim Qt5 immodule path (LP: #1642001).
  * debian/patches/gcin-qt5.patch:
- Add gcin Qt5 immodule (LP: #1482938).

 -- Gunnar Hjalmarsson   Wed, 16 Nov 2016 11:14:00
+0100

** Changed in: im-config (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/1642001

Title:
  uim-qt5 check is broken

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in im-config package in Debian:
  Fix Released

Bug description:
  [Impact]

  XIM support check for Qt5 in UIM is broken — it uses the same paths as
  for Qt4, but they've been changed.

  Fix uploaded to yakkety queue; xenial patch attached.

  [Test Case]

  After the change, this command:

  grep platforminputcontexts /usr/share/im-config/data/24_uim.rc

  should output:

  for IM_CONFIG_MARKER in
  
/usr/lib/*/qt5/plugins/platforminputcontexts/libuimplatforminputcontextplugin.so
  ; do

  [Regression Potential]

  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1642001/+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 1589535] Re: nm-applet silently timesout on long 'WPA/WPA2 Personal' password input

[Sebastien Bacher]

** Also affects: network-manager-applet (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: network-manager-applet (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  nm-applet silently timesout on long 'WPA/WPA2 Personal' password input

Status in Network Manager Applet:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  New

Bug description:
  1)
  ouroumov@Edge:~/Desktop$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2)
  apt-cache policy is unable to locate the package.

  3)
  Upon entering a long WPA/WPA2 Personal password after clicking the network 
icon in the top right panel, the connection should be added to network-manager, 
even if typing the password takes a while.

  4)
  If typing the password takes longer than ~25 seconds, upon clicking the 
"Connect" button in the password prompt dialog: nothing happens

  Steps to reproduce:

  - Install Ubuntu MATE 16.04 LTS (possibly other Ubuntu flavours using 
nm-applet too)
  - Run normal post-install full system update and reboot
  - Click the network icon in the top right corner of the default panel layout
  - Select from the Wi-Fi network list a network using WPA/WPA2 Personal
  - Enter the password, wait 30 seconds to click 'connect'

  Note:

  While this issue might seem trivial (using 'System -> Preferences ->
  Internet and Network -> Network Connections' allows one to correctly
  save the password) (and quickly copy/pasting the password from a text
  file works too) it is a serious usability problem for many people in
  France.

  The default home router Wi-Fi setup in France is WPA/WPA2 Personal
  with a random 26-character hexadecimal password. It takes a while to
  type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1589535/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package

[Launchpad Bug Tracker]

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

---
glib2.0 (2.51.0-2) experimental; urgency=medium

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

 -- Iain Lane   Wed, 23 Nov 2016 17:36:07 +

** Changed in: glib2.0 (Ubuntu)
   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/1638245

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

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  New
Status in glib2.0 source package in Yakkety:
  In Progress

Bug description:
  [ Description ]

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

  [ QA ]

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

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

  What should happen:
  The files moved into Trash.

  [ Regression potential ]

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

  [ Original ]

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1626972] Re: QEMU memfd_create fallback mechanism change for security drivers

[James Page]

This bug was fixed in the package qemu - 1:2.6.1+dfsg-0ubuntu7~cloud0
---

 qemu (1:2.6.1+dfsg-0ubuntu7~cloud0) xenial-ocata; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 qemu (1:2.6.1+dfsg-0ubuntu7) zesty; urgency=medium
 .
   [ Rafael David Tinoco ]
   * Fixed wrong migration blocker when vhost is used (LP: #1626972)
 - d/p/vhost_migration-blocker-only-if-shared-log-is-used.patch


** Changed in: cloud-archive
   Status: Fix Committed => Fix Released

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

Title:
  QEMU memfd_create fallback mechanism change for security drivers

Status in Ubuntu Cloud Archive:
  Fix Released
Status in QEMU:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Fix Committed
Status in qemu source package in Yakkety:
  In Progress
Status in qemu source package in Zesty:
  Fix Released

Bug description:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

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

   Cons:
   * To break live migration in other circumstances. 

  [Other Info]

   * Christian Ehrhardt has been following this.

  ORIGINAL DESCRIPTION:

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

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

  From qemu 2.5, logic is on :

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

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

  And you can see the errors:

  From the host trying to send the virtual machine:

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

  From the host trying to receive the virtual machine:

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

[Group.of.nepali.translators] [Bug 1628207] Re: boot arguments passed in CONFIG_CMDLINE not being picked up by kernel with gcc-ppc64-linux-gnu v5.4.0 and v6.1.1

[Matthias Klose]

** No longer affects: gcc-5-cross-ports (Ubuntu)

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

Title:
  boot arguments passed in CONFIG_CMDLINE not being picked up by kernel
  with gcc-ppc64-linux-gnu v5.4.0 and v6.1.1

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-5-cross package in Ubuntu:
  New
Status in gcc-6 package in Ubuntu:
  Fix Released
Status in gcc-5 source package in Xenial:
  Fix Released
Status in gccgo-6 source package in Xenial:
  New

Bug description:
  == Comment: #0 - Akshay Adiga - 2016-09-22 23:55:06 ==
  ---Problem Description---
  boot arguments (passed as CONFIG_CMDLINE)  are not being
  picked up by kernel while using gcc-ppc64-linux-gnu v5.4.0 and v6.1.1.
   (gcc v5.3.1 works fine)
   
   
  ---Steps to Reproduce---
  enable following config options in .config
  CONFIG_CMDLINE_BOOL=y
  CONFIG_CMDLINE=""
  CONFIG_CMDLINE_FORCE=y

  build kernel image and kexec without additional boot args.

  The system does not boot as it does not get the boot args.

  I have debugged to issue to gcc compiler optimization :
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-September/149026.html

  The problem has been reported and fixed in upstream gcc
 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71709

  Need to backport this fix for gcc-ppc64-linux-gnu v5.4.0 onwards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1628207/+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 1634475] Re: [SRU] Files missing from package

[James Page]

This bug was fixed in the package mistral - 3.0.0-2~cloud0
---

 mistral (3.0.0-2~cloud0) xenial-ocata; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 mistral (3.0.0-2) unstable; urgency=medium
 .
   [ Corey Bryant ]
   * d/rules, d/mistral-common.postinst.in, d/mistral-common.postrm:
 Install missing json files (LP: #1634475).
   * d/control: Add python-pep8 to Build-Depends.
 .
   [ Thomas Goirand ]
   * Fixed lsb-base depends.
 .
   [ Gauvain Pocentek ]
   * d/rules: install missing resources directory, needed when populating the
 mistral DB


** Changed in: cloud-archive
   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/1634475

Title:
  [SRU] Files missing from package

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive newton series:
  Fix Committed
Status in mistral package in Ubuntu:
  Fix Released
Status in mistral source package in Xenial:
  Fix Committed
Status in mistral source package in Yakkety:
  Fix Committed

Bug description:
  [Description]
  After the package is installed some of the files that support the 
initialisation of the database seem to missing. As does the policy.json.

  The files that are missing:

  /usr/lib/python2.7/dist-packages/mistral/actions/openstack/mapping.json
  /usr/lib/python2.7/dist-packages/mistral/resources (directory + contents)
  /etc/mistral/policy.json

  Without the DB files the schema initialisation fails:
  # mistral-db-manage --config-file /etc/mistral/mistral.conf populate
  Traceback (most recent call last):
    File "/usr/bin/mistral-db-manage", line 10, in 
  sys.exit(main())
    File 
"/usr/lib/python2.7/dist-packages/mistral/db/sqlalchemy/migration/cli.py", line 
129, in main
  CONF.command.func(config, CONF.command.name)
    File 
"/usr/lib/python2.7/dist-packages/mistral/db/sqlalchemy/migration/cli.py", line 
70, in do_populate
  action_manager.sync_db()
    File "/usr/lib/python2.7/dist-packages/mistral/services/action_manager.py", 
line 82, in sync_db
  register_action_classes()
    File "/usr/lib/python2.7/dist-packages/mistral/services/action_manager.py", 
line 128, in register_action_classes
  _register_dynamic_action_classes()
    File "/usr/lib/python2.7/dist-packages/mistral/services/action_manager.py", 
line 88, in _register_dynamic_action_classes
  actions = generator.create_actions()
    File 
"/usr/lib/python2.7/dist-packages/mistral/actions/openstack/action_generator/base.py",
 line 77, in create_actions
  mapping = get_mapping()
    File 
"/usr/lib/python2.7/dist-packages/mistral/actions/openstack/action_generator/base.py",
 line 45, in get_mapping
  MAPPING_PATH)).read())
  IOError: [Errno 2] No such file or directory: 
'/usr/lib/python2.7/dist-packages/mistral/actions/openstack/mapping.json'

  And without the policy.json clients cannot authorise.

  [Test Case]
  Reproduce db issue:
  lxc launch ubuntu-daily:yakkety
  lxc execbash
  apt update
  apt install mistral-api
  mistral-db-manage --config-file /etc/mistral/mistral.conf populate

  [Regression Potential]
  Very little as the fix just updates the package to install the missing json 
files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1634475/+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 1574079] Re: USB audio device is not recognized after startup in 16.04

[Adam Wyn Roberts]

** Package changed: fwupd (Ubuntu) => fwupdate-signed (Ubuntu)

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in fwupdate-signed package in Ubuntu:
  Fix Released
Status in fwupdate-signed source package in Xenial:
  Fix Released
Status in fwupdate-signed source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  High end USB audio devices don't work properly after fwupd is started from 
gnome-software.

  [Test case]
  Login to Ubuntu session and try to use a USB audio device.  See if it works 
properly.

  If you are applying this upgrade and testing a regression it's important that 
the device isn't in a bad state to start.  To guarantee this doesn't happen:
  1) Apply the update
  2) Power off your machine
  3) Unplug device
  4) Plug in device
  5) Power on machine
  6) Check if it works.

  [Regression Potential]
  This affects the DFU provider in Ubuntu.  The fix is only made to that part 
of the fwupd stack.
  No firmware for DFU has been published to the LVFS yet, so this shouldn't 
have any regression risk to Ubuntu.

  [Original bug]
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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