When I upgraded, I accepted the default of "lightdm" (if I remember
correctly). I presume that means Unity, because the system looks exactly
the way it was before the upgrade.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
Hi,
I haven't found the time to do this yet, sorry. Is it still an issue on
the current Xenial kernel?
Regards,
Daniel
--
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/1742658
Title:
lin
** Package changed: xorg (Ubuntu Cosmic) => xorg-server (Ubuntu Cosmic)
--
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/1794280
Title:
gdm doesn't start on a fresh installation of Cosmic
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu Cosmic)
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/b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (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/179
Public bug reported:
at apt upgrade time
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioD
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/179
Title:
package linux-image-4.15.0-36-
Do you use Unity or GNOME?
--
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/1790249
Title:
desktop sharing won't start after upgrading to 18.04
Status in linux package in Ubuntu:
Incomp
I'm on ubuntu 18.04 not sure how to check kernel version and I don't
want to mess with it on this computer. I haven't used the card for a
long time and the last time was on windows. Just thought I'd plug it in
and try, unfortunately it seems to fail.
--
You received this bug notification because
** Also affects: qa-regression-testing
Importance: Undecided
Status: 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/1717856
Title:
Kernel security test test_021_aslr_dapper
** Also affects: qa-regression-testing
Importance: Undecided
Status: 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/1747630
Title:
Kernel security test test_022_aslr_hardy_
*** This bug is a duplicate of bug 1757008 ***
https://bugs.launchpad.net/bugs/1757008
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1757008, so it is being marked as such. Please look
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 1775068
and then change the status of the bug to 'Confirmed'.
If, due to the nature
That means the workaround (increases the input length to 64) that works
for me doesn't work for you.
--
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/1784152
Title:
i2c_hid_get_input flood
Looks like the kernel crash is related to networking. If you can please
try disabling wifi and using a wired ethernet connection for testing.
Does that avoid it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
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/1795256
Title:
frequent crash of Ubuntu 18.04
Thanks. Unfortunately that only shows minor app crashes in the past
month.
Looking back at your CurrentDmesg.txt though, I can see one kernel crash
which is probably more relevant:
[ 1878.739957] WARNING: CPU: 2 PID: 0 at
/build/linux-SlLHxe/linux-4.15.0/net/core/dev.c:5645 net_rx_action+0x2cb/0
You have been subscribed to a public bug:
I had same problem in Ubuntu 16.04.3. But not frequent. It was happening
when I play HD video. But now after installing Ubuntu 18.04 the same
problem even when browsing. Its too frequent.
I have tried to reinstall Intel-microcode, bumblebee, xorg video
dr
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: 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/bu
Oh. Except comment #13 says not.
** Changed in: canonical-devices-system-image
Status: Fix Released => Confirmed
** Changed in: bluez (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
I assume this was released...
https://code.launchpad.net/~bluetooth/bluez/new-rel-5-37-plus-touch-
xenial-sync/+merge/283734
** Changed in: bluez (Ubuntu)
Status: In Progress => Fix Released
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Released
--
You
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1795541
Title:
bcmwl-kernel-source (not installed): bcmwl kernel module failed to
build
Status in
Public bug reported:
just find
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.3
Archit
Hi Guo, thanks for your tests!
So, to confirm:
a) With Ubuntu kernel 4.15.0-34, using the kernel parameter
"nvme_core.multipath=0", you _don't_ see the issue;
b) With kernel 4.17.0-041700rc1-generic, even using the parameter
"nvme_core.multipath=0", you *can reproduce* the issue.
Right?
I've
A bionic test kernel is also available with commits 3dbe97efe8bf and
9f0e89359775 applied.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1794110/bionic
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you ar
marked as confirmed per #3 and #4.
i have the apport file stashed away and can upload it as an attachment
upon request if anyone's interested.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
Correction:
xrandr --output eDP-1-1 --set "PRIME Synchronization" 1
xrandr --output HDMI-1-1 --set "PRIME Synchronization" 1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/177801
Kai-Heng Feng,
I installed the kernel as linked in post #18. It installed without a
problem and booted and ran on the laptop just like the official kernels.
I've confirmed it is 4.19.1 running.
Unfortunately, dmesg still reports many multiples of the error in
question each time I use the touchpa
I am ubuntu on 18.04.1 LTS.
With intel integrated gpu things are normal. With my nvidia gpu occured
two problems:
* I disabled login screen because it was creating two intances of Xorg
and gnome-shell each. I can see these with top and nvidia-smi. It
decreased cpu temps a lot even in idle time.
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/1795509
Title:
Kernel bug after removing Haup
I built a Bionic test kernel with a patch from upstream. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1736390
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Public bug reported:
This kernel bug happens right after removing the usb connector. No
streams were running.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-7-generic 4.18.0-7.8
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
A
** 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
** Description changed:
I have HP Elitebook 850 G5 and I'm experiencing this issue too.
Here is my udevadm info -e.
** Attachment added: "udevadm info -e"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+attachment/5195454/+files/udevadm.info.txt
--
You received this bug notification because you are a
** Changed in: cloud-images
Status: Confirmed => 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/1726818
Title:
vagrant artful64 box filesystem too small
Status in cl
I built a second test kernel.
The test kernel can also be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792580
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubunt
** 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) => Seth Forshee
(sforshee)
** Changed in: kernel-sru-workflow/prepare-package-meta
St
No better luck with 4.19.0-041900rc6-generic.
Upon reboot, running at 1920x1080 *interlaced*. No good - I am getting the
shakes just watching the screen. And it is slightly blurred.
Thanks for all the help and hard work!
pj
--
You received this bug notification because you are a member of Kernel
No change with kernel 4.19.0-041900rc5-generic, alas.
The bizarre thing is the Xorg log (~/.local/share/xorg/Xorg.0.log)
saying
[11.016] (II) modeset(0): Supported established timings:
and subsequently the finest mode being 1280x1024@75Hz. Then, in the
section(s) called
[11.017] (II)
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
** Changed in: ubuntu-z-systems
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.launchpad.net/bugs/1786902
Title:
[18.10 FEAT] SMC-Direct
Status in Ubuntu on IB
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for trackin
The test kernel I posted is built on top of upstream 4.15.18. To
confirm this is an Ubuntu specific bug, can you test 4.15.18? It can be
downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/
--
You received this bug notification because you are a member of Kernel
Packages, w
** Changed in: ubuntu-z-systems
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.launchpad.net/bugs/1784331
Title:
[18.10 FEAT] zcrypt DD: introduce APQN tags to
** Changed in: ubuntu-z-systems
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.launchpad.net/bugs/1789934
Title:
[18.10 FEAT] Add kernel config options for SMC-
** Changed in: ubuntu-power-systems
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.launchpad.net/bugs/1788097
Title:
performance drop with ATS enabled
Status i
No change with kernel 4.19.0-041900rc5-generic, alas.
The bizarre thing is the Xorg log (~/.local/share/xorg/Xorg.0.log)
saying
[11.016] (II) modeset(0): Supported established timings:
and subsequently the finest mode being 1280x1024@75Hz. Then, in the
section(s) called
[11.017] (II)
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
Public bug reported:
This bug is for tracking the 4.18.0-1001.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
** Affects: kernel-sru-work
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
Imp
** Changed in: linux (Ubuntu Cosmic)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu Bionic)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Triaged
** Changed in: linux (Ubu
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
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/1792349
Title:
Memory leaking when running kubernetes cronjobs
Status in linux pa
Public bug reported:
Per https://www.weave.works/blog/racy-conntrack-and-dns-lookup-timeouts
Kubernetes users are seeing DNS lookups from Pods taking 5 or more
seconds.
Please pick up the following patches to netfilter:
http://patchwork.ozlabs.org/patch/937963/
http://patchwork.ozlabs.org/patch/9
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
Tested with Dell XPS 9560 and Ubuntu 18.04.
After installing the proposed packages and rebooting, everything booted
correctly, although the nvidia driver was still loaded (I had my system
set to use intel) and power use was quite high (~23W).
*But* after following the test case steps and switchin
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
This bug was fixed in the package linux - 4.18.0-8.9
---
linux (4.18.0-8.9) cosmic; urgency=medium
* linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)
* Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lo
I tried to apply 2bf1071a8d50928a4ae366bb3108833166c2b70c to Bionic, but
it looks like a backport is needed.
It appears 2bf1071a8d5 is needed as a prereq for f08d08f3db5545. Do you
happen to already have a backport of 2bf1071a8d5 already done for
Bionic?
** Changed in: linux (Ubuntu)
Stat
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
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph
Salisbury (jsalisbury)
** Also affects: linux (Ubuntu Cosmic)
Importance: High
Assignee: Joseph Salisbury (jsalisbur
** 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
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tra
** 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
** 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-oem - 4.15.0-1021.24
---
linux-oem (4.15.0-1021.24) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all()
** 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-oem - 4.15.0-1021.24
---
linux-oem (4.15.0-1021.24) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all()
This bug was fixed in the package linux - 4.15.0-36.39
---
linux (4.15.0-36.39) bionic; urgency=medium
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely
linux (4.15.0-35.38) bionic;
*** This bug is a duplicate of bug 1794430 ***
https://bugs.launchpad.net/bugs/1794430
This bug was fixed in the package linux-aws - 4.15.0-1023.23
---
linux-aws (4.15.0-1023.23) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin
** 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: ubuntu-z-systems
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.launchpad.net/bugs/1787898
Title:
[18.10 FEAT] Add kernel config option "CONFIG_S
This bug was fixed in the package linux-kvm - 4.15.0-1023.23
---
linux-kvm (4.15.0-1023.23) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all()
I can confirm I also have this issue on an ACER Nitro 5 AN515-42-R5GT.
Ryzen 2500U + RX560X using latest BIOS available v1.08. I'm forced to
boot with noapic whether or not IOMMU is even enabled/disabled using
kernel 4.18.10.
Using 4.19.0rc2 I could get by using the GRUB additions:
i8042.nopnp ivr
This bug was fixed in the package linux-kvm - 4.15.0-1023.23
---
linux-kvm (4.15.0-1023.23) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all()
*** This bug is a duplicate of bug 1794428 ***
https://bugs.launchpad.net/bugs/1794428
This bug was fixed in the package linux-oem - 4.15.0-1021.24
---
linux-oem (4.15.0-1021.24) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin
*** This bug is a duplicate of bug 1794433 ***
https://bugs.launchpad.net/bugs/1794433
This bug was fixed in the package linux-kvm - 4.15.0-1023.23
---
linux-kvm (4.15.0-1023.23) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin
This bug was fixed in the package linux-oem - 4.15.0-1021.24
---
linux-oem (4.15.0-1021.24) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all()
*** This bug is a duplicate of bug 1794430 ***
https://bugs.launchpad.net/bugs/1794430
This bug was fixed in the package linux-aws - 4.15.0-1023.23
---
linux-aws (4.15.0-1023.23) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin
This bug was fixed in the package linux - 4.15.0-36.39
---
linux (4.15.0-36.39) bionic; urgency=medium
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely
linux (4.15.0-35.38) bionic;
*** This bug is a duplicate of bug 1794432 ***
https://bugs.launchpad.net/bugs/1794432
This bug was fixed in the package linux-gcp - 4.15.0-1021.22~16.04.1
---
linux-gcp (4.15.0-1021.22~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi tar
*** This bug is a duplicate of bug 1794432 ***
https://bugs.launchpad.net/bugs/1794432
This bug was fixed in the package linux-gcp - 4.15.0-1021.22
---
linux-gcp (4.15.0-1021.22) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin
This bug was fixed in the package linux-oem - 4.15.0-1021.24
---
linux-oem (4.15.0-1021.24) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all()
*** This bug is a duplicate of bug 1794428 ***
https://bugs.launchpad.net/bugs/1794428
This bug was fixed in the package linux-oem - 4.15.0-1021.24
---
linux-oem (4.15.0-1021.24) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin
** 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
** 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
1 - 100 of 288 matches
Mail list logo
