[Group.of.nepali.translators] [Bug 1827930] Re: [SRU] Please generate tarball for WSL

2019-06-06 Thread Launchpad Bug Tracker
This bug was fixed in the package livecd-rootfs - 2.578.5

---
livecd-rootfs (2.578.5) disco; urgency=medium

  [ Balint Reczey ]
  * Build WSL rootfs tarball (LP: #1827930)

  [ Steve Langasek ]
  * Strip translation files out of the minimal images, another thing that
goes unused when there is no human console user (and we already don't
have the locales themselves present on a minimal image).  LP: #1829333.

 -- Steve Langasek   Thu, 30 May 2019
12:13:55 -0700

** Changed in: livecd-rootfs (Ubuntu Disco)
   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/1827930

Title:
  [SRU] Please generate tarball for WSL

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * The tarball for Ubuntu WSL Windows Store apps is repacked from the
  ${release}-server-cloudimg-amd64-root.tar.xz tarball with a few minor
  changes as part or the appx build process. Since more customization is
  planned for the WSL tarball livecd-rootfs' code is a better place for
  maintaining them.

  [Test Case]

   * Check livecd-rootfs autopkgtest output and observe the wsl tarball being 
generated among other non-minimal images. When building minimal images the WSL 
tarball should not be built.
   * Optionally use the built tarball to build the Ubuntu WSL app and verify 
that it can be installed on Windows 10.

  [Regression Potential]

   * Since this is a separate tarball to be built there are no expected
  regressions affecting other images.

  [Other Info]
   * At the moment only LTS releases are released to the Microsoft Store thus 
SRUs to Disco and Cosmic can be skipped as they won't be used. There is an 
ongoing discussion on whether we make Disco available or if so with which 
additional changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1827930/+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 1831748] Re: Update /etc/nginx/sites-enabled/default with php-fpm 7.2

2019-06-06 Thread Paride Legovini
Thank you for taking the time to file this bug report and helping to
make Ubuntu better. Your report is valid, however this issue alone does
not justify a Stable Release Update (SRU), the procedure to fix bugs in
existing Ubuntu releases. The SRU procedure and policy is documented
here:

  https://wiki.ubuntu.com/StableReleaseUpdates

However there is no reason to keep things as they are in future
releases, so I targeted this bug to Ubuntu 19.10. As it is highly
probable for that comment to get out of sync again with the default
version of php (the two packages are updated independently), a comment
should be added asking the user to adapt the php version to match the
currently installed version.

** Also affects: nginx (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: nginx (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: nginx (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: nginx (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: nginx (Ubuntu Bionic)
   Status: New => Won't Fix

** Changed in: nginx (Ubuntu Cosmic)
   Status: New => Won't Fix

** Changed in: nginx (Ubuntu Disco)
   Status: New => Won't Fix

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

** Tags removed: fpm php
** Tags added: server-next

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

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

Title:
  Update /etc/nginx/sites-enabled/default with php-fpm 7.2

Status in nginx package in Ubuntu:
  Triaged
Status in nginx source package in Xenial:
  Won't Fix
Status in nginx source package in Bionic:
  Won't Fix
Status in nginx source package in Cosmic:
  Won't Fix
Status in nginx source package in Disco:
  Won't Fix

Bug description:
  After install Nginx creates a file called /etc/nginx/sites-
  enabled/default which is a link to /etc/nginx/sites-available/default

  A line inside is commented for use in PHP-FPM (7.0):

   #location ~ \.php$ {
  #   include snippets/fastcgi-php.conf;
  #
  #   # With php-fpm (or other unix sockets):
  #   fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
  #   # With php-cgi (or other tcp sockets):
  #   fastcgi_pass 127.0.0.1:9000;
  #}

  
  The php-fpm line should read: 
  #   fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;

  as Ubuntu 18.04 uses PHP 7.2 not Debians PHP 7.0

  A simple problem but a confusion I've noticed come up more than once.

  
  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  Installed: 1.14.0-0ubuntu1.2
Candidate: 1.14.0-0ubuntu1.2
Version table:
   *** 1.14.0-0ubuntu1.2 500
  500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.14.0-0ubuntu1 500
  500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1831748/+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 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour

2019-06-06 Thread Steve Langasek
** Also affects: initramfs-tools (Ubuntu Eoan)
   Importance: Medium
   Status: New

** Tags removed: rls-ee-incoming

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

Title:
  panic=-1 is completely ignored by the initrd causing unexpected
  behaviour

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools source package in Xenial:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in initramfs-tools source package in Eoan:
  New

Bug description:
  in Ubuntu Core we default to using panic=-1 on the kernel command line
  (documented at [1]) to speed up the auto-rollback mechanism of the
  kernel. on a kernel level this works just fine and the system reboots
  immediately ...

  when in the initramfs during boot and a panic occurs, no reboot
  happens at all, the initrd spawns a shell regardless of the panic=
  value ...

  this is caused by a filter in  /usr/share/initramfs-tools/init

  panic=*)
  panic="${x#panic=}"
  case ${panic} in
  *[![:digit:].]*)
  panic=
  ;;
  esac
  ;;

  this function only lets positive values through, else panic= simply
  gets unset

  the panic() function itself is also not capable of handling negative
  values, it has a sleep call that interprets negative values as
  commandline options instead of simply ignoring a negative sleep time
  [2] (line 11).

  the filter in the init script should allow the -1 value (to comply
  with the kernel documentation and behaviour) and the panic() function
  should properly skip the sleep call when a negative value for panic=
  is set.

  [1] 
https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931
  [2] https://paste.ubuntu.com/p/mswD8Cd869/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+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 1829196] Re: linux-gcp: 4.15.0-1033.35~16.04.1 -proposed tracker

2019-06-06 Thread Ubuntu Kernel Bot
All tasks have been completed and the bug is being set to Fix Released


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

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1829847 (linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829200
  phase: Ready for Security
  phase-changed: Thursday, 06. June 2019 08:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-gcp: 4.15.0-1033.35~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
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 snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1829847 (linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829200
  phase: Ready for Security
  phase-changed: Thursday, 06. June 2019 08:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829196/+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 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress

2019-06-06 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.7.5

---
apt (1.7.5) cosmic; urgency=medium

  * Add test case for local-only packages pinned to never
  * Prevent shutdown while running dpkg (LP: #1820886)
  * Add linux-{buildinfo,image-unsigned,source} versioned kernel pkgs
(LP: #1821640)

 -- Julian Andres Klode   Tue, 07 May 2019 11:04:15
+0200

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

** Changed in: apt (Ubuntu Bionic)
   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/1820886

Title:
  Potential inconsistency due to system halt/reboot being allowed when
  package installation in progress

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  Fix Released

Bug description:
  [System]
  Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, 
Cosmic).

  [Impact]
  Package installation turns into an inconsistent state if system is rebooted 
in the middle of an apt install/upgrade.

  [Test Case]
  1. User1 at Ubuntu box issues "sudo apt-get upgrade";
  2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
  3. System reboots and potentially turns into an inconsistent state.

  [Remarks]
  APT should automatically inhibit system halts/reboots while packages being 
installed/removed. A similar behavior to what is shown by unattended-upgrades.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress

2019-06-06 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.6.11

---
apt (1.6.11) bionic; urgency=medium

  * Add test case for local-only packages pinned to never
  * Prevent shutdown while running dpkg (LP: #1820886)
  * Add linux-{buildinfo,image-unsigned,source} versioned kernel pkgs
(LP: #1821640)

 -- Julian Andres Klode   Tue, 07 May 2019 11:19:29
+0200

** Changed in: apt (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/1820886

Title:
  Potential inconsistency due to system halt/reboot being allowed when
  package installation in progress

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  Fix Released

Bug description:
  [System]
  Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, 
Cosmic).

  [Impact]
  Package installation turns into an inconsistent state if system is rebooted 
in the middle of an apt install/upgrade.

  [Test Case]
  1. User1 at Ubuntu box issues "sudo apt-get upgrade";
  2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
  3. System reboots and potentially turns into an inconsistent state.

  [Remarks]
  APT should automatically inhibit system halts/reboots while packages being 
installed/removed. A similar behavior to what is shown by unattended-upgrades.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system

2019-06-06 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.7.5

---
apt (1.7.5) cosmic; urgency=medium

  * Add test case for local-only packages pinned to never
  * Prevent shutdown while running dpkg (LP: #1820886)
  * Add linux-{buildinfo,image-unsigned,source} versioned kernel pkgs
(LP: #1821640)

 -- Julian Andres Klode   Tue, 07 May 2019 11:04:15
+0200

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

** Changed in: apt (Ubuntu Bionic)
   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/1821640

Title:
  Missing pattern for linux-image-unsigned keeps autoremovable kernels
  on the system

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  Fix Released
Status in apt source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  Unattended-upgrades keeps versioned kernel packages because they don't match 
known kernel package patterns:

  ...
  Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it 
would also remove the following packages which should be kept in this step: 
linux-image-unsigned-4.18.0-14-generic
  ...

  For reproduction see LP: #1795696, but running u-u with --verbose.

  And APT does not apply proper kernel-version based protection to it.

  [Test case]
  linux-image-unsigned should popup in the same list in 01autoremove-kernels as 
linux-signed-image, and should be autoremovable iff it's signed counterpart is 
autoremovable.

  [Regression potential]
  Not really any, it's just an additional string in the entry. The only 
difference really possible therefore is that the set of autoremovable packages 
changes and unattended-upgrades and friends might autoremove different sets of 
them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system

2019-06-06 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.6.11

---
apt (1.6.11) bionic; urgency=medium

  * Add test case for local-only packages pinned to never
  * Prevent shutdown while running dpkg (LP: #1820886)
  * Add linux-{buildinfo,image-unsigned,source} versioned kernel pkgs
(LP: #1821640)

 -- Julian Andres Klode   Tue, 07 May 2019 11:19:29
+0200

** Changed in: apt (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/1821640

Title:
  Missing pattern for linux-image-unsigned keeps autoremovable kernels
  on the system

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  Fix Released
Status in apt source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  Unattended-upgrades keeps versioned kernel packages because they don't match 
known kernel package patterns:

  ...
  Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it 
would also remove the following packages which should be kept in this step: 
linux-image-unsigned-4.18.0-14-generic
  ...

  For reproduction see LP: #1795696, but running u-u with --verbose.

  And APT does not apply proper kernel-version based protection to it.

  [Test case]
  linux-image-unsigned should popup in the same list in 01autoremove-kernels as 
linux-signed-image, and should be autoremovable iff it's signed counterpart is 
autoremovable.

  [Regression potential]
  Not really any, it's just an additional string in the entry. The only 
difference really possible therefore is that the set of autoremovable packages 
changes and unattended-upgrades and friends might autoremove different sets of 
them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1812159] Re: q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels

2019-06-06 Thread Po-Hsu Lin
** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-kvm (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Also affects: linux-kvm (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: linux-kvm (Ubuntu Xenial)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-kvm (Ubuntu Bionic)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-kvm (Ubuntu Cosmic)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-kvm (Ubuntu Disco)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

** Changed in: linux-kvm (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

** Changed in: linux-kvm (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: linux-kvm (Ubuntu Disco)
   Status: New => In Progress

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

Title:
  q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM
  kernels

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Xenial:
  In Progress
Status in linux-kvm source package in Bionic:
  In Progress
Status in linux-kvm source package in Cosmic:
  In Progress
Status in linux-kvm source package in Disco:
  In Progress

Bug description:
  The test_380_config_sched_stack_end_check test failed on the Bionic
  KVM kernel

FAIL: test_380_config_sched_stack_end_check 
(__main__.KernelSecurityConfigTest)
Ensure SCHED_STACK_END_CHECK is set
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2628, in 
test_380_config_sched_stack_end_check
self.assertKernelConfig('SCHED_STACK_END_CHECK', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: SCHED_STACK_END_CHECK option was expected to be set in 
the kernel config

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 06:44:41 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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