[Group.of.nepali.translators] [Bug 1682103] Re: sysfs channel reads of lps22hb pressure sensor are stale

[Shrirang Bagul]

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

** Changed in: hwe-next
   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/1682103

Title:
  sysfs channel reads of lps22hb pressure sensor are stale

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  LPS22HB sensor IIO driver supports pressure and temperature channels,
  these are enumerated in sysfs. An attempt to read current values
  using:

  # cat /sys/bus/iio/devices/iio:deviceX/in_pressure_raw
  # cat /sys/bus/iio/devices/iio:deviceX/in_temp_raw

  always gives stale results and are never updated.

  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1682103/+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 1690574] Re: Fix autopkgtest regression with webkit2gtk 2.16.2

[Launchpad Bug Tracker]

This bug was fixed in the package sphinx - 1.5.3-1ubuntu0.1

---
sphinx (1.5.3-1ubuntu0.1) zesty; urgency=medium

  * Update jstests for compatibility with WebKitGTK+ 2.16.2 (LP: #1690574).
Now the title property can be no longer than 1000 characters, so we
cannot fetch the whole page using it. Instead, we compute the needed
numbers with JavaScript and then fetch them using the title property.

 -- Dmitry Shachnev   Sun, 14 May 2017 17:33:00
+0300

** Changed in: sphinx (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/1690574

Title:
  Fix autopkgtest regression with webkit2gtk 2.16.2

Status in sphinx package in Ubuntu:
  Fix Released
Status in sphinx source package in Xenial:
  Fix Released
Status in sphinx source package in Yakkety:
  Fix Released
Status in sphinx source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  sphinx's autopkgtests fail with webkit2gtk's 2.16.2 update (LP: #1690536). 
Since we need to update webkit2gtk for security updates, we need to update 
sphinx's autopkgtests too.

  Test Case
  -
  Check https://autopkgtest.ubuntu.com/packages/sphinx
  and make sure that the tests triggered by webkit2gtk 2.16.2 are passing

  Regression Potential
  
  This update only affects the "sphinxdoc" autopkgtest.

  Other Info
  ---
  The autopkgtests are maintained in Debian; this particular test is not from 
sphinx upstream.

  https://anonscm.debian.org/git/python-
  modules/packages/sphinx.git/commit/?id=75bf800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sphinx/+bug/1690574/+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 1690574] Re: Fix autopkgtest regression with webkit2gtk 2.16.2

[Launchpad Bug Tracker]

This bug was fixed in the package sphinx - 1.3.6-2ubuntu1.1

---
sphinx (1.3.6-2ubuntu1.1) xenial; urgency=medium

  * Update jstests for compatibility with WebKitGTK+ 2.16.2 (LP: #1690574).
Now the title property can be no longer than 1000 characters, so we
cannot fetch the whole page using it. Instead, we compute the needed
numbers with JavaScript and then fetch them using the title property.

 -- Dmitry Shachnev   Sun, 14 May 2017 23:10:17
+0300

** Changed in: sphinx (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/1690574

Title:
  Fix autopkgtest regression with webkit2gtk 2.16.2

Status in sphinx package in Ubuntu:
  Fix Released
Status in sphinx source package in Xenial:
  Fix Released
Status in sphinx source package in Yakkety:
  Fix Released
Status in sphinx source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  sphinx's autopkgtests fail with webkit2gtk's 2.16.2 update (LP: #1690536). 
Since we need to update webkit2gtk for security updates, we need to update 
sphinx's autopkgtests too.

  Test Case
  -
  Check https://autopkgtest.ubuntu.com/packages/sphinx
  and make sure that the tests triggered by webkit2gtk 2.16.2 are passing

  Regression Potential
  
  This update only affects the "sphinxdoc" autopkgtest.

  Other Info
  ---
  The autopkgtests are maintained in Debian; this particular test is not from 
sphinx upstream.

  https://anonscm.debian.org/git/python-
  modules/packages/sphinx.git/commit/?id=75bf800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sphinx/+bug/1690574/+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 1641889] Re: The network indicator shows the wrong status

[Shih-Yuan Lee]

** Changed in: oem-priority/xenial
   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/1641889

Title:
  The network indicator shows the wrong status

Status in Network Manager Applet:
  Unknown
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project xenial series:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released

Bug description:
  [Summary] The network indicator shows the wrong status

  [Reproduce Steps]
  1.Boot into Ubuntu OS , disconnect wireless connection
  Note : the issue can't be reproduced with wifi connected
  2.Enable/disable wifi function by pressing hotkey then check network manager 
status

  [Results]
  Expected: "Enable Wi-Fi" option should be OFF
  Actual:"Enable Wi-Fi" option is ON

  [Additional Information]
  Product Name:Inspiron-7460
  BIOS Version:1.0.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1641889/+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 1687711] Re: strongSwan 5.3.5 has a known incompatibility with iOS/macOS 10+

[Launchpad Bug Tracker]

This bug was fixed in the package strongswan - 5.3.5-1ubuntu3.2

---
strongswan (5.3.5-1ubuntu3.2) xenial; urgency=medium

  * d/p/ikev2-Only-add-NAT-D-notifies-to-DPDs-as-initiator.patch: fix issue
related to DPD vs iOS10 (LP: #1687711)

 -- Christian Ehrhardt   Wed, 03 May
2017 17:37:06 +0200

** Changed in: strongswan (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/1687711

Title:
  strongSwan 5.3.5 has a known incompatibility with iOS/macOS 10+

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

Bug description:
  [Impact]

   * iOS10+/MacOS10+ devices fail at dead peer detection and re-establish 
 the connection over and over

   * Backport of upstream fix.

  
  [Test Case]

   * Set up strongswan (the reporter did so via algo, but other preferred 
 setups are good as well) and prepare iOS10+ devices to dial in.

   * check for the reconnects to start based on broken dead peer
  detection

  
  [Regression Potential] 

   * Due to the fact that this is a backport there could be dependencies to 
 the newer code. The change isn't too bug and it looks safe, as well as 
 compiling and regression testing fine - but if we want to look out for 
 regressions that certainly is the biggest potential one.
   * From the behavior change itself it should be safe, to quote from 
 upstream "If a responder is natted it will usually be a static NAT 
 (unless it's a mediated connection) in which case adding these notifies 
 makes not much sense (if the initiator's NAT mapping had changed the 
 responder wouldn't be able to reach it anyway).

  [Other Info]
   
   * I can do general regression check, but for the actual issue 
 verification I lack the apple devices and have to rely on the reporters 
 (fortunately two active on the bug now, and confirmed on the ppa 
 already)

  
  ---

  Original bug asked to backport the full newer release, but given SRU
  policy and that it seems to be fixable with much smaller change we
  decided for a backported patch - keeping original content below:

  ---

  strongSwan is effectively incompatible with iOS 10+ and macOS 10.11+
  devices. Dead peer detection does not work for these devices and they
  continually re-establish security associations (SAs) as a result.
  Please see the issues described in further detail below:

  strongSwan confirmed the issue and patched it in 5.5.1:
  https://wiki.strongswan.org/issues/2126

  strongSwan recommends a workaround that breaks other functionality:
  
https://wiki.strongswan.org/projects/strongswan/wiki/AppleClients#IKEv2-on-iOS-9-and-iOS-10

  Ubuntu 17.04 has packaged strongSwan 5.5.1 which fixes this issue. I
  would recommend an SRU for strongSwan 5.3.5 to 5.5.1 in Ubuntu 16.04.

  [Impact]
  Ubuntu users are running into this bug in normal usage:
  https://github.com/trailofbits/algo/issues/430

  [Test Case]
  In order to test this issue:
  1. Deploy an Ubuntu 16.04 server with strongSwan via Algo 
(https://github.com/trailofbits/algo)
  2. Connect an iOS client
  3. Wait a few minutes for the reconnects to start based on broken dead peer 
detection

  In order to test the fix for this issue:
  1. Deploy an Ubuntu 17.04 server with strongSwan via Algo (modify config.cfg 
to select 17.04)
  2. Connect an iOS client
  3. Wait the same time period as before and notice that the connection does 
not drop

  [Regression Potential]
  strongSwan and IPSEC software in general change at a very slow rate. In our 
tests with Algo, the exact same ipsec.conf and related configuration work for 
strongSwan 5.5.1 that worked for 5.3.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1687711/+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 1641889] Re: The network indicator shows the wrong status

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager-applet -
1.2.6-0ubuntu0.16.04.3

---
network-manager-applet (1.2.6-0ubuntu0.16.04.3) xenial-proposed; urgency=medium

  * debian/patches/git_fix_wrong_status_for_wireless_toggle.patch
* Fix wrong status for wireless toggle (LP: #1641889)

 -- Ken VanDine   Tue, 09 May 2017 09:52:11
-0400

** Changed in: network-manager-applet (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/1641889

Title:
  The network indicator shows the wrong status

Status in Network Manager Applet:
  Unknown
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project xenial series:
  New
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released

Bug description:
  [Summary] The network indicator shows the wrong status

  [Reproduce Steps]
  1.Boot into Ubuntu OS , disconnect wireless connection
  Note : the issue can't be reproduced with wifi connected
  2.Enable/disable wifi function by pressing hotkey then check network manager 
status

  [Results]
  Expected: "Enable Wi-Fi" option should be OFF
  Actual:"Enable Wi-Fi" option is ON

  [Additional Information]
  Product Name:Inspiron-7460
  BIOS Version:1.0.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1641889/+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 - 1.3.1-1ubuntu10.10

---
libvirt (1.3.1-1ubuntu10.10) xenial; urgency=medium

  * Fix bad SRU backport to match apparmor structure of libvirt
in Xenial (LP: #1680384)
- drop d/p/ubuntu/apparmor-shutdown.patch as the libvirt code here doesn't
  trigger it.
- drop d/p/ubuntu/apparmor-vfio.patch as xenial still uses profiles from
  debian/apparmor/
- apply content of apparmor-vfio.patch to debian/apparmor/libvirt-qemu
  to fix the actual issue.

libvirt (1.3.1-1ubuntu10.9) xenial; 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   Tue, 16 May
2017 12:38:02 +0200

** Changed in: libvirt (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/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 Released
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 

[Group.of.nepali.translators] [Bug 1607663] Re: vino-server does not autostart on Ubuntu-GNOME

[Launchpad Bug Tracker]

This bug was fixed in the package vino - 3.8.1-0ubuntu9.2

---
vino (3.8.1-0ubuntu9.2) xenial; urgency=medium

  * Add debian/links to symlink the hidden vino autostart .desktop to
/usr/share/applications/ which is needed for the Desktop Sharing feature
in GNOME's Settings app to work. Thanks Florian Apolloner for the bug
report and suggested fix. (LP: #1607663)

 -- Jeremy Bicha   Sat, 01 Oct 2016 22:57:04 -0400

** Changed in: vino (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/1607663

Title:
  vino-server does not autostart on Ubuntu-GNOME

Status in Ubuntu GNOME:
  Fix Committed
Status in vino package in Ubuntu:
  Fix Released
Status in vino source package in Xenial:
  Fix Released

Bug description:
  Impact
  ==
  The Desktop Sharing option in GNOME's Settings apps silently doesn't work.

  Test Case
  =
  On the host computer:
  1. In Ubuntu GNOME, open the Settings app.
  2. Open the Sharing panel.
  3. In the headerbar, turn on Sharing.
  4. Click Screen Sharing. Turn it On. (If it was already On, turn it off then 
On.)

  On the guest computer:
  5. From a different computer connected to the same local network, attempt to 
connect to the host computer.

  For this, you can install Vinagre. Click Connect. Use Protocol: VNC
  and enter the IP address for the test computer in the Host: field.
  Click Connect.

  On the host computer:
  6. You probably need to approve a popup message to allow the remote user to 
connect.

  Regression Potential
  
  This only adds a symlinked NoDisplay=true .desktop to
  /usr/share/applications/

  Other Info
  ==
  The fix for Ubuntu 16.10 is a bit different. There we can just backport the 
systemd service file added to vino 3.22 since gnome-settings-daemon 3.22 
handles sharing services via systemd user services.

  I verified that the extra .service file does not affect the way vino-
  preferences works in Unity 16.10. It's just ignored and manually
  trying to start the service in Unity doesn't work either which is
  fine. For 17.04+ we should look at having Unity use the systemd user
  service too.

  Original Bug Report with Workaround
  ===
  Running gnome-settings-daemon -r --debug shows that it tries to locate 
vino-server.desktop which it cannot find and therefore fails to start. Looking 
at the debian package, a confirmed and working fix for Ubuntu 16.04 is: sudo ln 
-s /etc/xdg/autostart/vino-server.desktop 
/usr/share/applications/vino-server.desktop or only shipping that file in 
/usr/share/application

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1607663/+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 1612392] Re: [sru] Muon: missing dependency on software-properties-kde

[Launchpad Bug Tracker]

This bug was fixed in the package muon - 4:5.6.0-0ubuntu1.16.10.1

---
muon (4:5.6.0-0ubuntu1.16.10.1) yakkety; urgency=medium

  * Add software-properties-kde dependency. (LP: #1612392)

 -- Mattia Rizzolo   Tue, 18 Apr 2017 22:05:20 +0200

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

** Changed in: muon (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/1612392

Title:
  [sru] Muon: missing dependency on software-properties-kde

Status in Muon:
  Fix Released
Status in muon package in Ubuntu:
  Fix Released
Status in muon source package in Xenial:
  Fix Released
Status in muon source package in Yakkety:
  Fix Released
Status in muon source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  It is not possible to edit software sources through Muon because
  software-properties-kde is not installed by default.

  [Test Case]

  * Open Muon.
  * Click the menu Settings -> Configure Software Sources.
  * You are asked for your password, insert it.
  * The window to configure sources opens.

  [Regression Potential]

  * Low, this adds an already existing program which is not installed by 
default.
  * Before the split of plasma-discover, s-p-k was installed because Muon did 
depend on libmuon, which did depend on software-properties-kde.
  * This still assumes that `kdesu` is available.

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

[Billy Olsen]

This patch is for the trusty-mitaka version of swift for the trusty-
mitaka Ubuntu Cloud Archive

** Patch added: "trusty-mitaka patch"
   
https://bugs.launchpad.net/charm-swift-storage/+bug/1683076/+attachment/4882209/+files/lp1683076-trusty-mitaka.debdiff

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

** Changed in: cloud-archive/kilo
   Importance: Undecided => Critical

** Changed in: cloud-archive/mitaka
   Importance: Undecided => Critical

** Changed in: swift (Ubuntu Trusty)
   Importance: Undecided => Critical

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

** Tags added: sts-sru-needed

-- 
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:
  Won't Fix
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/

  [Impact]

   * Stopping rsyslog causes swift daemons to crash due to overflowing
  the call stack when attempting to write an entry to the logging
  subsystem and the attempt to write to /dev/log fails. When rsyslog
  stops, the /dev/log socket is unavailable and results in an exception.
  The swift logging code attempts to log the resultant error, which
  again results in an exception. This continues until the stack is
  overflowed and the swift daemons crash. When the swift daemons crash,
  the object, container and account data are not able to be replicated
  to other storage nodes in the system, which affects the data integrity
  of the data being written to the system.

   * The patch should be backported to stable releases in order to
  ensure that the data integrity of objects, accounts, and containers
  within Swift are not adversely affected due to failed logging
  subsystems.

   * The uploaded patches fix the bug by only attempting to log an entry
  to the logging subsystem if the current call stack does not include an
  attempt to write to the logs. If the current call stack includes an
  attempt to log to the logging subsystem, the log message is dropped
  avoiding the recursion.

  [Test Case]

   * Install swift storage cluster
   * Log into one of the swift storage nodes
   * Ensure the swift-{object,account,container}-replicator processes are 
running
   * Stop the rsyslog service
   * Wait a minute
   * Observe the swift-{object,account,container}-replicator processes are no 
longer running

  [Regression Potential]

   * This affects the logging capabilities provided by the Swift code.
  Possible regressions could occur in almost any subsystem, since the
  logging is universal throughout the code base and could result in lost
  log entries in the best regression scenario and possible crashing of
  swift daemons in the worst case scenario. The regression potential is
  mitigated by the fact that this patch has already been included
  upstream for over a year now and no regressions have been reported
  against this code since.

  [Other Info]

   * /dev/log is not provided by the rsyslog daemon in Xenial, but this
  patch still applies in that any persistent exception encountered when
  writing to /dev/log will cause the call stack to overflow and crash
  the swift daemons.

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 1686514] Re: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.9-144-g2825a917-0ubuntu1

---
cloud-init (0.7.9-144-g2825a917-0ubuntu1) artful; urgency=medium

  * New upstream snapshot.
- flake8: move the pinned version of flake8 up to 3.3.0
- tests: Apply workaround for snapd bug in test case. [Joshua Powers]
- RHEL/CentOS: Fix dual stack IPv4/IPv6 configuration. [Andreas Karis]
  (LP: #1679817, #1685534, #1685532)
- disk_setup: fix several issues with gpt disk partitions. (LP: #1692087)
- function spelling & docstring update [Joshua Powers]
- Fixing wrong file name regression. [Joshua Powers]
- tox: move pylint target to 1.7.1
- Fix get_interfaces_by_mac for empty macs (LP: #1692028)
- DigitalOcean: remove routes except for the public interface.
  [Ben Howard] (LP: #1681531.)
- netplan: pass macaddress, when specified, for vlans
  [Dimitri John Ledkov] (LP: #1690388)
- doc: various improvements for the docs on cc_users_groups.
  [Felix Dreissig]
- cc_ntp: write template before installing and add service restart
  [Ryan Harper] (LP: #1645644)
- cloudstack: fix tests to avoid accessing /var/lib/NetworkManager
  [Lars Kellogg-Stedman]
- tests: fix hardcoded path to mkfs.ext4 [Joshua Powers] (LP: #1691517)
- Actually skip warnings when .skip file is present. [Chris Brinker]
  (LP: #1691551)
- netplan: fix netplan render_network_state signature.
  [Dimitri John Ledkov] (LP: #1685944)
- Azure: fix reformatting of ephemeral disks on resize to large types.
  (LP: #1686514)
- Revert "tools/net-convert: fix argument order for render_network_state"
- make deb: Add devscripts dependency for make deb. Cleanup packages/bddeb.
  [Chad Smith] (LP: #1685935)
- tools/net-convert: fix argument order for render_network_state
  [Ryan Harper] (LP: #1685944)
- openstack: fix log message copy/paste typo in _get_url_settings
  [Lars Kellogg-Stedman]
- unittests: fix unittests run on centos [Joshua Powers]
- Improve detection of snappy to include os-release and kernel cmdline.
  (LP: #1689944)
- Add address to config entry generated by _klibc_to_config_entry.
  [Julien Castets] (LP: #1691135)
- sysconfig: Raise ValueError when multiple default gateways are present.
  [Chad Smith] (LP: #1687485)
- FreeBSD: improvements and fixes for use on Azure
  [Hongjiang Zhang] (LP: #1636345)
- Add unit tests for ds-identify, fix Ec2 bug found.
- fs_setup: if cmd is specified, use shell interpretation.
  [Paul Meyer] (LP: #1687712)
- doc: document network configuration defaults policy and formats.
  [Ryan Harper]
- Fix name of "uri" key in docs for "cc_apt_configure" module
  [Felix Dreissig]
- tests: Enable artful [Joshua Powers]

 -- Scott Moser   Tue, 23 May 2017 17:04:40 -0400

** Changed in: cloud-init (Ubuntu Artful)
   Status: In Progress => Fix Released

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

Title:
  Azure: cloud-init does not handle reformatting GPT partition ephemeral
  disks

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

Bug description:
  Some Azure instances such as L32 or G5 have very large ephemeral disks
  which are partitioned via GPT vs. smaller ephemeral disks that have
  dos disklabels.

  At first boot of an instance the ephemeral disk is prepared and
  formatted properly. But if the instance is deallocated and then
  reallocated (thus receiving a new ephemeral disk) then cloud-init does
  not handle reformatting GPT partition ephemeral disks properly.
  Therefore /mnt is never mounted again.

  Test cases:
   1. Deploy an L32(s) VM on Azure
   2. Log in and ensure that the ephemeral disk is formatted and mounted to /mnt
   3. Via the portal you can "Redeploy" the VM to a new Azure Host (or 
alternatively stop and deallocate the VM for some time, and then 
restart/reallocate the VM).

  Expected Results:
   - After reallocation we expect the ephemeral disk to be formatted and 
mounted to /mnt.

  Actual Results:
   - After reallocation /mnt is not mounted and there are errors in the 
cloud-init log.

  *This was tested on Ubuntu 16.04 - but may affect other releases.

  Note: This bug a regression from previous cloud-init releases. GPT
  support for Azure ephemeral disk handling was added to cloud-init via
  this bug: https://bugs.launchpad.net/ubuntu/+source/cloud-
  init/+bug/1422919.

  Related bugs:
   * bug 1691489: fstab entries written by 

[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 cloud-init -
0.7.9-144-g2825a917-0ubuntu1

---
cloud-init (0.7.9-144-g2825a917-0ubuntu1) artful; urgency=medium

  * New upstream snapshot.
- flake8: move the pinned version of flake8 up to 3.3.0
- tests: Apply workaround for snapd bug in test case. [Joshua Powers]
- RHEL/CentOS: Fix dual stack IPv4/IPv6 configuration. [Andreas Karis]
  (LP: #1679817, #1685534, #1685532)
- disk_setup: fix several issues with gpt disk partitions. (LP: #1692087)
- function spelling & docstring update [Joshua Powers]
- Fixing wrong file name regression. [Joshua Powers]
- tox: move pylint target to 1.7.1
- Fix get_interfaces_by_mac for empty macs (LP: #1692028)
- DigitalOcean: remove routes except for the public interface.
  [Ben Howard] (LP: #1681531.)
- netplan: pass macaddress, when specified, for vlans
  [Dimitri John Ledkov] (LP: #1690388)
- doc: various improvements for the docs on cc_users_groups.
  [Felix Dreissig]
- cc_ntp: write template before installing and add service restart
  [Ryan Harper] (LP: #1645644)
- cloudstack: fix tests to avoid accessing /var/lib/NetworkManager
  [Lars Kellogg-Stedman]
- tests: fix hardcoded path to mkfs.ext4 [Joshua Powers] (LP: #1691517)
- Actually skip warnings when .skip file is present. [Chris Brinker]
  (LP: #1691551)
- netplan: fix netplan render_network_state signature.
  [Dimitri John Ledkov] (LP: #1685944)
- Azure: fix reformatting of ephemeral disks on resize to large types.
  (LP: #1686514)
- Revert "tools/net-convert: fix argument order for render_network_state"
- make deb: Add devscripts dependency for make deb. Cleanup packages/bddeb.
  [Chad Smith] (LP: #1685935)
- tools/net-convert: fix argument order for render_network_state
  [Ryan Harper] (LP: #1685944)
- openstack: fix log message copy/paste typo in _get_url_settings
  [Lars Kellogg-Stedman]
- unittests: fix unittests run on centos [Joshua Powers]
- Improve detection of snappy to include os-release and kernel cmdline.
  (LP: #1689944)
- Add address to config entry generated by _klibc_to_config_entry.
  [Julien Castets] (LP: #1691135)
- sysconfig: Raise ValueError when multiple default gateways are present.
  [Chad Smith] (LP: #1687485)
- FreeBSD: improvements and fixes for use on Azure
  [Hongjiang Zhang] (LP: #1636345)
- Add unit tests for ds-identify, fix Ec2 bug found.
- fs_setup: if cmd is specified, use shell interpretation.
  [Paul Meyer] (LP: #1687712)
- doc: document network configuration defaults policy and formats.
  [Ryan Harper]
- Fix name of "uri" key in docs for "cc_apt_configure" module
  [Felix Dreissig]
- tests: Enable artful [Joshua Powers]

 -- Scott Moser   Tue, 23 May 2017 17:04:40 -0400

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/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:
  Fix Released
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:
  [Impact]
  Virtual devices such as VLANs, bridges and bonds may require the user to set 
a specific MAC address for proper operation on networks; where the same MAC may 
be used by default by the systems due to the methods used to create them.

  [Test case]
  /!\ This only works with the networkd renderer; NetworkManager does not 
currently support setting a MAC on bonds and bridges.

  1) Set a MAC address for a virtual device (bond, bridge or vlan),
  using the following syntax in netplan config:

  macaddress: ##:##:##:##:##:##

  2) Validate that the device gets the MAC address applied.

  [Regression potential]
  Failure to bring up a device configured in netplan or to set the MAC should 
be looked at as a possible regression. Other issues could include failure to 
write the configuration for networkd or NetworkManager.

  

  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 

[Group.of.nepali.translators] [Bug 1691551] Re: warnings are still printed after user touches file

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.9-144-g2825a917-0ubuntu1

---
cloud-init (0.7.9-144-g2825a917-0ubuntu1) artful; urgency=medium

  * New upstream snapshot.
- flake8: move the pinned version of flake8 up to 3.3.0
- tests: Apply workaround for snapd bug in test case. [Joshua Powers]
- RHEL/CentOS: Fix dual stack IPv4/IPv6 configuration. [Andreas Karis]
  (LP: #1679817, #1685534, #1685532)
- disk_setup: fix several issues with gpt disk partitions. (LP: #1692087)
- function spelling & docstring update [Joshua Powers]
- Fixing wrong file name regression. [Joshua Powers]
- tox: move pylint target to 1.7.1
- Fix get_interfaces_by_mac for empty macs (LP: #1692028)
- DigitalOcean: remove routes except for the public interface.
  [Ben Howard] (LP: #1681531.)
- netplan: pass macaddress, when specified, for vlans
  [Dimitri John Ledkov] (LP: #1690388)
- doc: various improvements for the docs on cc_users_groups.
  [Felix Dreissig]
- cc_ntp: write template before installing and add service restart
  [Ryan Harper] (LP: #1645644)
- cloudstack: fix tests to avoid accessing /var/lib/NetworkManager
  [Lars Kellogg-Stedman]
- tests: fix hardcoded path to mkfs.ext4 [Joshua Powers] (LP: #1691517)
- Actually skip warnings when .skip file is present. [Chris Brinker]
  (LP: #1691551)
- netplan: fix netplan render_network_state signature.
  [Dimitri John Ledkov] (LP: #1685944)
- Azure: fix reformatting of ephemeral disks on resize to large types.
  (LP: #1686514)
- Revert "tools/net-convert: fix argument order for render_network_state"
- make deb: Add devscripts dependency for make deb. Cleanup packages/bddeb.
  [Chad Smith] (LP: #1685935)
- tools/net-convert: fix argument order for render_network_state
  [Ryan Harper] (LP: #1685944)
- openstack: fix log message copy/paste typo in _get_url_settings
  [Lars Kellogg-Stedman]
- unittests: fix unittests run on centos [Joshua Powers]
- Improve detection of snappy to include os-release and kernel cmdline.
  (LP: #1689944)
- Add address to config entry generated by _klibc_to_config_entry.
  [Julien Castets] (LP: #1691135)
- sysconfig: Raise ValueError when multiple default gateways are present.
  [Chad Smith] (LP: #1687485)
- FreeBSD: improvements and fixes for use on Azure
  [Hongjiang Zhang] (LP: #1636345)
- Add unit tests for ds-identify, fix Ec2 bug found.
- fs_setup: if cmd is specified, use shell interpretation.
  [Paul Meyer] (LP: #1687712)
- doc: document network configuration defaults policy and formats.
  [Ryan Harper]
- Fix name of "uri" key in docs for "cc_apt_configure" module
  [Felix Dreissig]
- tests: Enable artful [Joshua Powers]

 -- Scott Moser   Tue, 23 May 2017 17:04:40 -0400

** Changed in: cloud-init (Ubuntu Artful)
   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/1691551

Title:
  warnings are still printed after user touches file

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

Bug description:
  When cloud-init shows a warning with Z99-cloudinit-warnings.sh (such
  as on login after a ds-identify error), it suggests that you can:

  Disable the warnings above by:
touch /home/ubuntu/.cloud-warnings.skip
  or
touch /var/lib/cloud/instance/warnings/.skip

  The second file (/var/lib/cloud/) is not honored.

  The easiest recreate is:
  $ name="x1"
  $ lxc launch ubuntu-daily:xenial $name
  $ sleep 10
  $ lxc exec $name -- sh -c 'd=/var/lib/cloud/instance/warnings/; mkdir -p $d; 
echo "WARNING WARNING FOO" > "$d/warn-foo"'

  ## see the warning is there.
  $ lxc exec $name -- bash --login https://bugs.launchpad.net/cloud-init/+bug/1691551/+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 1686679] Re: [SRU] Ubuntu16.04 : autofs takes extreamly long with large number of direct maps

[Nish Aravamudan]

Based upon Christian's analysis, 5.1.2 contains the requested fix and is
present in 17.04+

** Changed in: autofs5 (Ubuntu)
   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/1686679

Title:
  [SRU] Ubuntu16.04 : autofs takes extreamly long with large number of
  direct maps

Status in autofs5 package in Ubuntu:
  Fix Released
Status in autofs5 source package in Xenial:
  New
Status in autofs5 source package in Yakkety:
  New

Bug description:
  [Impact]

  autofs service in xenial takes extremely long time since its creating
  the directory hierarchy for all direct mounts maps, thus it will take
  too long to make all the automount shares available when using autofs
  with large direct mappings, customer is complaining about this point.
  So we need to backport the following upstream patch.

  
https://git.kernel.org/pub/scm/linux/storage/autofs/autofs.git/commit/?id=67e7d613a4b09eeffc57ab44a7acb52027d897b2

  [Test Case]

   * Create an autofs direct mount map with large direct mappings (eg:
  more than 20k)

   * Start autofs service to see if it will take too much time to
  automount all mappings.

  [Regression Potential]

  With this upstream patch, we can avoid creating path compnents on
  remote file system unless that file system is the root file system. so
  theoretically there is no regression potential.

  [Other Info]
   
  Redhat [1] also already backported the following patch, see: 
https://bugzilla.redhat.com/show_bug.cgi?id=1440769

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1686679/+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 1692398] Re: Input error can lead to continuous searches

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Artful)
   Status: Triaged => 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/1692398

Title:
  Input error can lead to continuous searches

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

Bug description:
  [Impact]
  An input error (e.g. a key being continuously pressed) in the gnome-software 
search field can lead to continuous searches being sent via snapd. This is 
beuause there is no limit in this search field.

  [Test Case]
  1. Open GNOME Software
  2. Click search button
  3. Continuously press and release 't'

  Expected result:
  Searches stop after a reasonable time.

  Observed result:
  Searches are continuously generated for each key press.

  [Regression potential]
  Low. The field is now limited to 100 characters and searches stop after this 
limit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1692398/+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 1623094] Re: cloud-init in xenial crashes on "null" vif type in network_data.json

[Scott Moser]

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

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

Title:
  cloud-init in xenial crashes on "null" vif type in network_data.json

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

Bug description:
   Begin SRU Template 
  [Impact]
  Instances of ubuntu launched on Rackspace public cloud would have broken 
networking and WARN messages in /var/log/cloud-init.log.

  With this new cloud-init in place, any vms launched with a config
  drive would not work properly.

  [Test Case]
  Show failure
   * create a vm on rackspace. using image ba8782e1-ec35-4bdc-b8f7-2f28e343094a
     openstack server create --config-drive=1 --key-name=brickies --flavor=2 
--image=ba8782e1-ec35-4bdc-b8f7-2f28e343094a  my-xenial-cfgdrv

   * ssh will fail to system. go to rackspace cloud console, view the
  servers' console and log in as root via password provided.

  Now, to fix:
   * log into system on console
   * get the proposed package:
     echo "deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc)-proposed 
main" | tee /etc/apt/sources.list.d/proposed.list
     apt-get update
     apt-get install cloud-init
 mkdir orig
 mv /var/lib/cloud /var/log/cloud-init* orig
   * reboot

  You should now be able to ssh into the system.

  [Regression Potential]
  Low regression potential, as this is a fix for a regression.
  It could potentially have fallout on other openstack cloud guests, but only 
in cases where there was already failure.
   End SRU Template 

  NOTE: this was originally reported in cpc-rax bug 1621968.  Re-
  reporting here for tracking purposes as requested.  Please see that
  issue for log files and more details.

  In recent versions of cloud-init[1], we've found that when we attach a
  configdrive to a cloud server cloud-init crashes before it has a
  chance to complete its tasks - most critically, generating the SSH
  keys.

  The root of this issue seems to be that cloud-init wants to parse the
  included network config on the configdrive.. Our network config uses a
  "null" vif type, which causes cloud-init to bomb out with an error
  like this:

  Sep 09 14:48:40 shtest2 cloud-init[2910]: ValueError: Unknown
  network_data link type: None

  [1]# dpkg -s cloud-init | grep ^Version
  Version: 0.7.7~bzr1256-0ubuntu1~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1623094/+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 1692900] [NEW] Xenial update to 4.4.69 stable release

[Stefan Bader]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.69 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

The following patches from the 4.4.69 stable release shall be applied:
* xen: adjust early dom0 p2m handling to xen hypervisor behavior
* target: Fix compare_and_write_callback handling for non GOOD status
* target/fileio: Fix zero-length READ and WRITE handling
* target: Convert ACL change queue_depth se_session reference usage
* iscsi-target: Set session_fall_back_to_erl0 when forcing reinstatement
* usb: host: xhci: print correct command ring address
* USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit
* USB: Proper handling of Race Condition when two USB class drivers try to
  call init_usb_class simultaneously
* staging: vt6656: use off stack for in buffer USB transfers.
* staging: vt6656: use off stack for out buffer USB transfers.
* staging: gdm724x: gdm_mux: fix use-after-free on module unload
* staging: comedi: jr3_pci: fix possible null pointer dereference
* staging: comedi: jr3_pci: cope with jiffies wraparound
* usb: misc: add missing continue in switch
* usb: Make sure usb/phy/of gets built-in
* usb: hub: Fix error loop seen after hub communication errors
* usb: hub: Do not attempt to autosuspend disconnected devices
* x86/boot: Fix BSS corruption/overwrite bug in early x86 kernel startup
* selftests/x86/ldt_gdt_32: Work around a glibc sigaction() bug
* x86, pmem: Fix cache flushing for iovec write < 8 bytes
* um: Fix PTRACE_POKEUSER on x86_64
* KVM: x86: fix user triggerable warning in kvm_apic_accept_events()
* KVM: arm/arm64: fix races in kvm_psci_vcpu_on
* block: fix blk_integrity_register to use template's interval_exp if not 0
* crypto: algif_aead - Require setkey before accept(2)
* dm era: save spacemap metadata root after the pre-commit
* vfio/type1: Remove locked page accounting workqueue
* IB/core: Fix sysfs registration error flow
* IB/IPoIB: ibX: failed to create mcg debug file
* IB/mlx4: Fix ib device initialization error flow
* IB/mlx4: Reduce SRIOV multicast cleanup warning message to debug level
* ext4: evict inline data when writing to memory map
* fs/xattr.c: zero out memory copied to userspace in getxattr
* ceph: fix memory leak in __ceph_setxattr()
* fs/block_dev: always invalidate cleancache in invalidate_bdev()
* Set unicode flag on cifs echo request to avoid Mac error
* SMB3: Work around mount failure when using SMB3 dialect to Macs
* CIFS: fix mapping of SFM_SPACE and SFM_PERIOD
* cifs: fix CIFS_IOC_GET_MNT_INFO oops
* CIFS: add misssing SFM mapping for doublequote
* padata: free correct variable
* arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses
* serial: samsung: Use right device for DMA-mapping calls
* serial: omap: fix runtime-pm handling on unbind
* serial: omap: suspend device on probe errors
* tty: pty: Fix ldisc flush after userspace become aware of the data already
* Bluetooth: Fix user channel for 32bit userspace on 64bit kernel
* Bluetooth: hci_bcm: add missing tty-device sanity check
* Bluetooth: hci_intel: add missing tty-device sanity check
* mac80211: pass RX aggregation window size to driver
* mac80211: pass block ack session timeout to to driver
* mac80211: RX BA support for sta max_rx_aggregation_subframes
* wlcore: Pass win_size taken from ieee80211_sta to FW
* wlcore: Add RX_BA_WIN_SIZE_CHANGE_EVENT event
* ipmi: Fix kernel panic at ipmi_ssif_thread()
* Linux 4.4.69

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Assignee: Stefan Bader (smb)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.69 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch 

[Group.of.nepali.translators] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software - 3.24.3-0ubuntu3

---
gnome-software (3.24.3-0ubuntu3) artful; urgency=medium

  * debian/patches/0006-Add-an-APT-plugin.patch:
- Handle multiple debconf connections (LP: #1688721)

 -- Robert Ancell   Tue, 23 May 2017
21:28:12 +1200

** Changed in: gnome-software (Ubuntu Artful)
   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/1688721

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result =
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path

  
  Record on errors.ubuntu.com
  https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f

  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1688721/+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 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Robert Ancell]

** No longer affects: gconf (Ubuntu)

** No longer affects: gconf (Ubuntu Xenial)

** No longer affects: gconf (Ubuntu Yakkety)

** No longer affects: gconf (Ubuntu Zesty)

** No longer affects: gconf (Ubuntu Artful)

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gnome-software package in Ubuntu:
  New
Status in gnome-software source package in Xenial:
  New
Status in gnome-software source package in Yakkety:
  New
Status in gnome-software source package in Zesty:
  New
Status in gnome-software source package in Artful:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result =
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path

  
  Record on errors.ubuntu.com
  https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f

  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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