[Group.of.nepali.translators] [Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting

[Yuan-Chen Cheng]

** Also affects: oem-priority
   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/1648388

Title:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system
  hangs while rebooting

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or 
UEFI mode.
  System hangs while rebooting

  Not found the issue in RAID0
  No issue on Ubuntu14.04
  Driver-OS inbox support

  Below as error messages
  ===
  INFO:  task systemd-shutdow:1 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task  jbd2/md126p2-8:1732 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task ext4lazyinit:1873 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task kworker/u66:4:3139 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  ===

  WORKAROUND: edit /etc/sysctl.conf with follow commands and the system don't 
hang while rebooting:
  vm.dirty_background_ratio=5
  vm.dirty_ratio=10
  kernel.panic=3
  kernel.hung_task_panic=1
  kernel.hung_task_timeout_secs=30

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f578df47-a1b8-4e66-bd37-904f943eb01b
  InstallationDate: Installed on 2016-12-15 (10 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: Dell DCS6430G
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=bc552762-1955-44b8-a83e-2a414f0e0bd1 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:

  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: 03/22/2016
  dmi.bios.vendor: Dell
  dmi.bios.version: 2.0.3
  dmi.board.name: 038VV0
  dmi.board.vendor: Dell
  dmi.board.version: X01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell
  dmi.modalias: 
dmi:bvnDell:bvr2.0.3:bd03/22/2016:svnDell:pnDCS6430G:pvr:rvnDell:rn038VV0:rvrX01:cvnDell:ct23:cvr:
  dmi.product.name: DCS6430G
  dmi.sys.vendor: Dell

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1648388/+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 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::inpu

[Daniel van Vugt]

Minor correction - Mir 0.27.0 is not released yet :)

** Changed in: mir
   Status: Fix Released => Fix Committed

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

Title:
  unity-system-compositor crashed with SIGSEGV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Released
Status in unity-system-compositor source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/. 

  It seems that the configuration change is requested just a moment
  before the device gets removed. The change actions are serialized,
  depending on where there memory of mir::input::DefaultDevice is
  allocated the segfault either occurs inside the lambda or inside
  underlying mir::input::LibInputDevice in the platform. The activities
  on input dispatch device removal and reconfiguration are serialized
  inside the input thread, so we just need to clean the action queue (or
  have multiple queues) before removing the devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+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 1671246] Re: kexec-tools does not build for armhf

[Launchpad Bug Tracker]

This bug was fixed in the package kexec-tools - 1:2.0.10-1ubuntu2.2

---
kexec-tools (1:2.0.10-1ubuntu2.2) xenial; urgency=medium

  [ Manoj Iyer ]
  * d/p/arm-do-not-build-iomem.o-target-with-no-soruce.patch:
Fix regression in previous release that caused armhf to FTBFS.
(LP: #1671246)

  [ dann frazier ]
  * Expanded above changelog entry for clarity.

 -- dann frazier   Wed, 08 Mar 2017 17:57:31
-0700

** Changed in: kexec-tools (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/1671246

Title:
  kexec-tools does not build for armhf

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in kexec-tools source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  On armhf system kexec build fails as follows:
  gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-fno-strict-aliasing -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 
-I./include -I./util_lib/include -Iinclude/ -I./kexec/libfdt 
-I./kexec/arch/arm/include  -c -MD -o kexec/arch/arm/phys_to_virt.o 
kexec/arch/arm/phys_to_virt.c
  make[1]: *** No rule to make target 'kexec/arch/arm/iomem.o', needed by 
'build/sbin/kexec'.  Stop.

  The fix for this issue is already upstream:

  From c901bae8683c59a7bc002bd6a1e3e4b6b7d9c5f1 Mon Sep 17 00:00:00 2001
  From: Simon Horman 
  Date: Fri, 9 Dec 2016 10:10:49 +0100
  Subject: [PATCH] arm: do not build iomem.o target with no soruce

  Header files should be added to the distribution but not
  used to derive targets for compilation. In this an attempt was
  made to build iomem.o, but iomem.c does not exist so this fails.

  Fixes: 1574ff1aae4f ("arm: include phys_to_virt.h and iomem.h in 
distribution")
  Signed-off-by: Simon Horman 
  Reviewed-by: Pratyush Anand 

  [Test Case]
  Build kexec-tools package from Xenial/Yakkety source in armhf system.

  [Regression Potential]
  Since patch is confined to arm there is a low overall risk of regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1671246/+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 1671246] Re: kexec-tools does not build for armhf

[Launchpad Bug Tracker]

This bug was fixed in the package kexec-tools - 1:2.0.10-2ubuntu1.2

---
kexec-tools (1:2.0.10-2ubuntu1.2) yakkety; urgency=medium

  [ Manoj Iyer ]
  * d/p/arm-do-not-build-iomem.o-target-with-no-soruce.patch:
Fix regression in previous release that caused armhf to FTBFS.
(LP: #1671246)

  [ dann frazier ]
  * Expanded above changelog entry for clarity.

 -- dann frazier   Wed, 08 Mar 2017 17:55:26
-0700

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

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

Title:
  kexec-tools does not build for armhf

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in kexec-tools source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  On armhf system kexec build fails as follows:
  gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-fno-strict-aliasing -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 
-I./include -I./util_lib/include -Iinclude/ -I./kexec/libfdt 
-I./kexec/arch/arm/include  -c -MD -o kexec/arch/arm/phys_to_virt.o 
kexec/arch/arm/phys_to_virt.c
  make[1]: *** No rule to make target 'kexec/arch/arm/iomem.o', needed by 
'build/sbin/kexec'.  Stop.

  The fix for this issue is already upstream:

  From c901bae8683c59a7bc002bd6a1e3e4b6b7d9c5f1 Mon Sep 17 00:00:00 2001
  From: Simon Horman 
  Date: Fri, 9 Dec 2016 10:10:49 +0100
  Subject: [PATCH] arm: do not build iomem.o target with no soruce

  Header files should be added to the distribution but not
  used to derive targets for compilation. In this an attempt was
  made to build iomem.o, but iomem.c does not exist so this fails.

  Fixes: 1574ff1aae4f ("arm: include phys_to_virt.h and iomem.h in 
distribution")
  Signed-off-by: Simon Horman 
  Reviewed-by: Pratyush Anand 

  [Test Case]
  Build kexec-tools package from Xenial/Yakkety source in armhf system.

  [Regression Potential]
  Since patch is confined to arm there is a low overall risk of regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1671246/+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 1673350] Re: dm-queue-length module is not included in installer/initramfs

[Launchpad Bug Tracker]

This bug was fixed in the package multipath-tools -
0.5.0+git1.656f8865-5ubuntu7.3

---
multipath-tools (0.5.0+git1.656f8865-5ubuntu7.3) yakkety; urgency=medium

  * debian/initramfs/hooks: drop dm-emc (it hasn't existed since 2.6.27) and
add dm-queue-length: it's required on some hardware, such as XtremIO, where
it is the default path selector. (LP: #1673350)

 -- Mathieu Trudel-Lapierre   Tue, 28 Mar 2017
09:58:21 -0400

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

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in hw-detect source package in Xenial:
  In Progress
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in multipath-tools source package in Xenial:
  Fix Committed
Status in hw-detect source package in Yakkety:
  In Progress
Status in initramfs-tools source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released
Status in multipath-tools source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+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 1688056] Re: Package outdated

[Launchpad Bug Tracker]

This bug was fixed in the package xfce4-weather-plugin -
0.8.9-0ubuntu0.16.04.1

---
xfce4-weather-plugin (0.8.9-0ubuntu0.16.04.1) xenial; urgency=medium

  * Backport to xenial.
- Fixes API connectivitity issues (LP: #1688056)

 -- Sean Davis   Wed, 24 May 2017 22:27:28
-0400

** Changed in: xfce4-weather-plugin (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/1688056

Title:
  Package outdated

Status in Xfce4 weather plugin:
  Invalid
Status in xfce4-weather-plugin package in Ubuntu:
  Invalid
Status in xfce4-weather-plugin source package in Xenial:
  Fix Released
Status in xfce4-weather-plugin source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

   * The API that powers xfce4-weather-plugin has changed.
   * As a result, xfce4-weather-plugin 0.8.6 is no longer able to connect and 
is functionally useless.
   * The latest version, 0.8.9 supports the latest API and works in Xenial.

  [Test Case]

   * Right click on the Xfce panel.
   * Go to Panel > Add New Items
   * Add "Weather Update" and configure it.
   * Nothing more happens.
   * Install 0.8.9.
   * Restart the panel (possibly the session)
   * Configure the plugin.
   * Current weather information is retrieved and displayed.

  [Regression Potential]

   * The only changes since 0.8.6 are translation updates, compiler warnings, 
and the new API endpoints.
   * As a result, regression potential is minimal until the API changes again.

  [Original Report]

  There is a new version because weather datacenter changed api:

  https://bugzilla.xfce.org/show_bug.cgi?id=13527

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-weather-plugin/+bug/1688056/+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 1589240] Re: Gnome on-screen keyboard doesn't appear when a text field is focused

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 3.18.5-0ubuntu0.3

---
gnome-shell (3.18.5-0ubuntu0.3) xenial; urgency=medium

  * Extend ubuntu-lightdm-user-switching.patch to allow
locking screen using LightDM (LP: #1684205)
  * Allow lightdm to be an alternate recommends for gdm3 to avoid debconf
question if a display manager is already installed (LP: #1690938)
  * Depend on caribou, needed for the Screen Keyboard (LP: #1589240)
  * Recommend chrome-gnome-shell, needed for Firefox, Chromium, Chrome and
Opera to work with https://extensions.gnome.org/ (LP: #1672175)

 -- Jeremy Bicha   Sat, 13 May 2017 17:46:47 -0400

** Changed in: gnome-shell (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/1589240

Title:
  Gnome on-screen keyboard doesn't appear when a text field is focused

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

Bug description:
  Impact
  --
  Without 'caribou' installed, the Screen Keyboard setting, if Enabled, only 
works for for the login screen, password prompts and the Activities Overview 
search.

  It looks the caribou gir and library are enough for those places, but
  the 'caribou' binary is needed for the Screen Keyboard to work in
  screen input in apps.

  Test Case
  -
  From Ubuntu GNOME, install the update.

  caribou should be installed now.

  Open the Settings app (gnome-control-center).
  Click Universal Access then turn on Screen Keyboard.

  Open Text Editor (gedit)
  Click (or tap) in the window to start typing.
  The onscreen keyboard should be

  Regression Potential
  
  I also tested with gnome-shell-extension-onboard installed. Onboard appears 
to completely ignore the Screen Keyboard setting (LP: #1690582). Also when 
Onboard is enabled, caribou is not shown at all except in the password prompts 
and Activities Overview search where onboard is currently not working. In other 
words, I tested whether having caribou installed would interfere with Onboard 
and I can see that Caribou provides no problem.

  Original Bug Report
  ---
  The gnome on-screen keyboard is hidden by default and should appear when a 
text field is focused.
  This behavior is working as expected clicking on one of the text field of the 
shell such as the search field in the gnome overview. Clicking on text fields 
not owned by the gnome-shell such as in gedit or in a terminal emulator doesn't 
un-hide the keyboard.

  Steps to reproduce the issue:
   * Enable the keyboard in accessibility.
   * Open a text editor. (I've tested with gedit)
   * Click on the text field/area.

  Expected behavior:
   * The keyboard should appear.

  Actual behavior:
   * The keyboard doesn't appear.

  Also, I think it would be useful to be able to choose:
   * Between the "fullscreen" mode (the default one) and a windowed mode.
   * Between the "show on focus" behavior and a "always shown" behavior.

  The "fullscreen" mode should be incompatibile with the "always shown"
  behavior unless there is a way to close it manually (a button on the
  on-screen keyboard) in order to prevent a deadlock-like situation
  where the keyboard is preventing us from closing itself because we
  can't click in a window behind it. That button already exists and has
  a similar behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jun  5 13:49:03 2016
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-04-22 (43 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1589240/+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 1589240] Re: Gnome on-screen keyboard doesn't appear when a text field is focused

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 3.20.4-0ubuntu3

---
gnome-shell (3.20.4-0ubuntu3) yakkety; urgency=medium

  * Extend ubuntu-lightdm-user-switching.patch to allow
locking screen using LightDM (LP: #1684205)
  * Allow lightdm to be an alternate recommends for gdm3 to avoid debconf
question if a display manager is already installed (LP: #1690938)
  * Depend on caribou, needed for the Screen Keyboard (LP: #1589240)
  * Recommend chrome-gnome-shell, needed for Firefox, Chromium, Chrome and
Opera to work with https://extensions.gnome.org/ (LP: #1672175)

 -- Jeremy Bicha   Mon, 15 May 2017 18:38:18 -0400

** Changed in: gnome-shell (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: gnome-shell (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/1589240

Title:
  Gnome on-screen keyboard doesn't appear when a text field is focused

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

Bug description:
  Impact
  --
  Without 'caribou' installed, the Screen Keyboard setting, if Enabled, only 
works for for the login screen, password prompts and the Activities Overview 
search.

  It looks the caribou gir and library are enough for those places, but
  the 'caribou' binary is needed for the Screen Keyboard to work in
  screen input in apps.

  Test Case
  -
  From Ubuntu GNOME, install the update.

  caribou should be installed now.

  Open the Settings app (gnome-control-center).
  Click Universal Access then turn on Screen Keyboard.

  Open Text Editor (gedit)
  Click (or tap) in the window to start typing.
  The onscreen keyboard should be

  Regression Potential
  
  I also tested with gnome-shell-extension-onboard installed. Onboard appears 
to completely ignore the Screen Keyboard setting (LP: #1690582). Also when 
Onboard is enabled, caribou is not shown at all except in the password prompts 
and Activities Overview search where onboard is currently not working. In other 
words, I tested whether having caribou installed would interfere with Onboard 
and I can see that Caribou provides no problem.

  Original Bug Report
  ---
  The gnome on-screen keyboard is hidden by default and should appear when a 
text field is focused.
  This behavior is working as expected clicking on one of the text field of the 
shell such as the search field in the gnome overview. Clicking on text fields 
not owned by the gnome-shell such as in gedit or in a terminal emulator doesn't 
un-hide the keyboard.

  Steps to reproduce the issue:
   * Enable the keyboard in accessibility.
   * Open a text editor. (I've tested with gedit)
   * Click on the text field/area.

  Expected behavior:
   * The keyboard should appear.

  Actual behavior:
   * The keyboard doesn't appear.

  Also, I think it would be useful to be able to choose:
   * Between the "fullscreen" mode (the default one) and a windowed mode.
   * Between the "show on focus" behavior and a "always shown" behavior.

  The "fullscreen" mode should be incompatibile with the "always shown"
  behavior unless there is a way to close it manually (a button on the
  on-screen keyboard) in order to prevent a deadlock-like situation
  where the keyboard is preventing us from closing itself because we
  can't click in a window behind it. That button already exists and has
  a similar behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jun  5 13:49:03 2016
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-04-22 (43 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1589240/+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 1672175] Re: gnome-shell should recommend chrome-gnome-shell

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 3.20.4-0ubuntu3

---
gnome-shell (3.20.4-0ubuntu3) yakkety; urgency=medium

  * Extend ubuntu-lightdm-user-switching.patch to allow
locking screen using LightDM (LP: #1684205)
  * Allow lightdm to be an alternate recommends for gdm3 to avoid debconf
question if a display manager is already installed (LP: #1690938)
  * Depend on caribou, needed for the Screen Keyboard (LP: #1589240)
  * Recommend chrome-gnome-shell, needed for Firefox, Chromium, Chrome and
Opera to work with https://extensions.gnome.org/ (LP: #1672175)

 -- Jeremy Bicha   Mon, 15 May 2017 18:38:18 -0400

** Changed in: gnome-shell (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/1672175

Title:
  gnome-shell should recommend chrome-gnome-shell

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

Bug description:
  Impact
  ==
  Users who have ubuntu-gnome-desktop installed recently got chrome-gnome-shell 
installed to fix a regression introduced in Firefox 52 (LP: #1323734).

  Some people use gnome-shell without that metapackage installed.

  Test Case
  =
  Does gnome-shell recommend chrome-gnome-shell?

  Regression Potential
  
  Low. chrome-gnome-shell was already tested (LP: #1652537)

  Other Info
  ==
  This is only a recommends since perhaps users of gnome-shell without 
ubuntu-gnome-desktop don't want a lot of extra packages installed. This isn't 
critical functionality.

  Ubuntu 17.04 was released with gnome-shell recommending chrome-gnome-
  shell.

  Currently, Ubuntu 17.10 Alpha's gnome-shell does not recommend chrome-
  gnome-shell because the Ubuntu Desktop Team is trying to get a minimal
  gnome-shell into main first then add the extra dependencies later. I
  expect chrome-gnome-shell to be in main and be restored as a
  recommends before 17.10 is released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1672175/+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 1690938] Re: Allow lightdm to be an alternate recommends for gdm3

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 3.18.5-0ubuntu0.3

---
gnome-shell (3.18.5-0ubuntu0.3) xenial; urgency=medium

  * Extend ubuntu-lightdm-user-switching.patch to allow
locking screen using LightDM (LP: #1684205)
  * Allow lightdm to be an alternate recommends for gdm3 to avoid debconf
question if a display manager is already installed (LP: #1690938)
  * Depend on caribou, needed for the Screen Keyboard (LP: #1589240)
  * Recommend chrome-gnome-shell, needed for Firefox, Chromium, Chrome and
Opera to work with https://extensions.gnome.org/ (LP: #1672175)

 -- Jeremy Bicha   Sat, 13 May 2017 17:46:47 -0400

** Changed in: gnome-shell (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/1690938

Title:
  Allow lightdm to be an alternate recommends for gdm3

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

Bug description:
  Impact
  --
  If an Ubuntu user installs gnome-shell, they will be shown a debconf prompt 
asking to choose between gdm3 and lightdm. No information is given as to why 
one or the other should be chosen.

  This can be fixed by recommending gdm3 | lightdm

  Test Case
  -
  From Ubuntu (Unity), install gnome-shell. gdm3 should not be installed and 
there should be no debconf prompt.

  Regression Potential
  
  None really. GDM does look a bit nicer with GNOME Shell than LightDM in 17.04 
and older releases but if a user wants GNOME Shell to look nice, they should 
just install Ubuntu GNOME. It's not worth the avoidable debconf question for 
that.

  Other Info
  --
  This was already done for artful as part of the GNOME transition.

  Users will still see a debconf prompt if they install ubuntu-gnome-
  desktop but there's not much we can do about that now in SRUs.

  All Ubuntu "desktop" flavors except for Ubuntu GNOME and Kubuntu use
  LightDM. Kubuntu currently uses sddm, but no one has bothered to get
  sddm working with GNOME Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1690938/+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 1684205] Re: Screen lock button missing when using LightDM

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 3.20.4-0ubuntu3

---
gnome-shell (3.20.4-0ubuntu3) yakkety; urgency=medium

  * Extend ubuntu-lightdm-user-switching.patch to allow
locking screen using LightDM (LP: #1684205)
  * Allow lightdm to be an alternate recommends for gdm3 to avoid debconf
question if a display manager is already installed (LP: #1690938)
  * Depend on caribou, needed for the Screen Keyboard (LP: #1589240)
  * Recommend chrome-gnome-shell, needed for Firefox, Chromium, Chrome and
Opera to work with https://extensions.gnome.org/ (LP: #1672175)

 -- Jeremy Bicha   Mon, 15 May 2017 18:38:18 -0400

** Changed in: gnome-shell (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: gnome-shell (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/1684205

Title:
  Screen lock button missing when using LightDM

Status in Ubuntu GNOME:
  Triaged
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Trusty:
  Triaged
Status in gnome-shell source package in Xenial:
  Fix Released
Status in gnome-shell source package in Yakkety:
  Fix Released
Status in gnome-shell source package in Zesty:
  Fix Released

Bug description:
  Impact
  ==
  A user who installs gnome-shell in Ubuntu 17.04 and earlier is asked to 
choose between gdm and lightdm. If the user chooses lightdm, the GNOME session 
will not have a lock button in the system status menu in the top right corner.

  Workaround
  ==
  The keyboard shortcut Super+L still works to lock your screen.

  Test Case
  =
  1. a. From Ubuntu GNOME 17.04, install unity-greeter. Choose lightdm as your 
default.
     b. Restart
     c. Log in to GNOME
     d. Click the far right of the top bar. Make sure that the lock button 
exists. Click it. Your screen should lock.

  Or
  1. a. From Ubuntu (Unity) 17.04, install ubuntu-gnome-desktop or gnome-shell. 
Choose lightdm as your default if asked.
     b. Restart
     c. Log in to GNOME
     d. Click the far right of the top bar. Make sure that the lock button 
exists. Click it. Your screen should lock.

  2. Make sure that the screen lock also still works if you use GDM
  instead.

  Regression Potential
  
  This patch update just allows LightDM to lock the screen if GDM is not 
running.

  Other Info
  ==
  GNOME didn't accept our LightDM patches when we proposed them a few years 
ago, so this will just need to be fixed in Ubuntu for now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1684205/+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 1684205] Re: Screen lock button missing when using LightDM

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 3.18.5-0ubuntu0.3

---
gnome-shell (3.18.5-0ubuntu0.3) xenial; urgency=medium

  * Extend ubuntu-lightdm-user-switching.patch to allow
locking screen using LightDM (LP: #1684205)
  * Allow lightdm to be an alternate recommends for gdm3 to avoid debconf
question if a display manager is already installed (LP: #1690938)
  * Depend on caribou, needed for the Screen Keyboard (LP: #1589240)
  * Recommend chrome-gnome-shell, needed for Firefox, Chromium, Chrome and
Opera to work with https://extensions.gnome.org/ (LP: #1672175)

 -- Jeremy Bicha   Sat, 13 May 2017 17:46:47 -0400

** Changed in: gnome-shell (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/1684205

Title:
  Screen lock button missing when using LightDM

Status in Ubuntu GNOME:
  Triaged
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Trusty:
  Triaged
Status in gnome-shell source package in Xenial:
  Fix Released
Status in gnome-shell source package in Yakkety:
  Fix Released
Status in gnome-shell source package in Zesty:
  Fix Released

Bug description:
  Impact
  ==
  A user who installs gnome-shell in Ubuntu 17.04 and earlier is asked to 
choose between gdm and lightdm. If the user chooses lightdm, the GNOME session 
will not have a lock button in the system status menu in the top right corner.

  Workaround
  ==
  The keyboard shortcut Super+L still works to lock your screen.

  Test Case
  =
  1. a. From Ubuntu GNOME 17.04, install unity-greeter. Choose lightdm as your 
default.
     b. Restart
     c. Log in to GNOME
     d. Click the far right of the top bar. Make sure that the lock button 
exists. Click it. Your screen should lock.

  Or
  1. a. From Ubuntu (Unity) 17.04, install ubuntu-gnome-desktop or gnome-shell. 
Choose lightdm as your default if asked.
     b. Restart
     c. Log in to GNOME
     d. Click the far right of the top bar. Make sure that the lock button 
exists. Click it. Your screen should lock.

  2. Make sure that the screen lock also still works if you use GDM
  instead.

  Regression Potential
  
  This patch update just allows LightDM to lock the screen if GDM is not 
running.

  Other Info
  ==
  GNOME didn't accept our LightDM patches when we proposed them a few years 
ago, so this will just need to be fixed in Ubuntu for now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1684205/+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 1690938] Re: Allow lightdm to be an alternate recommends for gdm3

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 3.20.4-0ubuntu3

---
gnome-shell (3.20.4-0ubuntu3) yakkety; urgency=medium

  * Extend ubuntu-lightdm-user-switching.patch to allow
locking screen using LightDM (LP: #1684205)
  * Allow lightdm to be an alternate recommends for gdm3 to avoid debconf
question if a display manager is already installed (LP: #1690938)
  * Depend on caribou, needed for the Screen Keyboard (LP: #1589240)
  * Recommend chrome-gnome-shell, needed for Firefox, Chromium, Chrome and
Opera to work with https://extensions.gnome.org/ (LP: #1672175)

 -- Jeremy Bicha   Mon, 15 May 2017 18:38:18 -0400

** Changed in: gnome-shell (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: gnome-shell (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/1690938

Title:
  Allow lightdm to be an alternate recommends for gdm3

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

Bug description:
  Impact
  --
  If an Ubuntu user installs gnome-shell, they will be shown a debconf prompt 
asking to choose between gdm3 and lightdm. No information is given as to why 
one or the other should be chosen.

  This can be fixed by recommending gdm3 | lightdm

  Test Case
  -
  From Ubuntu (Unity), install gnome-shell. gdm3 should not be installed and 
there should be no debconf prompt.

  Regression Potential
  
  None really. GDM does look a bit nicer with GNOME Shell than LightDM in 17.04 
and older releases but if a user wants GNOME Shell to look nice, they should 
just install Ubuntu GNOME. It's not worth the avoidable debconf question for 
that.

  Other Info
  --
  This was already done for artful as part of the GNOME transition.

  Users will still see a debconf prompt if they install ubuntu-gnome-
  desktop but there's not much we can do about that now in SRUs.

  All Ubuntu "desktop" flavors except for Ubuntu GNOME and Kubuntu use
  LightDM. Kubuntu currently uses sddm, but no one has bothered to get
  sddm working with GNOME Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1690938/+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 1573272] Re: default gateway route not installed for bond interfaces through reboot

[Launchpad Bug Tracker]

This bug was fixed in the package vlan - 1.9-3ubuntu10.4

---
vlan (1.9-3ubuntu10.4) trusty; urgency=medium

  * Don't trust ifup return code, as it returns 0 on failure; call ip link
set up after ifup to force vlan raw device up. (LP: #1573272)

 -- Dan Streetman   Mon, 05 Jun 2017
12:12:01 -0400

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

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

Title:
  default gateway route not installed for bond interfaces through reboot

Status in vlan package in Ubuntu:
  Fix Released
Status in vlan source package in Trusty:
  Fix Released
Status in vlan source package in Xenial:
  Fix Released
Status in vlan source package in Yakkety:
  Fix Released
Status in vlan source package in Zesty:
  Fix Released
Status in vlan source package in Artful:
  Fix Released
Status in vlan package in Debian:
  New

Bug description:
  [Impact]

  Systems using vlans, especially those using vlans on top of bond
  interfaces, in addition to default or other routes on the vlans, may
  find their vlan routes are not present at boot.

  The attached debdiff patches fix the vlan package's /etc/network/if-
  pre-up.d/vlan script.  Currently, the script will bring up a vlan's
  raw device if needed; but the problem is if the vlan's ifup processing
  happens before the raw device's ifup processing, the raw device may be
  taken down and back up (especially for bonds), and when the raw device
  is taken down, the vlan is as well, and thus loses all its routing
  configuration.  Instead of only bringing the raw device up using ip
  link up, the patch changes the vlan script to do a full ifup on the
  raw device, so it will remain up after the vlan is configured.

  [Test Case]

  Set up a system using two interfaces configured into a bond interface,
  with a vlan on top of that bond.  Add a default route and/or specific
  routes to the vlan interface.  Then edit the system as described in
  comment 8, and reboot.  The vlan's routes will not be present in the
  system.

  [Regression Potential]

  Any modifications to ifupdown or the scripts it uses may cause wider
  problems with network configuration.  Specifically, this could cause
  problems when using vlan interfaces, as it forces every vlan's raw
  device interface to be fully ifup'ed before the vlan interface can
  finish its ifup.

  [Other Info]

  original description below:

  
  Expectation:  After reboot, route for default gateway specified on bonded 
interface is installed according to "gateway x.x.x.x"  (where x.x.x.x is a 
valid IPv4 address) specified in /etc/network/interfaces or files sourced per 
/etc/network/interfaces

  Actual Result: After reboot, route is not installed. Interface does
  work otherwise (I can ping the gateway on that subnet, for instance).
  'ifdown -a' followed by  'ifup -a' (run with proper permission... so
  sudo) brings the gateway back until next reboot.

  Package:  I'm not familiar enough to be certain what is causing this,
  but I was seeing this in beta2 of 16.04 as well.

  *username snipped*@*hostname snipped*:~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04
  *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave
  ifenslave:
    Installed: 2.7ubuntu1
    Candidate: 2.7ubuntu1
    Version table:
   *** 2.7ubuntu1 100
  100 /var/lib/dpkg/status

  *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown
  ifupdown:
    Installed: 0.8.10ubuntu1
    Candidate: 0.8.10ubuntu1
    Version table:
   *** 0.8.10ubuntu1 100
  100 /var/lib/dpkg/status

    /etc/network/interfaces

  --
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto enp2s0f1
  iface enp2s0f1 inet manual
  bond-master bond0

  auto enp2s0f0
  iface enp2s0f0 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  address 10.96.96.2
  netmask 255.255.255.0
  network 10.96.96.0
  broadcast 10.96.96.255
  # dns-* options are implemented by the resolvconf package, if 
installed
  dns-search *snip*
  bond-mode balance-alb
  bond-slaves none
  bond-miimon 100
  auto bond0.3000
  iface bond0.3000 inet static
  address 172.21.33.29
  netmask 255.255.255.0
  network 172.21.33.0
  broadcast 172.21.33.255
  gateway 172.21.33.1
  dns-search *snip*
  vlan-raw-device bond0
  dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2

  

[Group.of.nepali.translators] [Bug 1684341] Re: EFI fallback binary should not be installed in --removable mode

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.11

---
grub2 (2.02~beta2-36ubuntu3.11) xenial; urgency=medium

  * Fix syntax error in debian/postinst.in.  (LP #1692181)

 -- Steve Langasek   Sat, 20 May 2017
12:59:17 -0700

** Changed in: grub2 (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/1684341

Title:
  EFI fallback binary should not be installed in --removable mode

Status in cloud-images:
  New
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Trusty:
  Confirmed
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2 source package in Yakkety:
  Fix Committed
Status in grub2 source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Building some images depending on calling grub-install --removable still 
installs fbx64.efi; which we don't want on removable media.

  [Test case]
  On an EFI system, run 'grub-install --removable --target=x86_64-efi'. Observe 
whether fbx64.efi is installed to /boot/efi/EFI/BOOT. It should not.

  [Regression potential]
  If any system is depending on running grub-install with --removable, and on 
fbx64.efi being installed in /boot/efi/EFI/BOOT; this would cause this 
assumption to fail -- leading to incorrect fallback behavior when BootEntries 
are not present on a system.

  Failures to boot with "System BootOrder not found" errors should be
  considered a possible regression.

  Any missing files in /boot/efi/EFI/BOOT or /boot/efi/EFI/ubuntu after
  install should be considered a potential regression of this update.

  
  

  
  The patch I did to fix names for the new naming of shim binaries included the 
addition of fbx64.efi; but it was done wrong: fbx64.efi should only exist under 
\EFI\BOOT, it's not required in the "removable" path; except if we're trying to 
force installing to the removable path *too*.

  In other words:
  1) we normally don't want /EFI/ubuntu/fbx64.efi to exist;

  and
  a) on a desktop or server, we want /EFI/BOOT/fbx64.efi to exist (ie. installs 
without --removable, and with --force-extra-removable used when grub-install 
was called);
  b) on removable media, we do not want /EFI/BOOT/fbx64.efi to exist (ie. when 
grub-installed is called with --removable).

  Furthermore, the (a) case is probably not the typical case we want to
  run grub-install with. Calls to grub-install with --force-extra-
  removable probably should be limited to shim-signed's postinst.

  In any case, let's move the fbx64.efi installation step to
  also_install_removable() in grub-installer to avoid installing it when
  it shouldn't be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1684341/+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 1694859] Re: arm64 kernel crashdump support

[dann frazier]

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

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

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

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

** Changed in: kexec-tools (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: kexec-tools (Ubuntu Zesty)
   Status: Confirmed => In Progress

** Changed in: kexec-tools (Ubuntu Zesty)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Incomplete
Status in makedumpfile source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  Confirmed
Status in kexec-tools source package in Zesty:
  In Progress
Status in linux source package in Zesty:
  Confirmed
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.

  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger

  Crash dump should occur, with artifacts collected in /var/crash.

  [Regression Risk]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1694859/+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 1667662] Re: SRU: backport rustc to 14.04 and 16.04

[Matthias Klose]

** Package changed: binutils (Ubuntu Trusty) => binutils-2.26 (Ubuntu
Trusty)

** Changed in: binutils-2.26 (Ubuntu Trusty)
   Status: New => Fix Released

** Package changed: cmake (Ubuntu Trusty) => cmake3 (Ubuntu Trusty)

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

** Changed in: llvm-toolchain-3.9 (Ubuntu Trusty)
   Status: New => Fix Released

** Changed in: llvm-toolchain-3.9 (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: llvm-toolchain-3.9 (Ubuntu)
   Status: New => Fix Released

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

** Changed in: rustc (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/1667662

Title:
  SRU: backport rustc to 14.04 and 16.04

Status in llvm-toolchain-3.9 package in Ubuntu:
  Fix Released
Status in llvm-toolchain-4.0 package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  Fix Released
Status in binutils-2.26 source package in Trusty:
  Fix Released
Status in cmake3 source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.9 source package in Trusty:
  Fix Released
Status in llvm-toolchain-4.0 source package in Trusty:
  New
Status in rustc source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.9 source package in Xenial:
  Fix Released
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in rustc source package in Xenial:
  Fix Released
Status in llvm-toolchain-3.9 source package in Yakkety:
  Fix Released
Status in llvm-toolchain-4.0 source package in Yakkety:
  New
Status in rustc source package in Yakkety:
  Fix Released

Bug description:
  newer firefox versions will require rust as a build dependency.
  Backport the recent rustc version and cmake, binutils, llvm versions
  from xenial to trusty.  It looks like xenial is recent and only needs
  the llvm backport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.9/+bug/1667662/+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 1614789] Re: zfs.target should not require zfs-share.service

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu17

---
zfs-linux (0.6.5.6-0ubuntu17) xenial; urgency=medium

  * Fix incorrect path to rm in zfs-share.service.in (LP: #1684731)
  * Set zfs-share.service to Wants in zfs.target (LP: #1614789)
- Change from Requires to Wants to stop systemctl mask
  zfs-share.service from breaking zfs mounts

 -- Colin Ian King   Mon, 22 May 2017 17:13:44
+0100

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

Title:
  zfs.target should not require zfs-share.service

Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  == SRU Xenial ==

  [Justification]

  Currently package zfsutils-linux contains systemd target file 
/lib/systemd/system/zfs.target that specifies following dependencies:
  Requires=zfs-mount.service
  Requires=zfs-share.service
  Wants=zed.service

  zfs-share.service is not essential in setups where file sharing is not
  used, or when it is configured without the use of the zfs utility. The
  user may therefore choose to mask this service. However, doing so has
  an unexpected and confusing effect, preventing zfs from starting on
  boot at all. This is because zfs.target is the only zfs-related unit
  that is wanted by multi-user.target, and if one of its required
  services is masked, zfs.target is skipped, together with zfs-
  mount.service. A solution is to replace "Requires=zfs-share.service"
  with "Wants=zfs-share.service".

  [Testcase]
  Steps to reproduce:
  systemctl mask zfs-share.service
  reboot

  Expected results:
  Module zfs is loaded
  zfs-mount.service is active and ZFS filesystems are mounted
  ZFS filesystems are not shared

  Observed results:
  Module zfs is not loaded
  ZFS filesystems are not mounted
  zpool status produces an error:
  "The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them."

  With the fix, the modules are loaded and zfs filesystems are mounted

  [Fix]
  A solution is to replace "Requires=zfs-share.service" with 
"Wants=zfs-share.service".

  [Regression Potential]
  Minimal, this affects the start up of a service that should be starting and 
currently isn't. Limited to just this specific scenario.

  -

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  $ apt-cache policy zfsutils-linux
  zfsutils-linux:
    Installed: 0.6.5.6-0ubuntu10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1614789/+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 1677239] Re: mir_demo_standalone_render_overlays fails to link

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.04.20170605-0ubuntu1

---
mir (0.26.3+16.04.20170605-0ubuntu1) xenial; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . unity-system-compositor crashed with SIGSEGV in
libinput_device_config_accel_is_available() from
libinput_device_config_accel_set_speed() from
mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:01:05 +

** Changed in: mir (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/1677239

Title:
  mir_demo_standalone_render_overlays fails to link

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in mir source package in Xenial:
  Fix Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console

  11:41:20 [ 52%] Linking CXX executable 
../../../../bin/mir_demo_standalone_render_overlays.bin
  11:41:20 cd 
/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1
  11:41:20 /usr/lib/ccache/c++ -g -O2 
-fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing 
-pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o 
../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic 
../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 
../../../capnproto/libmircapnproto.a -lkj -lcapnp 
../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system 
-lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 
-L/lib/x86_64-linux-gnu -ludev -ludev
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, 
unsigned long) const@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE'

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1677239/+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 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.10.20170605-0ubuntu1

---
mir (0.26.3+16.10.20170605-0ubuntu1) yakkety; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . unity-system-compositor crashed with SIGSEGV in
libinput_device_config_accel_is_available() from
libinput_device_config_accel_set_speed() from
mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
13:46:05 +

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

** Changed in: mir (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/1675357

Title:
  Mir sending key repeat events continually to nested shell after VT
  switch (causes Unity8 lockup for a while)

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Released
Status in qtmir source package in Xenial:
  Invalid
Status in unity8 source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

Bug description:
  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt

  Expected:
  * session is locked, but working

  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all

  It seems it's "catching up" in some way, maybe with input, maybe
  frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

  Causes:
  The mir::input::KeyRepeatDispatcher is running inside the nested mirserver 
even though there is another instance running inside the host server. A few 
months ago qtmir used to replace the key repeater by replacing mirs  
dispatcher. And key repeat is not disabled within the nested server. So both 
the host and the nested server are producing repeat events.
    Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hub when running inside the nested server. The 
input device hub would tell the key repeater when devices get removed - i.e. 
due to vt switching. So it never notices that the devices go away continues to 
produce those events indefinitely.

  This applies to all currently pressed buttons. I.e. you can open an
  edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to
  switch to another VT. On return 'w' will be repeated indefinitely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675357/+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 1675138] Re: Please transition to latest Boost

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.04.20170605-0ubuntu1

---
mir (0.26.3+16.04.20170605-0ubuntu1) xenial; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . unity-system-compositor crashed with SIGSEGV in
libinput_device_config_accel_is_available() from
libinput_device_config_accel_set_speed() from
mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:01:05 +

** Changed in: mir (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/1675138

Title:
  Please transition to latest Boost

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in mir source package in Xenial:
  Fix Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

Bug description:
  There is an ongoing transition to Boost 1.62 and mir is one of the last 
affected packages:
  http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1675138/+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 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.04.20170605-0ubuntu1

---
mir (0.26.3+16.04.20170605-0ubuntu1) xenial; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . unity-system-compositor crashed with SIGSEGV in
libinput_device_config_accel_is_available() from
libinput_device_config_accel_set_speed() from
mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:01:05 +

** Changed in: mir (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/1675357

Title:
  Mir sending key repeat events continually to nested shell after VT
  switch (causes Unity8 lockup for a while)

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Released
Status in qtmir source package in Xenial:
  Invalid
Status in unity8 source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

Bug description:
  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt

  Expected:
  * session is locked, but working

  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all

  It seems it's "catching up" in some way, maybe with input, maybe
  frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

  Causes:
  The mir::input::KeyRepeatDispatcher is running inside the nested mirserver 
even though there is another instance running inside the host server. A few 
months ago qtmir used to replace the key repeater by replacing mirs  
dispatcher. And key repeat is not disabled within the nested server. So both 
the host and the nested server are producing repeat events.
    Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hub when running inside the nested server. The 
input device hub would tell the key repeater when devices get removed - i.e. 
due to vt switching. So it never notices that the devices go away continues to 
produce those events indefinitely.

  This applies to all currently pressed buttons. I.e. you can open an
  edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to
  switch to another VT. On return 'w' will be repeated indefinitely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675357/+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 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::inpu

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.04.20170605-0ubuntu1

---
mir (0.26.3+16.04.20170605-0ubuntu1) xenial; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . unity-system-compositor crashed with SIGSEGV in
libinput_device_config_accel_is_available() from
libinput_device_config_accel_set_speed() from
mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:01:05 +

** Changed in: mir (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/1672955

Title:
  unity-system-compositor crashed with SIGSEGV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in Mir 0.26 series:
  Fix Released
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Released
Status in unity-system-compositor source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/. 

  It seems that the configuration change is requested just a moment
  before the device gets removed. The change actions are serialized,
  depending on where there memory of mir::input::DefaultDevice is
  allocated the segfault either occurs inside the lambda or inside
  underlying mir::input::LibInputDevice in the platform. The activities
  on input dispatch device removal and reconfiguration are serialized
  inside the input thread, so we just need to clean the action queue (or
  have multiple queues) before removing the devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+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 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::inpu

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.10.20170605-0ubuntu1

---
mir (0.26.3+16.10.20170605-0ubuntu1) yakkety; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . unity-system-compositor crashed with SIGSEGV in
libinput_device_config_accel_is_available() from
libinput_device_config_accel_set_speed() from
mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
13:46:05 +

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

** Changed in: mir (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/1672955

Title:
  unity-system-compositor crashed with SIGSEGV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in Mir 0.26 series:
  Fix Released
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Released
Status in unity-system-compositor source package in Xenial:
  Invalid
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/. 

  It seems that the configuration change is requested just a moment
  before the device gets removed. The change actions are serialized,
  depending on where there memory of mir::input::DefaultDevice is
  allocated the segfault either occurs inside the lambda or inside
  underlying mir::input::LibInputDevice in the platform. The activities
  on input dispatch device removal and reconfiguration are serialized
  inside the input thread, so we just need to clean the action queue (or
  have multiple queues) before removing the devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+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 1684731] Re: zfs-share.service: Failed at step EXEC spawning /usr/bin/rm: No such file or directory

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 0.6.5.8-0ubuntu4.3

---
zfs-linux (0.6.5.8-0ubuntu4.3) yakkety; urgency=low

  * Fix incorrect path to rm in zfs-share.service.in (LP: #1684731)

 -- Colin Ian King   Mon, 22 May 2017 17:13:44
+0100

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

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

Title:
  zfs-share.service: Failed at step EXEC spawning /usr/bin/rm: No such
  file or directory

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released
Status in zfs-linux source package in Yakkety:
  Fix Released
Status in zfs-linux source package in Zesty:
  Fix Released
Status in zfs-linux source package in Artful:
  Fix Released

Bug description:
  == SRU Xenial, Yakkety, Zesty ==

  [Justification]
  The path to rm is incorrect and hence it won't remove the /etc/dfs/sharetab

  [Fix]
  Set correct path, use /bin/rm and not /usr/bin/rm

  [Test Case]
  Without the fix, /etc/dfs/sharetab is not removed. With the fix, it is 
removed.  To test, touch /etc/dfs/sharetab and it should be removed on startup 
of the zfs share service.

  With the fix:
  $ systemctl status zfs-share.service

  ● zfs-share.service - ZFS file system shares
 Loaded: loaded (/lib/systemd/system/zfs-share.service; enabled; vendor 
preset
 Active: active (exited) since Wed 2017-05-31 14:22:31 BST; 11s ago
Process: 2483 ExecStart=/sbin/zfs share -a (code=exited, status=0/SUCCESS)
Process: 2476 ExecStartPre=/bin/rm -f /etc/dfs/sharetab (code=exited, 
status=0
   Main PID: 2483 (code=exited, status=0/SUCCESS)
  Tasks: 0 (limit: 4915)
 Memory: 0B
CPU: 0
 CGroup: /system.slice/zfs-share.service

  [Regression Potenial]
  Minimal, this affects the removal of a file that should be fixed. The only 
regression risk is if somebody is depending on this file, which they should not 
be doing so.

  wrong `rm` path on /lib/systemd/system/zfs-share.service

  ExecStartPre=-/usr/bin/rm -f /etc/dfs/sharetab

  there is no file such /usr/bin/rm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1684731/+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 1677239] Re: mir_demo_standalone_render_overlays fails to link

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.10.20170605-0ubuntu1

---
mir (0.26.3+16.10.20170605-0ubuntu1) yakkety; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . unity-system-compositor crashed with SIGSEGV in
libinput_device_config_accel_is_available() from
libinput_device_config_accel_set_speed() from
mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
13:46:05 +

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

** Changed in: mir (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/1677239

Title:
  mir_demo_standalone_render_overlays fails to link

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in mir source package in Xenial:
  Fix Released
Status in mir source package in Yakkety:
  Fix Released
Status in mir source package in Zesty:
  Fix Released

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console

  11:41:20 [ 52%] Linking CXX executable 
../../../../bin/mir_demo_standalone_render_overlays.bin
  11:41:20 cd 
/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1
  11:41:20 /usr/lib/ccache/c++ -g -O2 
-fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing 
-pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o 
../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic 
../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 
../../../capnproto/libmircapnproto.a -lkj -lcapnp 
../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system 
-lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 
-L/lib/x86_64-linux-gnu -ludev -ludev
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, 
unsigned long) const@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE'

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1677239/+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 1684731] Re: zfs-share.service: Failed at step EXEC spawning /usr/bin/rm: No such file or directory

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 0.6.5.9-5ubuntu4.1

---
zfs-linux (0.6.5.9-5ubuntu4.1) zesty; urgency=medium

  * Fix incorrect path to rm in zfs-share.service.in (LP: #1684731)

 -- Colin Ian King   Mon, 22 May 2017 17:13:44
+0100

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

Title:
  zfs-share.service: Failed at step EXEC spawning /usr/bin/rm: No such
  file or directory

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released
Status in zfs-linux source package in Yakkety:
  Fix Released
Status in zfs-linux source package in Zesty:
  Fix Released
Status in zfs-linux source package in Artful:
  Fix Released

Bug description:
  == SRU Xenial, Yakkety, Zesty ==

  [Justification]
  The path to rm is incorrect and hence it won't remove the /etc/dfs/sharetab

  [Fix]
  Set correct path, use /bin/rm and not /usr/bin/rm

  [Test Case]
  Without the fix, /etc/dfs/sharetab is not removed. With the fix, it is 
removed.  To test, touch /etc/dfs/sharetab and it should be removed on startup 
of the zfs share service.

  With the fix:
  $ systemctl status zfs-share.service

  ● zfs-share.service - ZFS file system shares
 Loaded: loaded (/lib/systemd/system/zfs-share.service; enabled; vendor 
preset
 Active: active (exited) since Wed 2017-05-31 14:22:31 BST; 11s ago
Process: 2483 ExecStart=/sbin/zfs share -a (code=exited, status=0/SUCCESS)
Process: 2476 ExecStartPre=/bin/rm -f /etc/dfs/sharetab (code=exited, 
status=0
   Main PID: 2483 (code=exited, status=0/SUCCESS)
  Tasks: 0 (limit: 4915)
 Memory: 0B
CPU: 0
 CGroup: /system.slice/zfs-share.service

  [Regression Potenial]
  Minimal, this affects the removal of a file that should be fixed. The only 
regression risk is if somebody is depending on this file, which they should not 
be doing so.

  wrong `rm` path on /lib/systemd/system/zfs-share.service

  ExecStartPre=-/usr/bin/rm -f /etc/dfs/sharetab

  there is no file such /usr/bin/rm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1684731/+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 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.04.20170605-0ubuntu1

---
mir (0.26.3+16.04.20170605-0ubuntu1) xenial; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . unity-system-compositor crashed with SIGSEGV in
libinput_device_config_accel_is_available() from
libinput_device_config_accel_set_speed() from
mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
11:01:05 +

** Changed in: mir (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/1685186

Title:
  [SRU] Mir needs to be updated to 0.26 in 16.04LTS

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

Bug description:
  [Impact]
  Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  [Test Case]

  Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
  against "Primary Ubuntu Archive" and deploy as described in
  https://developer.ubuntu.com/en/snappy/guides/mir-snaps/

  Expected: the client apps start and are visible on screen
  Actual: the client apps don't start and are not visible on screen

  [Regression Potential]
  Mir has two categories of dependent project:

    1 Unity8 and unity-system-compositor "server" packages
    2 toolkits and other "clients" of Mir

  "Server" packages from the archive will stop working in the LTS as
  they will continue using the earlier libmirserver.so.38 (from Mir
  0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26.
  This is unimportant as these packages were provided as an "early
  experience", not for serious use.

  "Client" packages are dependent only on libmirclient.so.9 which is ABI
  stable. The principle type of regression would be FTBFS where APIs
  have been deprecated in 0.26. The linked 0.26.3 release has these
  deprecations disabled for 16.04.

  The packages are available in silo:
  https://bileto.ubuntu.com/#/ticket/2736

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

  Anyone wanting these packages should switch to the "unity8-desktop-
  session" preview package in 17.04 where they are far more functional.

  [Alternatives]
  If we want to keep everything working in Xenial, we *could* bump the 
libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 
being NBS, but continuing to work against the Mir servers available in 16.04[*] 
(until and unless they are rebuilt).

  However, this does not enable the desired result for IoT deployments
  of toolkits (GTK, Qt etc) and other clients working against servers
  (specifically miral-kiosk) built against the updated libraries.

  To work for IoT these would need to rebuilt from source - at which
  point they (and their dependencies) would stop working against the
  servers in category 1.

  [*] with the exception of the servers provided in mir-examples, these
  would only work with clients linking against libmirclient.so.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+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 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.3+16.10.20170605-0ubuntu1

---
mir (0.26.3+16.10.20170605-0ubuntu1) yakkety; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
  . Make deprecations optional (and default to off for builds on 16.04 LTS)
  . Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
  . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
  . unity-system-compositor crashed with SIGSEGV in
libinput_device_config_accel_is_available() from
libinput_device_config_accel_set_speed() from
mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
  . Please transition to Boost 1.62 (LP: #1675138)
  . Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
  . mir_demo_standalone_render_overlays fails to link (LP: #1677239)

 -- Michał Sawicz   Mon, 05 Jun 2017
13:46:05 +

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

** Changed in: mir (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/1685186

Title:
  [SRU] Mir needs to be updated to 0.26 in 16.04LTS

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

Bug description:
  [Impact]
  Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  [Test Case]

  Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
  against "Primary Ubuntu Archive" and deploy as described in
  https://developer.ubuntu.com/en/snappy/guides/mir-snaps/

  Expected: the client apps start and are visible on screen
  Actual: the client apps don't start and are not visible on screen

  [Regression Potential]
  Mir has two categories of dependent project:

    1 Unity8 and unity-system-compositor "server" packages
    2 toolkits and other "clients" of Mir

  "Server" packages from the archive will stop working in the LTS as
  they will continue using the earlier libmirserver.so.38 (from Mir
  0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26.
  This is unimportant as these packages were provided as an "early
  experience", not for serious use.

  "Client" packages are dependent only on libmirclient.so.9 which is ABI
  stable. The principle type of regression would be FTBFS where APIs
  have been deprecated in 0.26. The linked 0.26.3 release has these
  deprecations disabled for 16.04.

  The packages are available in silo:
  https://bileto.ubuntu.com/#/ticket/2736

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

  Anyone wanting these packages should switch to the "unity8-desktop-
  session" preview package in 17.04 where they are far more functional.

  [Alternatives]
  If we want to keep everything working in Xenial, we *could* bump the 
libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 
being NBS, but continuing to work against the Mir servers available in 16.04[*] 
(until and unless they are rebuilt).

  However, this does not enable the desired result for IoT deployments
  of toolkits (GTK, Qt etc) and other clients working against servers
  (specifically miral-kiosk) built against the updated libraries.

  To work for IoT these would need to rebuilt from source - at which
  point they (and their dependencies) would stop working against the
  servers in category 1.

  [*] with the exception of the servers provided in mir-examples, these
  would only work with clients linking against libmirclient.so.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+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 1697565] Re: Snaps without icons don't show as installed

[Launchpad Bug Tracker]

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

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

  * debian/patches/0001-snap-Fix-icons-not-being-converted-to-pixbufs.patch:
- Fix snaps without icons not showing reliably (LP: #1697565)
  * debian/patches/0001-snap-Mark-snaps-as-sandboxed.patch:
  * debian/patches/0001-snap-Backport-fixes-from-master.patch:
- Show featured snaps (LP: #1663097)

 -- Robert Ancell   Thu, 15 Jun 2017
16:55:26 +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/1697565

Title:
  Snaps without icons don't show as installed

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:
  Snaps without icons don't show in the installed tab. They do show in
  search, because the icon is sourced from the store.

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