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-oem-5.17 - 5.17.0-1004.4
---
linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
* alsa: enable
This bug is awaiting verification that the linux/5.15.0-28.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' to 'verification-done-jammy'. If the problem
still exists, change
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967067
Title:
WCN6856 BT keep in OFF state after coldboot system
To
This never got applied to jammy...
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967067
Title:
WCN6856 BT
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
** Attachment added: "lp1967067-bt-test.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967067/+attachment/5579243/+files/lp1967067-bt-test.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With linux-oem-5.14/5.14.0-1033.36, this issue is not reproducible
within 20 cold reboots.
A script is used to run rtcwake to cold boot 20 times and attach
`bluetoothctl scan on` result to a log file. If the bluetooth device
cannot be probed, the scan should output "No default controller
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36
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' to 'verification-done-focal'. If the
problem still
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
SRU: https://lists.ubuntu.com/archives/kernel-
team/2022-April/129095.html (oem-5.14, oem-5.17, jammy, unstable)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ WCN6856 BT keep in OFF state after coldboot system.
+
+ [Fix]
+
+ Mainline commit 599ece4f8f07 ("Bluetooth: btusb:
Can confirm that 5.14.0-9031.34+exp.62 fixed this bug. cold-boot 50
times by script and BT can scan normally in all reboots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967067
Title:
WCN6856 BT
Included in following kernels in
https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/intermediate-kernel：
* linux-unstable/jammy version 5.17.0-9006.6+exp.9
* linux-oem-5.17/jammy version 5.17.0-9003.3+exp.5
* linux/jammy version 5.15.0-9024.24+exp.18
* linux-oem-5.14/focal version
commit 599ece4f8f07 ("Bluetooth: btusb: Improve stability for QCA
devices")[1] in mainline now and is to be released in v5.18.
[1]:
https://github.com/torvalds/linux/commit/599ece4f8f073097904d411ee70280a2ec890ad3
--
You received this bug notification because you are a member of Ubuntu
Bugs,
14 matches
Mail list logo
