This bug was fixed in the package linux - 5.3.0-22.24
---
linux (5.3.0-22.24) eoan; urgency=medium
* [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout
setting (LP: #1849682)
- Revert "md/raid0: avoid RAID0 data corruption due to layout confusion."
This bug was fixed in the package linux - 5.0.0-35.38
---
linux (5.0.0-35.38) disco; urgency=medium
* [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout
setting (LP: #1849682)
- SAUCE: Fix revert "md/raid0: avoid RAID0 data corruption due to layout
This bug was fixed in the package linux - 5.3.0-22.24
---
linux (5.3.0-22.24) eoan; urgency=medium
* [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout
setting (LP: #1849682)
- Revert "md/raid0: avoid RAID0 data corruption due to layout confusion."
This bug was fixed in the package linux-raspi2 - 5.3.0-1012.14
---
linux-raspi2 (5.3.0-1012.14) eoan; urgency=medium
[ Ubuntu: 5.3.0-22.24 ]
* [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout
setting (LP: #1849682)
- Revert "md/raid0: avoid RAI
This bug was fixed in the package linux - 4.15.0-69.78
---
linux (4.15.0-69.78) bionic; urgency=medium
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle page fault in vmread fix
* CVE-2018-12207
- KVM: MMU: drop vcpu param in gpte_access
- kvm: Convert kvm_l
** Changed in: qa-regression-testing
Status: Confirmed => In Progress
** Changed in: qa-regression-testing
Assignee: (unassigned) => Connor Kuehl (connork)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
I can reproduce Seb's issue in the snap-store snap as well
** Changed in: gnome-software (Ubuntu)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: gnome-software (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-software (Ubuntu)
Status: New => Co
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle
*** This bug is a duplicate of bug 1851507 ***
https://bugs.launchpad.net/bugs/1851507
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
This bug was fixed in the package linux-hwe-edge - 5.3.0-22.24~18.04.1
---
linux-hwe-edge (5.3.0-22.24~18.04.1) bionic; urgency=medium
[ Ubuntu: 5.3.0-22.24 ]
* [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout
setting (LP: #1849682)
- Revert "m
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle
This bug was fixed in the package linux-hwe - 4.15.0-69.78~16.04.1
---
linux-hwe (4.15.0-69.78~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle page fault in vmread fix
* CVE-2018-12207
- KVM: MMU: drop
This bug was fixed in the package linux-hwe - 5.0.0-35.38~18.04.1
---
linux-hwe (5.0.0-35.38~18.04.1) bionic; urgency=medium
[ Ubuntu: 5.0.0-35.38 ]
* [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout
setting (LP: #1849682)
- SAUCE: Fix revert "
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1027.31
---
linux-oem-osp1 (5.0.0-1027.31) bionic; urgency=medium
* CVE-2019-11135
- [Config] Disable TSX by default when possible
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 5
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle
This bug was fixed in the package linux-gcp - 5.0.0-1025.26~18.04.1
---
linux-gcp (5.0.0-1025.26~18.04.1) bionic; urgency=medium
[ Ubuntu: 5.0.0-1025.26 ]
* CVE-2019-11135
- [Config] gcp: Disable TSX by default when possible
* [REGRESSION] md/raid0: cannot assemble multi-z
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1027.31
---
linux-oem-osp1 (5.0.0-1027.31) bionic; urgency=medium
* CVE-2019-11135
- [Config] Disable TSX by default when possible
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 5
This bug was fixed in the package linux - 4.4.0-168.197
---
linux (4.4.0-168.197) xenial; urgency=medium
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct
- KVM: x86: MMU: Consolidate quickly_check_mmio_pf() and
is_mmio_page_fault()
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle
This bug was fixed in the package linux-aws - 4.4.0-1098.109
---
linux-aws (4.4.0-1098.109) xenial; urgency=medium
* CVE-2019-11135
- [Config] Disable TSX by default when possible
[ Ubuntu: 4.4.0-168.197 ]
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-
*** This bug is a duplicate of bug 1850485 ***
https://bugs.launchpad.net/bugs/1850485
This bug was fixed in the package linux-hwe-edge - 5.3.0-22.24~18.04.1
---
linux-hwe-edge (5.3.0-22.24~18.04.1) bionic; urgency=medium
[ Ubuntu: 5.3.0-22.24 ]
* [REGRESSION] md/raid0: can
This bug was fixed in the package linux-azure - 4.15.0-1063.68
---
linux-azure (4.15.0-1063.68) xenial; urgency=medium
* CVE-2019-11135
- [Config] azure: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX:
This bug was fixed in the package linux-oracle - 4.15.0-1029.32
---
linux-oracle (4.15.0-1029.32) bionic; urgency=medium
* CVE-2019-11135
- [Config] Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handl
This bug was fixed in the package linux-kvm - 4.4.0-1062.69
---
linux-kvm (4.4.0-1062.69) xenial; urgency=medium
* CVE-2019-11135
- [Config] Disable TSX by default when possible
[ Ubuntu: 4.4.0-168.197 ]
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-ch
*** This bug is a duplicate of bug 1849854 ***
https://bugs.launchpad.net/bugs/1849854
This bug was fixed in the package linux-hwe - 4.15.0-69.78~16.04.1
---
linux-hwe (4.15.0-69.78~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #18512
This bug was fixed in the package linux-gcp - 4.15.0-1049.52
---
linux-gcp (4.15.0-1049.52) xenial; urgency=medium
* CVE-2019-11135
- [Config] gcp: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle
This bug was fixed in the package linux-oracle - 4.15.0-1029.32~16.04.1
---
linux-oracle (4.15.0-1029.32~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-1029.32 ]
* CVE-2019-11135
- [Config] Disable TSX by default when possible
* KVM NULL pointer deref (LP: #1851205)
-
This bug was fixed in the package linux-gke-4.15 - 4.15.0-1048.51
---
linux-gke-4.15 (4.15.0-1048.51) bionic; urgency=medium
* CVE-2019-11135
- [Config] gke-4.15: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KV
This bug was fixed in the package linux-oracle - 4.15.0-1029.32~16.04.1
---
linux-oracle (4.15.0-1029.32~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-1029.32 ]
* CVE-2019-11135
- [Config] Disable TSX by default when possible
* KVM NULL pointer deref (LP: #1851205)
-
*** This bug is a duplicate of bug 1851507 ***
https://bugs.launchpad.net/bugs/1851507
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
This bug was fixed in the package linux-kvm - 4.15.0-1050.50
---
linux-kvm (4.15.0-1050.50) bionic; urgency=medium
* CVE-2019-11135
- [Config] Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle page
This bug was fixed in the package linux-aws-hwe - 4.15.0-1054.56~16.04.1
---
linux-aws-hwe (4.15.0-1054.56~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-1054.56 ]
* CVE-2019-11135
- [Config] Disable TSX by default when possible
* KVM NULL pointer deref (LP: #1851205)
*** This bug is a duplicate of bug 1850587 ***
https://bugs.launchpad.net/bugs/1850587
This bug was fixed in the package linux-hwe - 5.0.0-35.38~18.04.1
---
linux-hwe (5.0.0-35.38~18.04.1) bionic; urgency=medium
[ Ubuntu: 5.0.0-35.38 ]
* [REGRESSION] md/raid0: cannot assemb
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1027.31
---
linux-oem-osp1 (5.0.0-1027.31) bionic; urgency=medium
* CVE-2019-11135
- [Config] Disable TSX by default when possible
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 5
This bug was fixed in the package linux-gcp - 5.0.0-1025.26~18.04.1
---
linux-gcp (5.0.0-1025.26~18.04.1) bionic; urgency=medium
[ Ubuntu: 5.0.0-1025.26 ]
* CVE-2019-11135
- [Config] gcp: Disable TSX by default when possible
* [REGRESSION] md/raid0: cannot assemble multi-z
This bug was fixed in the package linux-gke-5.0 - 5.0.0-1025.26~18.04.1
---
linux-gke-5.0 (5.0.0-1025.26~18.04.1) bionic; urgency=medium
[ Ubuntu: 5.0.0-1025.26 ]
* CVE-2019-11135
- [Config] gcp: Disable TSX by default when possible
* [REGRESSION] md/raid0: cannot assemble
This bug was fixed in the package linux-azure - 5.0.0-1025.27
---
linux-azure (5.0.0-1025.27) disco; urgency=medium
* CVE-2019-11135
- [Config] azure: Disable TSX by default when possible
[ Ubuntu: 5.0.0-35.38 ]
* [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 wi
This bug was fixed in the package linux - 4.4.0-168.197
---
linux (4.4.0-168.197) xenial; urgency=medium
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct
- KVM: x86: MMU: Consolidate quickly_check_mmio_pf() and
is_mmio_page_fault()
This bug was fixed in the package linux-gcp - 5.0.0-1025.26~18.04.1
---
linux-gcp (5.0.0-1025.26~18.04.1) bionic; urgency=medium
[ Ubuntu: 5.0.0-1025.26 ]
* CVE-2019-11135
- [Config] gcp: Disable TSX by default when possible
* [REGRESSION] md/raid0: cannot assemble multi-z
This bug was fixed in the package linux-azure - 5.0.0-1025.27~18.04.1
---
linux-azure (5.0.0-1025.27~18.04.1) bionic; urgency=medium
[ Ubuntu: 5.0.0-1025.27 ]
* CVE-2019-11135
- [Config] azure: Disable TSX by default when possible
* [REGRESSION] md/raid0: cannot assemble m
This bug was fixed in the package linux-azure - 5.0.0-1025.27~18.04.1
---
linux-azure (5.0.0-1025.27~18.04.1) bionic; urgency=medium
[ Ubuntu: 5.0.0-1025.27 ]
* CVE-2019-11135
- [Config] azure: Disable TSX by default when possible
* [REGRESSION] md/raid0: cannot assemble m
This bug was fixed in the package linux - 4.4.0-168.197
---
linux (4.4.0-168.197) xenial; urgency=medium
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct
- KVM: x86: MMU: Consolidate quickly_check_mmio_pf() and
is_mmio_page_fault()
This bug was fixed in the package linux - 4.4.0-168.197
---
linux (4.4.0-168.197) xenial; urgency=medium
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct
- KVM: x86: MMU: Consolidate quickly_check_mmio_pf() and
is_mmio_page_fault()
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1027.31
---
linux-oem-osp1 (5.0.0-1027.31) bionic; urgency=medium
* CVE-2019-11135
- [Config] Disable TSX by default when possible
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 5
This bug was fixed in the package linux-azure - 5.0.0-1025.27
---
linux-azure (5.0.0-1025.27) disco; urgency=medium
* CVE-2019-11135
- [Config] azure: Disable TSX by default when possible
[ Ubuntu: 5.0.0-35.38 ]
* [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 wi
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle
This bug was fixed in the package linux - 4.4.0-168.197
---
linux (4.4.0-168.197) xenial; urgency=medium
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct
- KVM: x86: MMU: Consolidate quickly_check_mmio_pf() and
is_mmio_page_fault()
This bug was fixed in the package linux - 4.4.0-168.197
---
linux (4.4.0-168.197) xenial; urgency=medium
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct
- KVM: x86: MMU: Consolidate quickly_check_mmio_pf() and
is_mmio_page_fault()
This bug was fixed in the package linux-azure - 4.15.0-1063.68
---
linux-azure (4.15.0-1063.68) xenial; urgency=medium
* CVE-2019-11135
- [Config] azure: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX:
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1027.31
---
linux-oem-osp1 (5.0.0-1027.31) bionic; urgency=medium
* CVE-2019-11135
- [Config] Disable TSX by default when possible
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 5
This bug was fixed in the package linux - 4.4.0-168.197
---
linux (4.4.0-168.197) xenial; urgency=medium
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct
- KVM: x86: MMU: Consolidate quickly_check_mmio_pf() and
is_mmio_page_fault()
This bug was fixed in the package linux - 4.4.0-168.197
---
linux (4.4.0-168.197) xenial; urgency=medium
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct
- KVM: x86: MMU: Consolidate quickly_check_mmio_pf() and
is_mmio_page_fault()
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1027.31
---
linux-oem-osp1 (5.0.0-1027.31) bionic; urgency=medium
* CVE-2019-11135
- [Config] Disable TSX by default when possible
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 5
This bug was fixed in the package linux - 4.4.0-168.197
---
linux (4.4.0-168.197) xenial; urgency=medium
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct
- KVM: x86: MMU: Consolidate quickly_check_mmio_pf() and
is_mmio_page_fault()
This bug was fixed in the package linux-azure - 5.0.0-1025.27~18.04.1
---
linux-azure (5.0.0-1025.27~18.04.1) bionic; urgency=medium
[ Ubuntu: 5.0.0-1025.27 ]
* CVE-2019-11135
- [Config] azure: Disable TSX by default when possible
* [REGRESSION] md/raid0: cannot assemble m
This bug was fixed in the package linux - 4.4.0-168.197
---
linux (4.4.0-168.197) xenial; urgency=medium
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct
- KVM: x86: MMU: Consolidate quickly_check_mmio_pf() and
is_mmio_page_fault()
This bug was fixed in the package linux - 4.4.0-168.197
---
linux (4.4.0-168.197) xenial; urgency=medium
* CVE-2018-12207
- KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct
- KVM: x86: MMU: Consolidate quickly_check_mmio_pf() and
is_mmio_page_fault()
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1027.31
---
linux-oem-osp1 (5.0.0-1027.31) bionic; urgency=medium
* CVE-2019-11135
- [Config] Disable TSX by default when possible
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[ Ubuntu: 5
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle
This bug was fixed in the package linux-oem - 4.15.0-1063.72
---
linux-oem (4.15.0-1063.72) bionic; urgency=medium
* CVE-2019-11135
- [Config] oem: Disable TSX by default when possible
[ Ubuntu: 4.15.0-69.78 ]
* KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle
Hey Sam,
Trusty's HWE kvm smoke tests appear to have passed on amd64 but looks
like it's hiccuping on a couple of other arches. I don't know how useful
that information is here for this bug though. Given that Trusty is ESM,
is this SRU-able still?
--
You received this bug notification because yo
** Changed in: mutter
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851568
Title:
monitor configuration restored incorrectly upon Wayland login
To manage notification
Verified Fixed-Released updating bug
** Changed in: ubuntu-kernel-tests
Status: New => Triaged
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Sean Feole (sfeole)
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: ubuntu-kernel-tests
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847109
Title:
Ubuntu 18.04 - wrong cpu-mf counter number
To manage notif
Thank you for your reply.
Carefully following instructions about installing mysql, I could
completely uninstall and reinstall mysql.
It works, now, but the version is actually 5.7.
I'll try to install ver 8.0 later.
Thanks for your support. You may close the topic.
Best regards.
Le 12/11/2019 à
** Changed in: mutter
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852183
Title:
[X11] copy/paste (clipboard) is broken in Ubuntu 19.10
To manage notifications about
** Changed in: gnome-shell
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852118
Title:
Notifications don't have sound
To manage notifications about this bug go to:
ht
--- Comment From ch...@us.ibm.com 2019-11-12 18:01 EDT---
> You are disliking the fact that python2 is pulled in at all, right?
RIght
> But python3-ldap otherwise works fine under python3 for you in Bionic
RIght, although to get around the hard-dependency on python-ldap (thus
python2.7) w
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848173
Title:
Ubuntu 16.04.6 - Shared CEX7C cards defined in z/VM guest no
The only release we have <= Yakkety is Trusty which is ESM and I don't
believe we can SRU this change into QEMU anyways. The test gets skipped
so it doesn't appear to be reporting a failure. Closing this bug now.
** Changed in: ubuntu-kernel-tests
Status: Incomplete => Invalid
--
You rece
Verified Fix Released, updating bug
** Changed in: ubuntu-kernel-tests
Status: New => Triaged
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Sean Feole (sfeole)
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: ubuntu-kernel-tests
While performing validation, I was unable to reproduce the issue in
bionic-rocky deployment. Inspecting the code, the fix was not present. I
added logging, and confirmed that neutron is now including the key
"security_group_rules" in the response, therefore the error is no longer
triggered. I added
I just looked at the test results for this test suite across some GCP
cloud instances and it looks like it's failing across the 4.15 kernels.
** Changed in: ubuntu-kernel-tests
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
*** This bug is a duplicate of bug 1840854 ***
https://bugs.launchpad.net/bugs/1840854
Hello,
I believe this bug is a duplicate of Bug 1840854, and the fix should be
released in 4.15.0-59. Can you please review Bug 1840854 and try
installing a newer kernel, say 4.15.0-69, and let me know if i
I've run into similar problem, and I don't think it's e1000e driver
issue.
My device:
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
Connection (Lewisville) (rev 04)
Subsystem: Dell 82579LM Gigabit Network Connection (Lewisville)
Kernel driver in use: e1000
More infos:
powertop shows this when using intel gpu only (my workarounds from post
https://bugzilla.kernel.org/show_bug.cgi?id=156341#c139)
0.0%PCI Device: Intel Corporation Xeon E3-1200 v5/E3-1500
v5/6th Gen Core Processor PCIe Controller (x16)
0.0%P
Of course I've set the power to auto for everything
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803179
Title:
System does not reliably come out of suspend
To manage notifications about this bug
I've tryed the patches and can confirm that the issues with lockups are
gone with just using bumblebee (unloading nvidia module).
But still the problems are the same:
1.) Just unloading the nvidia modules keeps the power consumption up to 13/14W
which is 5-6W more (almoest double) in compare to i
ESM for Precise ended in April 2019.
** Changed in: linux (Ubuntu Precise)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ubuntu-kernel-tests
Status: Confirmed => Invalid
** Changed in: qa-regression-testing
S
Sam updated the quota rules in autotest-client-tests on Aug 26th in
commit 29ab00ab179418fce9310632a4a58edc5cf5a259 which addressed the
issue with ubuntu_ltp_syscalls
I pushed commit a54839d364ff085a28e4826a669ed840234dff4b to ensure the
correct rules are in place for ubuntu_quota_smoke_test and
** Changed in: ubuntu-kernel-tests
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837543
Title:
crypto_user02 in crypto from ubuntu_ltp failed
To manage notifica
I just tried this on an s390x box running Xenial. This is still an
issue, but I don't think constrained to T-LTS like mentioned earlier.
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ubunt
verified fix for SRU-2019.10.21
** Changed in: ubuntu-kernel-tests
Status: New => Triaged
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Sean Feole (sfeole)
** Changed in: ubuntu-kernel-tests
Status: Triaged => Fix Released
** Changed in: linux-hwe (Ubuntu)
This bug was fixed in the package landscape-client -
16.03-0ubuntu2.16.04.7
---
landscape-client (16.03-0ubuntu2.16.04.7) xenial; urgency=medium
* d/p/product-name-vminfo-1828217.patch: Add product_name to things scanned
for vm_info (LP: #1828217)
* d/landscape-client.postinst
This is still an issue: http://10.246.72.4/test-
results/3.13.0-174.225-generic/ms10-35-mcdivittB0-kernel__3.13.0-174.225__2019-10-04_10-32-00/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html
** Changed in: ubuntu-kernel-tests
Status: Confirmed => Triaged
** Changed in: linu
This bug was fixed in the package landscape-client -
16.03-0ubuntu2.16.04.7
---
landscape-client (16.03-0ubuntu2.16.04.7) xenial; urgency=medium
* d/p/product-name-vminfo-1828217.patch: Add product_name to things scanned
for vm_info (LP: #1828217)
* d/landscape-client.postinst
This bug was fixed in the package landscape-client -
16.03-0ubuntu2.16.04.7
---
landscape-client (16.03-0ubuntu2.16.04.7) xenial; urgency=medium
* d/p/product-name-vminfo-1828217.patch: Add product_name to things scanned
for vm_info (LP: #1828217)
* d/landscape-client.postinst
Oh and it's also for certain hosts. Connecting to a host on the same
network gives reliable 96Mbps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830197
Title:
e1000e driver - uploading slowed to a
This bug was fixed in the package landscape-client -
16.03-0ubuntu2.16.04.7
---
landscape-client (16.03-0ubuntu2.16.04.7) xenial; urgency=medium
* d/p/product-name-vminfo-1828217.patch: Add product_name to things scanned
for vm_info (LP: #1828217)
* d/landscape-client.postinst
Precise ESM reached end of life in April 2019.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ubuntu-kernel-tests
Status: Confirmed => Invalid
** Changed in: qa-regression-testing
Status: New => Invalid
--
You received this bug notification becau
This is still an issue: http://10.246.72.4/test-
results/3.13.0-174.225-generic/ms10-35-mcdivittB0-kernel__3.13.0-174.225__2019-10-04_10-32-00/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html
** Changed in: ubuntu-kernel-tests
Status: Confirmed => Triaged
** Changed in: linu
I am having the same problem, wifi adapter not detected Ubuntu 19.10 / Intel
9260.
[4.778071] Loading modules backported from iwlwifi
[4.778073] iwlwifi-stack-public:master:8042:654c426c
[4.931110] iwlwifi :73:00.0: enabling device ( -> 0002)
[5.297929] iwlwifi: probe of 0
On my X1 Carbon 4th gen, kernel 5.3.0-22-generic seems to have
completely fixed the issue. Yay!
$ uname -a
Linux evenedric 5.3.0-22-generic #24-Ubuntu SMP Sat Nov 9 17:34:30 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Changed in: linux (Ubuntu Cosmic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778705
Title:
skey in ubuntu-kvm-unit-test failed on X/C zVM
To manage notificati
This is still an issue: http://10.246.72.4/test-
results/3.13.0-174.225-generic/ms10-35-mcdivittB0-kernel__3.13.0-174.225__2019-10-04_08-59-00/ubuntu_qrt_kernel_security/results/ubuntu_qrt_kernel_security
.test-kernel-security.py/debug/ubuntu_qrt_kernel_security.test-kernel-
security.py.DEBUG.html
$ free
totalusedfree shared buff/cache available
Mem:1022440 299328 378272 808 344840 567588
Swap:603372 344256 259116
$ cat /proc/swaps
FilenameTypeSizeUsed
701 - 800 of 878 matches
Mail list logo