The kernels (5.15.0-88.98) have been tested without any issues.
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Consensus from maintainers is that it's a mistake that this option is on
for riscv64, especially since compat is off.
** Also affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-starfive (Ubuntu)
Importance: Undecided
Status: New
** Also
This will notably affect libc6-s390
--
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/2038583
Title:
Turning COMPAT_32BIT_TIME off on s390x
Status in Ubuntu on IBM z Systems:
New
Status
This bug was fixed in the package mutter - 45.0-3ubuntu3
---
mutter (45.0-3ubuntu3) mantic; urgency=medium
* Update build autopkgtest to not run dh_auto_test (LP: #2038564)
-- Jeremy Bícha Thu, 05 Oct 2023 14:29:32 -0400
** Changed in: mutter (Ubuntu Mantic)
Status: In
** Summary changed:
- Hello sir/mam I am getting some problem regarding my brightness control i
will expllain more about it in brief below.
+ [Lenovo IdeaPad Gaming 3 15ARH05] Unable to control my screen brightness
** Also affects: linux-hwe-6.2 (Ubuntu)
Importance: Undecided
Status:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
*** This bug is a duplicate of bug 1976276 ***
https://bugs.launchpad.net/bugs/1976276
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 1976276, so it is being marked as such. Please
You have been subscribed to a public bug:
Brightness doesn't change. The slide for brightness doesn't change the
level of brightness.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
Uname: Linux
** Tags removed: verification-needed-jammy-linux-aws
verification-needed-jammy-linux-azure
** Tags added: verification-done-jammy-linux-aws
verification-done-jammy-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Also affects: linux-ibm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2038582
Title:
Turning COMPAT_32BIT_TIME off on arm64
** Also affects: ubuntu-z-systems
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/2038583
Title:
Turning COMPAT_32BIT_TIME off on s390x
** Also affects: ubuntu-power-systems
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/2038587
Title:
Turning COMPAT_32BIT_TIME off on ppc64el
** Also affects: linux-ibm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: intel
Importance: Undecided
Status: New
--
You received this bug notification because you are a
The following changes since commit
294374341c622e5c2ffd15712cadabe0dd9865f1:
UBUNTU: Ubuntu-5.15.0-83.92 (2023-08-14 11:05:34 +0200)
are available in the Git repository at:
https://github.com/tdavenvidia/ubuntu_kernel_jammy/pull/3
for you to fetch changes up to
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 2038589
and then change the status of the bug to 'Confirmed'.
If, due to the
** Also affects: linux-oracle (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu)
Importance:
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oracle (Ubuntu)
Importance:
Public bug reported:
DAMBUF is backported using the two series of patches:
First, we need the series of 3 patches at:
https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/
- dma-buf: Fix pin callback comment
- RDMA/umem: Allow pinned dmabuf umem usage
- RDMA/efa: Add
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 2038582
and then change the status of the bug to 'Confirmed'.
If, due to the
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 2038579
and then change the status of the bug to 'Confirmed'.
If, due to the
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 2038583
and then change the status of the bug to 'Confirmed'.
If, due to the
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 2038584
and then change the status of the bug to 'Confirmed'.
If, due to the
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 2038586
and then change the status of the bug to 'Confirmed'.
If, due to the
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 2038587
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
This will prevent existing 32-bit powerpcle binaries to operate
correctly, if they are still using 32bit time. And even exists?
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic failure
in
Public bug reported:
This will prevent (?!) binaries to operate correctly, if they are still
using time32 but maybe riscv32 ABI uses 64-bit time_t anyway?
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic
Public bug reported:
This will prevent existing armhf binaries to operate correctly, if they
are still using 32bit time.
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic failure
in the field due to these
** Tags added: 32bit-time
** Tags added: y2038
--
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/2038579
Title:
Turning COMPAT_32BIT_TIME off on amd64
Status in linux package in Ubuntu:
Public bug reported:
This will prevent existing armhf binaries to operate correctly, if they
are still using 32bit time.
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic failure
in the field due to these
Public bug reported:
This will prevent existing s390 binaries to operate correctly, if they
are still using 32bit time.
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic failure
in the field due to these
c -- cloud-init status --wait
```
The `lxc exec mantic -- cloud-init status --wait` times out after 240s
and will fail our test as a result.
I have been able to replicate in a local VM
```
wget
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img
wget
Public bug reported:
This will prevent existing i386 binaries to operate correctly, if they
are still using 32bit time.
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic failure
in the field due to these
=16532
comm="systemctl" requested_mask="read" denied_mask="read"
peer="lxd-current-iguana_//"
Oct 05 21:35:04 novel-ram kernel: kauditd_printk_skb: 41 callbacks suppressed
Oct 05 21:35:04 novel-ram kernel: audit: type=1400 audit(16965417
This bug is awaiting verification that the linux/5.4.0-166.183 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-focal-linux' to 'verification-done-focal-linux'. If
the problem still
This bug is awaiting verification that the linux/5.4.0-166.183 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-focal-linux' to 'verification-done-focal-linux'. If
the problem still
This bug is awaiting verification that the linux/5.4.0-166.183 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-focal-linux' to 'verification-done-focal-linux'. If
the problem still
This bug is awaiting verification that the linux/5.4.0-166.183 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-focal-linux' to 'verification-done-focal-linux'. If
the problem still
This bug is awaiting verification that the linux/5.4.0-166.183 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-focal-linux' to 'verification-done-focal-linux'. If
the problem still
This bug is awaiting verification that the linux/5.4.0-166.183 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-focal-linux' to 'verification-done-focal-linux'. If
the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 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-linux-bluefield' to
** Changed in: util-linux (Ubuntu Mantic)
Milestone: None => ubuntu-23.10
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1024.24
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-linux-oem-6.1' to 'verification-done-
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1024.24
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-linux-oem-6.1' to 'verification-done-
This bug is awaiting verification that the linux-aws/5.15.0-1048.53
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1024.24
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-linux-oem-6.1' to 'verification-done-
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1024.24
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-linux-oem-6.1' to 'verification-done-
status --wait
```
The `lxc exec mantic -- cloud-init status --wait` times out after 240s
and will fail our test as a result.
I have been able to replicate in a local VM
```
wget
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img
wget --output-document
tatus --wait
```
The `lxc exec mantic -- cloud-init status --wait` times out after 240s
and will fail our test as a result.
I have been able to replicate in a local VM
```
wget
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64
nfo mantic
lxc exec mantic -- cloud-init status --wait
```
The `lxc exec mantic -- cloud-init status --wait` times out after 240s
and will fail our test as a result.
I have been able to replicate in a local VM
```
wget
http://cloud-images.ubuntu.com/mantic/20231005/mantic-ser
mantic -- cloud-init status --wait` times out after 240s
and will fail our test as a result.
I have been able to replicate in a local VM
```
wget
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img
wget --output-document=launch-qcow2-image-qemu.sh
--wait
```
The `lxc exec mantic -- cloud-init status --wait` times out after 240s
and will fail our test as a result.
I have been able to replicate in a local VM
```
wget
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img
wget --output-document=launch-qcow2-image
** Tags added: pc-kernel
** Tags removed: pc-kernel
** Tags added: pc-kernel-snap
--
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/2025054
Title:
snap-kernel-uc22 lacks atheros firmware
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/2038559
Title:
package
Public bug reported:
automated update of kernel package failed. Tooling says it will append
details.
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-34-generic 6.2.0-34.34
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
SRU: https://lists.ubuntu.com/archives/kernel-
team/2023-October/145972.html (unstable)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => You-Sheng
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/2038433
Title:
systemd autopkgtest
** 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/bugs/2038433
Title:
systemd autopkgtest regression on arm64 and
** Tags removed: kernel-spammed-jammy-linux-bluefield-v2
verification-needed-jammy verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in
** Tags removed: rls-mm-incoming
** Changed in: systemd (Ubuntu)
Importance: High => Medium
--
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/2036968
Title:
Mantic minimized/minimal
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dkms (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2038508
** Changed in: nvidia-graphics-drivers-418-server (Ubuntu)
Status: Incomplete => New
** Changed in: nvidia-graphics-drivers-450-server (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This bug was fixed in the package bumblebee - 3.2.1-29ubuntu1
---
bumblebee (3.2.1-29ubuntu1) mantic; urgency=medium
* Drop old drivers from Ubuntu specific depends, keep just two latest
series of drivers. LP: #2035189
-- Dimitri John Ledkov Thu, 05 Oct 2023
13:29:53 +0100
@vorlon I don't understand adding bumbleebee to this bug, as I am not
requesting to remove it, and it has many aternative depends. These are
updated in
https://launchpad.net/ubuntu/+source/bumblebee/3.2.1-29ubuntu1 in
proposed.
** Changed in: bumblebee (Ubuntu)
Status: In Progress => Fix
** Description changed:
This legacy driver had the last update on 2022.11.22, and is EOL
upstream. We should remove it from the archive before the next LTS,
maybe even before Mantic is released.
We're planning on migrating the kernel from fbdev drivers to using
simpledrm, but this
As Rayen had changed the bug status from "Confirmed" to "Fix Released"
by mistake, I just changed it back to the previous one, and hope that
kernel team will now pay attention, work and release an appropriate fix
for the above mentioned issues at the earliest.
** Changed in: linux-signed-hwe-6.2
I don't expect it helps your boot issue, but the UBSAN issue will be
fixed by this commit.
https://lore.kernel.org/amd-
gfx/78abc334-44ed-4632-8796-6bbe9c432...@amd.com/T/#me31ff6b88640b03be1a8edfc6fc8878ac78ca6bb
Please redo the test with 5.15.
--
You received this bug notification because
*** This bug is a duplicate of bug 2038546 ***
https://bugs.launchpad.net/bugs/2038546
** This bug has been marked a duplicate of bug 2038546
/lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
/lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the
StarFive VisionFive board which uses the starfive kernel flavor.
The file was available in Jammy and only recently removed from Mantic.
File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding
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 2038544
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Kernel 5.15.06.0-86 Mint 21.2 Asus Vivobook 17 amd graphics. After
login black screen.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
We tend to accidentally enable linux-source packages in new kernels. We
need to ensure this defaults off by default.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Andy Whitcroft (apw)
Status: In Progress
** Changed in: linux (Ubuntu)
FYI the linux-image-6.5.0-6-genric version also has the bluetooth random
disconnect/reconnect issue..
(using kubuntu or xubuntu instances .. all on the same physical hardware .. all
Mantic
** Summary changed:
- bluetooth connections are unstable with linux-image-6.5.0-7-generic
+ bluetooth
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/2038539
Title:
bluetooth connections are
this is for the development version .. Mantic daily iso xubuntu
10-05-2023
--
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/2038539
Title:
bluetooth connections are unstable with
did a whole fresh install to verify this .. initial kernel installed was
6.5.0-5 everything worked as expected .. upon upgrade to 6.5.0-7 the
bluetooth connections became unstable ..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
1 - 100 of 161 matches
Mail list logo
