I am NOT seeing the same on 22.04
```
ubuntu@cloudimg:~$ uname --kernel-release
5.15.0-87-generic
ubuntu@cloudimg:~$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
** Description changed:
[ Impact ]
- Affects devices that use SoundWire-Audio Codec-ALC713 and SoundWire-Jack
Codec-ALC713.
- Without correct configurations in userspace above codecs cannot be used.
+ Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack
Codec-ALC713.
+ Without
Hello there! I am using Ubuntu 22.04 LTS on honor magickbook 15.
Bluetooth doesn't see any devices. If u need additional information I
can post it here.
>Does it work after you turn it on?
It doesn’t react in any way to turning it on and off, it just says “Turn on the
Bluetooth adapter” all the
@kamalmostafa indeed yes. I had missed this.
See below for the output from 20.04 with 5.15 kernel.
```
ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting
--numjobs=8 --name=fiojob1
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
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-gcp-tcpx' to 'verification-done-
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
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-gcp-tcpx' to 'verification-done-
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/2042945
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
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-gcp-tcpx' to 'verification-done-
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
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-gcp-tcpx' to 'verification-done-
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
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-gcp-tcpx' to 'verification-done-
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
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-gcp-tcpx' to 'verification-done-
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
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-gcp-tcpx' to 'verification-done-
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
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-gcp-tcpx' to 'verification-done-
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
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-gcp-tcpx' to 'verification-done-
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
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-gcp-tcpx' to 'verification-done-
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
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-gcp-tcpx' to 'verification-done-
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1002.2
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-gcp-tcpx' to 'verification-done-
** Changed in: linux-riscv (Ubuntu)
Assignee: (unassigned) => Heinrich Schuchardt (xypron)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/2043061
Title:
System suspension is
In the old kernel there was the bug in the previous one it was resolved.
Now they've apparently put the drive with the bug back in.
--
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/2039744
Extra system information with dmesg nouveau crash stack added:
** Attachment added: "nouveau_crash.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2042835/+attachment/5717389/+files/nouveau_crash.txt
--
You received this bug notification because you are a member of Kernel
Regarding the swapped page read failure issue, I've sent a patch upstream for
review. Visit the link if you're interested:
https://lists.crash-utility.osci.io/archives/list/de...@lists.crash-utility.osci.io/thread/76EA25KPIRKQY5JDFFNYQY2C4CDRLZP2/
--
You received this bug notification because
This definitly is related somehow to the 6.2.0-36 kernel and/or ubuntu,
because other distributions like Bodhi basing on ubuntu packages/core
exactly behave the same with a scrambled/puzzled display running the
6.2.0-36 kernel from ubuntu. This seems to be a major issue.
--
You received this bug
Public bug reported:
After the user has installed and used Ubuntu 23.10 on VisionFive 2 (Model
1.3B), his system is always suspended with slow or no response.
StarFive FAE has reproduced the issue in the following practices.
1. Install the Ubuntu system on VisionFive 2.
2. Type in the account
I believe the key to the reproducer is having the kdump-tools package
installed in the chroot. The kdump-tools package provides a
/etc/kernel/postinst.d/kdump-tools script, which has the following
snippet:
(Apologies for formatting, the interface removes the leading spaces from
this code)
43
The complete recreate steps with errors are the following:
Steps to reproduce:
1. Create a directory on a BCM head node or any Linux sever, say
/cm/images/dgx-h100-image
2. Download and unpack the DGX-OS base tar archive into the above
directory
$ wget
Public bug reported:
Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.15.0-1040-nvidia
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating
Still happening for me on both 23.10 (which won't detect my GF199 GPU
at all and has no nVidia utils package) and a black screen after the
last kernel update on 22.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This bug was fixed in the package ipu6-drivers -
0~git202310180730.3f813580-0ubuntu0.24.04.1
---
ipu6-drivers (0~git202310180730.3f813580-0ubuntu0.24.04.1) noble; urgency=low
[ Hao Yao ]
* New upstream 20230802_1500_mtl_plat release.
* New upstream 20230911_0620_mtl_plat_pv
This bug was fixed in the package ipu6-drivers -
0~git202310180730.3f813580-0ubuntu0.24.04.1
---
ipu6-drivers (0~git202310180730.3f813580-0ubuntu0.24.04.1) noble; urgency=low
[ Hao Yao ]
* New upstream 20230802_1500_mtl_plat release.
* New upstream 20230911_0620_mtl_plat_pv
This bug was fixed in the package ivsc-driver -
0~git202212210258.94ecb88b-0ubuntu0.24.04.1
---
ivsc-driver (0~git202212210258.94ecb88b-0ubuntu0.24.04.1) noble; urgency=low
[ You-Sheng Yang ]
* Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
- ljca: try to
Interesting finding:
Using Phil's setup outlined in Comment #5 I am able to reproduce the
performance problem (e.g. 665MiB/s with stock v5.4 kernel versus
581MiB/s after upgrading to v5.15). But I also note that with the v5.15
kernel, fio always gets a segfault in libglusterfs.so while running
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-November/146804.html
(jammy)
* https://lists.ubuntu.com/archives/kernel-team/2023-November/146805.html
(mantic)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ Missing mei_vsc firmware for HM2172 and OV02E sensor.
+
+
Cancelled previous SRU to include updates for AX201 as well.
** Changed in: linux-firmware (Ubuntu Jammy)
Status: In Progress => Triaged
** Changed in: linux-firmware (Ubuntu Mantic)
Status: In Progress => Incomplete
** Changed in: linux-firmware (Ubuntu Jammy)
Status:
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-firmware (Ubuntu
** Merge proposal linked:
https://code.launchpad.net/~mfo/ubuntu/+source/crash/+git/crash/+merge/455353
** Description changed:
- Work in progress; rebasing on 8.0.3+ds1-3, and testing.
+ Merge Request / git-ubuntu:
+
+
amd64
-
vm
lxc launch --vm -c limits.cpu=2 -c limits.memory=2GiB
ubuntu-daily:noble noble-vm
lxc shell noble-vm
# uname -rv
6.5.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct 7 01:35:40 UTC
2023
kdump-tools
sudo apt update && apt install -y
armhf
(fails to kexec to the crash kernel, anyway, for doc purposes)
-
vm
sudo modprobe nbd
sudo qemu-nbd -c /dev/nbd0 noble-server-cloudimg-armhf.img
mkdir mnt
sudo mount /dev/nbd0p16 mnt
sudo cp mnt/vmlinuz-*-generic mnt/initrd.img-*-generic .
common for arm64, ppc64el, s390x, armhf:
---
cloud-init data iso:
echo 'local-hostname: test' >meta-data
PUBKEY=$(cat $HOME/.ssh/id_rsa.pub)
cat
ppc64el
---
vm
SERIES=noble
ARCH=ppc64el
DISK=${SERIES}_${ARCH}.qcow2
wget
https://cloud-images.ubuntu.com/$SERIES/current/${SERIES}-server-cloudimg-${ARCH}.img
qemu-img create -F qcow2 -b ${SERIES}-server-cloudimg-${ARCH}.img -f
qcow2 $DISK 8G
arm64
-
vm
SERIES=noble
ARCH=arm64
DISK=${SERIES}_${ARCH}.qcow2
wget
https://cloud-images.ubuntu.com/$SERIES/current/${SERIES}-server-cloudimg-${ARCH}.img
qemu-img create -F qcow2 -b ${SERIES}-server-cloudimg-${ARCH}.img -f
qcow2 $DISK 8G
s390x
-
vm
sudo apt install -y qemu-system-s390x
qemu-system-s390x \
-machine s390-ccw-virtio -cpu qemu \
\
-smp cpus=2 -m 2048 \
-nodefaults -no-user-config \
-nographic -serial stdio \
\
-drive
The test packages in `ppa:mfo/noble-crash-v2` have worked well
(ie, crash can actually start, and is able to get a backtrace)
in amd64, arm64, ppc64el, and s390x (armhf couldn't even kexec).
This is a lot better than the current state (crash quits early)
in all these architectures, so I will move
Upstream patch 'Support-module-memory-layout-change-on-Linux-6.4'
is required to crash to open a 6.5 kernel crashdump on Noble too.
# crash ./usr/lib/debug/boot/vmlinux-*-generic /var/crash/*/dump.*
...
crash: invalid structure member offset: module_core_size
FILE: kernel.c LINE: 3781
** 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/2041668
Title:
Memory leak in 23.10 kernel (6.5.0-10)
Status
Replying to my self here: I do not see an easy way to install the
'official driver' without (potentially) bricking my laptop, so I think I
will take a cautious approach (delay until I really have time to deal
with potential problems, prepare by doing a timeshift, document
everything I need to do,
Note for testers: I had to modify Phil's launch-qcow2-image-qemu-40G.sh
script as follows. Without this change qemu drops me into the UEFI
Interactive Shell.
diff launch-qcow2-image-qemu-40G.sh.orig launch-qcow2-image-qemu-40G.sh
194c194
< -device scsi-hd,drive=boot-disk \
---
> -device
Juerg,
Again thank you for patience. I redid a 'journalctl -b -1', see attached
file. Comparing it to the current boot ('journalctl -b' in my working
mode), I see a line that may be the symptom:
Nov 07 20:24:03 linux kernel: amd_gpio AMDI0030:00: Invalid config param
0014
I remember seeing
Testing on amd64, arm64, armhf, ppc64el, and s390x with QEMU VMs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2042357
Title:
Merge crash 8.0.3+ds1-3 into Noble
Status in crash
Yes, enabling TPM 2.0 in BIOS and setting 'tpm_tis.interrupts=0' as
suggested in #36 works!
As I stated before, 6.5.* used to work. This matches your comment that
6.5 has my model on it's list. Would be great if this list or the new
disabled-by-default setting could be backported.
For my own
After a bit of a fight, I've managed to get the MIPI camera working on
my Lenovo ThinkPad X1 Carbon Gen 10. Here's what I've got:
- I'm using Ubuntu 22.04.3 LTS.
- I'm using Kernel 6.2.0-34-generic (with 6.2.0-35-generic for example it
doesn't work for me)
With the above, I followed these
FWIW, this appears to be an issue in the upstream 6.5 kernel. It's discussed
in more detail here:
https://lore.kernel.org/all/1694366...@msgid.manchmal.in-ulm.de/
A fix was applied to the mainline kernel here:
Providing exact reproducer steps using Qemu locally -
Launch script:
https://gist.github.com/philroche/8242106415ef35b446d7e625b6d60c90 and
cloud image I used for testing @ http://cloud-
images.ubuntu.com/minimal/releases/focal/release/
```
# Download the VM launch script
wget
Lenovo and other machines seem to suffer from TPM interrupt storms and
there's a growing list of models in the kernel for which interrupts are
disabled. The L590 is on that list but not yet in our 6.2 kernel.
Upstream finally decided to disable interrupts by default since it's
causing so many
Actually, can you re-enable the TPM in the BIOS, add
'tpm_tis.interrupts=0' to the kernel commandline and check if you can
boot a new kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
We probably need this:
https://lore.kernel.org/lkml/87wmy2rqjy.wl-ti...@suse.de/T/#md6808fff127dcbcb6a2a905d774cc5cf5f87f68b
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2036988
Thanks, that's valuable information. Can you try to get boot logs with a
problematic kernel? Remove 'quiet splash' from the commandline option
and maybe add 'debug ignore_loglevel'.
For the record, 6.2.0-36 contains the following TPM related commits:
955df4f87760 tpm, tpm_tis: Claim locality when
** Description changed:
This is a public version of https://bugs.launchpad.net/bugs/2042423
- Starting in 6.5.0-6.6, the BMC output on machines with Aspeed 2600 rev
- 52 GPUs stopped working. The machines boot find if "nomodeset" is set,
- but without "nomodeset", the machine does
** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2023201
Title:
Add support of Smart Amplifier IC
> I did try, long time ago
Well, have you tried the kernel-provided btw88 driver with the current
6.2 kernel? You'll get much better support if an official driver is not
working.
Also, your journal log is incomplete. It's missing the boot messages and
only seems to contain the tail.
--
You
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-November/146789.html
(jammy)
* https://lists.ubuntu.com/archives/kernel-team/2023-November/146790.html
(lunar)
* https://lists.ubuntu.com/archives/kernel-team/2023-November/146791.html
(mantic)
** Changed in: linux-firmware (Ubuntu
FYI I created a ticket with Azure Support and they say "We have found
the bug and Microsoft is working with the Canonical side. waiting for
the update from canonical side"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
People on the Linux Mint thread:
https://forums.linuxmint.com/viewtopic.php?t=405762
...are reporting that kernel 6.2 solves the problem for them. I haven't tested
this for myself yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags removed: verification-needed-lunar-linux-azure
verification-needed-mantic-linux-azure
** Tags added: verification-done-lunar-linux-azure
verification-done-mantic-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Changed in: ipu6-drivers (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: ivsc-driver (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in
Will do!
The .crash file is empty as well and the error ubuntu error says nothing
is on the tracker.
--
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/2041219
Title:
GUI Freezes Randomly
Regarding the swapped page read failure, I've created an upstream PR. If you're
interested, please visit the following link:
https://github.com/crash-utility/crash/pull/159
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
Public bug reported:
SRU Justification:
[Impact]
Currently, the offsets calculated for programming crspace type events on
BlueField-3 are incorrect and this leads to a mismatch of counter numbers
between the driver and actual HW where, for example, event2 in the driver is
actually event4 in
** Tags added: oem-priority originate-from-2040121 somerville
--
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/2042999
Title:
BT/WiFi coex stability issue on RTL8851BE/RTL8852BE
This bug is awaiting verification that the linux-azure/6.5.0-1009.9
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
*** This bug is a duplicate of bug 2033198 ***
https://bugs.launchpad.net/bugs/2033198
** This bug has been marked a duplicate of bug 2033198
package linux-tools-common (not installed) failed to install/upgrade: trying
to overwrite '/usr/bin/acpidbg', which is also in package
*** This bug is a duplicate of bug 2033198 ***
https://bugs.launchpad.net/bugs/2033198
** This bug has been marked a duplicate of bug 2033198
package linux-tools-common (not installed) failed to install/upgrade: trying
to overwrite '/usr/bin/acpidbg', which is also in package
The first patch is already in Jammy
commit 06adda263bd3776b019f282318efe18dd5bfa173
Author: Karan Tilak Kumar
Date: Thu Jul 27 12:39:19 2023 -0700
scsi: fnic: Replace return codes in fnic_clean_pending_aborts()
BugLink: https://bugs.launchpad.net/bugs/2038382
commit
** Attachment added: "package for Mantic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040140/+attachment/5717151/+files/firmware-sof-signed_2.2.6-1ubuntu1.2_all.deb
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "test package for Jammy"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040140/+attachment/5717152/+files/firmware-sof-signed_2.0-1ubuntu4.3_all.deb
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
*** This bug is a duplicate of bug 2037762 ***
https://bugs.launchpad.net/bugs/2037762
** This bug has been marked a duplicate of bug 2037762
UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43
--
You received this bug
I had the same problem (keyboard not working, touchpad working) for a
6.x kernel. The workaround from Johannes and Bernd worked for me, though
I only used "quiet splash i8042.nomux=1" and did not test the additional
"i8042.reset".
System: Fujitsu Lifebook 7U15A1, Ubuntu 22.04.3 LTS, Kernel
** 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-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2037513
Title:
HP ProBook
** Summary changed:
- BT/WiFi coexit stability issue on RTL8851BE/RTL8852BE
+ BT/WiFi coex stability issue on RTL8851BE/RTL8852BE
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Can confirm it affected me as well for what regards the wireless. I don't use
Bluetooth so I can't confirm on that side.
The solution with linux-firmware-20230804.tar.xz worked for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The mantic kernel picked up the f81bb0ac7872893241319ea82504956676ef02fd
change from the https://bugs.launchpad.net/bugs/2035588 v6.5.3 upstream
stable release. This change was originally in the 6.6.0 kernel.
This change was dependant on the upstream change
commit
** Summary changed:
- [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Focal
+ [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
+1 on -proposed mutter. I'm using Ubuntu 23.10 w/ Linux 6.5.0-10-generic
kernel, ThinkPad T14 Gen 3 (AMD), it helped resolving the problem.
Many thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thank you very much, Jannik!
I can confirm that this workaround fixes the problem for me, too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2036988
Title:
Unable to boot on
The proposed commits have been in mainline, and is supposed to be
included in linux-firmware/noble some time later.
For Lunar, we don't have RTL8851BE.
** Also affects: linux-firmware (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Lunar)
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Lunar)
Status: In Progress =>
** Changed in: linux-lowlatency (Ubuntu Lunar)
Status: In Progress => Won't Fix
** Changed in: linux-lowlatency (Ubuntu Jammy)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
1.Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
2.Connected BT KB/MS,and then connected WIFI, select an AP to connect
3.Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond
smoothly.
Proposed firmware upstreamed as:
*
87 matches
Mail list logo
