[Group.of.nepali.translators] [Bug 1581540] Re: Add oprofile support for z13

[Dimitri John Ledkov]

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

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

Title:
  Add oprofile support for z13

Status in Ubuntu on IBM z Systems:
  Triaged
Status in oprofile package in Ubuntu:
  New
Status in oprofile source package in Xenial:
  New

Bug description:
  == Comment: #0 - Aziz Rozyev  - 2016-04-20 11:19:50 ==
  ---Problem Description---
  operf failure, 'strace operf' shows that it tries to get 'cpu_type' from 
/proc/cpuinfo, whereas there is no such field in cpuinfo. 
   
  Contact Information = Aziz Rozyev/aziz.roz...@ru.ibm.com 
   
  ---uname output---
  Linux s35lp26 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:07:12 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = z13 lpar type: 2964 model: 703 N96 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   run 'operf' 
   
  Userspace tool common name: operf 
   
  The userspace tool has the following bit modes: tested on 64bit 

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Aziz Rozyev/aziz.roz...@ru.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #4 - Andreas Arnez  - 2016-05-12 04:52:40 ==
  So far oprofile didn't support z13.  A patch for adding z13 support has now 
been posted upstream:
http://marc.info/?l=oprofile-list=146298177508640=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1581540/+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 1556141] Re: s390/mm: four page table levels vs. fork

[Dimitri John Ledkov]

** Changed in: linux-snapdragon (Ubuntu)
   Status: New => Invalid

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

Title:
  s390/mm: four page table levels vs. fork

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

Bug description:
  == Comment: #0 - Hendrik Brueckner  - 2016-03-11 
08:30:57 ==
  Please backport:

  http://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/commit/?h
  =for-linus=3446c13b268af86391d06611327006b059b8bab1

  s390/mm: four page table levels vs. fork
  The fork of a process with four page table levels is broken since
  git commit 6252d702c5311ce9 "[S390] dynamic page tables."

  All new mm contexts are created with three page table levels and
  an asce limit of 4TB. If the parent has four levels dup_mmap will
  add vmas to the new context which are outside of the asce limit.
  The subsequent call to copy_page_range will walk the three level
  page table structure of the new process with non-zero pgd and pud
  indexes. This leads to memory 

[Group.of.nepali.translators] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

[Treviño]

I've moved the part related to idle backlight reset to bug #1583861

** No longer affects: upower (Ubuntu)

** No longer affects: upower (Ubuntu Xenial)

** No longer affects: upower

** Patch removed: "upower-always-get-kbd-brightness.debdiff"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+attachment/4665009/+files/upower-always-get-kbd-brightness.debdiff

** Patch removed: "0001-Fixed-dell-laptop-keyboard-backlight.patch"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+attachment/4640489/+files/0001-Fixed-dell-laptop-keyboard-backlight.patch

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in unity-settings-daemon source package in Xenial:
  Fix Committed

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+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 1583357] Re: [Hyper-V] Rebase Hyper-V to 4.6 kernel

[Joseph Salisbury]

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

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

Title:
  [Hyper-V] Rebase Hyper-V to 4.6 kernel

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

Bug description:
  Please rebase Hyper-V support to the final v4.6 upstream kernel.

  The following files comprise Hyper-V support in the upstream kernel:
  arch/x86/kernel/cpu/mshyperv.c
  arch/x86/include/asm/mshyperv.h
  arch/x86/include/uapi/asm/hyperv.h
  include/linux/hyperv.h
  drivers/hv/channel.c
  drivers/hv/channel_mgmt.c
  drivers/hv/connection.c
  drivers/hv/hv_balloon.c
  drivers/hv/hv.c
  drivers/hv/hv_fcopy.c
  drivers/hv/hv_kvp.c
  drivers/hv/hv_snapshot.c
  drivers/hv/hv_util.c
  drivers/hv/hv_utils_transport.c
  drivers/hv/hv_utils_transport.h
  drivers/hv/hyperv_vmbus.h
  drivers/hv/ring_buffer.c
  drivers/hv/vmbus_drv.c
  tools/hv/hv_fcopy_daemon.c
  tools/hv/hv_get_dhcp_info.sh
  tools/hv/hv_get_dns_info.sh
  tools/hv/hv_kvp_daemon.c
  tools/hv/hv_set_ifconfig.sh
  tools/hv/hv_vss_daemon.c
  tools/hv/lsvmbus
  drivers/input/serio/hyperv-keyboard.c
  drivers/net/hyperv/hyperv_net.h
  drivers/net/hyperv/netvsc.c
  drivers/net/hyperv/netvsc_drv.c
  drivers/net/hyperv/rndis_filter.c
  drivers/scsi/storvsc_drv.c
  drivers/hid/hid-hyperv.c
  drivers/pci/host/pci-hyperv.c
  drivers/video/fbdev/hyperv_fb.c

  While I know a number of post-4.4 commits are already committed, I am
  including all of the commits from 4.4 to 4.6 for reference:

  mshyperv.c : commit 1e2ae9ec072f3b7887f456426bc2cf23b80f661a : 
x86/hyperv: Avoid reporting bogus NMI status for Gen2 instances
  mshyperv.c : commit 1b74dde7c47c19a73ea3e9fac95ac27b5d3d50c5 : x86/cpu: 
Convert printk(KERN_ ...) to pr_(...)
  hyperv.h : commit 45870a441361d1c05a5f767c4ece2f6e30e0da9c : Drivers: hv: 
ring_buffer: remove stray smp_read_barrier_depends()
  hyperv.h : commit e8d6ca023efce3bd80050dcd9e708ee3cf8babd4 : Drivers: hv: 
vmbus: define the new offer type for Hyper-V socket (hvsock)
  hyperv.h : commit 5c23a1a5c60b0f472cfa61cd7d8279f8aaeb5b64 : Drivers: hv: 
vmbus: define a new VMBus message type for hvsock
  hyperv.h : commit 499e8401a515d04daa986b995da710d2b9737764 : Drivers: hv: 
vmbus: add a per-channel rescind callback
  hyperv.h : commit 3c75354d043ad546148d6992e40033ecaefc5ea5 : Drivers: hv: 
vmbus: add a helper function to set a channel's pending send size
  hyperv.h : commit 8981da320a11217589aa3c50f9e891bcdef07ece : Drivers: hv: 
vmbus: add a hvsock flag in struct hv_driver
  hyperv.h : commit b9830d120cbe155863399f25eaef6aa8353e767f : Drivers: hv: 
util: Pass the channel information during the init call
  channel.c : commit 63d55b2aeb5e4faa170316fee73c3c47ea9268c7 : Drivers: 
hv: vmbus: serialize process_chn_event() and vmbus_close_internal()
  channel.c : commit 5c23a1a5c60b0f472cfa61cd7d8279f8aaeb5b64 : Drivers: 
hv: vmbus: define a new VMBus message type for hvsock
  channel.c : commit fe760e4d64fe5c17c39e86c410d41f6587ee88bc : Drivers: 
hv: vmbus: Give control over how the ring access is serialized
  channel.c : commit 8599846d73997cdbccf63f23394d871cfad1e5e6 : Drivers: 
hv: vmbus: Fix a Host signaling bug
  channel_mgmt.c : commit fe760e4d64fe5c17c39e86c410d41f6587ee88bc : 
Drivers: hv: vmbus: Give control over how the ring access is serialized
  channel_mgmt.c : commit 79fd8e706637a5c7c41f9498fe0fbfb437abfdc8 : 
Drivers: hv: vmbus: avoid infinite loop in init_vp_index()
  channel_mgmt.c : commit 75ff3a8a9168df750b5bd0589e897a6c0517a9f1 : 
Drivers: hv: vmbus: avoid wait_for_completion() on crash
  channel_mgmt.c : commit 5c23a1a5c60b0f472cfa61cd7d8279f8aaeb5b64 : 
Drivers: hv: vmbus: define a new VMBus message type for hvsock
  connection.c : commit d6f591e339d23f434efda11917da511870891472 : Drivers: 
hv: vmbus: channge vmbus_connection.channel_lock to mutex
  connection.c : commit 75ff3a8a9168df750b5bd0589e897a6c0517a9f1 : Drivers: 
hv: vmbus: avoid wait_for_completion() on crash
  connection.c : commit 1b807e1011af46a595ba46c75ad5e20ad7177af7 : Drivers: 
hv: vmbus: Cleanup vmbus_set_event()
  hv.c : commit a108393dbf764efb2405f21ca759806c65b8bc16 : drivers:hv: 
Export the API to invoke a hypercall on Hyper-V
  hv.c : commit c35b82ef0294ae5052120615f5cfcef17c5a6bf7 : drivers/hv: 
correct tsc page sequence invalid value
  hv.c : commit 9220e39b5c900c67ddcb517d52fe52d90fb5e3c8 : Drivers: hv: 
vmbus: fix build warning
  hv.c : commit d81274aae61c0a045cd0f34191c51fa64ba58bc4 : Drivers: hv: 
vmbus: Support handling messages on multiple CPUs
  hv.c : commit 3ccb4fd8f492f99aece21acc1bd6142275f26236 : Drivers: hv: 
vmbus: don't manipulate with 

[Group.of.nepali.translators] [Bug 1573188] Re: unity7 interface doesn't cover indicators or notifications

[Brian Murray]

Hello Kyle, or anyone else affected,

Accepted snapd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/snapd/2.0.5 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-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/1573188

Title:
  unity7 interface doesn't cover indicators or notifications

Status in Snappy:
  In Progress
Status in snapd package in Ubuntu:
  Triaged
Status in snapd source package in Xenial:
  Fix Committed

Bug description:
  Using the "unity7" interface, it seems that the access required to
  utilize indicators or display notifications is not granted (note that
  installing with --devmode works).

  To duplicate:

  1) Build/install the Qt systray example snap here:
  https://github.com/kyrofa/qt-example-snaps/tree/master/systray

  2) Install without devmode, e.g. sudo snap install
  systray_1_amd64.snap

  3) Launch from the terminal with the `systray` command.

  4) Click "Show Message".

  5) Note the presence of a launcher icon, the lack of an indicator, and
  a very ugly notification, like this: http://pasteboard.co/nF8fKsP.png

  6) Uninstall the snap: sudo snap remove systray

  7) Install the snap with devmode, e.g. sudo snap install --devmode
  systray_1_amd64.snap

  8) Launch from the terminal again.

  9) Click "Show Message".

  10) Note the presence of a launcher icon, the presence of an indicator
  (with a broken icon, but that may be a different issue), and a pretty
  notification, like this: http://pasteboard.co/nFoPlFh.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1573188/+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 1571702] Re: unable to take VM screenshot

[Launchpad Bug Tracker]

This bug was fixed in the package virt-manager - 1:1.3.2-3ubuntu2

---
virt-manager (1:1.3.2-3ubuntu2) yakkety; urgency=medium

  * debian/patches/0001-details-Fix-screenshot-on-F24-rawhide-bz-1297988.patch:
Cherry-pick from upstream. Fix screenshot capture with newer
gdk-pixbuf/pygobject. (LP: #1571702)

 -- Iain Lane   Wed, 18 May 2016 11:08:46
+0100

** Changed in: virt-manager (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  unable to take VM screenshot

Status in virt-manager package in Ubuntu:
  Fix Released
Status in virt-manager source package in Xenial:
  Fix Committed

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  [ Description, reproducer ]

  Start a KVM VM in via virt-manager. In the VM window, click "Virtual
  Machine", then "Take Screenshot" and "Save". It should save a
  screenshot.

  Instead of creating a screenshot, it creates an empty png file and
  virt-manager throws this error:

  Error taking screenshot: argument 1 must be convertible to a buffer,
  not _ResultTuple

  Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/details.py", line 1455, in 
control_vm_screenshot
  return self._take_screenshot()
    File "/usr/share/virt-manager/virtManager/details.py", line 1507, in 
_take_screenshot
  file(filename, "wb").write(ret)
  TypeError: argument 1 must be convertible to a buffer, not _ResultTuple

  [ Fix ]

  Looks like "ret" is now a named tuple. Upstream have a fix to check
  for this and take 'buffer' if so. We cherry-pick this commit.

  [ Development fix ]

  The same.

  [ Regression potential ]

  I'm not sure which part of the stack changed, I can imagine that if
  you run on an older version there might have been problems if you got
  the non-named tuple. But upstream cared for this by making the new
  codepath conditional, so I can't think of any other possibilities.

  virt-manager:
    Installed: 1:1.3.2-3ubuntu1
    Candidate: 1:1.3.2-3ubuntu1
    Version table:
   *** 1:1.3.2-3ubuntu1 500
  500 http://be.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  500 http://be.archive.ubuntu.com/ubuntu xenial/universe i386 Packages
  100 /var/lib/dpkg/status

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virt-manager 1:1.3.2-3ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 18 17:16:49 2016
  InstallationDate: Installed on 2016-04-05 (13 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1571702/+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 1571018] Re: CVE-2015-8845

[Steve Beattie]

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

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

Title:
  CVE-2015-8845

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

[Group.of.nepali.translators] [Bug 1578351] Re: mitaka ksclient fails to connect to v6 keystone

[Launchpad Bug Tracker]

This bug was fixed in the package python-urllib3 -
1.13.1-2ubuntu0.16.04.1

---
python-urllib3 (1.13.1-2ubuntu0.16.04.1) xenial; urgency=medium

  * d/p/06_revert_square_brackets_httplib.patch: Cherry pick revert of
change to behaviour with httplib which breaks IPv6 square bracket
handling (LP: #1578351).

 -- James Page   Tue, 10 May 2016 10:00:32 +0100

** Changed in: python-urllib3 (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/1578351

Title:
  mitaka ksclient fails to connect to v6 keystone

Status in Ubuntu Cloud Archive:
  Fix Committed
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in python-urllib3 package in Ubuntu:
  Fix Released
Status in python-urllib3 source package in Xenial:
  Fix Released
Status in python-urllib3 source package in Yakkety:
  Fix Released
Status in keystone package in Juju Charms Collection:
  Fix Committed

Bug description:
  [Impact]
  urllib3 is not stripping [] from IPv6 URL's, resulting in double square 
brackets which breaks connectivity to targets.

  [Test Case]
  
  Deploy OpenStack with IPv6 preferred; keystone service is unable to self 
configure as extra brackets are inserted to the URL hostname resulting in 
failed connections.

  [Regression Potential]
  Change in behaviour was reverted upstream; regression potential minimal.

  [Original Bug Report]
  2016-05-04 15:02:13 INFO shared-db-relation-changed   File 
"/usr/lib/python2.7/dist-packages/keystoneclient/session.py", line 449, in 
_send_request
  2016-05-04 15:02:13 INFO shared-db-relation-changed raise 
exceptions.ConnectionRefused(msg)
  2016-05-04 15:02:13 INFO shared-db-relation-changed 
keystoneauth1.exceptions.connection.ConnectFailure: Unable to establish 
connection to 
http://[2001:db8:0:1:f816:3eff:fe2d:9445]:35347/v2.0/OS-KSADM/services

  Full traceback is here http://paste.ubuntu.com/16224193/

  This works fine with Liberty

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1578351/+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 1235472] Re: New messages do not show in Empathy

[Launchpad Bug Tracker]

This bug was fixed in the package adium-theme-ubuntu - 0.3.4-0ubuntu1.1

---
adium-theme-ubuntu (0.3.4-0ubuntu1.1) xenial-proposed; urgency=medium

  [ Andrew Shadura ]
  * Update the theme to work with recent Empathy (LP: #1235472).

 -- Ken VanDine   Fri, 06 May 2016 11:39:27
-0400

** Changed in: adium-theme-ubuntu (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/1235472

Title:
  New messages do not show in Empathy

Status in adium-theme-ubuntu package in Ubuntu:
  Fix Released
Status in adium-theme-ubuntu source package in Xenial:
  Fix Released

Bug description:
  I send a message to a friend (using my Google account), close that particular 
chat window, and when I receive a notification on my system stating he or she 
replied, I go back to Empathy and click back on the user's name.
  It opens up the same chat thread, but with his or her comments nowhere to be 
found.

  I can't seem to see what the issue may be :/

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: empathy 3.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  4 17:09:12 2013
  InstallationDate: Installed on 2013-10-04 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Beta amd64 
(20130926)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)


  [Impact]

   * Breaks chat view for the chat history

  [Test Case]

   * Start a chat with a friend and close the window
   * After being notified you received a reply, open the chat window to see the 
reply
   * Verify you see your previous message and the reply

  [Regression Potential]

   * Chat might not be rendered is the worse case, which is the current
  case in 16.04.  So no regression potential.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adium-theme-ubuntu/+bug/1235472/+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 1578821] Re: I'm not able to install galician language in Ubuntu 16.04

[Launchpad Bug Tracker]

This bug was fixed in the package language-selector - 0.165.2

---
language-selector (0.165.2) xenial; urgency=medium

  * language_support_pkgs.py:
Hack to exclude hunspell-gl from the installation candidates
(LP: #1578821).

 -- Gunnar Hjalmarsson   Wed, 11 May 2016 01:44:00
+0200

** Changed in: language-selector (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/1578821

Title:
  I'm not able to install galician language in Ubuntu 16.04

Status in language-selector package in Ubuntu:
  Confirmed
Status in libreoffice-dictionaries package in Ubuntu:
  Confirmed
Status in language-selector source package in Xenial:
  Fix Released
Status in libreoffice-dictionaries package in Debian:
  New

Bug description:
  [Impact]

  Installing the Galician language via Language Support fails. The
  reason is that there is currently two hunspell spellchecking packages
  in the archive:

  * hunspell-gl-es, provided by the hunspell-gl-es source package
  * hunspell-gl, provided by the libreoffice-dictionaries source package

  Even if hunspell-gl-es conflicts to hunspell-gl, having both of them
  available in the archive is not compatible with the way the writing
  aids is pulled via Language Selector. The proposed upload in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/lo-dicts-symlinks

  drops the hunspell-gl binary from libreoffice-dictionaries.

  [Test Case]

   * Open Language Support
   * Try to install Galician

  [Regression Potential]

  Low.

  [Original description]

  Hi

  I just installed Ubuntu 16.04. So as I try to install galician
  language I get this notification:

  Transaction failed: Package dependencies cannot be resolved
   The following packages have unmet dependencies:

  hunspell-gl-es:

  Then nothing happens. Several fellows got the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1578821/+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 1528466] Re: Mellanox ConnectX4 MTU limits: max and min

[Kamal Mostafa]

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

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

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

** No longer affects: linux-lts-wily (Ubuntu Xenial)

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

Title:
  Mellanox ConnectX4 MTU limits: max and min

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-wily package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  
  Max MTU limit should be 9978 

  Tested on Ubuntu 14.04.4 daily build, this issue exist also in 15.10.

  reproduce

  # ifconfig p2p1  mtu 900   
  SIOCSIFMTU: Invalid argument   

  # dmesg

  [62898.559808] mlx5_core :20:00.0 p2p1: mlx5e_change_mtu: Bad MTU 
(900) > (1) Max
  [63058.512668] command failed, status bad parameter(0x3), syndrome 0x648afc

  
  Upstream commit that fix the issue  

  commit 60825c35bf023553f8524f6695f176236e54df97  
  Author: Doron Tsur  
  Date:   Thu Nov 12 19:35:27 2015 +0200   

  net/mlx5e: Max mtu comparison fix
   
  On change mtu the driver compares between hardware queried mtu and
  software requested mtu. We need to compare between software   
  representation of the queried mtu and the requested mtu.  

  Fixes: facc9699f0fe ('net/mlx5e: Fix HW MTU settings')
  Signed-off-by: Doron Tsur    
  Signed-off-by: Saeed Mahameed    
  Signed-off-by: Or Gerlitz  
  Signed-off-by: David S. Miller   


  # cat /etc/os-release
  NAME="Ubuntu"
  VERSION="14.04.3 LTS, Trusty Tahr"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 14.04.3 LTS"
  VERSION_ID="14.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;

  # uname -r
  4.2.0-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528466/+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 1580526] Re: Pull in the amdgpu/radeon code from Linux 4.5.3

[Kamal Mostafa]

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

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

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

Title:
  Pull in the amdgpu/radeon code from Linux 4.5.3

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

Bug description:
  Pull in the amdgpu/radeon code from Linux 4.5.3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580526/+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 1575555] Re: Chrome/Chromium use "Thin" as default font weight

[Launchpad Bug Tracker]

This bug was fixed in the package fonts-noto-cjk -
1:1.004+repack2-1~ubuntu1

---
fonts-noto-cjk (1:1.004+repack2-1~ubuntu1) xenial; urgency=medium

  * No-change backport to 16.04 as SRU to fix display problems in Chromium.
(LP: #157)

 -- Iain Lane   Thu, 05 May 2016 15:28:24
+0100

** Changed in: fonts-noto-cjk (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/157

Title:
  Chrome/Chromium use "Thin" as default font weight

Status in fonts-noto-cjk package in Ubuntu:
  Fix Released
Status in fonts-noto-cjk source package in Xenial:
  Fix Released
Status in fonts-noto-cjk package in Debian:
  Fix Released

Bug description:
  [Impact]

  Chromium and Google Chrome use "Thin" as the default Noto Sans CJK
  font weight, which makes some Chinese and Japanese web pages difficult
  to read, and thus gives a bad user experience.

  The fonts-noto-cjk version in the PPA

  https://launchpad.net/~gunnarhj/+archive/ubuntu/fonts-noto-cjk

  installs 7 weight specific font files instead of a single "super"
  file. This works around the Chromium/Chrome issue.

  Note: It has been fixed in yakkety via autosync, so "backporting"
  yakkety (as an SRU) instead of uploading from the PPA is an option.

  [Test Case]

  To reproduce the bug:

  * Install Chromium or Google Chrome.
  * Go to  and notice the very thin characters.
  * Install fonts-noto-cjk from the PPA and notice the difference.

  [Regression Potential]

  This is about another font packaging form, without any change in glyph
  coverage, so the the regression risk should be low.

  [Original description]

  The package seems to only "thin" variant of the font, which makes it
  very unreadable in applications such as Chrome (when it has to fall
  back on Chinese fonts on a mostly-English page). I had to remove the
  package and then manually download the font from Google website and
  install it to make the regular weight available

  Release: 16.04 LTS
  Package Version: 1.004+repack1-1
  Expected: All weights of the noto cjk font to be installed
  Happened: Only the "thin" weight of the font seems to be installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/157/+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 1574801] Re: zfs posix default permissions lost on reboot or unmount

[Tim Gardner]

** Changed in: linux (Ubuntu Yakkety)
   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/1574801

Title:
  zfs posix default permissions lost on reboot or unmount

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

Bug description:
  [SRU Justification][XENIAL]
  Commit 4967a3e introduced a typo that caused the ZPL to store the
  intended default ACL as an access ACL. Due to caching this problem
  may not become visible until the filesystem is remounted or the inode
  is evicted from the cache. 

  [FIX]
  
https://github.com/zfsonlinux/zfs/commit/98f03691a4c08f38ca4538c468e9523f8e6b24be

  [TESTCASE]
  from https://github.com/zfsonlinux/zfs/issues/4520:

  [root@localhost ~]# cd /mnt/data/
  [root@localhost data]# mkdir test_dir
  [root@localhost data]# setfacl -R --mask -m u:uadm:rwX test_dir/
  [root@localhost data]# setfacl -R -d --mask -m u:uadm:rwX test_dir/
  [root@localhost data]# getfacl test_dir/
  # file: test_dir/
  # owner: root
  # group: root
  user::rwx
  user:uadm:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:uadm:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  [root@localhost data]# reboot

  After a reboot without the fix one gets the following ACLs:

  [root@localhost ~]# cd /mnt/data/
  [root@localhost data]# getfacl test_dir/
  # file: test_dir/
  # owner: root
  # group: root
  user::rwx
  user:uadm:rwx
  group::r-x
  mask::rwx
  other::r-x

  With the fix:

  [root@localhost data]# getfacl test_dir/
  # file: test_dir/
  # owner: root
  # group: root
  user::rwx
  user:uadm:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:uadm:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  [REGRESSION POTENTAL]
  Minimal ZFS only and touches just acl setting. This corrects just the 
ACL_TYPE_DEFAULT case for the ACL setting for ZFS, and sets it to the *correct* 
name. It is a trivial one line fix.

  --

  Ubuntu 16.04 server

  Problem: Posix default permissions on zfs datasets are lost after
  rebooting the server or unmounting/remount.

  See here for details and fix:
  https://github.com/zfsonlinux/zfs/issues/4520

  ---
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Apr 24 22:44 seq
   crw-rw+ 1 root audio 116, 33 Apr 24 22:44 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 07/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B-X series
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6702:bd07/23/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnP8B-Xseries:rvr:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Group.of.nepali.translators] [Bug 1575014] Re: /etc/X11/Xsession.d/65snappy cause XRDP error

[jklasdf]

This also prevents KDE from starting correctly:
http://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1576500

** Also affects: plasma-desktop (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  /etc/X11/Xsession.d/65snappy cause XRDP error

Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  In Progress
Status in plasma-desktop source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Triaged

Bug description:
  This is different issue with XRDP connection error to GNOME3 Unity.
  This will affect XRDP connection to LXDE, Xfce and MATE Desktop.

  $ sudo apt-get install -y xubuntu-desktop
  $ echo "xfce4-session" > ~/.xsession
  $ sudo reboot
  # RDP connect after boot and then cause error.

  /etc/X11/Xsession.d/65snappy always add /var/lib/snapd/desktop to
  XDG_DATA_DIRS however /var/lib/snapd/desktop is not exists.

  If starting Xsession by XRDP with correct XDG_DATA_DIRS,
  e.g. /usr/share/xfce4, XDRP will work.

  But if starting Xsession with empty XDG_DATA_DIRS, Xsession by XRDP
  will use incorrect XDG_DATA_DIRS and cause crash or unavailable
  desktop item.

  XRDP on ubuntu 15.10 will work with empty XDG_DATA_DIRS.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: snapd 2.0.2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue Apr 26 16:35:01 2016
  InstallationDate: Installed on 2016-04-24 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.X11.Xsession.d.65snappy: [modified]
  mtime.conffile..etc.X11.Xsession.d.65snappy: 2016-04-26T16:23:37.137298

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1575014/+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 1579766] Re: sbsigntool: add kernel signing command (sign-file)

[Andy Whitcroft]

Validated on trusty.

** Also affects: sbsigntool (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Changed in: sbsigntool (Ubuntu Wily)
   Status: New => Fix Committed

** Changed in: sbsigntool (Ubuntu Precise)
   Status: New => Won't Fix

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

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

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

** Changed in: sbsigntool (Ubuntu Xenial)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: sbsigntool (Ubuntu Wily)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: sbsigntool (Ubuntu Trusty)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Tags added: verification-done-trusty

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

Title:
  sbsigntool: add kernel signing command (sign-file)

Status in sbsigntool package in Ubuntu:
  Fix Released
Status in sbsigntool source package in Precise:
  Won't Fix
Status in sbsigntool source package in Trusty:
  Fix Committed
Status in sbsigntool source package in Wily:
  Fix Committed
Status in sbsigntool source package in Xenial:
  Fix Committed
Status in sbsigntool source package in Yakkety:
  Fix Released

Bug description:
  We need launchpad to have access to the kernel module signing command
  (sign-file).  Add this to the sbsigntool package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sbsigntool/+bug/1579766/+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 1583085] Re: [SRU] New stable micro release

[Michael Vogt]

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

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

Title:
  [SRU] New stable micro release

Status in snapd package in Ubuntu:
  New
Status in snapd source package in Xenial:
  New

Bug description:
  The snappy team released a new 2.0.5 micro release that we want SRU
  into xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1583085/+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 1572941] Re: s390-dasd module does not perform with preseed file

[Launchpad Bug Tracker]

This bug was fixed in the package s390-dasd - 0.0.36ubuntu2

---
s390-dasd (0.0.36ubuntu2) yakkety; urgency=medium

  * Inproduce preseed step in the state machine, based on s390-zfcp
implementation. LP: #1572941
  * Add s390-dasd/dasd key to preseed dasd drives to be activated, using
this key also enables auto_format if it wasn't explicitely specified.
  * Add s390-dasd/auto_format and s390-dasd/force_format preseed only keys
to dasdfmt devices when needed and always.
  * Use chzdev to activate devices and block until they are ready to be
used, otherwise dasdfmt fails.
  * Add more error messages when opening and reading geometry of the
device, prior to dasdfmt.
  * Fix di_snprintfcat compiler warning.

 -- Dimitri John Ledkov   Wed, 18 May 2016 12:46:15
+0100

** Changed in: s390-dasd (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/1572941

Title:
  s390-dasd module does not perform with preseed file

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  In Progress
Status in installation-guide package in Ubuntu:
  Confirmed
Status in s390-dasd package in Ubuntu:
  Fix Released
Status in installation-guide source package in Xenial:
  New
Status in s390-dasd source package in Xenial:
  Confirmed

Bug description:
  [Impact]

   * Enable preseeding activation of dasd drives, and formating them
  with dasdfmt. Otherwise, unattended installation cannot be preseeded.

  [Test Case]

   * perform unattanded installation onto dasd drives:
   - single, unformatted
   - single, formatted
   - single, formatted, force reformat
   - multiple dasd drives

  [Regression Potential]

   * Interractive code path is unchanged, when no keys are preseeded.
  Code follows closely s390-zfcp preseed logic.

  [Other Info]
   
   * New preseed keys:

  d-i s390-dasd/dasd string 0.0.0200,0.0.0201
  d-i s390-dasd/auto_format boolean false
  (true, if dasd key used above)
  d-i s390-dasd/force_format boolean false

  
  == Comment: #1 - Ekaterina Teplova  - 2016-04-20 05:41:13 ==
  Installer version 20101020ubuntu431
  Started installation with preseed file. Installation stops at formatting step 
(s390-dasd preseed statement).

  Attaching syslog and hardware-summary.

  Could you please document in Release Notes the following restriction
  for Ubuntu16.04:

  "It is currently not possible to perform a fully unattended
  installation on DASD devices."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1572941/+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 1576780] Re: Needs to implement the full DEP-11 icon spec for compatibility with 3rd-party repos

[Iain Lane]

** Also affects: appstream-glib (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Needs to implement the full DEP-11 icon spec for compatibility with
  3rd-party repos

Status in appstream-glib package in Ubuntu:
  Fix Released
Status in appstream-glib source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * The AppStream YAML spec describes a way to include width/height properties 
in cached-icon metadata, which isn't forward-compatible to the old spec.
   * asglib doesn't implement the full spec in the release present in Xenial, 
so it ignores cached icons with size info, as well as it doesn't support 
several features present in the spec, e.g. the remote icon type.
   * This leads to AppStream components from 3rd-party repos/PPAs not showing 
up in GNOME Software, since asglib is unable to find icons if they use a more 
recent version of the spec.
   * The attched patch fixes this.

  [Test Case 1]

   * Close all instances of GNOME Software (also the background daemon!)
   * Launch GNOME Software again: All apps should be present, you should notice 
no change.

  [Test Case 2]

   * Close all instances of GNOME Software (also the background daemon!)
   * Get new-style metadata, e.g. from Elementary or Debian[1], or simply add 
the SIL repo which is shipping that metadata now: http://packages.sil.org/ 
(that would be the easiest way to test)
   * Launch GNOME Software again: All apps should be present, including the 
3rd-party ones (search for "FieldWorks").

  [1]: ftp://ftp.debian.org/debian/dists/stretch/main/dep11/

  [Regression Potential]

   * This is adding a missing feature, restoring compatibility with 3rd-
  party repos. The existing data should be parsed as before, so I don't
  see much regression potential ("Test Case 1" needs to work)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/hughsie/appstream-glib/commit/628e3cfb1c62c3177d6decd86102217f2546e0a2
   * The fix is also present in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1576780/+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 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen

[Ara Pulido]

** No longer affects: oem-priority/trusty

** Changed in: oem-priority
   Status: Incomplete => Invalid

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

Title:
  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen

Status in OEM Priority Project:
  Invalid
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Incomplete
Status in Unity 7.2 series:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete
Status in unity source package in Xenial:
  Incomplete

Bug description:

  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen, Installed 14.04, still have same
  issue.

  Quickly tapped dash home more than three times by touch screen.Found
  touch screen and touchpad lost click function.

  Note:
  1.When this issue occured, cursor still can be moved by touch screen/touchpad.
  2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.

  Steps to Reproduce:
  1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
  2.Quickly tapped dash home more than three times by touch screen.
  3.Found touch screen and touchpad lost click function.

  This bug is reported from private OEM project, also check
  https://launchpad.net/bugs/1297067

  ==

  using xinput --query-state can actually see the button press event

  ⎡ Virtual core pointer id=2   [master pointer (3)]
  ⎜ ↳ Virtual core XTEST pointer id=4   [slave pointer (2)]
  ⎜ ↳ syntp id=6[slave pointer (2)]
  ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)]

  #xinput --query-state 11
  2 classes :
  ButtonClass
   button[1]=up
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
  ValuatorClass Mode=Absolute Proximity=In
   valuator[0]=398
   valuator[1]=1652
   valuator[2]=5
   valuator[3]=3
   valuator[4]=0
   valuator[5]=399
   valuator[6]=1653

  #xinput --query-state 6
  2 classes :
  ButtonClass
   button[1]=down
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
   button[6]=up
   button[7]=up
   button[8]=up
  ValuatorClass Mode=Relative Proximity=In
   valuator[0]=1
   valuator[1]=394

  touchpad's button and touchpanel's
  valuator[2] and valuator[3] will changed after we press the button (or 
monitor)

  Also I found press "super" on keyboard will recover the
  touchscreen/touchpad loss.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.20.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Apr 21 16:50:04 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-daan2-precise-amd64-20140416-1
  InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf 
in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 
20140416-06:52
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1310518/+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 1286878] Re: Doesn't scale well on a hidpi display

[Ara Pulido]

** Changed in: oem-priority
   Status: New => Fix Released

** No longer affects: oem-priority/trusty

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

Title:
  Doesn't scale well on a hidpi display

Status in OEM Priority Project:
  Fix Released
Status in unity-greeter package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-greeter source package in Xenial:
  Triaged
Status in unity-settings-daemon source package in Xenial:
  Fix Released

Bug description:
  unity-greeter does not scale on hidpi diplays like the rest of unity
  does in trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1286878/+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 1576333] Re: runs to early, causes dependency loops

[Launchpad Bug Tracker]

This bug was fixed in the package pollinate - 4.18-0ubuntu2

---
pollinate (4.18-0ubuntu2) yakkety; urgency=medium

  * debian/pollinate.service: Move installation from network.target to
multi-user.target. network.target is too early and causes dependency loops
with e. g. NFS. (LP: #1576333)
  * debian/pollinate.preinst: Clean up old enablement symlink on upgrade. This
needs to be kept until after 18.04 LTS.

 -- Martin Pitt   Thu, 19 May 2016 09:40:15
+0200

** Changed in: pollinate (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/1576333

Title:
  runs to early, causes dependency loops

Status in pollinate package in Ubuntu:
  Fix Released
Status in pollinate source package in Xenial:
  In Progress
Status in pollinate source package in Yakkety:
  Fix Released

Bug description:
  The first half of the original bug report got fixed in bug 1578833,
  but pollinate still runs to early.

  SRU INFORMATION
  ===
  Impact: Causes service failures during boot when using NFS mounts, regression 
from bug 1578833
  Reproducer:
   - sudo apt-get install -y nfs-common pollinate
   - echo "1.2.3.4:/foo /mnt nfs defaults,nofail 0 0" | sudo tee -a /etc/fstab
     (This will start network-online.target during early boot)
   - sudo reboot
   - Confirm that "sudo journalctl -b -p warning" shows a dependency loop, and 
most probably "systemctl status network-online.target" is not running.
   - Upgrade to the proposed pollinate update, reboot.
   - Confirm that there is no dependency loop any more and "systemctl status 
network-online.target" is active.
   - Confirm that "systemctl status pollinate" is "enabled" (it will have 
"start: condition failed", but that is intended).
   - Confirm that /etc/systemd/system/network.target.wants/pollinate.service 
does not exist any more.

  Regression potential: Low. This merely changes when pollinate.service
  gets activated, and network.target is too early (nothing should
  actually be started by network.target, this is mostly meant for
  shutdown). The main thing that can go wrong is that the upgrade still
  leaves the old
  /etc/systemd/system/network.target.wants/pollinate.service symlink
  behind (the maintainer scripts have to clean that up).

  Original bug report:

  pollinate runs too early on some of the instances i launch.  Basically
  nothing guarantees that it will have network access when it attempts
  to run.

  failure looks something like:
  $ lxc launch xenial x1
  $ sleep 4
  $ lxc exec x1 systemctl status pollinate
  ● pollinate.service - Seed the pseudo random number generator on first boot
     Loaded: loaded (/lib/systemd/system/pollinate.service; enabled; vendor 
preset: enabled)
     Active: inactive (dead) since Thu 2016-04-28 17:16:03 UTC; 1min 17s ago
    Process: 86 ExecStart=/usr/bin/pollinate (code=exited, status=0/SUCCESS)
   Main PID: 86 (code=exited, status=0/SUCCESS)

  Apr 28 17:16:03 ubuntu systemd[1]: Starting Seed the pseudo random number 
generator on first boot...
  Apr 28 17:16:03 ubuntu pollinate[106]: client sent challenge to 
[https://entropy.ubuntu.com/]
  Apr 28 17:16:03 ubuntu pollinate[86]: <13>Apr 28 17:16:03 pollinate[86]: 
client sent challenge to [https://entropy.ubuntu.com/]
  Apr 28 17:16:03 ubuntu pollinate[149]: [432B blob data]
  Apr 28 17:16:03 ubuntu pollinate[86]: Apr 28 17:16:03 ubuntu <13>Apr 28 
17:16:03 pollinate[86]: WARNING: Network communication failed [0]\n  % Total
% Received % Xferd  Average Speed   TimeTime Time  Current
  Apr 28 17:16:03 ubuntu pollinate[86]:  Dload  
Upload   Total   SpentLeft  Speed
  Apr 28 17:16:03 ubuntu pollinate[86]: [139B blob data]
  Apr 28 17:16:03 ubuntu pollinate[86]: 17:16:03.859980 * Closing connection 0
  Apr 28 17:16:03 ubuntu pollinate[86]: curl: (6) Could not resolve host: 
entropy.ubuntu.com
  Apr 28 17:16:03 ubuntu systemd[1]: Started Seed the pseudo random number 
generator on first boot.

  This seems like it might work:
  # diff -u /lib/systemd/system/pollinate.service.dist  
/lib/systemd/system/pollinate.service
  --- /lib/systemd/system/pollinate.service.dist2016-04-28 
17:19:10.807971336 +
  +++ /lib/systemd/system/pollinate.service 2016-04-28 17:19:17.839874541 
+
  @@ -2,6 +2,7 @@
   Description=Seed the pseudo random number generator on first boot
   DefaultDependencies=no
   After=sysinit.target
  +After=network.target
   Before=ssh.service

   [Service]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pollinate 4.15-0ubuntu1 [modified: usr/bin/pollinate]
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu 

[Group.of.nepali.translators] [Bug 1580674] Re: [SRU] mitaka point releases

[James Page]

Martin

All of the OpenStack packaged used to be covered by an explicit MRE so
we've not done explicit test plans for a long time; they will be run
through the regression test suite we've had in place for the last four
years which at a high level is:

  deploy openstack from proposed using Juju
  run tempest functional test suite from upstream against deployed cloud

(obviously quite a bit in the details there)

** Changed in: neutron-lbaas (Ubuntu Xenial)
   Status: Incomplete => Won't Fix

** Changed in: neutron-vpnaas (Ubuntu Xenial)
   Status: Incomplete => Won't Fix

** Changed in: neutron-fwaas (Ubuntu Xenial)
   Status: Incomplete => Won't Fix

** Description changed:

  New point releases for misc openstack components for the mitaka release:
  
  neutron 8.1.0
+ 
+ The following components have new upstream releases, but don't actually
+ contain any new functionality, so we'll skip for Ubuntu:
+ 
  neutron-fwaas 8.1.0
  neutron-lbaas 8.1.0
  neutron-vpnaas 8.1.0

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

Title:
  [SRU] mitaka point releases

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  New
Status in Landscape Server:
  New
Status in Landscape Server 16.05 series:
  New
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron-fwaas package in Ubuntu:
  Fix Released
Status in neutron-lbaas package in Ubuntu:
  Fix Released
Status in neutron-vpnaas package in Ubuntu:
  Fix Released
Status in neutron source package in Xenial:
  Fix Committed
Status in neutron-fwaas source package in Xenial:
  Won't Fix
Status in neutron-lbaas source package in Xenial:
  Won't Fix
Status in neutron-vpnaas source package in Xenial:
  Won't Fix
Status in neutron-api package in Juju Charms Collection:
  Fix Committed
Status in neutron-gateway package in Juju Charms Collection:
  Fix Committed
Status in neutron-openvswitch package in Juju Charms Collection:
  Fix Committed

Bug description:
  New point releases for misc openstack components for the mitaka
  release:

  neutron 8.1.0

  The following components have new upstream releases, but don't
  actually contain any new functionality, so we'll skip for Ubuntu:

  neutron-fwaas 8.1.0
  neutron-lbaas 8.1.0
  neutron-vpnaas 8.1.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1580674/+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 1582847] Re: linux-raspi2: 4.4.0-1011.14 -proposed tracker

[Steve Beattie]

USN needed

** Changed in: kernel-sru-workflow/security-signoff
   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/1582847

Title:
  linux-raspi2: 4.4.0-1011.14 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1582431
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582847/+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 1582679] Re: linux-snapdragon: 4.4.0-1014.16 -proposed tracker

[Steve Beattie]

USN needed

** Changed in: kernel-sru-workflow/security-signoff
   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/1582679

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1582431
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582679/+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 1582431] Re: linux: 4.4.0-23.41 -proposed tracker

[Steve Beattie]

USN needed

** Changed in: kernel-sru-workflow/security-signoff
   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/1582431

Title:
  linux: 4.4.0-23.41 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+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 1581201] Re: CVE-2016-3713

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Invalid

** Description changed:

  A privileged user inside of a KVM guest can read/write host kernel
  memory by setting MTRRs
  
- Break-Fix: 910a6aae4e2e45855efc4a268e43eed2d8445575 -
+ Break-Fix: 910a6aae4e2e45855efc4a268e43eed2d8445575 local-2016-3713

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

Title:
  CVE-2016-3713

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