[Group.of.nepali.translators] [Bug 1485752] Re: drop oneiric /run compatibility link

[Scott Moser]

** Also affects: cloud-initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-initramfs-tools (Ubuntu)
   Status: New => Fix Released

** Changed in: cloud-initramfs-tools (Ubuntu)
   Importance: Undecided => Medium

** Also affects: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cloud-initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

** No longer affects: initramfs-tools (Ubuntu Xenial)

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

Title:
  drop oneiric /run compatibility link

Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  In Progress

Bug description:
  Drop: Maintain compatibility with pre- /run configurations -- this was
  for compatibility with oneiric which is now long gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1485752/+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 1636333] Re: Squirrelmail - missing Subject/Body on some messages in 16.04

[Launchpad Bug Tracker]

This bug was fixed in the package squirrelmail -
2:1.4.23~svn20120406-2ubuntu2

---
squirrelmail (2:1.4.23~svn20120406-2ubuntu2) zesty; urgency=medium

  * debian/patches/php7_remove_e_modifier_preg_replace: Remove use of
deprecated /e modifier in preg_replace.  Thanks to Thijs Kinkhorst
.  Closes LP: #1636333.

 -- Nishanth Aravamudan   Mon, 28 Nov
2016 16:23:55 -0800

** Changed in: squirrelmail (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/1636333

Title:
  Squirrelmail - missing Subject/Body on some messages in 16.04

Status in squirrelmail package in Ubuntu:
  Fix Released
Status in squirrelmail source package in Xenial:
  Confirmed
Status in squirrelmail source package in Yakkety:
  Confirmed

Bug description:
  [Impact]

   * In Ubuntu 16.04, Squirrelmail has a regression from 14.04.  Certain 
messages are missing the subject or message body.  Investigation reveals that 
this is due to the removal of the /e modifier in preg_replace in PHP 7.  The 
server logs show numerous error messages similar to the following:
   
  [Mon Oct 24 19:40:36.248894 2016] [:error] [pid 4699] [client 
AAA.BBB.CCC.DDD:12345] PHP Warning:  preg_replace(): The /e modifier is no 
longer supported, use preg_replace_callback instead in 
/usr/share/squirrelmail/functions/decode/utf_8.php on line 87, referer: xyz

   * Upstream has resolved this issue:
  https://sourceforge.net/p/squirrelmail/code/14359/

   * After applying the patch in 14359 (plus the trivial 14347 which is
  necessary to make 14359 apply cleanly), the problems go away.

  [Test Case]

   * Install and configure squirrelmail. Determine if all emails have
  subject and message body.

 (@Scott, do you have a better test case?)

  [Regression Potential]

   * Squirrelmail as currently packaged is broken in 16.04, 16.10 and
  17.04, due to syntax changes in PHP7.0. The risk for regression is
  consequentially very low, as the fix involves backporting upstream
  fixes that make the code-base PHP7.0-compliant.

  ---

  PPA with the patches applied: https://launchpad.net/~swt-
  techie/+archive/ubuntu/squirrelmail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squirrelmail/+bug/1636333/+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 1619459] Re: workdir only used for root mount not recursed

[Scott Moser]

** Also affects: cloud-initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
   Status: Fix Committed => 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/1619459

Title:
  workdir only used for root mount not recursed

Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  In Progress

Bug description:
  to reproduce, boot a yakkety disk1.img. this is a uefi image, so it
  has multiple partitions.

  
  sudo sh -c 'echo overlayroot=tmpfs > /etc/overlayroot.local.conf && reboot'

  you'll see it hang. the reason i believe is the info written to
  /etc/fstab for the non-root mounts does not include workdir
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1619459/+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 1644615] Re: linux-snapdragon: 4.4.0-1038.42 -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/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: 1644611
  phase: Uploaded
+ kernel-stable-phase-changed:Tuesday, 29. November 2016 00:33 UTC
+ kernel-stable-phase:Promoted to proposed

** 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: 1644611
- phase: Uploaded
- kernel-stable-phase-changed:Tuesday, 29. November 2016 00:33 UTC
- kernel-stable-phase:Promoted to proposed
+ 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/1644615

Title:
  linux-snapdragon: 4.4.0-1038.42 -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:
  New
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: 1644611
  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/1644615/+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 1536181] Re: bind9-resolvconf service doesn't work

[Launchpad Bug Tracker]

This bug was fixed in the package bind9 - 1:9.10.3.dfsg.P4-8ubuntu1.3

---
bind9 (1:9.10.3.dfsg.P4-8ubuntu1.3) xenial; urgency=medium

  * Add RemainAfterExit to bind9-resolvconf unit configuration file
(LP: #1536181).

 -- Nishanth Aravamudan   Tue, 15 Nov
2016 08:30:31 -0800

** Changed in: bind9 (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/1536181

Title:
  bind9-resolvconf service doesn't work

Status in bind9 package in Ubuntu:
  Fix Released
Status in bind9 source package in Xenial:
  Fix Released
Status in bind9 source package in Yakkety:
  In Progress
Status in bind9 package in Debian:
  New

Bug description:
  [Impact]

   * If using the bind9-resolvconf service to have the local named
  managed resolv.conf, the service exits after running starting, and the
  system resolv.conf ends up reverting to the default content.

   * The user is effectively prevented from using bind9-resolvconf to
  manage their local resolv.conf.

   * The issue is that the bind9-resolvconf service needs to detected as
  still running even after the /etc/resolv.conf modification occurs. As
  per Debian Bug 744304: "RemainAfterExit tells systemd that a service
  should be considered running even after it exited. Currently, systemd
  thinks the service went inactive after the ExecStart command exits,
  and then immediately calls the ExecStop command, thus removing
  127.0.0.1 from resolvconf."

  [Test Case]

   * Install bind9-resolvconf with a local bind9 configuration. Start
  the bind9-resolvconf service and the prior content of /etc/resolv.conf
  will remain even if it differs from bind9's configuration.

  [Regression Potential]

   * I believe the regression potential to be very low for this change.
  The bind9-resolvconf service currently does not work as expected.
  Users may have made manual changes locally, as suggested in this bug,
  but those seem to generally not be permanent solutions and should not
  collide with the change to the service.

  ---

  I enabled the bind9-resolvconf service and restarted my system,
  because I want to use the named running on localhost as my nameserver.

  Even after the restart, however, the nameservers in /etc/resolv.conf
  (actually /var/run/resolvconf/resolv.conf) were still the ones
  provided by DHCP. This, despite the fact that the logs claim that
  bind9-resolvconf ran successfully during boot.

  I tried manually running "sudo systemctl start bind9-resolv.conf", and
  again, the logs claim it ran, but /etc/resolv.conf was unmodified.

  Finally, I manually ran "sudo /bin/sh -c 'echo nameserver 127.0.0.1 |
  /sbin/resolvconf -a lo.named'", i.e., the command listed in
  /lib/systemd/system/bind9-resolv.conf.service, and _that_ successfully
  updated /etc/resolv.conf.

  After doing that, interestingly, "sudo systemctl stop
  bind9-resolv.conf" _also_ doesn't change /etc/resolv.conf, i.e., it
  still retains the 127.0.0.1 line which I added by running the
  resolvconf command manually.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bind9 1:9.9.5.dfsg-11ubuntu1.2
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 20 08:03:35 2016
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   bind9utils 1:9.9.5.dfsg-11ubuntu1.2
   apparmor   2.10-0ubuntu6
  SourcePackage: bind9
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.bind.named.conf: [modified]
  modified.conffile..etc.bind.named.conf.local: [modified]
  mtime.conffile..etc.bind.named.conf: 2016-01-16T19:01:39.827033
  mtime.conffile..etc.bind.named.conf.local: 2016-01-16T21:13:51.991632

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1536181/+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 1585940] Re: [SRU] ERROR "can't get udev device" when iscsi multipath enabled

[Launchpad Bug Tracker]

This bug was fixed in the package python-os-brick - 1.2.0-2ubuntu0.1

---
python-os-brick (1.2.0-2ubuntu0.1) xenial; urgency=medium

  * d/p/fix-wrong-path-used-in-iscsi-multipath-l.patch: Backport
fix for ERROR "can't get udev device" when iscsi multipath enabled (LP: 
#1585940).

 -- Edward Hope-Morley   Mon, 07 Nov
2016 16:40:52 +0100

** Changed in: python-os-brick (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/1585940

Title:
  [SRU] ERROR "can't get udev device" when iscsi multipath enabled

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in os-brick:
  Fix Released
Status in python-os-brick package in Ubuntu:
  Invalid
Status in python-os-brick source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Fallback device detection for multipath connections is currently
  broken.

  [Test Case]

   * Enable cinder/nova multipath but do not make multiple paths
  available (such that are no /dev/disk/path/by-id/dm* devices)

   * Create a cinder volume and attach to Nova instance

   * Check that volume was attached successfully and that /var/log/nova
  /nova-compute.log does not display the error mentioned below.

  [Regression Potential]

   * None

  
  SUMMARY:
  Wrong path used when detecting multipath id

  ANALYSE:
  when multipath device path was not found via LUN wwn, os-brick would use 
device path like below:

  /dev/disk/by-path/ip-192.168.3.52:3260-iscsi-
  iqn.1992-04.com.emc:cx.apm00153906536.b5-lun-155

  to detect multipath id via 'multipath -l '

  but this cause error:
  : can't get udev device

  actually, we should use its real path like /dev/sdb, dev/sda to detect
  the multipath id.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1585940/+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 1633220] Re: Dovecot panics when sieve filter outputs much data

[Launchpad Bug Tracker]

This bug was fixed in the package dovecot - 1:2.2.22-1ubuntu2.2

---
dovecot (1:2.2.22-1ubuntu2.2) xenial; urgency=medium

  * d/p/fix-sieve-pigeonhole-crash-on-huge-mails.patch: Fix sieve-pigeonhole
crash when filtering too much data (LP: #1633220)

 -- Christian Ehrhardt   Wed, 09 Nov
2016 13:13:08 +0100

** Changed in: dovecot (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/1633220

Title:
  Dovecot panics when sieve filter outputs much data

Status in dovecot package in Ubuntu:
  Fix Released
Status in dovecot source package in Xenial:
  Fix Released
Status in dovecot source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * a crash of sieve when filtering large mails

   * The fix is done via a backport of upstream
     https://github.com/dovecot/pigeonhole/commit/a95b0579 which solves
     it by destroying the output stream before the fd is closed.
     Patch is nice and small, just moving two lines and applies as-is.

  [Test Case]

   * Set up dovecot with sieve filtering on top:
     - https://help.ubuntu.com/lts/serverguide/dovecot-server.html
     - http://wiki2.dovecot.org/Pigeonhole/Sieve/Examples
     - https://easyengine.io/tutorials/mail/server/sieve-filtering/
     Then push a bunch of larger mails through, >60k seems to be the area to
     trigger it.

   * It can be complex to set up, but fortunately the reporter is very
     active and willing to verify Xenial and Yakkety in their setup.

  [Regression Potential]

   * The change itself is rather minimal and from upstream.

   * given the change any regression we might overlook should be contained
     to sieve which is not default enabled without a user configuring it.

   * Did build and autopkgtest prior to suggest the upload all working 
 as expected (known to fail in Xenial, I fixed that back in Yakkety).

  [Other Info]

   * The change as done upstream is active for quite a while upstream and
     not changed anymore later on. It was even moved into dovecot-core to be
     reused for more use-cases and none of them triggered the need to
     rewrite the code, see:
     
https://github.com/dovecot/core/blob/master/src/lib-program-client/program-client.c#L94

  

  When using dovecot with vnd.dovecot.filter, where the filter returns
  at least ~60KB of data back to dovecot, dovecot panics (see dovecot
  log in attached apport report).

  The error's origin is the pigeonhole plugin. The described error is
  already fixed in the github repo for sieve-pigeonhole [1].

  We successfully managed to apply the patch locally for ubuntu's
  current version of pigeonhole (0.4.13 (7b14904)) by simply cherry
  picking the mentioned commit.

  System information:
    Description:Ubuntu 16.04.1 LTS
    Release:16.04
    dovecot-core:
  Installed: 1:2.2.22-1ubuntu2.1
    dovecot-sieve:
  Installed: 1:2.2.22-1ubuntu2.1

    $ doveconf | head -n2
    # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf
    # Pigeonhole version 0.4.13 (7b14904)

  [1] https://github.com/dovecot/pigeonhole/commit/a95b0579

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1633220/+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 1633220] Re: Dovecot panics when sieve filter outputs much data

[Launchpad Bug Tracker]

This bug was fixed in the package dovecot - 1:2.2.24-1ubuntu1.1

---
dovecot (1:2.2.24-1ubuntu1.1) yakkety; urgency=medium

  * d/p/fix-sieve-pigeonhole-crash-on-huge-mails.patch: Fix sieve-pigeonhole
crash when filtering too much data (LP: #1633220)

 -- Christian Ehrhardt   Wed, 09 Nov
2016 13:13:28 +0100

** Changed in: dovecot (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/1633220

Title:
  Dovecot panics when sieve filter outputs much data

Status in dovecot package in Ubuntu:
  Fix Released
Status in dovecot source package in Xenial:
  Fix Released
Status in dovecot source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * a crash of sieve when filtering large mails

   * The fix is done via a backport of upstream
     https://github.com/dovecot/pigeonhole/commit/a95b0579 which solves
     it by destroying the output stream before the fd is closed.
     Patch is nice and small, just moving two lines and applies as-is.

  [Test Case]

   * Set up dovecot with sieve filtering on top:
     - https://help.ubuntu.com/lts/serverguide/dovecot-server.html
     - http://wiki2.dovecot.org/Pigeonhole/Sieve/Examples
     - https://easyengine.io/tutorials/mail/server/sieve-filtering/
     Then push a bunch of larger mails through, >60k seems to be the area to
     trigger it.

   * It can be complex to set up, but fortunately the reporter is very
     active and willing to verify Xenial and Yakkety in their setup.

  [Regression Potential]

   * The change itself is rather minimal and from upstream.

   * given the change any regression we might overlook should be contained
     to sieve which is not default enabled without a user configuring it.

   * Did build and autopkgtest prior to suggest the upload all working 
 as expected (known to fail in Xenial, I fixed that back in Yakkety).

  [Other Info]

   * The change as done upstream is active for quite a while upstream and
     not changed anymore later on. It was even moved into dovecot-core to be
     reused for more use-cases and none of them triggered the need to
     rewrite the code, see:
     
https://github.com/dovecot/core/blob/master/src/lib-program-client/program-client.c#L94

  

  When using dovecot with vnd.dovecot.filter, where the filter returns
  at least ~60KB of data back to dovecot, dovecot panics (see dovecot
  log in attached apport report).

  The error's origin is the pigeonhole plugin. The described error is
  already fixed in the github repo for sieve-pigeonhole [1].

  We successfully managed to apply the patch locally for ubuntu's
  current version of pigeonhole (0.4.13 (7b14904)) by simply cherry
  picking the mentioned commit.

  System information:
    Description:Ubuntu 16.04.1 LTS
    Release:16.04
    dovecot-core:
  Installed: 1:2.2.22-1ubuntu2.1
    dovecot-sieve:
  Installed: 1:2.2.22-1ubuntu2.1

    $ doveconf | head -n2
    # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf
    # Pigeonhole version 0.4.13 (7b14904)

  [1] https://github.com/dovecot/pigeonhole/commit/a95b0579

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

---
gtk+2.0 (2.24.30-4ubuntu3) yakkety; 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 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/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 Committed
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 1616943] Re: Can't auth against U1 in g-s

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software - 3.20.1+git20161013.0
.d77d6cf-0ubuntu2

---
gnome-software (3.20.1+git20161013.0.d77d6cf-0ubuntu2) yakkety; urgency=medium

  * debian/control{,.in}: Build-Depend on libsnapd-glib-dev, to successfully
build the Snap plugin.
  * debian/rules: Pass --enable-snap, so that configure bails out if the Snap
plugin won't be built.

gnome-software (3.20.1+git20161013.0.d77d6cf-0ubuntu1) yakkety;
urgency=medium

  * New upstream snapshot from the wip/ubuntu branch at
git://git.gnome.org/gnome-software.
- Use snapd-glib to perform snapd login. This fixes non-root access being
  removed in snapd. (LP: #1616943)

 -- Iain Lane   Thu, 13 Oct 2016 16:52:55 +0100

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

Title:
  Can't auth against U1 in g-s

Status in gnome-software package in Ubuntu:
  Fix Released
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in snapd-glib source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Authentication using Ubuntu One credentials to install/remove snaps always  
fails. This is due to a behaviour change in snapd (no longer accepts login 
requests from non-root users). Existing credentials continue to work.

  [Test Case]
  1. Delete any existing credentials by deleting passwords marked 
"com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse.
  2. Start GNOME Software
  3. Search for a snap (e.g. "moon-buggy")
  4. Install Snap
  5. Enter Ubuntu One credentials when prompted

  Observed result:
  Dialog says "Incorrect email or password".

  Expected result:
  Authentication completes and the snap is installed.

  [Regression Potential]
  The solution is to use a new D-Bus service (snapd-login-service) and new 
library (snapd-glib) to get the Macaroon from snapd. This has some risk of 
introducing new bugs. The change is minimised (other snapd code paths 
unchanged) and the alternative is login to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+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 1596486] Re: libmuse_core.so: cannot open shared object file

[Launchpad Bug Tracker]

This bug was fixed in the package muse - 2.1.2-1ubuntu0.16.04.1

---
muse (2.1.2-1ubuntu0.16.04.1) xenial; urgency=medium

  * Force muse modules to be installed under /usr/lib/muse. (LP:
#1596486)

 -- James Cowgill   Fri, 02 Sep 2016 13:53:36 +0100

** Changed in: muse (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/1596486

Title:
  libmuse_core.so: cannot open shared object file

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

Bug description:
  [Impact]

  Since Ubuntu 15.10, muse does not start and gives the following error:

  $ muse
  muse: error while loading shared libraries: libmuse_core.so: cannot open 
shared object file: No such file or directory

  The fix for this should be backported to Xenial since muse is
  currently useless "as is".

  [Technical Details]

  Force muse modules to be installed under /usr/lib/muse

  Ubuntu CMake contains the script 'MultiArchCross.cmake' which is invoked for 
all Make packages and sets CMAKE_INSTALL_LIBDIR to include the multiarch path
  without the install prefix (ie something like "lib/x86_64-linux-gnu"). This
  variable is not defined when building on Debian.

  Muse constructs a LIB_INSTALL_DIR variable (when it's not defined) using
  CMAKE_INSTALL_LIBDIR or an alternate fallback. Unfortunately later on in the
  script when handling the RPATH settings, Muse assumes that LIB_INSTALL_DIR is 
an absolute path. This is true on Debian, but not on Ubuntu. This causes a 
bogus RPATH to be inserted into the main Muse executable which prevents Muse 
from finding any of it's modules and immediately crashes on startup.

  The simple fix is to force LIB_INSTALL_DIR=/usr/lib. Although an
  Ubuntu specific problem, it does no harm to do this on Debian as well.

  [Test Case]

  From within a terminal window, run "muse". The following error is printed:
  muse: error while loading shared libraries: libmuse_core.so: cannot open 
shared object file: No such file or directory

  When working normally, the muse arranger window should appear. If an error
  appears about Jack not running, you can ignore it.

  [Regression Potential]

  Muse is a totally independent application with no reverse dependencies
  in the archive. Therefore it is unlikely there will be any regressions
  in other packages.

  Since Muse is completely non-functional in Xenial, it's difficult for
  it to regress any further. :)

  [Other Info]

  A workaround for this bug is to set the linker path manually when
  running muse. For example:

  LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/muse/modules muse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/muse/+bug/1596486/+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 1640786] Re: netfilter regression introducing a performance slowdown in binary arp/ip/ip6tables

[Joseph Salisbury]

** No longer affects: linux (Ubuntu Trusty)

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

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

** Changed in: linux (Ubuntu Xenial)
   Status: New => 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/1640786

Title:
  netfilter regression introducing a performance slowdown in binary
  arp/ip/ip6tables

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

Bug description:
  Explanation :

  It has been brought to my attention that Ubuntu kernel 4.4 has a
  severe netfilter regression affecting the performance of
  "/sbin/iptables" command, especially when adding large number of
  policies. My source have documented everything here[2].

  I was able to reproduce the situation on my side, and a kernel bisect
  identified the same offending commit[1] as my source found for this
  bug.

  Running the commit right before the offending one have proven to have
  expected performance :

  # commit [71ae0dff] <== Offending commit
  real 0m33.314s
  user 0m1.520s
  sys 0m26.192s

  # commit [d7b59742] <== Right before offending commit
  real 0m5.952s
  user 0m0.124s
  sys 0m0.220s

  Reproducer :

  $ iptables -F
  $ echo 3 > /proc/sys/vm/drop_caches
  $ time (./list-addrs 3000 | xargs -n1 iptables -A FORWARD -j ACCEPT -s)

  "list-addrs" script can be found here[3]

  Note :

  * "iptables-restore" doesn't suffer of that netfilter regression, and
  I'm also aware that "iptables-restore" is the favourite approach since
  it is way more efficient than iptables that is executed over and over,
  once for each policy one want to set, but since "/sbin/iptables" takes
  vastly longer to perform with that commit, I think this need to be
  address anyway.

  * I also tried with the latest and greatest iptables upstream code,
  and got the same result.

  Reference :
  [1] - 
https://github.com/torvalds/linux/commit/71ae0dff02d756e4d2ca710b79f2ff5390029a5f
  [2] - https://gist.github.com/williammartin/b75e3faf5964648299e4d985413e6c0c
  [3] - 
https://gist.github.com/williammartin/b75e3faf5964648299e4d985413e6c0c#file-list-addrs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640786/+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 1643901] Re: flxdec security update tracking bug

[Mathew Hodson]

** No longer affects: gst-plugins-good0.10 (Ubuntu Yakkety)

** No longer affects: gst-plugins-good0.10 (Ubuntu Zesty)

** Changed in: gst-plugins-good0.10 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gst-plugins-good0.10 (Ubuntu)
   Status: Invalid => Fix Released

** No longer affects: gst-plugins-good1.0 (Ubuntu Precise)

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

Title:
  flxdec security update tracking bug

Status in gst-plugins-good0.10 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Confirmed
Status in gst-plugins-good0.10 source package in Precise:
  Fix Released
Status in gst-plugins-good0.10 source package in Trusty:
  Fix Released
Status in gst-plugins-good1.0 source package in Trusty:
  Fix Released
Status in gst-plugins-good0.10 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Yakkety:
  Fix Released
Status in gst-plugins-good1.0 source package in Zesty:
  Confirmed

Bug description:
  This bug is to track the security update to fix the flxdec out-of-
  bounds write.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1643901/+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 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

[Matthias Klumpp]

The Debian bug is about the warning message not being actionable when it
appears, it does *not* appear at Debian under normal circumstances,
hence it is a completely different issue (and one that isn't easily
solvable).

** Changed in: appstream (Debian)
   Importance: Unknown => Undecided

** Changed in: appstream (Debian)
   Status: Unknown => New

** Changed in: appstream (Debian)
 Remote watch: Debian Bug tracker #820774 => None

** Package changed: appstream (Debian) => debian

** Changed in: debian
   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/1644498

Title:
  apt-get update returns "AppStream cache update completed, but some
  metadata was ignored due to errors." periodically

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  In Progress
Status in Debian:
  Invalid

Bug description:
  [Impact]

   * The recent update of the Ubuntu asgen instance yielded it to
  generate modern metadata. While we could tell asgen to generate old-
  style metadata, fixing appstream is the better idea, since we already
  applied similar patches to appstream-glib (and having this package
  hold back updates is a bad idea). Currently, the unknown metadata is
  considered to be broken by appstream and it displays a warning about
  that issue during an `apt update`

   * The attached patch includes a second change to make AppStream more
  robust against broken YAML data, ensuring LP #1579712 can not be
  triggered on purpose or due to broken disks creating damaged YAML
  structure.

  [Test Case 1]

   * apt update
   * Check for errors about metadata being ignored

  [Test Case 2]

   * appstreamcli refresh --force
   * Check for errors about metadata being ignored
   * Check if we ignored data that should be present
 (search for it via `appstreamcli search `)
   * Run `appstreamcli status` and see if we still have information on the same 
amount of components as prior to the update.

  [Regression Potential]

   * Medium; The works case would be KDE Discover and GNOME Software
  loosing information on available software, but this risk is very low
  and the patch to fix this bug is very simple and has almost no
  regression potential. The YAML parser fix patch is a bit more complex,
  but should have no sideeffects.

  [Original report]

  Periodically I get emails from a machine with the subject:

  Cron  if [ -x /etc/munin/plugins/apt_all ]; then
  /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
  /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
  >/dev/null; fi

  And a body of:

  AppStream cache update completed, but some metadata was ignored due to
  errors.

  I have a machine monitored by Munin.  One of the plugins used on that
  machine is /etc/munin/plugins/apt which periodically counts the number
  of packets that can be upgraded.  This is achieved by a crontab entry
  installed from the package which looks like this:

  #
  # cron-jobs for munin-node
  #

  MAILTO=root

  # If the APT plugin is enabled, update packages databases approx. once
  # an hour (12 invokations an hour, 1 in 12 chance that the update will
  # happen), but ensure that there will never be more than two hour (7200
  # seconds) interval between updates..
  */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then 
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x 
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 
>/dev/null; fi

  For many months everything has been running smoothly.  On the 23rd
  November 2016 I started getting the "AppStream cache update completed,
  but some metadata was ignored due to errors." messages at a rate of
  about ten a day.

  I did a quick Google search which turned up a handful of bugs from earlier 
this year, such as
  Bug1575248.  That is marked as Fixed Released though, so I am raising this 
new bug.

  If there are any further diagnostic details I can provide, please let
  me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 09:57:18 2016
  InstallationDate: Installed on 2013-05-08 (1295 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
  JournalErrors:
   -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 
GMT. --
   Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
  SourcePackage: appstream
 

[Group.of.nepali.translators] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

[Mathew Hodson]

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

** Bug watch added: Debian Bug tracker #820774
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820774

** Also affects: appstream (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820774
   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/1644498

Title:
  apt-get update returns "AppStream cache update completed, but some
  metadata was ignored due to errors." periodically

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  In Progress
Status in appstream package in Debian:
  Unknown

Bug description:
  [Impact]

   * The recent update of the Ubuntu asgen instance yielded it to
  generate modern metadata. While we could tell asgen to generate old-
  style metadata, fixing appstream is the better idea, since we already
  applied similar patches to appstream-glib (and having this package
  hold back updates is a bad idea). Currently, the unknown metadata is
  considered to be broken by appstream and it displays a warning about
  that issue during an `apt update`

   * The attached patch includes a second change to make AppStream more
  robust against broken YAML data, ensuring LP #1579712 can not be
  triggered on purpose or due to broken disks creating damaged YAML
  structure.

  [Test Case 1]

   * apt update
   * Check for errors about metadata being ignored

  [Test Case 2]

   * appstreamcli refresh --force
   * Check for errors about metadata being ignored
   * Check if we ignored data that should be present
 (search for it via `appstreamcli search `)
   * Run `appstreamcli status` and see if we still have information on the same 
amount of components as prior to the update.

  [Regression Potential]

   * Medium; The works case would be KDE Discover and GNOME Software
  loosing information on available software, but this risk is very low
  and the patch to fix this bug is very simple and has almost no
  regression potential. The YAML parser fix patch is a bit more complex,
  but should have no sideeffects.

  [Original report]

  Periodically I get emails from a machine with the subject:

  Cron  if [ -x /etc/munin/plugins/apt_all ]; then
  /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
  /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
  >/dev/null; fi

  And a body of:

  AppStream cache update completed, but some metadata was ignored due to
  errors.

  I have a machine monitored by Munin.  One of the plugins used on that
  machine is /etc/munin/plugins/apt which periodically counts the number
  of packets that can be upgraded.  This is achieved by a crontab entry
  installed from the package which looks like this:

  #
  # cron-jobs for munin-node
  #

  MAILTO=root

  # If the APT plugin is enabled, update packages databases approx. once
  # an hour (12 invokations an hour, 1 in 12 chance that the update will
  # happen), but ensure that there will never be more than two hour (7200
  # seconds) interval between updates..
  */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then 
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x 
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 
>/dev/null; fi

  For many months everything has been running smoothly.  On the 23rd
  November 2016 I started getting the "AppStream cache update completed,
  but some metadata was ignored due to errors." messages at a rate of
  about ten a day.

  I did a quick Google search which turned up a handful of bugs from earlier 
this year, such as
  Bug1575248.  That is marked as Fixed Released though, so I am raising this 
new bug.

  If there are any further diagnostic details I can provide, please let
  me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 09:57:18 2016
  InstallationDate: Installed on 2013-05-08 (1295 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
  JournalErrors:
   -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 
GMT. --
   Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
  SourcePackage: appstream
  UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago)

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

[Group.of.nepali.translators] [Bug 1645453] [NEW] Xenial update to v4.4.35 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.35 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.35 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/1645453

Title:
  Xenial update to v4.4.35 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.35 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.35 stable release shall be
  applied:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645453/+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 1636838] Re: Failed to boot

[Launchpad Bug Tracker]

This bug was fixed in the package u-boot - 2016.03+dfsg1-6ubuntu2

---
u-boot (2016.03+dfsg1-6ubuntu2) zesty; urgency=medium

  * From upstream u-boot: (LP: #1636838)
- debian/patches/rpi-import-mkknlimg.patch: import tools/mkknlimg from
  Xenial/raspi2 - scripts/mkknlimg @ 83a3ebb
- debian/u-boot-rpi.postinst: pass u-boot.bin through mkknlimg before
  installing it as /boot/firmware/uboot.bin
- debian/patches/serial-pl01x-Add-support-for-devices-with-the-rate-p.patch:
  Skip serial clock initialization when it's done by the firmware.

 -- Paolo Pisati   Wed, 09 Nov 2016 17:09:29
+0200

** Changed in: u-boot (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/1636838

Title:
  Failed to boot

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux-firmware-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in u-boot package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Xenial:
  New
Status in linux-firmware-raspi2 source package in Xenial:
  New
Status in linux-raspi2 source package in Xenial:
  New
Status in u-boot source package in Xenial:
  New

Bug description:
  [Impact]

   * Unable to boot into system after upgrade to 4.4.0-1030.37

  [Test Case]

   * fresh install ubuntu-16.04.1-preinstalled-server-
  armhf+raspi2.img.xz

   * enable -proposed and 'apt full-upgrade'

  [Regression Potential]

   * red led still on, but few green led blinks then stay at the black
  screen(hdmi on)

  [Other Info]

   * restore the working boot partition backup image could recover the
  situation

  [Solution]

  * The latest X/raspi2 kernel in -proposed blows the space the
  bootloader reserves for the DTB, making the board unbootable (it only
  happens with classic rpi2 images created by the Foundation, Snappy is
  fine)

  * Ppa:p-pisati/misc has these 3 new packages that fix it:

   - linux-firmware-raspi2 - contains the latest Broadom fw release, and
 upon installation checks that /boot/firmware/config.txt contains the
 new DTB memory location, and if not, it does the necessary
 modification on behalf of the user
   
   - flash-kernel - modifies uboot.env to find the DTB in the new memory 
location
   
   - uboot -  update uboot to work with the new boot firmware (aka skip
 serial initialization if already done by the fw), contains the
 mkknlimg required when installing a new u-boot binary and correctly
 installs the uboot binary in the vfat partition

  [How to test it]

  * Install a fresh foundation image, add my misc ppa and the xenial
  -proposed repository, apt-get update && dist-upgrade, once the board
  completes the upgrade reboot it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1636838/+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 1618543] Re: freeipmi lacks IPv6 support

[LaMont Jones]

** Also affects: freeipmi (Ubuntu Yakkety)
   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/1618543

Title:
  freeipmi lacks IPv6 support

Status in MAAS:
  Triaged
Status in freeipmi package in Ubuntu:
  Triaged
Status in freeipmi source package in Xenial:
  New
Status in freeipmi source package in Yakkety:
  New

Bug description:
  1.4.11 lacks any ipv6 support.  1.5.3 (current upstream from 1 Aug
  2016) also lacks ipv6 support.

  Note that both ipmitool (since 2014 or so) and openipmi (since
  2003-11-11) support IPv6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1618543/+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 1644615] Re: linux-snapdragon: 4.4.0-1038.42 -proposed tracker

[Brad Figg]

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

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

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

** 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) => Luis Henriques 
(henrix)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

** 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 --
  kernel-stable-master-bug: 1644611
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Monday, 28. November 2016 15:31 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: 1644611
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 28. November 2016 15:31 UTC
+ 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/1644615

Title:
  linux-snapdragon: 4.4.0-1038.42 -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:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: 1644611
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1644615/+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 1643524] Re: linux-hwe-edge: 4.8.0-28.30~16.04.1 -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/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

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

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

** Changed in: kernel-sru-workflow/verification-testing
   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/1643524

Title:
  linux-hwe-edge: 4.8.0-28.30~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Incomplete
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-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-28.30~16.04.1 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: 1641083

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1643524/+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 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

[Robie Basak]

Based on the investigation so far, it seems to me that this is entirely
a kernel bug, and there is nothing required in the bridge-utils package
in order to fix this issue. So I'm marking this bug as Invalid for
bridge-utils. The kernel tasks remain open. If this is incorrect, please
explain why you expect to need a fix in bridge-utils and reopen that
task.

** Changed in: bridge-utils (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: bridge-utils (Ubuntu Xenial)
   Status: Confirmed => Invalid

** Changed in: bridge-utils (Ubuntu Yakkety)
   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/1616107

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Invalid

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 

[Group.of.nepali.translators] [Bug 1645278] Re: Upstream stable 4.4.34 and 4.8.10 regression

[Luis Henriques]

** Summary changed:

- Upstream stable 4.4.34 regression
+ Upstream stable 4.4.34 and 4.8.10 regression

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

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Luis Henriques (henrix)

** Description changed:

- Upstream stable release 4.4.34 introduced a regression that is already
- fixed in mainline but hasn't been applied to stable kernels yet (nor to
- Ubuntu kernels).  Here's the thread where the bug was reported:
+ Upstream stable releases 4.4.34 and 4.8.10 introduced a regression that
+ is already fixed in mainline but hasn't been applied to stable kernels
+ yet (nor to Ubuntu kernels).  Here's the thread where the bug was
+ reported:
  
-   http://lkml.iu.edu/hypermail/linux/kernel/1611.2/04851.html
+   http://lkml.iu.edu/hypermail/linux/kernel/1611.2/04851.html
  
  Here's a partial transcript of the report:
  
-  "This update broke PXE boot on our 4-way AMD boxes. The kernel panics in
-   eth_type_trans(), presumably during kernel-level IP autoconfiguration,
-   see [1]. Bisection points me at 5c67f947 (net: __skb_flow_dissect()
-   must cap its return value). And indeed, reverting this commit fixes
-   the problem for me."
+  "This update broke PXE boot on our 4-way AMD boxes. The kernel panics in
+   eth_type_trans(), presumably during kernel-level IP autoconfiguration,
+   see [1]. Bisection points me at 5c67f947 (net: __skb_flow_dissect()
+   must cap its return value). And indeed, reverting this commit fixes
+   the problem for me."
  
  This issue is fixed with mainline commit:
  
  commit c9b8af1330198ae241cd545e1f040019010d44d9
  Author: Eric Dumazet 
  Date:   Tue Nov 22 11:17:30 2016 -0800
  
- flow_dissect: call init_default_flow_dissectors() earlier
+ flow_dissect: call init_default_flow_dissectors() earlier

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

Title:
  Upstream stable 4.4.34 and 4.8.10 regression

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Upstream stable releases 4.4.34 and 4.8.10 introduced a regression
  that is already fixed in mainline but hasn't been applied to stable
  kernels yet (nor to Ubuntu kernels).  Here's the thread where the bug
  was reported:

    http://lkml.iu.edu/hypermail/linux/kernel/1611.2/04851.html

  Here's a partial transcript of the report:

   "This update broke PXE boot on our 4-way AMD boxes. The kernel panics in
    eth_type_trans(), presumably during kernel-level IP autoconfiguration,
    see [1]. Bisection points me at 5c67f947 (net: __skb_flow_dissect()
    must cap its return value). And indeed, reverting this commit fixes
    the problem for me."

  This issue is fixed with mainline commit:

  commit c9b8af1330198ae241cd545e1f040019010d44d9
  Author: Eric Dumazet 
  Date:   Tue Nov 22 11:17:30 2016 -0800

  flow_dissect: call init_default_flow_dissectors() earlier

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645278/+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 1643797] Re: System stalls when creating device node on booting

[Luis Henriques]

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

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

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

Title:
  System stalls when creating device node on booting

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  We've found on some Apollo Lake system stalls for around 4 seconds on
  function `wait_for_completion` when creating nodes in devtmpfs. With
  70+ nodes created it can be stalled for 5+ minutes when booting.

  With bisecting we've found the patch can fix this issue:

  commit 0905f04eb21fc1c2e690bed5d0418a061d56c225
  Author: Yuyang Du 
  AuthorDate: Thu Dec 17 07:34:27 2015 +0800
  Commit: Ingo Molnar 
  CommitDate: Wed Jan 6 11:06:29 2016 +0100

  sched/fair: Fix new task's load avg removed from source CPU in
  wake_up_new_task()

  This patch can be clean picked, and shows positive result on multiple
  Apollo Lake system. The patch is already in v4.5+ so Yakkety is not
  affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1643797/+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 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

[Iain Lane]

Uploaded, thank you!

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

** Changed in: appstream (Ubuntu Xenial)
   Status: New => In Progress

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

** Changed in: appstream (Ubuntu Xenial)
 Assignee: (unassigned) => Matthias Klumpp (ximion)

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

Title:
  apt-get update returns "AppStream cache update completed, but some
  metadata was ignored due to errors." periodically

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

Bug description:
  [Impact]

   * The recent update of the Ubuntu asgen instance yielded it to
  generate modern metadata. While we could tell asgen to generate old-
  style metadata, fixing appstream is the better idea, since we already
  applied similar patches to appstream-glib (and having this package
  hold back updates is a bad idea). Currently, the unknown metadata is
  considered to be broken by appstream and it displays a warning about
  that issue during an `apt update`

   * The attached patch includes a second change to make AppStream more
  robust against broken YAML data, ensuring LP #1579712 can not be
  triggered on purpose or due to broken disks creating damaged YAML
  structure.

  [Test Case 1]

   * apt update
   * Check for errors about metadata being ignored

  [Test Case 2]

   * appstreamcli refresh --force
   * Check for errors about metadata being ignored
   * Check if we ignored data that should be present
 (search for it via `appstreamcli search `)
   * Run `appstreamcli status` and see if we still have information on the same 
amount of components as prior to the update.

  [Regression Potential]

   * Medium; The works case would be KDE Discover and GNOME Software
  loosing information on available software, but this risk is very low
  and the patch to fix this bug is very simple and has almost no
  regression potential. The YAML parser fix patch is a bit more complex,
  but should have no sideeffects.

  [Original report]

  Periodically I get emails from a machine with the subject:

  Cron  if [ -x /etc/munin/plugins/apt_all ]; then
  /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
  /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
  >/dev/null; fi

  And a body of:

  AppStream cache update completed, but some metadata was ignored due to
  errors.

  I have a machine monitored by Munin.  One of the plugins used on that
  machine is /etc/munin/plugins/apt which periodically counts the number
  of packets that can be upgraded.  This is achieved by a crontab entry
  installed from the package which looks like this:

  #
  # cron-jobs for munin-node
  #

  MAILTO=root

  # If the APT plugin is enabled, update packages databases approx. once
  # an hour (12 invokations an hour, 1 in 12 chance that the update will
  # happen), but ensure that there will never be more than two hour (7200
  # seconds) interval between updates..
  */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then 
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x 
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 
>/dev/null; fi

  For many months everything has been running smoothly.  On the 23rd
  November 2016 I started getting the "AppStream cache update completed,
  but some metadata was ignored due to errors." messages at a rate of
  about ten a day.

  I did a quick Google search which turned up a handful of bugs from earlier 
this year, such as
  Bug1575248.  That is marked as Fixed Released though, so I am raising this 
new bug.

  If there are any further diagnostic details I can provide, please let
  me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 09:57:18 2016
  InstallationDate: Installed on 2013-05-08 (1295 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
  JournalErrors:
   -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 
GMT. --
   Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
  SourcePackage: appstream
  UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago)

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

[Group.of.nepali.translators] [Bug 1641203] Re: SSSD can't process GPO from Active Directory when it contains lines with no equal sign

[Robie Basak]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Looks like the commit wanted is 21a28c in sssd, which is present in
1.14.2 but not 1.13.4. So this is Fix Committed as 1.14.2 is in zesty-
proposed.

Additionally it looks like backports of fbaaf4, 9591b1 and 8481bb are
needed to ding-libs. These are present in 0.6.0 in Zesty but not 0.5.0
in Xenial and Yakkety. So this is Fix Released for Zesty, and open in
Xenial.

For a fix for an existing stable release, please comment with a
justification against https://wiki.ubuntu.com/StableReleaseUpdates#When
and complete steps 1 through 4 in
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure - and go ahead
with all the steps if you can. This needs to be for both ding-libs and
sssd. If you could prepare the backports, that would be ideal. Note that
that SRU team would need to make a final decision but I think it seems
likely that it would be OK in this case.

** Also affects: ding-libs (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: ding-libs (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: ding-libs (Ubuntu)
   Status: New => Fix Released

** Changed in: ding-libs (Ubuntu Xenial)
   Status: New => Triaged

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

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

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

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

** Changed in: ding-libs (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  SSSD can't process GPO from Active Directory when it contains lines
  with no equal sign

Status in ding-libs package in Ubuntu:
  Fix Released
Status in sssd package in Ubuntu:
  Fix Committed
Status in ding-libs source package in Xenial:
  Triaged
Status in sssd source package in Xenial:
  Triaged

Bug description:
  (Fri Nov 11 14:55:52 2016) [sssd[be[MYDOMAIN.COM]]] 
[ad_gpo_store_policy_settings] (0x0020): 
[/var/lib/sss/gpo_cache/mydomain.com/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/Machine/Microsoft/Windows
 NT/SecEdit/GptTmpl.inf]: ini_config_parse failed [5][Input/output error]
  (Fri Nov 11 14:55:52 2016) [sssd[be[MYDOMAIN.COM]]] 
[ad_gpo_store_policy_settings] (0x0020): Error (5) on line 20: Equal sign is 
missing.
  (Fri Nov 11 14:55:52 2016) [sssd[be[MYDOMAIN.COM]]] 
[ad_gpo_store_policy_settings] (0x0020): Error encountered: 5.
  (Fri Nov 11 14:55:52 2016) [sssd[be[MYDOMAIN.COM]]] [ad_gpo_cse_done] 
(0x0040): ad_gpo_store_policy_settings failed: [5](Input/output error)
  (Fri Nov 11 14:55:52 2016) [sssd[be[MYDOMAIN.COM]]] [ad_gpo_access_done] 
(0x0040): GPO-based access control failed.
  (Fri Nov 11 14:55:52 2016) [sssd[be[MYDOMAIN.COM]]] [be_pam_handler_callback] 
(0x0100): Backend returned: (3, 4, Input/output error) [Internal Error]

  Upstreams bugreport and patch:
  https://fedorahosted.org/sssd/ticket/2751

  Please backport to xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ding-libs/+bug/1641203/+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 1645278] [NEW] Upstream stable 4.4.34 regression

[Luis Henriques]

Public bug reported:

Upstream stable release 4.4.34 introduced a regression that is already
fixed in mainline but hasn't been applied to stable kernels yet (nor to
Ubuntu kernels).  Here's the thread where the bug was reported:

  http://lkml.iu.edu/hypermail/linux/kernel/1611.2/04851.html

Here's a partial transcript of the report:

 "This update broke PXE boot on our 4-way AMD boxes. The kernel panics in
  eth_type_trans(), presumably during kernel-level IP autoconfiguration,
  see [1]. Bisection points me at 5c67f947 (net: __skb_flow_dissect()
  must cap its return value). And indeed, reverting this commit fixes
  the problem for me."

This issue is fixed with mainline commit:

commit c9b8af1330198ae241cd545e1f040019010d44d9
Author: Eric Dumazet 
Date:   Tue Nov 22 11:17:30 2016 -0800

flow_dissect: call init_default_flow_dissectors() earlier

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Luis Henriques (henrix)
 Status: Triaged

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Luis Henriques (henrix)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Luis Henriques (henrix)

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

Title:
  Upstream stable 4.4.34 regression

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

Bug description:
  Upstream stable release 4.4.34 introduced a regression that is already
  fixed in mainline but hasn't been applied to stable kernels yet (nor
  to Ubuntu kernels).  Here's the thread where the bug was reported:

http://lkml.iu.edu/hypermail/linux/kernel/1611.2/04851.html

  Here's a partial transcript of the report:

   "This update broke PXE boot on our 4-way AMD boxes. The kernel panics in
eth_type_trans(), presumably during kernel-level IP autoconfiguration,
see [1]. Bisection points me at 5c67f947 (net: __skb_flow_dissect()
must cap its return value). And indeed, reverting this commit fixes
the problem for me."

  This issue is fixed with mainline commit:

  commit c9b8af1330198ae241cd545e1f040019010d44d9
  Author: Eric Dumazet 
  Date:   Tue Nov 22 11:17:30 2016 -0800

  flow_dissect: call init_default_flow_dissectors() earlier

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645278/+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 1644530] Re: keepalived fails to restart cleanly due to the wrong systemd settings

[ChristianEhrhardt]

Thank you for your report and your help to make Ubuntu better.
1.2.24 is already in the coming Ubuntu relase, so that is fixed there.

To consider an SRU [1] there should be some clear steps to reproduce this issue.
Did you find on your debugging a reliable way to trigger this issue so it can 
be tested and verified?

1: https://wiki.ubuntu.com/StableReleaseUpdates

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

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

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

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

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

Title:
  keepalived fails to restart cleanly due to the wrong systemd settings

Status in keepalived package in Ubuntu:
  Fix Released
Status in keepalived source package in Xenial:
  Confirmed

Bug description:
  Because "PIDFile=" directive is missing in the systemd unit file,
  keepalived sometimes fails to kill all old processes. The old
  processes remain with old settings and cause unexpected behaviors. The
  detail of this bug is described in this ticket in upstream:
  https://github.com/acassen/keepalived/issues/443.

  The official systemd unit file is available since version 1.2.24 by
  this commit:

  
https://github.com/acassen/keepalived/commit/635ab69afb44cd8573663e62f292c6bb84b44f15

  This includes "PIDFile" directive correctly:

  PIDFile=/var/run/keepalived.pid

  We should go the same way.

  I am using Ubuntu 16.04.1, kernel 4.4.0-45-generic.

  Package: keepalived
  Version: 1.2.19-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1644530/+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 1640513] Re: linux-raspi2: 4.4.0-1032.39 -proposed tracker

[Po-Hsu Lin]

** Changed in: kernel-sru-workflow/regression-testing
   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/1640513

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

Status in Kernel SRU Workflow:
  Incomplete
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
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:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-1032.39 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: 1636941
  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/1640513/+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