This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.13.0-46.51
---
linux (5.13.0-46.51) impish; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.13.0-45.50) impish; urgency=medium
* impish/linux: 5.13.0-45.50 -proposed tracker (LP: #1974347)
*
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.13.0-46.51
---
linux (5.13.0-46.51) impish; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.13.0-45.50) impish; urgency=medium
* impish/linux: 5.13.0-45.50 -proposed tracker (LP: #1974347)
*
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.13.0-46.51
---
linux (5.13.0-46.51) impish; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.13.0-45.50) impish; urgency=medium
* impish/linux: 5.13.0-45.50 -proposed tracker (LP: #1974347)
*
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux-aws - 5.15.0-1009.11
---
linux-aws (5.15.0-1009.11) jammy; urgency=medium
* jammy/linux-aws: 5.15.0-1009.11 -proposed tracker (LP: #1974290)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
** Patch added:
"debdiff_signed_jammy_2.20.0-0ubuntu3_to_2.20.0-0ubuntu3.1.patch"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1971993/+attachment/5594575/+files/debdiff_signed_jammy_2.20.0-0ubuntu3_to_2.20.0-0ubuntu3.1.patch
--
You received this bug notification because you
** Patch added:
"debdiff_signed_kinetic_2.20.0-0ubuntu3_to_2.20.0-0ubuntu4.patch"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1971993/+attachment/5594573/+files/debdiff_signed_kinetic_2.20.0-0ubuntu3_to_2.20.0-0ubuntu4.patch
--
You received this bug notification because you
** Patch added: "debdiff_jammy_2.20.0-0ubuntu3_to_2.20.0-0ubuntu3.1.patch"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1971993/+attachment/5594574/+files/debdiff_jammy_2.20.0-0ubuntu3_to_2.20.0-0ubuntu3.1.patch
--
You received this bug notification because you are a member of
This bug was fixed in the package linux - 5.15.0-35.36
---
linux (5.15.0-35.36) jammy; urgency=medium
* CVE-2022-21499
- SAUCE: debug: Lock down kgdb
linux (5.15.0-34.35) jammy; urgency=medium
* jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)
* AMD APU s2idle
** Patch added: "debdiff_kinetic_2.20.0-0ubuntu3_to_2.20.0-0ubuntu4.patch"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1971993/+attachment/5594572/+files/debdiff_kinetic_2.20.0-0ubuntu3_to_2.20.0-0ubuntu4.patch
--
You received this bug notification because you are a member of
This bug was fixed in the package nvidia-graphics-drivers-510-server -
510.73.08-0ubuntu0.21.10.1
---
nvidia-graphics-drivers-510-server (510.73.08-0ubuntu0.21.10.1) impish;
urgency=medium
* New upstream release (LP: #1975509):
- When calculating the address of grid barrier
This bug was fixed in the package nvidia-graphics-drivers-510-server -
510.73.08-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-510-server (510.73.08-0ubuntu0.22.04.1) jammy;
urgency=medium
* New upstream release (LP: #1975509):
- When calculating the address of grid barrier
(In reply to Cameron Berkenpas from comment #429)
> Created attachment 298789 [details]
> linux-legion-sound-0.0.13.patch
>
> auto mute is now properly disabled as per Takashi's suggestion.
>
> This patch is against the latest Linus tree, but applies against 5.14.3 just
> fine.
>
> This patch
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 1977476
and then change the status of the bug to 'Confirmed'.
If, due to the
Please run
apport-collect 1977476
on the affected system.
** Tags added: jammy
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mate-power-manager (Ubuntu)
Importance: Undecided
Status: New
** Also affects: acpi (Ubuntu)
Importance:
** Tags added: kinetic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927807
Title:
"https" address causes zsync download to fail with error 'could not
read control file from URL'
To manage
Public bug reported:
i set ubuntu to sleep and i find everything crashing when i wake up the
laptop as if i didnot go to suspend mood and i just restarted the
labtop. chrome tells me that it crahsed . i donot know what to do or
where is the problem is
ProblemType: Bug
DistroRelease: Ubuntu 20.04
oem-5.17 verification missing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958770
Title:
Aquantia GbE LAN driver causes UBSAN error during kernel boot
To manage notifications about this bug go
oem-5.17 verification missing
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969326
Title:
Enable hotspot feature for Realtek 8821CE
To manage
oem-5.17 verification missing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968861
Title:
Support Cirrus audio codec configurations for Odin platform
To manage notifications about this bug go to:
oem-5.17 verification missing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969434
Title:
build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
To manage notifications about this bug go to:
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972802
Title:
enable config for fixing 5.17 kernel won't load mok
To manage notifications about this bug go
oem-5.17 verification missing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973104
Title:
e1000e report hardware hang
To manage notifications about this bug go to:
The problem still persist in Ubuntu 22.04. Should I file a new issue?
** Attachment added: "ubuntu_22.04_missing_glyphs."
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1967009/+attachment/5594565/+files/ubuntu_22.04..png
--
You received this bug notification because you are a
Performing verification for Bionic.
Bionic seems to hibernate okay on both Xen and KVM based instances, so I tested
both t2.medium and c5.large instance types. Each had 20gb of storage, with
advanced > enable encryption > yes.
I also made sure to enable Advanced settings > Stop State
301 - 353 of 353 matches
Mail list logo