ago 23 14:40:18 calabresa audit[5997]: AVC apparmor="DENIED" operation="ptrace"
profile="/usr/sbin/libvirtd" pid=5997 comm="libvirtd" requested_mask="read"
denied_mask="read" peer="unconfined"
ago 22 18:00:12 calabresa audit[4409]: AVC apparmor="DENIED" operation="ptrace"
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-trusty
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787982
Title:
linux: 3.13.0-157.207
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
Certification-testing was completed with 3.13.0-154.204 (bug 1784299).
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thank you for dedicating some of your time to this matter! :)
Here is the requested output:
revisor@revisor-XPS-15-9560:~$ lspci -vvnn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core
Processor Host Bridge/DRAM Registers [8086:5910] (rev 05)
Subsystem: Dell Xeon
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1786110
Title:
SMB3: Fix regression in server reconnect
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787177
Title:
linux: 4.4.0-134.160
** Changed in: ubuntu-power-systems
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788549
Title:
powerpc/powernv/pci: Work around races in PCI bridge
So, investigated this into an apparmor difference between 4.17 and 4.18.
This is due to commit 338d0be437ef10e247a35aed83dbab182cf406a2
("apparmor: fix ptrace read check").
libvirtd here is using only trace, and not read. The patch below for
libvirtd apparmor policy fixes it for me.
---
Public bug reported:
Using the Ubuntu 18.04.1 LTS default kernel 4.15.0-32-generic system
hangs/stalls during boot displaying the error shown below, kernels 4.13
and 4.17 don't show this bug. This seem to be an extended APIC issue in
the kernel on certain xeon skylake models and was already
Had this too, for the first time, on Ubuntu 18.04 LTS.
[287327.941338] [drm] Reducing the compressed framebuffer size. This may lead
to less power savings than a non-reduced-size. Try to increase stolen memory
size if available in BIOS.
[287336.517202] [drm] Reducing the compressed framebuffer
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1788616
and then change the status of the bug to 'Confirmed'.
If, due to the
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => New
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device
This bug was fixed in the package linux-aws - 4.15.0-1020.20
---
linux-aws (4.15.0-1020.20) bionic; urgency=medium
* linux-aws: 4.15.0-1020.20 -proposed tracker (LP: #1787154)
[ Ubuntu: 4.15.0-33.36 ]
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device
This bug was fixed in the package linux-gcp - 4.15.0-1018.19
---
linux-gcp (4.15.0-1018.19) bionic; urgency=medium
* linux-gcp: 4.15.0-1018.19 -proposed tracker (LP: #1787156)
* linux-gcp: add a signed kernel (LP: #1782557)
- [Configuration] enable EFI signing support
[
This bug was fixed in the package linux-kvm - 4.15.0-1020.20
---
linux-kvm (4.15.0-1020.20) bionic; urgency=medium
* linux-kvm: 4.15.0-1020.20 -proposed tracker (LP: #1787158)
* DEBUG_WX is not set in Bionic KVM kernel (LP: #1782721)
- kvm: [Config] enable CONFIG_DEBUG_WX
** Description changed:
IPv6 PMTU discovery fails when using source-specific routing on Ubuntu
18.04.
I have attached a test case called pmtu-sads.sh which is based on
tools/testing/selftests/net/pmtu.sh in the linux source.
- I have verified that the test succeeds on:
- Ubuntu
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1788623
and then change the status of the bug to 'Confirmed'.
If, due to the
Patch which fixes the bug for me.
** Patch added: "net/ipv6/route: Fix PMTU for source-specific routes"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788623/+attachment/5179773/+files/0001-net-ipv6-route-Fix-PMTU-for-source-specific-routes.patch
--
You received this bug notification
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1786352
Title:
Bionic update: upstream stable patchset
This seems to be a regression on bionic; I have been using libvirtd
inside a container for several weeks; today when I tore down and rebuilt
the container I hit this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
Public bug reported:
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
** Affects: linux (Ubuntu)
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
Public bug reported:
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
** Affects: linux (Ubuntu)
Public bug reported:
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 --
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective
Status in linux package
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective
You have been subscribed to a public bug:
A few days ago purchased a couple of TP-LINK TG-3468 network cards
(reviewed by Phoronix here:
https://www.phoronix.com/scan.php?page=news_item=MTY2ODQ), both brand
new, not reused. After installed them to a pc, to my surprise, one of
them was correctly
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788730
Title:
TP-LINK TG-3468 network card not recognized correctly
Status in linux package
Here's dmesg with 4.15.0-30-generic #33~lp1783906DEBUG running for 10 mins:
https://paste.ubuntu.com/p/Qc9Kpb62ch/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1783906
Title:
Linux
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1788730
and then change the status of the bug to 'Confirmed'.
If, due to the
@mpontillo Bionic has always suffered from this bug. The patch set has
only been backport to Cosmic and the fixes have not yet been backported
to Bionic.
Have you, by chance, recently reconfigured your container to be an
unprivileged container when it was previously a privileged container? (I
Were you maybe using a privileged container before? Those aren't
affected by the /sys ownership issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784501
Title:
libvirtd is unable
3.13.0-157.207~precise1 - generic
Regression test CMPL, RTB.
27 / 28 tests were run, missing: ubuntu_boot
Issue to note in amd64:
ubuntu_qrt_kernel_security - CONFIG_RETPOLINE=y in kernel (bug 1786894)
26 / 27 tests were run, missing: ubuntu_boot
Issue to note in i386:
Public bug reported:
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 --
Public bug reported:
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 --
Public bug reported:
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 --
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-precise
** Tags removed: block-proposed
--
You received this bug notification because
Public bug reported:
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 --
Public bug reported:
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 --
Public bug reported:
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 --
Public bug reported:
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 --
Public bug reported:
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 --
** 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
+
+ backports: bug 1788767
Can you try 4.15.0-33 in -proposed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788583
Title:
Cannot resume HP ProBook 470 G4 after suspending or hibernating
Status in linux
The issue still exits on Debian 9
Please help, thanks so much
** Attachment added: "Screenshot at 2018-08-24 11-17-00.png"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1629632/+attachment/5180073/+files/Screenshot%20at%202018-08-24%2011-17-00.png
--
You received this bug
Nothing has changed regarding privileged vs. unprivileged settings.
I just set this up again with a privileged container, and I believe the
cause of the regression to actually be in libvirt. I think it must have
silently ignored the bridge configuration error before and marked the
network active
** Summary changed:
- linux: -proposed tracker
+ linux: 4.15.0-34.37 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) =>
** Changed in: broadcom-sta (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: bcmwl (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1787544
Title:
linux-oem: 4.15.0-1017.20
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1782070
Title:
[Redpine] Upgrades to improve
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788742
Title:
linux: -proposed tracker
Status in linux package in Ubuntu:
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1781895
Title:
Bluetooth: Redpine: Bionics: L2test
Public bug reported:
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
** Affects: kernel-sru-workflow
Public bug reported:
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 --
Public bug reported:
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
backports:
derivatives:
** Affects:
Public bug reported:
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
backports: bug 1788765
** 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
+
+ backports: bug 1788754
Public bug reported:
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 --
Public bug reported:
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
backports: bug 1788767 (linux-aws), bug
Public bug reported:
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 --
This bug was fixed in the package linux-lts-xenial -
4.4.0-134.160~14.04.1
---
linux-lts-xenial (4.4.0-134.160~14.04.1) trusty; urgency=medium
* linux-lts-xenial: 4.4.0-134.160~14.04.1 -proposed tracker (LP:
#1787179)
* linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)
*
This bug was fixed in the package linux-lts-xenial -
4.4.0-134.160~14.04.1
---
linux-lts-xenial (4.4.0-134.160~14.04.1) trusty; urgency=medium
* linux-lts-xenial: 4.4.0-134.160~14.04.1 -proposed tracker (LP:
#1787179)
* linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)
*
This bug was fixed in the package linux-aws - 4.4.0-1066.76
---
linux-aws (4.4.0-1066.76) xenial; urgency=medium
* linux-aws: 4.4.0-1066.76 -proposed tracker (LP: #1787180)
* Xenial update to 4.4.136 stable release (LP: #1776177)
- [Config] Add
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux-aws - 4.4.0-1028.31
---
linux-aws (4.4.0-1028.31) trusty; urgency=medium
* linux-aws: 4.4.0-1028.31 -proposed tracker (LP: #1787178)
* Xenial update to 4.4.136 stable release (LP: #1776177)
- [Config] Add
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux-aws - 4.4.0-1066.76
---
linux-aws (4.4.0-1066.76) xenial; urgency=medium
* linux-aws: 4.4.0-1066.76 -proposed tracker (LP: #1787180)
* Xenial update to 4.4.136 stable release (LP: #1776177)
- [Config] Add
This bug was fixed in the package linux-kvm - 4.4.0-1032.38
---
linux-kvm (4.4.0-1032.38) xenial; urgency=medium
* linux-kvm: 4.4.0-1032.38 -proposed tracker (LP: #1787182)
* Xenial update to 4.4.136 stable release (LP: #1776177)
- [Config] Add
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
well, I think you forgot to attach the patch. So I called editconfig
myself and disabled the TANGO platform. For unknown reasons, this also
enables CONFIG_ARCH_HAS_FILTER_PGPROT in config.common.ubuntu... Anyway,
the new kernel boots and suspends/resume just fine.
** Patch added: "q.diff"
This bug was fixed in the package linux - 4.4.0-134.160
---
linux (4.4.0-134.160) xenial; urgency=medium
* linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE:
This bug was fixed in the package linux - 4.4.0-134.160
---
linux (4.4.0-134.160) xenial; urgency=medium
* linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE:
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787058
Title:
ThinkPad systems have no HDMI sound when using
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1786981
Title:
[Bionic] i2c: xlp9xx: Add SMBAlert support
Status
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Confirmed
**
I can confirm the "nouveau.modeset=0" trick seems to be working for me
so far (meaning, I am able to suspend the system again).
I upgraded from 16.04 two days ago - suspend has been working fine for
the entire lifetime of the 16.04 install.
A colleague has also reported suspend/hibernate
The package has been published and the bug is being set to 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:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
--
You received this bug notification
This bug was fixed in the package linux - 4.4.0-134.160
---
linux (4.4.0-134.160) xenial; urgency=medium
* linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE:
This bug was fixed in the package linux - 4.4.0-134.160
---
linux (4.4.0-134.160) xenial; urgency=medium
* linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE:
This bug was fixed in the package linux - 4.4.0-134.160
---
linux (4.4.0-134.160) xenial; urgency=medium
* linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE:
This bug was fixed in the package linux - 4.4.0-134.160
---
linux (4.4.0-134.160) xenial; urgency=medium
* linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE:
This bug was fixed in the package linux - 4.4.0-134.160
---
linux (4.4.0-134.160) xenial; urgency=medium
* linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE:
This bug was fixed in the package linux - 4.4.0-134.160
---
linux (4.4.0-134.160) xenial; urgency=medium
* linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE:
This bug was fixed in the package linux - 4.4.0-134.160
---
linux (4.4.0-134.160) xenial; urgency=medium
* linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE:
This bug was fixed in the package linux - 4.4.0-134.160
---
linux (4.4.0-134.160) xenial; urgency=medium
* linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE:
This bug was fixed in the package linux-kvm - 4.4.0-1032.38
---
linux-kvm (4.4.0-1032.38) xenial; urgency=medium
* linux-kvm: 4.4.0-1032.38 -proposed tracker (LP: #1787182)
* Xenial update to 4.4.136 stable release (LP: #1776177)
- [Config] Add
I experience this, too, in bionic.
Possibly related to bug 1730458.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674763
Title:
Warnings then GPF originating from nouveau under zesty
This bug was fixed in the package linux-kvm - 4.4.0-1032.38
---
linux-kvm (4.4.0-1032.38) xenial; urgency=medium
* linux-kvm: 4.4.0-1032.38 -proposed tracker (LP: #1787182)
* Xenial update to 4.4.136 stable release (LP: #1776177)
- [Config] Add
101 - 200 of 344 matches
Mail list logo
