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: Und
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 nature
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 allo
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 all
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 i
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 i
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 i
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 i
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 (main/2
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)
* CVE-2022-1158
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 i
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 i
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 i
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 i
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 i
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 i
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)
* CVE-2022-1158
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 i
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 i
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 i
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 i
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 i
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 i
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 i
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 i
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 i
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 i
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 i
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 i
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 i
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 i
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 i
This bug was fixed in the package linux-azure - 5.13.0-1026.30
---
linux-azure (5.13.0-1026.30) impish; urgency=medium
* impish/linux-azure: 5.13.0-1026.30 -proposed tracker (LP: #1974334)
* [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555
netvsc_probe+0x3c
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)
* CVE-2022-1158
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 i
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 i
This bug was fixed in the package linux-azure - 5.13.0-1026.30
---
linux-azure (5.13.0-1026.30) impish; urgency=medium
* impish/linux-azure: 5.13.0-1026.30 -proposed tracker (LP: #1974334)
* [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555
netvsc_probe+0x3c
This bug was fixed in the package linux-azure - 5.15.0-1008.9
---
linux-azure (5.15.0-1008.9) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (mai
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 i
This bug was fixed in the package linux-azure - 5.13.0-1026.30
---
linux-azure (5.13.0-1026.30) impish; urgency=medium
* impish/linux-azure: 5.13.0-1026.30 -proposed tracker (LP: #1974334)
* [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555
netvsc_probe+0x3c
This bug was fixed in the package linux-azure - 5.15.0-1008.9
---
linux-azure (5.15.0-1008.9) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (mai
This bug was fixed in the package linux-azure - 5.15.0-1008.9
---
linux-azure (5.15.0-1008.9) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (mai
This bug was fixed in the package linux-azure - 5.15.0-1008.9
---
linux-azure (5.15.0-1008.9) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (mai
This bug was fixed in the package linux-azure - 5.15.0-1008.9
---
linux-azure (5.15.0-1008.9) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (mai
This bug was fixed in the package linux-azure - 5.15.0-1008.9
---
linux-azure (5.15.0-1008.9) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (mai
This bug was fixed in the package linux-azure - 5.15.0-1008.9
---
linux-azure (5.15.0-1008.9) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1008.9 -proposed tracker (LP: #1974294)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (mai
This bug was fixed in the package linux-azure - 5.13.0-1026.30
---
linux-azure (5.13.0-1026.30) impish; urgency=medium
* impish/linux-azure: 5.13.0-1026.30 -proposed tracker (LP: #1974334)
* [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555
netvsc_probe+0x3c
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1904225
Title:
Use ACPI S5 for reboot
Status in HWE Next:
New
Sta
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1902848
Title:
Support Intel AX210 wifi [8086:2725] Subsystem [8086
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1892288
Title:
Comet Lake PCH-H RAID not support on Ubuntu20.04
Sta
** Changed in: oem-priority
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1887910
Title:
[bionic]blutoothd segfault when you cancel the keyboa
** Changed in: oem-priority
Status: New => 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/1967274
Title:
Screen sometimes can't update [Failed to post KMS update: CRT
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1912676
Title:
Fix regression introduced by codec PM change
Statu
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1908366
Title:
Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1890130
Title:
Add support for Intel Bluetooth Device Typhoon Peak
** Changed in: oem-priority
Status: New => Fix Released
--
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/1957094
Title:
on-demand mode doesn't work with nvidia-390
Status
You have been subscribed to a public bug:
---Problem Description---
Upgrade from Ubuntu 21.10 to 22.4 fails
I run do-release-upgrade and I got a message upgrade completed with
errors. I rebooted the server and it is now in an undefined state
between 21.10 and 22.04. Not all packages have been ins
Default Comment by Bridge
** Attachment added: "apt log"
https://bugs.launchpad.net/bugs/1977493/+attachment/5594578/+files/term.log
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You received
** Tags added: kern-3468
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1976613
Title:
Enable Asus USB-BT500 Bluetooth dongle(0b05:190e)
Status in HWE Next:
New
Status in lin
** Package changed: linux (Ubuntu) => pam (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
--
You received this bug notification because you are a mem
This bug is awaiting verification that the linux/5.15.0-36.37 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-36.37 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-36.37 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-36.37 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-36.37 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-36.37 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-36.37 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-36.37 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-36.37 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-36.37 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
You have been subscribed to a public bug:
Description: zfcp: fix failed recovery on gone remote port, non-NPIV
FCP dev
Symptom: With non-NPIV FCP devices, failed recovery on gone remote port.
As follow-on error, failed paths after storage target NPIV
failover
Public bug reported:
Description: zfcp: fix failed recovery on gone remote port, non-NPIV
FCP dev
Symptom: With non-NPIV FCP devices, failed recovery on gone remote port.
As follow-on error, failed paths after storage target NPIV
failover with IBM FCP storage
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: snappy-hwe-snaps
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1973835
Title:
Ubuntu 2
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-z-systems
Importance:
Going to wontfix for bionic since there doesn't seem to be a need for it
at this point
** Changed in: bluez (Ubuntu Bionic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://b
You have been subscribed to a public bug:
Description: hypfs: fix listing z/VM guests with access control group
set
Symptom: hypfs/hyptop info doesn't include z/VM guests with access
control group set
Problem: Currently if z/VM guest is allowed to retrieve hypervisor
I am also affected by this issue. Thinkpad X260 / Ubuntu 22.04. Previous
versions were working fine. On 22.04, kernel 5.13 did not have the issue
but the Wifi was not working.
Is there anything I could do to help diagnose the issue?
--
You received this bug notification because you are a member
Public bug reported:
Description: hypfs: fix listing z/VM guests with access control group
set
Symptom: hypfs/hyptop info doesn't include z/VM guests with access
control group set
Problem: Currently if z/VM guest is allowed to retrieve hypervisor
perfo
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (
Public bug reported:
Today I have updated from 20.04 to 22.04. Now it is impossible to
connect to ALMAWIFI that is my university wifi network. Being this part
of EDUROAM, I strongly suspect that EDUROAM has been broken as well.
The system seems to be able to connect to regular wifi networks, such
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/1977526
Title:
Regression: upgrade to ubuntu
as no activity for quite some time (same in the external bug), mark
incomplete in oem-priority
** Changed in: oem-priority
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1063.64)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
bbswitch/0.8-4ubuntu1 (arm64)
acpi-call/1.1.0-4 (arm64)
Please visit the excuses page listed below and i
How can I test the fix?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1969326
Title:
Enable hotspot feature for Realtek 8821CE
Status in HWE Next:
New
Status in OEM Priority
@kaihengfeng, the first test with unloading a limited amount of modules
(due to rmmod -f limitations) did not result in 0% battery drain. So the
next step would be a modified kernel that allows unloading all modules
(see #56). Do you maybe have another suggestion of how to find out which
module nee
*** This bug is a duplicate of bug 1958267 ***
https://bugs.launchpad.net/bugs/1958267
In fact a duplicate, sorry for the noise
** This bug has been marked a duplicate of bug 1958267
wpa can't connect to servers using TLS 1.1 or older
--
You received this bug notification because you are
** Changed in: linux (Ubuntu Focal)
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/1976116
Title:
Focal update: v5.4.191 upstream stable relea
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1063.97) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/unknown (arm64)
nvidia-graphics-drivers-390/390.151-0ubuntu0.20.04.1 (armhf)
Please visit the excuses
My internal display doesn't wake up after sleep on 22.04. There was a
bug report but I can't see it any longer.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu.
https://bugs.launchpad.net/bugs/1860934
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubunt
Sorry to Bother, Do you order from Amazon?
John Sonderegger
--
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/406728
Title:
[Dell Inc. MM061] suspend/resume failure
Status in linux packag
Sorry to Bother, Do you order from Amazon?
John Sonderegger
json...@yahoo.com
Propelled by Penguin Power
--
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/406728
Title:
[Dell Inc. MM061] su
Public bug reported:
After restart the labtop the system raise an error alert.
I've just upgrade system (sudo apt-get upgrade) using terminal due
graphic assistant did not work.
Audio in youtube doesn't work but using system test does.
Video is working well.
Thank you very much,
ProblemType:
apport information
** Tags added: apport-collected
** Description changed:
powersave governor frequency and gets higher after resume from
suspension, getting worse performance than ondemand governor with the
computer on "idle state". powersave seems to lock on the smaller cpu
frequency
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1977476/+attachment/5594731/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1977476/+attachment/5594733/+files/Lspci.txt
--
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/1977476
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1977476/+attachment/5594730/+files/CRDA.txt
--
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/1977476
Ti
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1977476/+attachment/5594732/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1977476/+attachment/5594741/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1977476/+attachment/5594739/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
1 - 100 of 119 matches
Mail list logo