[Group.of.nepali.translators] [Bug 1702110] Re: linux-joule: -proposed tracker

[Andy Whitcroft]

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

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

Title:
  linux-joule:  -proposed tracker

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1702110/+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 1675288] Re: security fix to runc in docker-1.12.3 wasn't picked

[Michael Hudson-Doyle]

** Changed in: runc (Ubuntu Yakkety)
   Status: Fix Committed => Won't Fix

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

Title:
  security fix to runc in docker-1.12.3 wasn't picked

Status in runc package in Ubuntu:
  Fix Released
Status in runc source package in Xenial:
  Fix Released
Status in runc source package in Yakkety:
  Won't Fix

Bug description:
  [Impact]
  https://github.com/docker/docker/issues/27590#issuecomment-255241013

  The steps are very clear, it's very easy to recur, so I don't repeat
  here.

  The CVE link: https://cve.mitre.org/cgi-
  bin/cvename.cgi?name=CVE-2016-8867

  [Test case]
  $ tmp=$(mktemp -d)
  $ cd $tmp
  $ cat > Dockerfile << EOF
  FROM debian
  RUN useradd example
  RUN id
  USER example
  RUN id
  RUN cat /etc/shadow
  CMD /bin/bash
  EOF
  $ docker build --no-cache -t example .

  The 'cat /etc/shadow' in the Dockerfile should fail.

  [Regression potential]
  We're fixing this by moving to the exact commit of runc the docker 1.12.6 
release expects, so there shouldn't be any issues. In addition 
https://wiki.ubuntu.com/DockerUpdates applies.

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

** Changed in: mir
   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 Released
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 1675138] Re: Please transition to latest Boost

[Daniel van Vugt]

** Changed in: mir
   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 Released
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)

[Daniel van Vugt]

** Changed in: mir
   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 Released
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 1675288] Re: security fix to runc in docker-1.12.3 wasn't picked

[Launchpad Bug Tracker]

This bug was fixed in the package runc -
1.0.0~rc2+docker1.12.6-0ubuntu1~16.04.1

---
runc (1.0.0~rc2+docker1.12.6-0ubuntu1~16.04.1) xenial; urgency=medium

  * Backport to Xenial. (LP: #1675288)

 -- Michael Hudson-Doyle   Tue, 28 Mar 2017
13:49:34 +1300

** Changed in: runc (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/1675288

Title:
  security fix to runc in docker-1.12.3 wasn't picked

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

Bug description:
  [Impact]
  https://github.com/docker/docker/issues/27590#issuecomment-255241013

  The steps are very clear, it's very easy to recur, so I don't repeat
  here.

  The CVE link: https://cve.mitre.org/cgi-
  bin/cvename.cgi?name=CVE-2016-8867

  [Test case]
  $ tmp=$(mktemp -d)
  $ cd $tmp
  $ cat > Dockerfile << EOF
  FROM debian
  RUN useradd example
  RUN id
  USER example
  RUN id
  RUN cat /etc/shadow
  CMD /bin/bash
  EOF
  $ docker build --no-cache -t example .

  The 'cat /etc/shadow' in the Dockerfile should fail.

  [Regression potential]
  We're fixing this by moving to the exact commit of runc the docker 1.12.6 
release expects, so there shouldn't be any issues. In addition 
https://wiki.ubuntu.com/DockerUpdates applies.

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

[Daniel van Vugt]

** Changed in: mir
   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 Released
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 1693893] Re: Fix out-of-bounds read, potential heap buffer overflow, and other CVEs

[Launchpad Bug Tracker]

This bug was fixed in the package vlc - 2.2.6-2ubuntu1

---
vlc (2.2.6-2ubuntu1) artful; urgency=high

  * SECURITY UPDATE: Crash due to Out-of-Bound Heap Memory Write (LP: #1693893)
- fix-CVE-2017-10699.patch
- CVE-2017-10699

 -- Simon Quigley   Mon, 10 Jul 2017 01:33:27 -0500

** Changed in: vlc (Ubuntu Artful)
   Status: In Progress => Fix Released

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

Title:
  Fix out-of-bounds read, potential heap buffer overflow, and other CVEs

Status in vlc package in Ubuntu:
  Fix Released
Status in vlc source package in Trusty:
  In Progress
Status in vlc source package in Xenial:
  Fix Released
Status in vlc source package in Zesty:
  Fix Released
Status in vlc source package in Artful:
  Fix Released

Bug description:
  This bug is meant to track the following public VLC CVEs and their
  status in Ubuntu. Here are the affected Ubuntu releases and the CVEs
  that affect that specific release:

  - Xenial:
    - 2016-5108
    - 2017-10699
    - 2017-8310
    - 2017-8311
    - 2017-8312
    - 2017-8313

  - Zesty:
    - 2017-10699
    - 2017-8310
    - 2017-8311
    - 2017-8312
    - 2017-8313
    - Already fixed in the package:
  - 2016-5108

  - Artful:
    - 2017-10699
    - Already fixed in the package:
  - 2016-5108
  - 2017-8310
  - 2017-8311
  - 2017-8312
  - 2017-8313

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1693893/+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 1693893] Re: Fix out-of-bounds read, potential heap buffer overflow, and other CVEs

[Launchpad Bug Tracker]

This bug was fixed in the package vlc - 2.2.4-14ubuntu2.1

---
vlc (2.2.4-14ubuntu2.1) zesty-security; urgency=high

  * SECURITY UPDATE: Crash due to Out-of-Bound Heap Memory Write (LP: #1693893)
- fix-CVE-2017-10699.patch
- CVE-2017-10699
  * SECURITY UPDATE: Fix potential out of bound reads
- fix-CVE-2017-8310.patch
- CVE-2017-8310
  * SECURITY UPDATE: Fix invalid double increment
- fix-CVE-2017-8311.patch
- CVE-2017-8311
  * SECURITY UPDATE: Fix potential heap buffer overflow
- fix-CVE-2017-8312.patch
- CVE-2017-8312
  * SECURITY UPDATE: ParseJSS: fix out-of-bounds read
- fix-CVE-2017-8313.patch
- CVE-2017-8313

 -- Simon Quigley   Sun, 09 Jul 2017 22:37:06 -0500

** Changed in: vlc (Ubuntu Zesty)
   Status: In Progress => Fix Released

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

Title:
  Fix out-of-bounds read, potential heap buffer overflow, and other CVEs

Status in vlc package in Ubuntu:
  In Progress
Status in vlc source package in Trusty:
  In Progress
Status in vlc source package in Xenial:
  Fix Released
Status in vlc source package in Zesty:
  Fix Released
Status in vlc source package in Artful:
  In Progress

Bug description:
  This bug is meant to track the following public VLC CVEs and their
  status in Ubuntu. Here are the affected Ubuntu releases and the CVEs
  that affect that specific release:

  - Xenial:
    - 2016-5108
    - 2017-10699
    - 2017-8310
    - 2017-8311
    - 2017-8312
    - 2017-8313

  - Zesty:
    - 2017-10699
    - 2017-8310
    - 2017-8311
    - 2017-8312
    - 2017-8313
    - Already fixed in the package:
  - 2016-5108

  - Artful:
    - 2017-10699
    - Already fixed in the package:
  - 2016-5108
  - 2017-8310
  - 2017-8311
  - 2017-8312
  - 2017-8313

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1693893/+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 1693893] Re: Fix out-of-bounds read, potential heap buffer overflow, and other CVEs

[Launchpad Bug Tracker]

This bug was fixed in the package vlc - 2.2.2-5ubuntu0.16.04.3

---
vlc (2.2.2-5ubuntu0.16.04.3) xenial-security; urgency=high

  * SECURITY UPDATE: reject invalid QuickTime IMA files (LP: #1693893)
- fix-CVE-2016-5108.patch
- CVE-2016-5108
  * SECURITY UPDATE: Crash due to Out-of-Bound Heap Memory Write
- fix-CVE-2017-10699.patch
- CVE-2017-10699
  * SECURITY UPDATE: Fix potential out of bound reads
- fix-CVE-2017-8310.patch
- CVE-2017-8310
  * SECURITY UPDATE: Fix invalid double increment
- fix-CVE-2017-8311.patch
- CVE-2017-8311
  * SECURITY UPDATE: Fix potential heap buffer overflow
- fix-CVE-2017-8312.patch
- CVE-2017-8312
  * SECURITY UPDATE: ParseJSS: fix out-of-bounds read
- fix-CVE-2017-8313.patch
- CVE-2017-8313

 -- Simon Quigley   Fri, 07 Jul 2017 06:54:34 -0500

** Changed in: vlc (Ubuntu Xenial)
   Status: In Progress => Fix Released

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

Title:
  Fix out-of-bounds read, potential heap buffer overflow, and other CVEs

Status in vlc package in Ubuntu:
  In Progress
Status in vlc source package in Trusty:
  In Progress
Status in vlc source package in Xenial:
  Fix Released
Status in vlc source package in Zesty:
  In Progress
Status in vlc source package in Artful:
  In Progress

Bug description:
  This bug is meant to track the following public VLC CVEs and their
  status in Ubuntu. Here are the affected Ubuntu releases and the CVEs
  that affect that specific release:

  - Xenial:
    - 2016-5108
    - 2017-10699
    - 2017-8310
    - 2017-8311
    - 2017-8312
    - 2017-8313

  - Zesty:
    - 2017-10699
    - 2017-8310
    - 2017-8311
    - 2017-8312
    - 2017-8313
    - Already fixed in the package:
  - 2016-5108

  - Artful:
    - 2017-10699
    - Already fixed in the package:
  - 2016-5108
  - 2017-8310
  - 2017-8311
  - 2017-8312
  - 2017-8313

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1693893/+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 1703461] [NEW] Update to 3.20.5

[Robert Ancell]

Public bug reported:

[Impact]
Ubuntu 16.04 is running a version of gnome-software based on 3.20.1 which is an 
older stable release (latest stable release is 3.20.5). The Ubuntu changes were 
managed in a git branch that is difficult to manage. We have not been able to 
bring in all the stable changes to this branch and it is difficult to modify. 
We have rebased our changes on 3.20.5 [1] and propose these as a Stable Release 
Update.

[1] https://lists.ubuntu.com/archives/ubuntu-
desktop/2017-June/005011.html

[Test Case]
1. Run GNOME Software

Expected result:
Running latest stable release, no regressions from 3.20.1

Observed result:
Running older release.

[Regression Potential]
Due to the number of changes there is a risk of regression. These changes are 
all on a stable branch, so upstream considers them to be safe. We ran this 
version from a PPA to check for issues, and there don't seem to be any problems.

** Affects: gnome-software (Ubuntu)
 Importance: Medium
 Status: Fix Released

** Affects: gnome-software (Ubuntu Xenial)
 Importance: Wishlist
 Assignee: Robert Ancell (robert-ancell)
 Status: New

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: gnome-software (Ubuntu)
   Status: New => Fix Released

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Undecided => Wishlist

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-software (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Update to 3.20.5

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

Bug description:
  [Impact]
  Ubuntu 16.04 is running a version of gnome-software based on 3.20.1 which is 
an older stable release (latest stable release is 3.20.5). The Ubuntu changes 
were managed in a git branch that is difficult to manage. We have not been able 
to bring in all the stable changes to this branch and it is difficult to 
modify. We have rebased our changes on 3.20.5 [1] and propose these as a Stable 
Release Update.

  [1] https://lists.ubuntu.com/archives/ubuntu-
  desktop/2017-June/005011.html

  [Test Case]
  1. Run GNOME Software

  Expected result:
  Running latest stable release, no regressions from 3.20.1

  Observed result:
  Running older release.

  [Regression Potential]
  Due to the number of changes there is a risk of regression. These changes are 
all on a stable branch, so upstream considers them to be safe. We ran this 
version from a PPA to check for issues, and there don't seem to be any problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1703461/+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 1703025] Re: linux-gcp: 4.8.0-1002.2 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

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

Title:
  linux-gcp: 4.8.0-1002.2 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Invalid => 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/1703025

Title:
  linux-gcp: 4.8.0-1002.2 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Invalid => 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/1703025

Title:
  linux-gcp: 4.8.0-1002.2 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1703025/+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 1701073] Re: CVE-2017-2619 regression breaks symlinks to directories

[Andreas Hasenack]

Reopening the artful task, since the fix isn't there.

** Changed in: samba (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: samba (Ubuntu)
 Assignee: Marc Deslauriers (mdeslaur) => Andreas Hasenack (ahasenack)

** Changed in: samba (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  CVE-2017-2619 regression breaks symlinks to directories

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

Bug description:
  Found in current version in Xenial (4.3.11+dfsg-0ubuntu0.16.04.7).
  When share's path is '/', symlinks do not work properly from Windows
  client. Gives "Cannot Access" error.

  To reproduce:

  1. Install samba and related dependencies

  apt install -y samba

  2. Add a share at the end of the default file that uses '/' as the
  path:

  [reproducer]
  comment = share
  browseable = no
  writeable = yes
  create mode = 0600
  directory mode = 0700
  path = /

  3. Attempt to access a symlink somewhere within the path of the share
  with a Windows client.

  4. Receive "Windows cannot access..." related error

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1701073/+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 1695876] Re: German Documentation file displays incorrect CUPS version

[Eric Desrochers]

# Sponsor review :

Additionally ...

3) A quilt header in DEP3 format is missing in "fix-typo-in-doc-
de.patch"

http://dep.debian.net/deps/dep3/

- Eric

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

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

** Changed in: cups (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: cups (Ubuntu)
 Assignee: Ivy Alexander (ivyalexander) => (unassigned)

** Changed in: cups (Ubuntu Xenial)
 Assignee: (unassigned) => Ivy Alexander (ivyalexander)

** Changed in: cups (Ubuntu Xenial)
   Importance: Undecided => Low

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

** Changed in: cups (Ubuntu Xenial)
   Status: Confirmed => In Progress

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

Title:
  German Documentation file displays incorrect CUPS version

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  In Progress

Bug description:
  The /doc/de/index.html.in file in the package source has an incorrect
  version number written into a header instead of using '@CUPS_VERSION@'
  to populate this file as in the other languages' version of the same
  file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
  having the wrong version once CUPS is installed:

  ...
  

  CUPS 2.0.2
  ...

  instead of:

  ...
  

  CUPS @CUPS_VERSION@
  ...

  resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1695876/+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 1695546] Re: Out of bounds write in resolved with crafted TCP responses

[Dimitri John Ledkov]

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

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

** Also affects: systemd (Ubuntu Artful)
   Importance: High
 Assignee: Dimitri John Ledkov (xnox)
   Status: Fix Released

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

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

** Changed in: systemd (Ubuntu Yakkety)
   Status: New => Fix Released

** Changed in: systemd (Ubuntu Zesty)
   Status: New => Fix Released

** Description changed:

- Certain sizes passed to dns_packet_new can cause it to allocate a buffer
- that's too small. A page-aligned number - sizeof(DnsPacket) +
- sizeof(iphdr) + sizeof(udphdr) will do this - so, on x86 this will be a
- page-aligned number - 80. Eg, calling dns_packet_new with a size of 4016
- will result in an allocation of 4096 bytes, but 108 bytes of this are
- for the DnsPacket struct.
+ [Impact]
+ Certain sizes passed to dns_packet_new can cause it to allocate a buffer 
that's too small. A page-aligned number - sizeof(DnsPacket) + sizeof(iphdr) + 
sizeof(udphdr) will do this - so, on x86 this will be a page-aligned number - 
80. Eg, calling dns_packet_new with a size of 4016 will result in an allocation 
of 4096 bytes, but 108 bytes of this are for the DnsPacket struct.
  
  A malicious DNS server can exploit this by responding with a specially
  crafted TCP payload to trick systemd-resolved in to allocating a buffer
  that's too small, and subsequently write arbitrary data beyond the end
  of it.
  
  To demonstrate this you can run the attached python script. This is a
  mock DNS server that sends a response where the first two bytes of the
  TCP payload specify a size of 4016 (note, this size is picked to trigger
  an out of bounds write on x86 - you'll probably need to pick a different
  number for x86-64). You'll need to temporarily set your DNS server to
  127.0.0.1.
+ 
+ [Testcase]
+ Launch the attached script on i386, point resolved at the started dns server, 
execute a dns query via resolved observe that it crashes.
+ Upgrade systemd package and observe that resolved no longer crashes.
+ 
+ [Regression Potential]
+ Low, resolved is not used by default in xenial. This is a bug fix to 
resolved, in case somebody does use resolved in xenial.

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

Title:
  Out of bounds write in resolved with crafted TCP responses

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

Bug description:
  [Impact]
  Certain sizes passed to dns_packet_new can cause it to allocate a buffer 
that's too small. A page-aligned number - sizeof(DnsPacket) + sizeof(iphdr) + 
sizeof(udphdr) will do this - so, on x86 this will be a page-aligned number - 
80. Eg, calling dns_packet_new with a size of 4016 will result in an allocation 
of 4096 bytes, but 108 bytes of this are for the DnsPacket struct.

  A malicious DNS server can exploit this by responding with a specially
  crafted TCP payload to trick systemd-resolved in to allocating a
  buffer that's too small, and subsequently write arbitrary data beyond
  the end of it.

  To demonstrate this you can run the attached python script. This is a
  mock DNS server that sends a response where the first two bytes of the
  TCP payload specify a size of 4016 (note, this size is picked to
  trigger an out of bounds write on x86 - you'll probably need to pick a
  different number for x86-64). You'll need to temporarily set your DNS
  server to 127.0.0.1.

  [Testcase]
  Launch the attached script on i386, point resolved at the started dns server, 
execute a dns query via resolved observe that it crashes.
  Upgrade systemd package and observe that resolved no longer crashes.

  [Regression Potential]
  Low, resolved is not used by default in xenial. This is a bug fix to 
resolved, in case somebody does use resolved in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1695546/+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 1702109] Re: linux-gke: 4.4.0-1019.19 -proposed tracker

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

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

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

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

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

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

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

Title:
  linux-aws: 4.4.0-1023.32 -proposed tracker

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

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

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

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

[Kleber Sacilotto de Souza]

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1702103
  phase: Uploaded
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1702106/+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 1703372] [NEW] [SRU] python-openstackclient 2.3.1point release for xenial

[Corey Bryant]

Public bug reported:

[Description]
Xenial currently has python-openstackclient 2.3.0. This SRU is to release the 
stable point release of python-openstackclient 2.3.1.

This contains 2 bug fixes:

21cbc1b14e61f712278b6551a9c5e2cfc4624f5f arguments are not locale decoded into 
Unicode
53a79c33f88cea83fb2a90408dd3f5e8dd48a2f5 Fix SSL/TLS verification for network 
commands

[Test Case]
Perform regression testing by juju deploying two openstack clouds, one against 
-proposed and one against -updates, and then run tempest integration smoke 
tests[1] to verify those deployed clouds, and evaluate any differences in 
results. [1] https://github.com/openstack/tempest/blob/master/README.rst

[Regression Potential]
Low. This is a stable point release from upstream.

** Affects: python-openstackclient (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: python-openstackclient (Ubuntu Xenial)
 Importance: Medium
 Assignee: Corey Bryant (corey.bryant)
 Status: Triaged

** Also affects: python-openstackclient (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: python-openstackclient (Ubuntu)
   Status: New => Invalid

** Changed in: python-openstackclient (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: python-openstackclient (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: python-openstackclient (Ubuntu Xenial)
 Assignee: (unassigned) => Corey Bryant (corey.bryant)

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

Title:
  [SRU] python-openstackclient 2.3.1point release for xenial

Status in python-openstackclient package in Ubuntu:
  Invalid
Status in python-openstackclient source package in Xenial:
  Triaged

Bug description:
  [Description]
  Xenial currently has python-openstackclient 2.3.0. This SRU is to release the 
stable point release of python-openstackclient 2.3.1.

  This contains 2 bug fixes:

  21cbc1b14e61f712278b6551a9c5e2cfc4624f5f arguments are not locale decoded 
into Unicode
  53a79c33f88cea83fb2a90408dd3f5e8dd48a2f5 Fix SSL/TLS verification for network 
commands

  [Test Case]
  Perform regression testing by juju deploying two openstack clouds, one 
against -proposed and one against -updates, and then run tempest integration 
smoke tests[1] to verify those deployed clouds, and evaluate any differences in 
results. [1] https://github.com/openstack/tempest/blob/master/README.rst

  [Regression Potential]
  Low. This is a stable point release from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-openstackclient/+bug/1703372/+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 1570491] Re: Network client (neutron) initialized without specifying region

[Corey Bryant]

Ubuntu SRU details:

[Description]
The newInitialize neutron client with region name

The openstack client initializes all clients except neutron with the
region name. This prevents openstack client from using network related
commands in multi-region deployments.

[Test Case]
Deploy a multi-region cloud and use the openstack client against it. The first 
network service is selected.

[Regression Potential]
Low. This is a small bug fix that is being backported from version 2.4.0 to 
2.3.1.

** Also affects: python-openstackclient (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: python-openstackclient (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: python-openstackclient (Ubuntu)
   Status: New => Invalid

** Changed in: python-openstackclient (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: python-openstackclient (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: python-openstackclient (Ubuntu Xenial)
 Assignee: (unassigned) => Corey Bryant (corey.bryant)

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

Title:
  Network client (neutron) initialized without specifying region

Status in python-openstackclient:
  Fix Released
Status in python-openstackclient package in Ubuntu:
  Invalid
Status in python-openstackclient source package in Xenial:
  Triaged

Bug description:
  All network (neutron) related commands does not take region into
  account. In configuration where are more then one region, first one
  for network service is selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-openstackclient/+bug/1570491/+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 1571816] Re: Gnome Software catalog entry missing for Wine

[Launchpad Bug Tracker]

This bug was fixed in the package wine1.6 - 1:1.6.2-0ubuntu14.2

---
wine1.6 (1:1.6.2-0ubuntu14.2) xenial; urgency=medium

  * Set X-AppStream-Ignore=true for included .desktop files to correct
wine's display name in the Software app (LP: #1571816)

 -- Jeremy Bicha   Wed, 22 Feb 2017 19:15:58 -0500

** Changed in: wine1.6 (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/1571816

Title:
  Gnome Software catalog entry missing for Wine

Status in wine package in Ubuntu:
  Fix Released
Status in wine-development package in Ubuntu:
  Fix Released
Status in wine1.6 package in Ubuntu:
  Invalid
Status in wine-development source package in Xenial:
  Fix Released
Status in wine1.6 source package in Xenial:
  Fix Released
Status in wine source package in Yakkety:
  Fix Released
Status in wine-development source package in Yakkety:
  Fix Released

Bug description:
  Original Bug Report
  ===
  A very beautiful app, but is missing in the Gnome-Software catalog!!!
  You can install it from terminal but if you search for it in gnome-software  
you can´t install it.

  Impact
  ==
  If you search for Wine in the Software app in Ubuntu 16.04 LTS or 16.10, you 
get no results for wine.

  Test Case
  =
  Note that you probably need to wait a day or two after this package is 
published to -proposed for the appstream generator to work and this test case 
to work.

  1. Enable proposed updates
  2. Open the Software app. Search for wine

  There should be two wine entries, one named Wine, one named Wine (development 
version).
  3. Optionally install wine

  Note that wine in Ubuntu 16.10 and newer and wine-development in all
  versions does not currently install any .desktop launchers. One way to
  verify that wine is installed by running wineconsole-stable or
  wineconsole-development

  For wine in Ubuntu 16.04, you can verify wine1.6 is installed by
  running the Notepad app which should be installed.

  Regression Potential
  
  Almost none. This just adds an app icon and appstream metadata.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1571816/+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 1394582] Re: patch - fix logic flaw, make seahorse-tool's encrypt command work

[Bug Watch Updater]

** Changed in: libcryptui (Debian)
   Status: Confirmed => Fix Released

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

Title:
  patch - fix logic flaw, make seahorse-tool's encrypt command work

Status in libcryptui:
  Fix Released
Status in libcryptui package in Ubuntu:
  Triaged
Status in libcryptui source package in Xenial:
  Triaged
Status in libcryptui package in Debian:
  Fix Released

Bug description:
  [Impact]

  The prompt recipients dialog that's called when you run seahorse-tool
  with --encrypt argument is broken.

  Clicking on OK button does nothing, and encryption of the chosen file
  does not happen.

  The prompt recipients dialog has been broken in this commit:

  
https://github.com/GNOME/libcryptui/commit/cd74aa6bf810a5ce0935d2ec89d6db64dbbde24d
  #diff-f0ea8a1eef5386b0149314d2a1743e85L202

  The attached debdiffs fix the logic there and makes seahorse-tool's
  encrypt command work again. Therefore, seahorse plugins for both
  Nautilus and Nemo should start working as well. Clicking on OK button
  works, and the file gets encrypted as it should.

  So the fix should be ported to the listed stable releases. In 14.04
  things haven't been broken yet.

  [Test Case]

  Steps to reproduce:

  1. Run "seahorse-tool --encrypt some_file".
  2. In the dialog that appears, choose the recipient by clicking on a checkbox.
  3. Click on OK button.
  4. The dialog just closes and the file doesn't get encrypted as it should.

  [Regression Potential]

  No regressions have been found during several months of testing. I
  consider the regression risk to be very low here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libcryptui/+bug/1394582/+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 1703025] Re: linux-gcp: 4.8.0-1002.2 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

** Description changed:

  This bug is for tracking the 4.8.0-1002.2 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux-gcp: 4.8.0-1002.2 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1703025/+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 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler

[xylo]

** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-375 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
  not supported by compiler

Status in dkms package in Ubuntu:
  Invalid
Status in gcc-defaults package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Installing the latest 4.4.0-22 kernel ends with that error logged into 
dkmsbuildlog
  (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine)

  https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt

  make "CC=cc"  KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build 
M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 
NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build 
NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia 
nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules
  make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic'
  arch/x86/Makefile:133: stack-protector enabled but compiler support broken
  Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: 
-fstack-protector-strong not supported by compiler

  the latest error logged is:

  /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error:
  code model kernel does not support PIC mode

  Looks like it is related to the latest changes updates: gcc-6/gcc-5 
5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the 
packages built with gcc-6)
  Maybe some alternatives has not been updated to take care of these changes, 
as asked some time ago:
  http://askubuntu.com/questions/26498/choose-gcc-and-g-version

  This has been firstly reported against a nvidia crash:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gcc 4:5.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 08:41:32 2016
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2014 F pulseaudio
   /dev/snd/pcmC0D0p:   oem2014 F...m pulseaudio
   /dev/snd/controlC0:  oem2014 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: ubuntu
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  yakkety
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  

[Group.of.nepali.translators] [Bug 1703025] Re: linux-gcp: 4.8.0-1002.2 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  linux-gcp: 4.8.0-1002.2 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

[Andy Whitcroft]

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Tags added: kernel-block-ppa

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => 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/1703025

Title:
  linux-gcp: 4.8.0-1002.2 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

[Brad Figg]

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the 4.8.0-1002.2 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-stable-phase-changed:Friday, 07. July 2017 21:31 UTC
  kernel-stable-phase:Packaging
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Packaging

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.8.0-1002.2 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-stable-phase-changed:Friday, 07. July 2017 21:31 UTC
- kernel-stable-phase:Packaging
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Packaging
+ kernel-stable-phase-changed:Monday, 10. July 2017 10:47 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.8.0-1002.2 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
- phase: Packaging
- kernel-stable-phase-changed:Monday, 10. July 2017 10:47 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux-gcp: 4.8.0-1002.2 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1703025/+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 1576424] Re: Gimp crashes with text tool & caps lock

[Launchpad Bug Tracker]

This bug was fixed in the package gtk+2.0 - 2.24.30-1ubuntu1.16.04.1

---
gtk+2.0 (2.24.30-1ubuntu1.16.04.1) xenial; urgency=medium

  * debian/patches/lp1576424-explicitly-disconnect-keymap-signals.patch
- GtkEntry: Explicitly disconnect keymap signals. (LP: #1576424)

 -- Martin Wimpress   Tue, 04 Oct 2016
17:07:26 +0100

** Changed in: gtk+2.0 (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/1576424

Title:
  Gimp crashes with text tool & caps lock

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Xenial:
  Fix Released
Status in gtk+2.0 source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Gimp crashes with a segfault when I use caps lock while renaming a
  layer. It is possible Caps lock causes crashes in other events also.

  [Test Case]

  Steps to reproduce:

  1. Open a new blank gimp document
  2. select the text tool
  3. type a couple of words of text (gimp will create a text layer above the 
background layer)
  4. with the text tool still selected, click on the background layer (just to 
move away from the text layer)
  5. now double click on the text layer to rename the layer (layer name gets 
highlighted)
  6. press the caps lock key
  7. click on the background layer again (without renaming or doing anything to 
the text layer)
  Now repeat steps 5 and 6.
  Gimp crashes.

  [Regression Potential]

  None expected. The patch used has been taken from upstream
  development.

  
https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad

  Packages for Xenial and Yakkety have been built in a PPA and
  regression tested.

  [ Other Info ]

  I can force this to happen every time I launch Gimp. Rebooting makes
  no difference. It seems to be the second time I press caps lock that
  forces the crash. I tried launching Gimp with caps lock on vs caps
  lock off, but I don't believe it made any difference. I can force a
  crash every time following the above sequence.

  I deleted my gimp preferences folder then rebooted for good measure.
  Gimp created a fresh preferences folder, but it hasn't solved the
  problem. I was originally in single window mode, but the new
  preferences folder put me back to multi window, but it crashes either
  way.

  I ran dmesg | tail after the crash and got the following line:

  gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0
  error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000]

  I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver
  (available from the Additional Drivers tab). In that same tab, I also
  have enabled Processor microcode firmware for Intel CPUs. Terminal
  tells me Gimp version is 2.8.16-1ubuntu1

  I'm not very experienced with bug reporting and not sure what other
  information I need to supply. Gimp was absolutely rock solid on this
  machine with 15.10, so it may be a Xubuntu issue.

  Hope someone can take a look at this. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1576424/+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 1679435] Re: GNOME Software fails to install .deb packages that trigger debconf prompts

[Amr Ibrahim]

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

Title:
  GNOME Software fails to install .deb packages that trigger debconf
  prompts

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

Bug description:
  [Impact]
  GNOME Software doesn't provide debconf support when using aptd. This means 
any package installation / upgrade that triggers a debconf prompt can fail. The 
requested package might not do a prompt, but some dependency can.

  [Test Case]
  1. Install a .deb file that causes a debconf prompt 
(https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests contains a test 
package).
  $ gnome-software --local-filename=noisy-fake-driver_0.6_amd64.deb

  Expected result:
  Package is installed after a debconf prompt is shown.

  Observed result:
  Package fails to install, no prompt is shown.

  [Regression Potential]
  The solution was to provide a pipe when using aptd to allow the debconf 
prompt to be handled in the session. This could introduce new bugs and/or 
security issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1679435/+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 1639507] Re: unity-control-center in installed software is listed with wrong icon and title

[Launchpad Bug Tracker]

This bug was fixed in the package unity-control-center -
15.04.0+16.04.20170214-0ubuntu1

---
unity-control-center (15.04.0+16.04.20170214-0ubuntu1) xenial; urgency=medium

  [ Iain Lane ]
  * user-accounts: Reset the AccountsService password mode when setting
the password. There's a codepath for directly setting the password
when the user is setting their own, but this doesn't set the AS mode
back to ACT_USER_PASSWORD_MODE_REGULAR. If you don't change this and
you're in ACT_USER_PASSWORD_MODE_NONE, then you end up staying in
the nopasswdlogin group. (LP: #1630156)

  [ Robert Ancell ]
  * Add AppData (LP: #1639507)

 -- i...@orangesquash.org.uk (i...@orangesquash.org.uk)  Tue, 14 Feb
2017 09:17:30 +

** Changed in: unity-control-center (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/1639507

Title:
  unity-control-center in installed software is listed with wrong icon
  and title

Status in unity-control-center package in Ubuntu:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Released
Status in unity-control-center source package in Yakkety:
  Fix Released
Status in unity-control-center source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  In Ubuntu Software under Installed programs the listing for 
gnome-control-center package has title "Wacom Tablet" and tablet icon.
  This is dangerously confusing, as average user can easily remove control 
center without knowing it.
  I propose disabling gnome-control-center removal from Ubuntu Software by 
moving it to "System Applications" section.

  [Test Case]
  1. From a terminal run:
  $ gnome-software --details-pkg unity-control-center

  Observed result:
  The title/description is from one of the panels inside u-c-c, e.g. "Wacom 
Tablet" or "Universal Access".

  Expected result:
  The title and description should be for unity-control-center.
  NOTE: This requires the appdata to be updated and re-downloaded before this 
can occur.

  [Regression Potential]
  Low, we now just distribute appdata information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1639507/+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 1630156] Re: No password needed to Log in after cancel the password and then reset again

[Launchpad Bug Tracker]

This bug was fixed in the package unity-control-center -
15.04.0+16.04.20170214-0ubuntu1

---
unity-control-center (15.04.0+16.04.20170214-0ubuntu1) xenial; urgency=medium

  [ Iain Lane ]
  * user-accounts: Reset the AccountsService password mode when setting
the password. There's a codepath for directly setting the password
when the user is setting their own, but this doesn't set the AS mode
back to ACT_USER_PASSWORD_MODE_REGULAR. If you don't change this and
you're in ACT_USER_PASSWORD_MODE_NONE, then you end up staying in
the nopasswdlogin group. (LP: #1630156)

  [ Robert Ancell ]
  * Add AppData (LP: #1639507)

 -- i...@orangesquash.org.uk (i...@orangesquash.org.uk)  Tue, 14 Feb
2017 09:17:30 +

** Changed in: unity-control-center (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/1630156

Title:
  No password needed to Log in after cancel the password and then reset
  again

Status in Light Display Manager:
  Invalid
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project trusty series:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Released
Status in unity-control-center source package in Yakkety:
  Fix Released

Bug description:
  [ Description ]

  If you use unity-control-center to set the current user from "Log in
  without a password" to having a password again, the user is not
  removed from the 'nopasswdlogin' UNIX group, and so can log in without
  a password still.

  [ Test case ]

  1. Open the dash, type "User Accounts", open the user accounts panel of 
unity-control-center.
  2. Make sure the current user (which must be an admin) is selected in the 
list of user's on the left hand side.
  3. Click "Unlock" at the top right, and enter the user's password.
  4. Click the dots to the right of "Password", to open the dialog where you 
can change the password mode.
  5. In the combo box at the top, select "Log in without a password". Save the 
dialog.
  6. Open a terminal, and execute `grep nopasswdlogin /etc/group'. Note that 
the current user is present.
  7. Re-open the password dialog as in step 4.
  8. Select "Set a password now", and set a password. Save the dialog.
  9. Open a terminal, and execute `grep nopasswdlogin /etc/group'.

  At step 9, if the bug is present then the user will still be in the
  group. If it is fixed then the user will not.

  [ Fix ]

  unity-control-center's user-accounts panel contains a codepath to call
  `passwd' directly when changing the current user's password. There's
  another path when setting the password for a different user which uses
  AccountsService. In the former codepath, the AccountsService call
  required to remove the user from `nopasswdlogin' is not executed
  (act_user_set_password_mode (..., ACT_USER_PASSWORD_MODE_REGULAR)).

  The proposed fix (in the attached MP) is to always make this call when
  setting a password, even in this passwd case.

  [ QA ]

  Run the test case above. Additionally,

   - Try to use the dialog to change passwords without unlocking it.
   - Try to change both the current and another user's password.

  Make sure the nopasswdlogin membership is right at all times and the
  new password always gets applied (e.g. try logging out and in to check
  the settings).

  [ Regression potential ]

  The fix changes a couple of things

- We now call act_user_set_password_mode () after running passwd.
- We now call act_user_set_password () before act_user_set_password_mode 
(), which is the opposite of the previous order.

  AFAIK both of these changes are fine, but we should run the QA tests
  above to get confidence that they didn't break password setting.

  [ Original description ]

  1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system 
setting.
  2. Click "Password --> Action --> Log in without password -->Change to clear 
Log in password. (as doing so, the user is added to group "nopasswdlogin")
  3. Check that the user is in the nopasswdlogin group
  4. Then do the similar action "Set a password now" as the same way to set Log 
in password.
  5. Check that the user is *not* in the nopasswdlogin group.

  The key problem is: it won't remove user from nopasswdlogin in step 4.
  At step 5, you are left in the group.

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

[Group.of.nepali.translators] [Bug 1639507] Re: unity-control-center in installed software is listed with wrong icon and title

[Launchpad Bug Tracker]

This bug was fixed in the package unity-control-center -
15.04.0+16.10.20170214-0ubuntu1

---
unity-control-center (15.04.0+16.10.20170214-0ubuntu1) yakkety; urgency=medium

  [ Iain Lane ]
  * user-accounts: Reset the AccountsService password mode when setting
the password. There's a codepath for directly setting the password
when the user is setting their own, but this doesn't set the AS mode
back to ACT_USER_PASSWORD_MODE_REGULAR. If you don't change this and
you're in ACT_USER_PASSWORD_MODE_NONE, then you end up staying in
the nopasswdlogin group. (LP: #1630156)

  [ Robert Ancell ]
  * Add AppData (LP: #1639507)

 -- i...@orangesquash.org.uk (i...@orangesquash.org.uk)  Tue, 14 Feb
2017 09:16:44 +

** Changed in: unity-control-center (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/1639507

Title:
  unity-control-center in installed software is listed with wrong icon
  and title

Status in unity-control-center package in Ubuntu:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Released
Status in unity-control-center source package in Yakkety:
  Fix Released
Status in unity-control-center source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  In Ubuntu Software under Installed programs the listing for 
gnome-control-center package has title "Wacom Tablet" and tablet icon.
  This is dangerously confusing, as average user can easily remove control 
center without knowing it.
  I propose disabling gnome-control-center removal from Ubuntu Software by 
moving it to "System Applications" section.

  [Test Case]
  1. From a terminal run:
  $ gnome-software --details-pkg unity-control-center

  Observed result:
  The title/description is from one of the panels inside u-c-c, e.g. "Wacom 
Tablet" or "Universal Access".

  Expected result:
  The title and description should be for unity-control-center.
  NOTE: This requires the appdata to be updated and re-downloaded before this 
can occur.

  [Regression Potential]
  Low, we now just distribute appdata information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1639507/+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 1692127] Re: duplicate signature for Package problems can be too short

[Launchpad Bug Tracker]

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

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

  * test/test_signal_crashes.py: delete the test which uses an arbitrary
unpredictable core file size.

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

  * test/test_signal_crashes.py: a ulimit of 1M bytes isn't enough to produce
a core file anymore so bump it to 10M.

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

  * data/general-hooks/ubuntu.py: Modify how a duplicate signature is created
for package installation failures. (LP: #1692127)

 -- Brian Murray   Thu, 29 Jun 2017 13:30:39 -0700

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

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

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

Title:
  duplicate signature for Package problems can be too short

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

Bug description:
  [Impact]
  apport is creating a shorter than appropriate duplicate signature in 
apport-package bug reports which can lead to misconsolidation and confused 
developers.

  [Test Case]
  1) Boot a system with an old kernel installed or a freshly installed system
  2) edit /etc/default/grub and replace a ` with a '
  3) Upgrade the kernel, watch it crash
  4) Discover a crash report with a DuplicateSignature whose 2nd line starts 
with "Examining"

  With the version of the package from -proposed the DuplicateSignature
  in this case should really have a 2nd line that starts with 'Setting
  up linux-image* ...'. While in this particular case not much is lost
  in other cases valuable information will be missing.

  [Regression Potential]
  The code change is correct and has been tested in artful, additionally I'm 
using the same regular expression to clean up apport-package reports as they 
come in to LP. The only risk here is a typo in the patch that would cause the 
hook (the change is in the ubuntu general hook) to error out which apport would 
handle gracefully and we just wouldn't have a DuplicateSignature.

  [The Original Description]
  Steve brought up bug 1691983 and how it's duplicate signature is missing 
information.  It contains:

  package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  Installing for x86_64-efi platform.
  Installation finished. No error reported.
  Running in non-interactive mode, doing nothing.
  dpkg: error processing package shim-signed (--configure):
   subprocess installed post-installation script returned error exit status 1

  But is missing:

  Setting up shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
  locale: Cannot set LC_CTYPE to default locale: No such file or directory
  locale: Cannot set LC_MESSAGES to default locale: No such file or directory
  locale: Cannot set LC_ALL to default locale: No such file or directory
  debconf: unable to initialize frontend: Passthrough
  debconf: (Cannot connect to /tmp/aptdaemon-7jrqb_du/debconf.socket: 
Connection refused at (eval 18) line 3.)
  debconf: falling back to frontend: Noninteractive

  This is because of the following code in data/general-hooks/ubuntu.py:

  145 PKG_MSGS = ('Authenticating', 'De-configuring', 'Examining',
  146 'Installing ', 'Preparing', 'Processing 
triggers', 'Purging',
  147 'Removing', 'Replaced', 'Replacing', 'Setting up',
  148 'Unpacking', 'Would remove')
  149 for line in termlog.split('\n'):
  150 if line.startswith(PKG_MSGS):
  151 dupe_sig = '%s\n' % line
  152 continue

  The shim-signed package prints a line starts with "Installing " and
  that matches PKG_MSGS so we reset the dupe_sig because that's a
  message we'd expect from a package manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1692127/+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 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Łukasz Zemczak]

Since no one is able to verify the yakkety version of this SRU for so
long, I am dropping the dbus version with the fix for the bug from
yakkety-proposed.

** Changed in: dbus (Ubuntu Yakkety)
   Status: Fix Committed => Won't Fix

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Fix Released
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Won't Fix
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  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
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To 

[Group.of.nepali.translators] [Bug 1692127] Re: duplicate signature for Package problems can be too short

[Launchpad Bug Tracker]

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

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

  * test/test_signal_crashes.py: delete the test which uses an arbitrary
unpredictable core file size.

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

  * test/test_signal_crashes.py: a ulimit of 1M bytes isn't enough to produce
a core file anymore so bump it to 10M.

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

  * data/general-hooks/ubuntu.py: Modify how a duplicate signature is created
for package installation failures. (LP: #1692127)

 -- Brian Murray   Thu, 29 Jun 2017 11:41:12 -0700

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

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

Title:
  duplicate signature for Package problems can be too short

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

Bug description:
  [Impact]
  apport is creating a shorter than appropriate duplicate signature in 
apport-package bug reports which can lead to misconsolidation and confused 
developers.

  [Test Case]
  1) Boot a system with an old kernel installed or a freshly installed system
  2) edit /etc/default/grub and replace a ` with a '
  3) Upgrade the kernel, watch it crash
  4) Discover a crash report with a DuplicateSignature whose 2nd line starts 
with "Examining"

  With the version of the package from -proposed the DuplicateSignature
  in this case should really have a 2nd line that starts with 'Setting
  up linux-image* ...'. While in this particular case not much is lost
  in other cases valuable information will be missing.

  [Regression Potential]
  The code change is correct and has been tested in artful, additionally I'm 
using the same regular expression to clean up apport-package reports as they 
come in to LP. The only risk here is a typo in the patch that would cause the 
hook (the change is in the ubuntu general hook) to error out which apport would 
handle gracefully and we just wouldn't have a DuplicateSignature.

  [The Original Description]
  Steve brought up bug 1691983 and how it's duplicate signature is missing 
information.  It contains:

  package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  Installing for x86_64-efi platform.
  Installation finished. No error reported.
  Running in non-interactive mode, doing nothing.
  dpkg: error processing package shim-signed (--configure):
   subprocess installed post-installation script returned error exit status 1

  But is missing:

  Setting up shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
  locale: Cannot set LC_CTYPE to default locale: No such file or directory
  locale: Cannot set LC_MESSAGES to default locale: No such file or directory
  locale: Cannot set LC_ALL to default locale: No such file or directory
  debconf: unable to initialize frontend: Passthrough
  debconf: (Cannot connect to /tmp/aptdaemon-7jrqb_du/debconf.socket: 
Connection refused at (eval 18) line 3.)
  debconf: falling back to frontend: Noninteractive

  This is because of the following code in data/general-hooks/ubuntu.py:

  145 PKG_MSGS = ('Authenticating', 'De-configuring', 'Examining',
  146 'Installing ', 'Preparing', 'Processing 
triggers', 'Purging',
  147 'Removing', 'Replaced', 'Replacing', 'Setting up',
  148 'Unpacking', 'Would remove')
  149 for line in termlog.split('\n'):
  150 if line.startswith(PKG_MSGS):
  151 dupe_sig = '%s\n' % line
  152 continue

  The shim-signed package prints a line starts with "Installing " and
  that matches PKG_MSGS so we reset the dupe_sig because that's a
  message we'd expect from a package manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1692127/+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 1700373] Re: intel-microcode is out of date, version 20170511 fixes errata on 6th and 7th generation platforms

[Launchpad Bug Tracker]

This bug was fixed in the package intel-microcode -
3.20170511.1~ubuntu17.04.0

---
intel-microcode (3.20170511.1~ubuntu17.04.0) zesty; urgency=medium

  * Backport of new upstream microde release to address Hyper Threading
bug. LP: #1700373.

intel-microcode (3.20170511.1) unstable; urgency=medium

  * New upstream microcode datafile 20170511
+ Updated Microcodes:
  sig 0x000306c3, pf_mask 0x32, 2017-01-27, rev 0x0022, size 22528
  sig 0x000306d4, pf_mask 0xc0, 2017-01-27, rev 0x0025, size 17408
  sig 0x000306f2, pf_mask 0x6f, 2017-01-30, rev 0x003a, size 32768
  sig 0x000306f4, pf_mask 0x80, 2017-01-30, rev 0x000f, size 16384
  sig 0x00040651, pf_mask 0x72, 2017-01-27, rev 0x0020, size 20480
  sig 0x00040661, pf_mask 0x32, 2017-01-27, rev 0x0017, size 24576
  sig 0x00040671, pf_mask 0x22, 2017-01-27, rev 0x0017, size 11264
  sig 0x000406e3, pf_mask 0xc0, 2017-04-09, rev 0x00ba, size 98304
  sig 0x000406f1, pf_mask 0xef, 2017-03-01, rev 0xb21, size 26624
  sig 0x000506e3, pf_mask 0x36, 2017-04-09, rev 0x00ba, size 98304
+ This release fixes undisclosed errata on the desktop, mobile and
  server processor models from the Haswell, Broadwell, and Skylake
  families, including even the high-end multi-socket server Xeons
+ Likely fix the TSC-Deadline LAPIC errata (BDF89, SKL142 and
  similar) on several processor families
+ Fix erratum BDF90 on Xeon E7v4, E5v4(?) (closes: #862606)
+ Likely fix serious or critical Skylake errata: SKL138/144,
  SKL137/145, SLK149
* Likely fix nightmare-level Skylake erratum SKL150.  Fortunately,
  either this erratum is very-low-hitting, or gcc/clang/icc/msvc
  won't usually issue the affected opcode pattern and it ends up
  being rare.
  SKL150 - Short loops using both the AH/BH/CH/DH registers and
  the corresponding wide register *may* result in unpredictable
  system behavior.  Requires both logical processors of the same
  core (i.e. sibling hyperthreads) to be active to trigger, as
  well as a "complex set of micro-architectural conditions"
  * source: remove unneeded intel-ucode/ directory
Since release 20170511, upstream ships the microcodes both in .dat
format, and as Linux-style split /lib/firmware/intel-ucode files.
It is simpler to just use the .dat format file for now, so remove
the intel-ucode/ directory. Note: before removal, it was verified
that there were no discrepancies between the two microcode sets
(.dat and intel-ucode/)
  * source: remove superseded upstream data file: 20161104

 -- Dimitri John Ledkov   Mon, 26 Jun 2017 16:22:13
+0100

** Changed in: intel-microcode (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/1700373

Title:
  intel-microcode is out of date, version 20170511 fixes errata on 6th
  and 7th generation platforms

Status in intel-microcode package in Ubuntu:
  Fix Released
Status in intel-microcode source package in Trusty:
  Won't Fix
Status in intel-microcode source package in Xenial:
  Confirmed
Status in intel-microcode source package in Yakkety:
  Confirmed
Status in intel-microcode source package in Zesty:
  Fix Released
Status in intel-microcode source package in Artful:
  Fix Released

Bug description:
  [Impact]

  * A security fix has been made available as part of intel-microcode
  * It is advisable to apply it
  * Thus an SRU of the latest intel-microcode is desirable for all stable 
releases

  [Test Case]

  * Upgrade intel-microcode package, if it is already installed / one is
  running on Intel CPUs

  * Reboot and verify no averse results, and/or that microcode for your
  cpu was loaded as expected.

  [Test case reporting]
  * Please paste the output of:

  dpkg-query -W intel-microcode
  grep -E 'model|stepping' /proc/cpuinfo | sort -u
  journalctl -k | grep microcode

  [Regression Potential]
  Microcode are proprietary blobs, and can cause any number of new errors and 
regressions. Microcode bugs have been reported before, therefore longer than 
usual phasing and monitoring of intel-microcode bugs should be done with extra 
care.

  [Other]
  caml discussion describing test case to reproduce the crash.
  https://caml.inria.fr/mantis/view.php?id=7452

  =

  [Original bug report]

  NB: I am *not* directly affected by this bug.

  Henrique emailed a warning to Debian devel today [1] on a potentially
  serious issue with (sky|kaby)lake processors. Excerpt:

  "This warning advisory is relevant for users of systems with the Intel
  processors code-named "Skylake" and "Kaby Lake".  These are: the 6th and
  7th generation Intel Core processors (desktop, embedded, mobile 

[Group.of.nepali.translators] [Bug 1700027] Re: Update google compute-image-packages to 20170622

[Launchpad Bug Tracker]

This bug was fixed in the package gce-compute-image-packages -
20170622-0ubuntu1~16.04.0

---
gce-compute-image-packages (20170622-0ubuntu1~16.04.0) xenial; urgency=medium

  * Backport to xenial.
  * New upstream version 20170622 (LP: #1700027)
- Add Linux guest environment support for OS Login
  * Add google-compute-engine-oslogin binary package

 -- Balint Reczey   Fri, 23 Jun 2017 10:42:27 +0200

** Changed in: gce-compute-image-packages (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/1700027

Title:
  Update google compute-image-packages to 20170622

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  Fix Released
Status in gce-compute-image-packages source package in Xenial:
  Fix Released
Status in gce-compute-image-packages source package in Yakkety:
  Fix Released
Status in gce-compute-image-packages source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  compute-image-packages is provided by Google for installation within
  guests that run on Google Compute Engine. It is a collection of tools
  and daemons, packaged as gce-compute-image-packages, that ensure that
  the Ubuntu images published to GCE run properly on their platform.

  Cloud platforms evolve at a rate that can't be handled in six-month
  increments, and they will often develop features that they would like
  to be available to customers who don't want to upgrade from earlier
  Ubuntu releases. As such, updating gce-compute-image-packages to more
  recent upstream releases is required within all Ubuntu releases, so
  they continue to function properly in their environment.

  With this release we also add a new binary package to the suite -
  google-compute-engine-oslogin which is for a future feature of using
  OS Login on GCE VM instances.

  [Test Case]

  When a new version of gce-compute-image-packages is uploaded to
  -proposed, the following will be done:

   * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
   * the CPC team will write new automated tests to cover new testable 
functionality (if any) in the new package
   * the automated testing that the CPC team normally runs against GCE images 
before they are published will be run against the -proposed image
   * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

  If all the testing indicates that the image containing the new package
  is acceptable, verification will be considered to be done.

  [Other Information]

  This bug is used for tracking of releasing the new upstream version
  for all supported series, as per the approved policy mentioned in the
  following MRE:

  https://wiki.ubuntu.com/gce-compute-image-packages-Updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1700027/+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 1700027] Re: Update google compute-image-packages to 20170622

[Launchpad Bug Tracker]

This bug was fixed in the package gce-compute-image-packages -
20170622-0ubuntu1~16.10.0

---
gce-compute-image-packages (20170622-0ubuntu1~16.10.0) yakkety; urgency=medium

  * Backport to yakkety.
  * New upstream version 20170622 (LP: #1700027)
- Add Linux guest environment support for OS Login
  * Add google-compute-engine-oslogin binary package

 -- Balint Reczey   Fri, 23 Jun 2017 10:42:27 +0200

** Changed in: gce-compute-image-packages (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: gce-compute-image-packages (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/1700027

Title:
  Update google compute-image-packages to 20170622

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  Fix Released
Status in gce-compute-image-packages source package in Xenial:
  Fix Released
Status in gce-compute-image-packages source package in Yakkety:
  Fix Released
Status in gce-compute-image-packages source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  compute-image-packages is provided by Google for installation within
  guests that run on Google Compute Engine. It is a collection of tools
  and daemons, packaged as gce-compute-image-packages, that ensure that
  the Ubuntu images published to GCE run properly on their platform.

  Cloud platforms evolve at a rate that can't be handled in six-month
  increments, and they will often develop features that they would like
  to be available to customers who don't want to upgrade from earlier
  Ubuntu releases. As such, updating gce-compute-image-packages to more
  recent upstream releases is required within all Ubuntu releases, so
  they continue to function properly in their environment.

  With this release we also add a new binary package to the suite -
  google-compute-engine-oslogin which is for a future feature of using
  OS Login on GCE VM instances.

  [Test Case]

  When a new version of gce-compute-image-packages is uploaded to
  -proposed, the following will be done:

   * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
   * the CPC team will write new automated tests to cover new testable 
functionality (if any) in the new package
   * the automated testing that the CPC team normally runs against GCE images 
before they are published will be run against the -proposed image
   * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

  If all the testing indicates that the image containing the new package
  is acceptable, verification will be considered to be done.

  [Other Information]

  This bug is used for tracking of releasing the new upstream version
  for all supported series, as per the approved policy mentioned in the
  following MRE:

  https://wiki.ubuntu.com/gce-compute-image-packages-Updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1700027/+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 1700027] Re: Update google compute-image-packages to 20170622

[Launchpad Bug Tracker]

This bug was fixed in the package gce-compute-image-packages -
20170622-0ubuntu1~17.04.0

---
gce-compute-image-packages (20170622-0ubuntu1~17.04.0) zesty; urgency=medium

  * Backport to zesty.
  * New upstream version 20170622 (LP: #1700027)
- Add Linux guest environment support for OS Login
  * Add google-compute-engine-oslogin binary package

 -- Balint Reczey   Fri, 23 Jun 2017 10:42:27 +0200

** Changed in: gce-compute-image-packages (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/1700027

Title:
  Update google compute-image-packages to 20170622

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  Fix Released
Status in gce-compute-image-packages source package in Xenial:
  Fix Released
Status in gce-compute-image-packages source package in Yakkety:
  Fix Released
Status in gce-compute-image-packages source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  compute-image-packages is provided by Google for installation within
  guests that run on Google Compute Engine. It is a collection of tools
  and daemons, packaged as gce-compute-image-packages, that ensure that
  the Ubuntu images published to GCE run properly on their platform.

  Cloud platforms evolve at a rate that can't be handled in six-month
  increments, and they will often develop features that they would like
  to be available to customers who don't want to upgrade from earlier
  Ubuntu releases. As such, updating gce-compute-image-packages to more
  recent upstream releases is required within all Ubuntu releases, so
  they continue to function properly in their environment.

  With this release we also add a new binary package to the suite -
  google-compute-engine-oslogin which is for a future feature of using
  OS Login on GCE VM instances.

  [Test Case]

  When a new version of gce-compute-image-packages is uploaded to
  -proposed, the following will be done:

   * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
   * the CPC team will write new automated tests to cover new testable 
functionality (if any) in the new package
   * the automated testing that the CPC team normally runs against GCE images 
before they are published will be run against the -proposed image
   * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

  If all the testing indicates that the image containing the new package
  is acceptable, verification will be considered to be done.

  [Other Information]

  This bug is used for tracking of releasing the new upstream version
  for all supported series, as per the approved policy mentioned in the
  following MRE:

  https://wiki.ubuntu.com/gce-compute-image-packages-Updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1700027/+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 1699354] Re: upgrade juju-mongodb3.2 to 3.2.15

[Launchpad Bug Tracker]

This bug was fixed in the package juju-mongodb3.2 - 3.2.15-0ubuntu1

---
juju-mongodb3.2 (3.2.15-0ubuntu1) artful; urgency=medium

  * New upstream release. (LP: #1699354)

 -- Michael Hudson-Doyle   Mon, 10 Jul 2017
11:48:35 +1200

** Changed in: juju-mongodb3.2 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  upgrade juju-mongodb3.2 to 3.2.15

Status in juju-mongodb3.2 package in Ubuntu:
  Fix Released
Status in juju-mongodb3.2 source package in Xenial:
  New
Status in juju-mongodb3.2 source package in Yakkety:
  New
Status in juju-mongodb3.2 source package in Zesty:
  New

Bug description:
  [Impact]
  The previous juju-mongodb3.2 version was 3.2.12. 3.2.13, 3.2.14 and 3.2.15 
contain numerous bug fixes, some of which are important to Juju. Of particular 
interest are:

  https://jira.mongodb.org/browse/SERVER-25318
  https://jira.mongodb.org/browse/SERVER-26076
  https://jira.mongodb.org/browse/SERVER-26381
  https://jira.mongodb.org/browse/SERVER-28548
  https://jira.mongodb.org/browse/SERVER-24963
  https://jira.mongodb.org/browse/SERVER-28026
  https://jira.mongodb.org/browse/SERVER-26452
  https://jira.mongodb.org/browse/SERVER-22053
  https://jira.mongodb.org/browse/SERVER-26136
  https://jira.mongodb.org/browse/SERVER-25789
  https://jira.mongodb.org/browse/SERVER-27347
  https://jira.mongodb.org/browse/SERVER-28877
  https://jira.mongodb.org/browse/SERVER-28578

  There are also numerous performance related improvements, especially
  for the WiredTiger storage engine.

  [Test Case]
  Nothing specific as the above bugs only appear in large systems.

  [Regression potential]
  Slight, as the only consumer of this package is juju. Juju's CI will be run 
on the proposed packages before this bug is marked verification-done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb3.2/+bug/1699354/+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 1466926] Re: reload apache2 with mpm_event cause scoreboard is full

[Haw Loeung]

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

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

Title:
  reload apache2  with mpm_event cause  scoreboard is full

Status in apache2 package in Ubuntu:
  Fix Released
Status in apache2 source package in Trusty:
  Confirmed
Status in apache2 source package in Xenial:
  Confirmed
Status in apache2 source package in Zesty:
  Fix Released

Bug description:
  On the clean install Ubuntu 14.04 with Apache without almost any
  client load the Apache server with the command "service apache2
  reload" itself allocates slots marked with "Gracefully finishing" for
  which rejects new connections.

  For full rejection of new requests is sufficient to perform 4x command
  "service apache2 reload".

  Ubuntu 14.04.2 LTS
  Apache 2.4.7-ubuntu4.4 (mpm_event)
  Kernel 2.16.0-30-generic

  
  Reproduce problem:
  #
  1/ service apache2 start
  __W_
  ___.
  ..

  2/ service apache2 reload

  .GGG
  GGG__W__
  __

  3/ service apache2 reload

  ___W_GGG
  GGG__...
  ..

  4/ service apache2 reload

  
  G___
  W_

  5/ service apache2 reload -> Server Apache not responding 
  With logs in apache error log file:
  ... [mpm_event:error] [pid 9381:tid 1234563234] AH00485: scoreboard is full, 
not at MaxRequestWorkers
  ...
  #

  
  My workaround was change to  MPM module  from "mpm_event" to "mpm_worker".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1466926/+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 1466926] Re: reload apache2 with mpm_event cause scoreboard is full

[Haw Loeung]

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

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

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

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

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

Title:
  reload apache2  with mpm_event cause  scoreboard is full

Status in apache2 package in Ubuntu:
  Fix Released
Status in apache2 source package in Trusty:
  Confirmed
Status in apache2 source package in Xenial:
  Confirmed

Bug description:
  On the clean install Ubuntu 14.04 with Apache without almost any
  client load the Apache server with the command "service apache2
  reload" itself allocates slots marked with "Gracefully finishing" for
  which rejects new connections.

  For full rejection of new requests is sufficient to perform 4x command
  "service apache2 reload".

  Ubuntu 14.04.2 LTS
  Apache 2.4.7-ubuntu4.4 (mpm_event)
  Kernel 2.16.0-30-generic

  
  Reproduce problem:
  #
  1/ service apache2 start
  __W_
  ___.
  ..

  2/ service apache2 reload

  .GGG
  GGG__W__
  __

  3/ service apache2 reload

  ___W_GGG
  GGG__...
  ..

  4/ service apache2 reload

  
  G___
  W_

  5/ service apache2 reload -> Server Apache not responding 
  With logs in apache error log file:
  ... [mpm_event:error] [pid 9381:tid 1234563234] AH00485: scoreboard is full, 
not at MaxRequestWorkers
  ...
  #

  
  My workaround was change to  MPM module  from "mpm_event" to "mpm_worker".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1466926/+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 1690321] Re: Fix CVE-2017-7294

[Po-Hsu Lin]

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

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

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

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

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

Title:
  Fix CVE-2017-7294

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Tracking bug for fixing CVE-2017-7294

  Affected file: drivers/gpu/drm/vmwgfx/vmwgfx_surface.c
  Fix: e7e11f99564222d82f0ce84bd521e57d78a6b678

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