** 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 -propos
** 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.
https://b
** 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
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.
--- /etc/appa
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1787390
Title:
linux-azure: 4.15.0-1022.22~1
I am seeing the following as well:
https://github.com/linux-test-project/ltp/blob/3c87ef2961dedb10d1f674c6a530e00dbab8ec1b/testcases/kernel/syscalls/open/open10.c
open10 1 TPASS : Test passed in block0.
open10 2 TPASS : Test passed in block1.
open10 3 TFAIL : open10.c:352
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1787155
Title:
linux-azure: 4.15.0-102
** Changed in: kernel-sru-workflow/automated-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
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"
profile="/usr/sbin/libv
Forgot about testing with proposed, thanks.
Installed 4.15.0-33 and that seems to fix the 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/1788049
Title:
Kernel 4.15.0-32 disabl
What's interesting, is that lowriter does not crash in 32-bit LinuxMint-Mate 19
(based on Ubuntu Bionic 18.04)
with either 4.15.0-20 initial kernel, or -33 updated from Bionic.
with 32-bit Lubuntu 18.04 it still crashes under -33 kernel, so the fix is
clearly in some different place.
probably Lin
Hi, Josh.
I wasn't able to reproduce those errors using the ltp commit you have
specified or the current master branch.
Can you provide more details about the environment you are running the
tests on and the instance type as well?
--
You received this bug notification because you are a member o
** 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
** 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 - 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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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: apparm
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)
* l
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)
* l
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 CONFIG_CC_OPTIMIZE_FOR_PERFORMA
** 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 CONFIG_CC_OPTIMIZE_FOR_PERFORMA
** 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 CONFIG_CC_OPTIMIZE_FOR_PERFORMA
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 CONFIG_CC_OPTIMIZE_FOR_PERFORMA
** 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-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 CONFIG_CC_OPTIMIZE_FOR_PERFORMA
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 CONFIG_CC_OPTIMIZE_FOR_PERFORMA
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
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/1788623
Title:
regression: IPv6 PMTU discovery fails with source-specific ro
** 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/1787477
Title:
Reconcile hns3 SAUCE patches with upstream
Status
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: T
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New =
** 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/1787240
Title:
[Bionic] i2c: xlp9xx: Fix case where SSIF read tran
** 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/1786878
Title:
[Regression] kernel crashdump fails on arm64
Stat
** 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 the
** 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
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/1788623
Title:
regression: IPv6 PMTU discover
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/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sr
** 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 s
** 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
** Desc
** 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 status and testing results related to that upload.
For an explanation of the tasks and the associ
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 problems
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"
http
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 becaus
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:
https:
@hendrikc could you confirm if the hibernation works on your system? I
got 4.15.0-33-generic and nvidia-390.48, nvidia 1080ti, i7, I can
suspend the system but not hibernate.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
The official 4.15.0.33 does indeed contain the bluetooth fix (and other
issues in the proposed version have also be sorted).
Many thanks to all those who do this work. Apologies for being a bit
impatient,
--
You received this bug notification because you are a member of Kernel
Packages, which i
I do not experience the bug anymore after upgrading kernel to
4.18.4-041804-generic. Looks like the bug has already been fixed in latest
kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packa
We ran the LTP tests on a Standard_D14v2 and these 2 failures only
happened on 4.15.0-1022, and they passed o n 4.15.0-1021, 1020, and
1018.
In the dmesg log here's the only thing interesting:
[ 661.232275] EXT4-fs (loop0): mounting ext2 file system using the ext4
subsystem
[ 661.257207] EXT4-
qemu-system-x86 broken when running kernel 4.15.0-33-generic as well -
same result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).
Totally black screen immediately - no bios flashes.
--
You received this bug notification because you are a member of Kernel
Packages, whi
Confirmed that the bug is not present in Ubuntu-4.15.0-33 kernel and can
boot successfully
--
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/1788616
Title:
Hang during boot due to 4.15 kern
Really appreciate the quick fix :)
--
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/1788616
Title:
Hang during boot due to 4.15 kernel issue
Status in linux package in Ubuntu:
Fix Commi
This bug was fixed in the package linux - 3.13.0-157.207
---
linux (3.13.0-157.207) trusty; urgency=medium
* linux: 3.13.0-157.207 -proposed tracker (LP: #1787982)
* CVE-2017-5715 (Spectre v2 retpoline)
- SAUCE: Fix "x86/retpoline/entry: Convert entry assembler indirect jumps
This bug was fixed in the package linux - 3.13.0-157.207
---
linux (3.13.0-157.207) trusty; urgency=medium
* linux: 3.13.0-157.207 -proposed tracker (LP: #1787982)
* CVE-2017-5715 (Spectre v2 retpoline)
- SAUCE: Fix "x86/retpoline/entry: Convert entry assembler indirect jumps
This bug was fixed in the package linux - 3.13.0-157.207
---
linux (3.13.0-157.207) trusty; urgency=medium
* linux: 3.13.0-157.207 -proposed tracker (LP: #1787982)
* CVE-2017-5715 (Spectre v2 retpoline)
- SAUCE: Fix "x86/retpoline/entry: Convert entry assembler indirect jumps
This bug was fixed in the package linux - 3.13.0-157.207
---
linux (3.13.0-157.207) trusty; urgency=medium
* linux: 3.13.0-157.207 -proposed tracker (LP: #1787982)
* CVE-2017-5715 (Spectre v2 retpoline)
- SAUCE: Fix "x86/retpoline/entry: Convert entry assembler indirect jumps
This bug was fixed in the package linux - 3.13.0-157.207
---
linux (3.13.0-157.207) trusty; urgency=medium
* linux: 3.13.0-157.207 -proposed tracker (LP: #1787982)
* CVE-2017-5715 (Spectre v2 retpoline)
- SAUCE: Fix "x86/retpoline/entry: Convert entry assembler indirect jumps
This bug was fixed in the package linux - 3.13.0-157.207
---
linux (3.13.0-157.207) trusty; urgency=medium
* linux: 3.13.0-157.207 -proposed tracker (LP: #1787982)
* CVE-2017-5715 (Spectre v2 retpoline)
- SAUCE: Fix "x86/retpoline/entry: Convert entry assembler indirect jumps
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/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sr
Public bug reported:
when cheese starts, shortly the view of the webcam is visible and then shows an
error.
When run from the command line, the terminal shows:
(cheese:6379): Gtk-WARNING **: 01:08:46.810: Theme parsing error:
cheese.css:7:35: The style property GtkScrollbar:min-slider-length is
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 1788725
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta-hwe (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/
** Tags added: patch
--
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/1787945
Title:
Tango platform uses __initcall without further checks
Status in linux package in Ubuntu:
Confirmed
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
** 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
** 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.
https://bugs.launchpad.n
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&px=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
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 nature
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 4.1
** 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 201
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.
htt
@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
don'
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 to
** 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 -pro
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 'verifica
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)
Importan
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 'verifica
201 - 300 of 344 matches
Mail list logo
