[Group.of.nepali.translators] [Bug 1560162] Re: Xenial: scaling is horribly out on xps13 install session

[Yuan-Chen Cheng]

base on current status, mark it fix release on oem-priority. re-open if
it's not apply to you.

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

Title:
  Xenial: scaling is horribly out on xps13 install session

Status in OEM Priority Project:
  Fix Released
Status in metacity package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Released

Bug description:
  STEPS:
  Requirements laptop desktop with a hidpi screen (Here xps 13)
  1. Grab the latest daily image and trigger an install
  2. On the first page notice the of centre and over scaled window

  EXPECTED:
  I expect to see something resembling a normal scaled desktop install

  ACTUAL:
  Things are not quite correct see attached screenshots

  ubiquity/xenial 2.21.49 amd64

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

Re: [Group.of.nepali.translators] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

[Rolf Leggewie]

On 08.02.2017 04:29, Joseph Salisbury wrote:
> There should be a fix coming from upstream shortly:
> https://lkml.org/lkml/2017/2/6/969

Great! Thanks.


** No longer affects: linux (Ubuntu Vivid)

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1619918/+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 1662749] [NEW] GNOME Software has entry in Startup Applications

[Robert Ancell]

Public bug reported:

[Impact]
GNOME Software shows in the startup applications list and can be disabled. This 
is a feature that should not be easily disabled by the user.

[Test Case]
1. Open Startup Applications

Expected result:
GNOME Software is not shown

Observed result:
GNOME Software is shown and can be disabled.

[Regression Potential]
Low - this just hides this entry.

** Affects: gnome-software
 Importance: Unknown
 Status: Unknown

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

** Affects: gnome-software (Ubuntu Xenial)
 Importance: Low
 Status: Triaged

** Affects: gnome-software (Ubuntu Yakkety)
 Importance: Low
 Status: Triaged

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

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

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

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

** Changed in: gnome-software (Ubuntu Yakkety)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Triaged

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

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

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

** Bug watch added: GNOME Bug Tracker #773615
   https://bugzilla.gnome.org/show_bug.cgi?id=773615

** Also affects: gnome-software via
   https://bugzilla.gnome.org/show_bug.cgi?id=773615
   Importance: Unknown
   Status: Unknown

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

Title:
  GNOME Software has entry in Startup Applications

Status in GNOME Software:
  Unknown
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Triaged

Bug description:
  [Impact]
  GNOME Software shows in the startup applications list and can be disabled. 
This is a feature that should not be easily disabled by the user.

  [Test Case]
  1. Open Startup Applications

  Expected result:
  GNOME Software is not shown

  Observed result:
  GNOME Software is shown and can be disabled.

  [Regression Potential]
  Low - this just hides this entry.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1662749/+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 1662750] [NEW] Remove 3rd party / non-free license warnings and just show license as Unknown

[Robert Ancell]

Public bug reported:

[Impact]
GNOME Software currently shows a large warning about software being 3rd party / 
non-free when the license information is shown. This is occurring for all snaps 
due to bug 167. This is misleading and would be simpler to just state the 
license is "Unknown".

[Test Case]
1. Open GNOME Software and select a snap (e.g. moon-buggy)

Expected result:
moon-buggy is shown with an unknown license.

Observed result:
A large warning is shown about it being 3rd party / non-free.

[Regression potential]
Low. We now hide the warning and show the license field even when it is unkown.

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

** Affects: gnome-software (Ubuntu Xenial)
 Importance: Medium
 Status: Triaged

** Affects: gnome-software (Ubuntu Yakkety)
 Importance: Medium
 Status: Triaged

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

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

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

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu Yakkety)
   Status: New => Triaged

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

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

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

** Description changed:

  [Impact]
- GNOME Software currently shows a large warning about software being 3rd party 
/ non-free when the license information is shown. This is ocurring for all 
snaps due to bug . This is misleading and would be simpler to just state the 
license is "Unknown".
+ GNOME Software currently shows a large warning about software being 3rd party 
/ non-free when the license information is shown. This is occurring for all 
snaps due to bug 167. This is misleading and would be simpler to just state 
the license is "Unknown".
  
  [Test Case]
  1. Open GNOME Software and select a snap (e.g. moon-buggy)
  
  Expected result:
  moon-buggy is shown with an unknown license.
  
  Observed result:
  A large warning is shown about it being 3rd party / non-free.
  
  [Regression potential]
  Low. We now hide the warning and show the license field even when it is 
unkown.

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

Title:
  Remove 3rd party / non-free license warnings and just show license as
  Unknown

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

Bug description:
  [Impact]
  GNOME Software currently shows a large warning about software being 3rd party 
/ non-free when the license information is shown. This is occurring for all 
snaps due to bug 167. This is misleading and would be simpler to just state 
the license is "Unknown".

  [Test Case]
  1. Open GNOME Software and select a snap (e.g. moon-buggy)

  Expected result:
  moon-buggy is shown with an unknown license.

  Observed result:
  A large warning is shown about it being 3rd party / non-free.

  [Regression potential]
  Low. We now hide the warning and show the license field even when it is 
unkown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1662750/+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 1645698] Re: [SRU] Upgrade network-manager to latest point release

[Yuan-Chen Cheng]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Status: New => Triaged

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+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 1660724] Re: linux-snapdragon: 4.4.0-1047.51 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

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

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

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

** Description changed:

  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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1660704
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Wednesday, 08. February 2017 00:45 UTC

** Description changed:

  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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1660704
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Wednesday, 08. February 2017 00:45 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

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

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

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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1660704
  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/1660724/+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 1649856] Re: [SRU] ceph 10.2.5

[Launchpad Bug Tracker]

This bug was fixed in the package ceph - 10.2.5-0ubuntu0.16.04.1

---
ceph (10.2.5-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream stable release (LP: #1649856):
- d/p/32bit-ftbfs.patch: Drop, no longer required.
- d/p/*: Refresh.
- d/ceph-common.install: Switch to RSA keys for drop.ceph.com.
  * d/rules: Install upstream provided systemd targets and ensure they
are enabled and started on install to ensure that integrations aligned
to upstream packaging work with Ubuntu packages (LP: #1646583).
  * d/ceph.*,d/*.logrotate: Install logrotate configuration
in ceph-common, ensuring that all daemons get log rotation on
log files, deal with removal of logrotate configuration in
ceph for upgrades (LP: #1609866).

 -- James Page   Wed, 18 Jan 2017 13:59:57 +

** Changed in: ceph (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/1649856

Title:
  [SRU] ceph 10.2.5

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

Bug description:
  New upstream stable release.

  http://docs.ceph.com/docs/master/release-notes/#v10-2-5-jewel

  Normal regression testing; deployment of existing packages using
  openstack charms, openstack tempest smoke test, upgrade to proposed
  packages; re-test cloud.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1649856/+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 1646583] Re: Ceph mon doesn't restart on reboot with Xenial when using ceph-{mon, osd}@ systemd units

[Launchpad Bug Tracker]

This bug was fixed in the package ceph - 10.2.5-0ubuntu0.16.04.1

---
ceph (10.2.5-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream stable release (LP: #1649856):
- d/p/32bit-ftbfs.patch: Drop, no longer required.
- d/p/*: Refresh.
- d/ceph-common.install: Switch to RSA keys for drop.ceph.com.
  * d/rules: Install upstream provided systemd targets and ensure they
are enabled and started on install to ensure that integrations aligned
to upstream packaging work with Ubuntu packages (LP: #1646583).
  * d/ceph.*,d/*.logrotate: Install logrotate configuration
in ceph-common, ensuring that all daemons get log rotation on
log files, deal with removal of logrotate configuration in
ceph for upgrades (LP: #1609866).

 -- James Page   Wed, 18 Jan 2017 13:59:57 +

** Changed in: ceph (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/1646583

Title:
  Ceph mon doesn't restart on reboot with Xenial when using
  ceph-{mon,osd}@ systemd units

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

Bug description:
  [Impact]
  Users of the ceph-osd@ and ceph-mon@ systemd units are not able to reboot 
servers; the targets which ensure that daemons managed this way are missing 
from the packages.  There is also no nice way to restart all ceph daemons on a 
machine due to the missing systemd targets.

  [Test Case]
  Install ceph-mon and ceph-osd machines
  Enable and initialise cluster using ceph-osd@ and ceph-mon@ unit files.
  Confirm working
  Reboot machines
  ceph-mon units will not start automatically after reboot
  ceph-osd units will start, but only due to udev rule processing

  [Regression Potential]
  Minimal; we're introducing the missing targets to the packages; these targets 
will be enabled and started on install, and the change to the packaging ensures 
that the ceph-mon/mds/create-keys systemd service units
  provided directly by the packaging are managed as before (not auto enabled 
and started).

  [Original Bug Report]
  The ceph monitor and osd daemons do not restart automatically on server 
reboot on Xenial.

  $ apt-cache policy ceph
  ceph:
    Installed: 10.2.2-0ubuntu0.16.04.2
    Candidate: 10.2.2-0ubuntu0.16.04.2
    Version table:
   *** 10.2.2-0ubuntu0.16.04.2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   10.1.2-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  This is likely caused by the same clash between upstream target files
  and Ubuntu systemd unit files that is noted in [1] but I have opened a
  separate bug because I believe the severity of not having Ceph restart
  automatically on server reboot is higher severity than not being able
  to start/stop all services with one command, which is what is reported
  in [1].

  The source of the Ubuntu package [2] does not have the necessary
  target files that upstream Ceph added to allow for restart on reboot
  under this commit [3] which is included in Ceph's github tag 10.2.2.

  [1] https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1627640
  [2] https://bugs.launchpad.net/ubuntu/+source/ceph/10.2.3-0ubuntu0.16.04.2
  [3] 
https://github.com/ceph/ceph/commit/15c4ad44010c798af7804e287ba71dcc289f806f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1646583/+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 1649856] Re: [SRU] ceph 10.2.5

[Launchpad Bug Tracker]

This bug was fixed in the package ceph - 10.2.5-0ubuntu0.16.10.1

---
ceph (10.2.5-0ubuntu0.16.10.1) yakkety; urgency=medium

  * New upstream stable release (LP: #1649856):
- d/p/32bit-ftbfs.patch: Drop, no longer required.
- d/p/*: Refresh.
- d/ceph-common.install: Switch to RSA keys for drop.ceph.com.
  * d/rules: Install upstream provided systemd targets and ensure they
are enabled and started on install to ensure that integrations aligned
to upstream packaging work with Ubuntu packages (LP: #1646583).
  * d/ceph.{postinst,preinst,postrm}: Ensure that ceph logrotate
configuration is purged on upgrade from pre-yakkety installs
(LP: #1635844).
  * d/ceph-base.*,d/*.logrotate: Install logrotate configuration
in ceph-common, ensuring that all daemons get log rotation on
log files, deal with removal of logrotate configuration in
ceph-base for upgrades (LP: #1609866).

 -- James Page   Wed, 18 Jan 2017 11:39:04 +

** Changed in: ceph (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/1649856

Title:
  [SRU] ceph 10.2.5

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

Bug description:
  New upstream stable release.

  http://docs.ceph.com/docs/master/release-notes/#v10-2-5-jewel

  Normal regression testing; deployment of existing packages using
  openstack charms, openstack tempest smoke test, upgrade to proposed
  packages; re-test cloud.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1649856/+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 1646583] Re: Ceph mon doesn't restart on reboot with Xenial when using ceph-{mon, osd}@ systemd units

[Launchpad Bug Tracker]

This bug was fixed in the package ceph - 10.2.5-0ubuntu0.16.10.1

---
ceph (10.2.5-0ubuntu0.16.10.1) yakkety; urgency=medium

  * New upstream stable release (LP: #1649856):
- d/p/32bit-ftbfs.patch: Drop, no longer required.
- d/p/*: Refresh.
- d/ceph-common.install: Switch to RSA keys for drop.ceph.com.
  * d/rules: Install upstream provided systemd targets and ensure they
are enabled and started on install to ensure that integrations aligned
to upstream packaging work with Ubuntu packages (LP: #1646583).
  * d/ceph.{postinst,preinst,postrm}: Ensure that ceph logrotate
configuration is purged on upgrade from pre-yakkety installs
(LP: #1635844).
  * d/ceph-base.*,d/*.logrotate: Install logrotate configuration
in ceph-common, ensuring that all daemons get log rotation on
log files, deal with removal of logrotate configuration in
ceph-base for upgrades (LP: #1609866).

 -- James Page   Wed, 18 Jan 2017 11:39:04 +

** Changed in: ceph (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/1646583

Title:
  Ceph mon doesn't restart on reboot with Xenial when using
  ceph-{mon,osd}@ systemd units

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

Bug description:
  [Impact]
  Users of the ceph-osd@ and ceph-mon@ systemd units are not able to reboot 
servers; the targets which ensure that daemons managed this way are missing 
from the packages.  There is also no nice way to restart all ceph daemons on a 
machine due to the missing systemd targets.

  [Test Case]
  Install ceph-mon and ceph-osd machines
  Enable and initialise cluster using ceph-osd@ and ceph-mon@ unit files.
  Confirm working
  Reboot machines
  ceph-mon units will not start automatically after reboot
  ceph-osd units will start, but only due to udev rule processing

  [Regression Potential]
  Minimal; we're introducing the missing targets to the packages; these targets 
will be enabled and started on install, and the change to the packaging ensures 
that the ceph-mon/mds/create-keys systemd service units
  provided directly by the packaging are managed as before (not auto enabled 
and started).

  [Original Bug Report]
  The ceph monitor and osd daemons do not restart automatically on server 
reboot on Xenial.

  $ apt-cache policy ceph
  ceph:
    Installed: 10.2.2-0ubuntu0.16.04.2
    Candidate: 10.2.2-0ubuntu0.16.04.2
    Version table:
   *** 10.2.2-0ubuntu0.16.04.2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   10.1.2-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  This is likely caused by the same clash between upstream target files
  and Ubuntu systemd unit files that is noted in [1] but I have opened a
  separate bug because I believe the severity of not having Ceph restart
  automatically on server reboot is higher severity than not being able
  to start/stop all services with one command, which is what is reported
  in [1].

  The source of the Ubuntu package [2] does not have the necessary
  target files that upstream Ceph added to allow for restart on reboot
  under this commit [3] which is included in Ceph's github tag 10.2.2.

  [1] https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1627640
  [2] https://bugs.launchpad.net/ubuntu/+source/ceph/10.2.3-0ubuntu0.16.04.2
  [3] 
https://github.com/ceph/ceph/commit/15c4ad44010c798af7804e287ba71dcc289f806f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1646583/+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 1656480] Re: QEMU Does not Send L2 Broadcasts After Live Migration

[Launchpad Bug Tracker]

This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.8

---
qemu (1:2.5+dfsg-5ubuntu10.8) xenial; urgency=medium

  [ Dmitrii Shcherbakov ]
  *  d/p/ubuntu/net-fix-qemu_announce_self-not-emitting-packets.patch:
 Cherrypick upstream patch: net: fix qemu_announce_self not emitting
 packets (LP: #1656480)

 -- Christian Ehrhardt   Mon, 23 Jan
2017 15:12:05 +0100

** Changed in: qemu (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/1656480

Title:
  QEMU Does not Send L2 Broadcasts After Live Migration

Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  L2 broadcasts are sent out in order to update MAC tables of the switches in 
the same broadcast domain. If this is not done after live migration there may 
be a temporary downtime period for clients trying to connect to services 
residing on a migrated VM due to the fact that switches will still forward 
frames to the old destination. It will also lead to varying behaviors depending 
on the operating system or software installed in the guest OS with regards to 
network activity: there may be cases when VM's network activity will force the 
MAC table update across the L2 network but this is not guaranteed.

  [Test case]
  Steps are provided in the bug description.

  [Regression Potential]
  Small: the change is trivial and is present both in the upstream QEMU and the 
newer ubuntu releases. This is also not a heavily changing code path in the 
upstream.

  --

  In short:
  1) Get two Xenial hosts (instead, could be two lxd containers with QEMU 
inside or two VMs with nested virtualization enabled - doesn't matter);
  1) Create a libvirt domain that uses QEMU (can be a bare instance, even 
without a disk, with a NIC without an IP address since we are testing L2 
broadcasts);
  2) Launch an instance;
  3) Start listening for RARP packets on the destination host's bridge (QEMU 
uses a RARP L3 header and a broadcast L2 header which is easy to filter as no 
other software sends RARPs nowadays);
  3) Do virsh migrate --live domain desturi;
  4) Observe that no RARP packets are sent.

  The expected result (QEMU actually sends 5 of those, grep for
  SELF_ANNOUNCE_ROUNDS == 5 in the sources):

  sudo tcpdump -e -i br0 rarp
  tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
  listening on br0, link-type EN10MB (Ethernet), capture size 262144 bytes
  18:19:32.460765 52:54:00:25:49:b7 (oui Unknown) > Broadcast, ethertype 
Reverse ARP (0x8035), length 60: Reverse Request who-is 52:54:00:25:49:b7 (oui 
Unknown) tell 52:54:00:25:49:b7 (oui Unknown), length 46
  18:19:32.504609 52:54:00:25:49:b7 (oui Unknown) > Broadcast, ethertype 
Reverse ARP (0x8035), length 60: Reverse Request who-is 52:54:00:25:49:b7 (oui 
Unknown) tell 52:54:00:25:49:b7 (oui Unknown), length

  ---
  lsb_release -r
  Release:  16.04

  dpkg --status qemu-kvm | grep Version
  Version: 1:2.5+dfsg-5ubuntu10.6
  --

  Fortunately, there is already a fix for this:
  https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg04645.html

  
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=ca1ee3d6b546e841a1b9db413eb8fa09f13a061b;hp=14e60aaece20a1cfc059a69f6491b0899f9257a8

  The issue was introduced in fefe2a78abde932e0f340b21bded2c86def1d242:
  
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=fefe2a78abde932e0f340b21bded2c86def1d242

  $ apt-get source qemu

  # we are looking at qemu_2.5+dfsg debian branch
  $ ls qemu*dsc
  qemu_2.5+dfsg-5ubuntu10.6.dsc

  $ git remote show origin | grep Fetch
    Fetch URL: git://anonscm.debian.org/pkg-qemu/qemu.git

  $ git checkout debian/qemu_2.5+dfsg-5
  HEAD is now at aa4dbf2... Uploading version 2.5+dfsg-5 to unstable

  The commit that introduced the issue is present in qemu_2.5+dfsg-5.
  $ git merge-base --is-ancestor fefe2a78abde932e0f340b21bded2c86def1d242 HEAD 
; echo $?
  0

  There are no patches for it:

  grep -RiP 'QEMU_NET_PACKET_FLAG_RAW' qemu-2.5+dfsg/debian/patches/ ; echo $?
  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1656480/+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 1662378] Re: many OOMs on busy xenial IMAP server with lots of available memory

[Joseph Salisbury]

Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced.   If this is a
regression, we can perform a kernel bisect to identify the commit that
introduced the problem.

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

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

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

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

** Tags added: kernel-key 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/1662378

Title:
  many OOMs on busy xenial IMAP server with lots of available memory

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

Bug description:
  We recently noticed that a busy xenial IMAP server with about 22 days
  uptime has been logging a lot of OOM messages.  The machine has 24G of
  memory.  Below please find some typical memory info.

  I noted that there was about 11G of memory allocated to slab, and
  since all of the oom-killer invoked messages report order=2 or order=3
  (see below for gfp_flags) I thought that maybe fragmentation was a
  factor.  After doing echo 2 > /proc/sys/vm/drop_caches to release
  reclaimable slab memory, no OOMs were logged for around 30 minutes,
  but then they started up again, although perhaps not as frequently as
  before, and the amount of memory in slab was back up around its former
  size.  To the best of my knowledge we do not have any custom VM-
  related sysctl tweaks on this machine.

  Attached please find version.log and lspci-vnvn.log.  And here's a link to a 
kern.log from a little before time of boot onwards, containing all of the 
oom-killer messages: 
  https://people.canonical.com/~pjdc/grenadilla-sanitized-kern.log.xz

  == Breakdown of Failed Allocations ===

  pjdc@grenadilla:~$ grep -o 'gfp_mask=.*, order=.' 
kern.log-version-with-oom-killer-invoked | sort | uniq -c | sort -n
 1990 gfp_mask=0x26000c0, order=2
 4043 gfp_mask=0x240c0c0, order=3
  pjdc@grenadilla:~$ _

  == Representative (Probably) Memory Info ==

  pjdc@grenadilla:~$ free -m
totalusedfree  shared  buff/cache   
available
  Mem:  240971762 213 266   22121   
21087
  Swap: 17492 101   17391
  pjdc@grenadilla:~$ cat /proc/meminfo 
  MemTotal:   24676320 kB
  MemFree:  219440 kB
  MemAvailable:   21593416 kB
  Buffers: 6186648 kB
  Cached:  4255608 kB
  SwapCached: 3732 kB
  Active:  7593140 kB
  Inactive:4404824 kB
  Active(anon):1319736 kB
  Inactive(anon):   508544 kB
  Active(file):6273404 kB
  Inactive(file):  3896280 kB
  Unevictable:   0 kB
  Mlocked:   0 kB
  SwapTotal:  17912436 kB
  SwapFree:   17808972 kB
  Dirty:   524 kB
  Writeback: 0 kB
  AnonPages:   1553244 kB
  Mapped:   219868 kB
  Shmem:272576 kB
  Slab:   12209796 kB
  SReclaimable:   11572836 kB
  SUnreclaim:   636960 kB
  KernelStack:   14464 kB
  PageTables:54864 kB
  NFS_Unstable:  0 kB
  Bounce:0 kB
  WritebackTmp:  0 kB
  CommitLimit:30250596 kB
  Committed_AS:2640808 kB
  VmallocTotal:   34359738367 kB
  VmallocUsed:   0 kB
  VmallocChunk:  0 kB
  HardwareCorrupted: 0 kB
  AnonHugePages: 18432 kB
  CmaTotal:  0 kB
  CmaFree:   0 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   2048 kB
  DirectMap4k: 2371708 kB
  DirectMap2M:22784000 kB
  pjdc@grenadilla:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662378/+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 1662381] Re: linux-image-4.4.0-62-generic breaks Lenovo T440s on Ultradock

[Joseph Salisbury]

Would it be possible for you to test this latest kernel and post back if it 
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
enable and use -proposed. 

Thank you in advance!

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

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

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

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

** Tags added: kernel-da-key needs-bisect

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

Title:
  linux-image-4.4.0-62-generic breaks Lenovo T440s on Ultradock

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

Bug description:
  When using with dock, attached monitor is not detected, laptop monitor
  remains blank.  Requires a reboot

  4.4.0-59 works fine.  I'm guessing this is due to the i915 patches for
  DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-generic 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  weinberg   2945 F pulseaudio
   /dev/snd/controlC2:  weinberg   2945 F pulseaudio
   /dev/snd/controlC0:  weinberg   2945 F pulseaudio
   /dev/snd/controlC1:  weinberg   2945 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  6 20:15:05 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=b572432a-a870-4698-af05-eb9ac5b5dfb5
  InstallationDate: Installed on 2016-05-06 (276 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=0a196d38-a419-4a42-b659-7108068e6ce5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ARA0S100
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662381/+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 1662566] Re: [Intel/drm] stuck on render ring

[Joseph Salisbury]

Does this issue go away if you boot into a prior kernel version?

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

** Changed in: linux (Ubuntu)
   Importance: Medium => High

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

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

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

** Tags added: kernel-da-key

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

Title:
  [Intel/drm] stuck on render ring

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

Bug description:
  GPU hangs and Compiz crashes after resume from suspend.

  This has happened rather frequently lately and was not a problem
  before. But I cannot identify if there is a recent package update
  which is to blame. I am on an updated Ubuntu 16.04 (without -proposed
  enabled).

  GPU crash dump is attached.

  [21649.490673] [drm] stuck on render ring
  [21649.491690] [drm] GPU HANG: ecode 7:0:0x85dfbff8, in compiz [3583], 
reason: Ring hung, action: reset
  [21649.491692] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [21649.491692] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [21649.491693] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [21649.491694] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [21649.491695] [drm] GPU crash dump saved to /sys/class/drm/card0/error
  [21649.491723] [ cut here ]
  [21649.491754] WARNING: CPU: 1 PID: 21430 at 
/build/linux-7x12eW/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
  [21649.491756] WARN_ON(__i915_wait_request(mmio_flip->req, 
mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips))
  [21649.491757] Modules linked in:
  [21649.491759]  hid_logitech_hidpp hid_logitech_dj usbhid uas usb_storage 
drbg ansi_cprng ctr ccm bnep nls_iso8859_1 pn544_mei mei_phy pn544 hci nfc arc4 
dell_wmi sparse_keymap dell_laptop dcdbas dell_smm_hwmon intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel btusb kvm irqbypass 
crct10dif_pclmul btrtl crc32_pclmul ghash_clmulni_intel snd_soc_rt5640 
snd_soc_rl6231 iwlmvm uvcvideo snd_soc_core btbcm videobuf2_vmalloc mac80211 
aesni_intel snd_compress videobuf2_memops videobuf2_v4l2 ac97_bus 
videobuf2_core snd_pcm_dmaengine btintel joydev snd_hda_codec_hdmi v4l2_common 
aes_x86_64 lrw videodev gf128mul glue_helper bluetooth ablk_helper cryptd 
iwlwifi snd_hda_codec_realtek snd_hda_codec_generic input_leds media serio_raw 
cfg80211 snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep mei_me
  [21649.491799]  lpc_ich mei snd_pcm shpchp snd_seq_midi snd_seq_midi_event 
snd_rawmidi snd_seq snd_seq_device snd_timer 8250_fintek dell_smo8800 snd 
elan_i2c soundcore mac_hid dw_dmac snd_soc_sst_acpi dw_dmac_core 
spi_pxa2xx_platform dell_rbtn 8250_dw i2c_designware_platform 
i2c_designware_core parport_pc ppdev lp parport autofs4 i915 psmouse 
i2c_algo_bit e1000e ahci drm_kms_helper libahci syscopyarea sysfillrect 
sysimgblt sdhci_pci fb_sys_fops ptp drm pps_core wmi sdhci_acpi video sdhci 
i2c_hid hid fjes
  [21649.491831] CPU: 1 PID: 21430 Comm: kworker/1:1 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [21649.491832] Hardware name: Dell Inc. Latitude E7440/07F3F4, BIOS A20 
12/22/2016
  [21649.491850] Workqueue: events intel_mmio_flip_work_func [i915]
  [21649.491851]  0286 97fa5dc1 88040646fd20 
813f6f33
  [21649.491853]  88040646fd68 c02c0ab8 88040646fd58 
810812d2
  [21649.491855]  8803e88a4600 88041ea965c0 88041ea9af00 
0040
  [21649.491857] Call Trace:
  [21649.491861]  [] dump_stack+0x63/0x90
  [21649.491864]  [] warn_slowpath_common+0x82/0xc0
  [21649.491865]  [] warn_slowpath_fmt+0x5c/0x80
  [21649.491868]  [] ? __switch_to+0x1dc/0x5c0
  [21649.491883]  [] intel_mmio_flip_work_func+0x38e/0x3d0 
[i915]
  [21649.491886]  [] process_one_work+0x165/0x480
  [21649.491887]  [] worker_thread+0x4b/0x4c0
  [21649.491889]  [] ? process_one_work+0x480/0x480
  [21649.491891]  [] ? process_one_work+0x480/0x480
  [21649.491892]  [] kthread+0xd8/0xf0
  [21649.491894]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [21649.491897]  [] ret_from_fork+0x3f/0x70
  [21649.491898]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [21649.491899] ---[ end trace 051e5be39aa982ac ]---
  [21649.493882] drm/i915: Resetting chip after gpu hang
  [21655.502550] [drm] stuck on render ring
  [21655.503514] [drm] GPU HANG: ecode 7:0:0x85dfbff8, in compiz [3583], 
reason: Ring hung, action: reset
  

[Group.of.nepali.translators] [Bug 1662589] Re: Touchpad not working correctly after kernel upgrade

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc7

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

** Tags added: kernel-da-key needs-bisect xenial

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

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

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

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

Title:
  Touchpad not working correctly after kernel upgrade

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

Bug description:
  Since the kernel upgraded from 4.4.0-31-generic the touchpad on my
  Toshiba Tecra laptop has not been functioning correctly.

  Whenever I try and do two finger srcolling it also thinks I'm doing a
  two finger tap to to rightclick, making two finger scrolling almost
  impossible.

  It is the same for both kernel updates since 4.4.0-31.  If I boot from
  4.4.0-31 then the touchpad works fine.

  If I do an xinput in the later kernels it shows :-
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Wired Keyboard 600id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Comfort Mouse 6000id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Microsoft Wired Keyboard 600id=9[slave  
keyboard (3)]
  ↳ TOSHIBA Web Camera - FHDid=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Toshiba input device  

  
  The AlpsPS/2 devices aren't aren't present when booting with 4.4.0.31:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Wired Keyboard 600id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Comfort Mouse 6000id=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=14   [slave  pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Microsoft Wired Keyboard 600id=9[slave  
keyboard (3)]
  ↳ TOSHIBA Web Camera - FHDid=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Toshiba input deviceid=15 [slave  keyboard 
(3)]

  Any ideas?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662589/+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 1553176] Re: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload

[Mike Pontillo]

** Also affects: maas/1.9
   Importance: Undecided
   Status: New

** Changed in: maas/1.9
Milestone: None => 1.9.5

** Changed in: maas/1.9
   Status: New => In Progress

** Changed in: maas/1.9
 Assignee: (unassigned) => LaMont Jones (lamont)

** Changed in: maas/1.9
   Importance: Undecided => High

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

Title:
  BIND ignores nanoseconds field in timestamps, fails to load newer
  versions of zones on reload

Status in BIND:
  Fix Released
Status in MAAS:
  Fix Released
Status in MAAS 1.9 series:
  In Progress
Status in bind9 package in Ubuntu:
  Fix Released
Status in bind9 source package in Trusty:
  Fix Committed
Status in bind9 source package in Xenial:
  Fix Released

Bug description:
  Since 2.6, linux has supported nanosecond granular time in stat(2)
  returns.  BIND has a comment in the code that it might use it, but
  continues to ignore it.

  As of 9.9.3b2, named checks the time of (at least) zone files on disk
  (expanding to include include files in 9.10.0a2).  Because the check
  is only done to a granularity of seconds, changing the zone file twice
  in the same second can cause BIND to decide that it need not reload
  the zone, even though it is out of date.

  [Impact]

   * If a zone file is changed (generally by automated processes) more
  than once in a second, bind9 happily thinks it has already loaded the
  zone.  A trivial demonstration of the bug can be seen at
  paste.ubuntu.com/23921121/ -- http://paste.ubuntu.com/23921176/ is the
  same test with the fixed code.  Making this a test case is somewhat
  problematic in that it needs to make sure that they happen inside of
  the same second.

   * MAAS is exactly the sort of use case that hits this bug.

   * The upload changes BIND's utility function to actual use the
  st_mtim.tv_nsec instead of '0'.

  [Test Case]

   * See the pastebin above.  (Change a zone file and reload it, and
  then do it again less than a second later.)

  [Regression Potential]

   * Ignoring the whole "rebuilds sometimes break things", the most
  likely regression would be one where something was either relying on
  BIND not reloading the dozone (unlikely), or otherwise relying on the
  modify time on a zone file to some arbitrary value.

  [Other Info]

    This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial
  March 2016.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1553176/+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 1587886] Re: strongswan ipsec status issue with apparmor

[ChristianEhrhardt]

Hi,
not sure what Neutron picked up - I'll ping one from the Cloud Archive Team.
Does it even have an own strongswan or just that from the Xenial Archive I'd 
guess?

For Xenial in general an SRU makes sense.

The change itself is as simple as:
https://git.launchpad.net/~paelzer/ubuntu/+source/strongswan/commit/?h=merge-zesty=9b3a90368229add8313f8624beee02f5840dbf0e

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

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

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

Title:
  strongswan ipsec status issue with apparmor

Status in One Hundred Papercuts:
  Triaged
Status in strongswan package in Ubuntu:
  Fix Released
Status in strongswan source package in Xenial:
  Triaged

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy strongswan
  strongswan:
Installed: 5.3.5-1ubuntu3
Candidate: 5.3.5-1ubuntu3
Version table:
   *** 5.3.5-1ubuntu3 500
  500 http://au.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://au.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status


  Looks like 'ipsec status' might be causing strongswan's charon to
  write to run/systemd/journal/dev-log instead of /run/systemd/journal
  /dev-log and apparmor doesn't like it.

  Extract from /etc/apparmor.d/abstractions/base :
/{,var/}run/systemd/journal/dev-log w,

  With an established ipsec connection, issue the following :

  $ sudo ipsec status
  connecting to 'unix:///var/run/charon.ctl' failed: Permission denied
  failed to connect to stroke socket 'unix:///var/run/charon.ctl'

  
  $ journalctl
  ...
  Jun 01 12:15:07 ThinkCentre-M900 kernel: audit: type=1400 
audit(1464785297.366:491): apparmor="DENIED" operation="connect" info="Failed 
name lookup - disconnected path" error=-13 profile="/usr/lib/ipsec/charon" 
name="run/systemd/journal/dev-log" pid=4994 comm="charon" requested_mask="w" 
denied_mask="w" fsuid=0 ouid=0
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: strongswan 5.3.5-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  1 23:06:53 2016
  InstallationDate: Installed on 2016-05-11 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: strongswan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1587886/+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 1661842] Re: 0001-Only-use-AV_CODEC_ID_WRAPPED_AVFRAME-on-new-enough-l.patch fixes ftbfs but breaks plugin functionality

[Iain Lane]

I reproduced this, it's a problem with the combination of the shipped
ffmpeg and 1.8.3.

** Bug watch added: GNOME Bug Tracker #778283
   https://bugzilla.gnome.org/show_bug.cgi?id=778283

** Also affects: gstreamer via
   https://bugzilla.gnome.org/show_bug.cgi?id=778283
   Importance: Unknown
   Status: Unknown

** Changed in: gst-libav1.0 (Ubuntu)
   Status: Confirmed => Fix Released

** Also affects: gst-libav1.0 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Summary changed:

- 0001-Only-use-AV_CODEC_ID_WRAPPED_AVFRAME-on-new-enough-l.patch fixes ftbfs 
but breaks plugin functionality
+ gstreamer 1.8.3 incorrectly removes some decoders and encoders when built 
against ffmpeg 2.8.10

** Changed in: gst-libav1.0 (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: gst-libav1.0 (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  gstreamer 1.8.3 incorrectly removes some decoders and encoders when
  built against ffmpeg 2.8.10

Status in GStreamer:
  Unknown
Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Triaged

Bug description:
  That is with the current ffmpeg shared in 16.04. So maybe consider reverting 
patch, i.e. 1.8.2-1 seems to work ok.
  Otherwise consider building with plugin supplied ffmpeg (called libav), there 
is recent precedent for static linking as seen by vlc last year.

  Sample files - 
  wmapro
  
http://samples.mplayerhq.hu/A-codecs/WMA9/wmapro/New%20Stories%20(Highway%20Blues)-2.wma

  wmal
  http://samples.mplayerhq.hu/A-codecs/lossless/luckynight.wma

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gstreamer1.0-libav 1.8.3-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb  4 08:51:10 2017
  SourcePackage: gst-libav1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1661842/+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 1662507] [NEW] Xenial update to v4.4.47 stable release

[Tim Gardner]

Public bug reported:


SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.4.47 stable release shall be
applied:

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

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


** Tags: kernel-stable-tracking-bug

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

** Also affects: linux (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/1662507

Title:
  Xenial update to v4.4.47 stable release

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

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the v4.4.47 stable release shall be
  applied:

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