Thanks.
Yes it sounds like you had an old proposed kernel, in between the
current 'updates' and 'proposed' versions. But no matter, if the bug is
fixed in "5.13.0-28-generic #31" then great!
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notific
I am on the proposed-channel. I don't know how I got that version but I
switched to "normal". Output of uname -a
... 5.13.0-28-generic #31-Ubuntu SMP ...
Seems to be the one you mentioned.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
To be more precise, after logging in I normally press a button on the
mouse, then the Blutooth icon shows me the connection as active in the
bar. After 5-10 seconds it is gone again. The mouse no longer reacts. It
takes about 20 seconds, then I have a connection again for abou
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Status: New => Triaged
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notifi
Interesting because I thought you were using Ubuntu 21.10 but that's not
a listed kernel version for 21.10:
https://launchpad.net/ubuntu/impish/+source/linux
If you can verify the fix is in a version that's in Ubuntu then we can
mark the bug as fixed.
--
You received this bug notification bec
I think the strlcat thing is a red herring or an indication that the
test environment is somehow in a bad shape. This could be explained if
there was two versions of liblxc on the system for example.
Outside of that, I'm also seeing:
```
lxc-start tmp.KEpxw2rh0e 20220205081512.354 ERRORutils
Matt, double-thank you for pointing out the OEM kernel versioning system
I had no idea existed. Plus, I have been testing the C kernel for two
weeks now and had no issues with the WIFI waking up.
(I had, though, an issue with the Bluetooth not reconnecting my devices
correctly a couple of times --
Bug report won't expire due to bug watch.
No response to comment #1 after nearly two months
Looks like reporter running an EOL release
Closing as "Invalid"
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
The following devices are breaking away after connecting the scanner
(compared lsusb -v -v -v before and afterwards):
Bus 002 Device 003: ID 05e3:0612 Genesys Logic, Inc.
idVendor 0x05e3 Genesys Logic, Inc.
Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc.
idVendor 0x05e
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1956849
Title:
Almost all USB ports suddenly stopped working; unbootab
I do not actually know about Focal... but is NOT fixed in Impish,
and this is the only thing assigned to a person.
** Changed in: linux (Ubuntu Impish)
Status: Fix Released => Confirmed
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: Fix Released => Confirmed
--
You received
Any news on this one? I can boot the Ubuntu Jammy desktop using acpi=force and
install the desktop.
However, on subsequent boots it hangs with the same error in spite of the
changed grub config.
Also, shutdown does not work at all. Ubuntu just hangs silently.
This is on VMware Fusion (latest te
I am experiencing the same problem with a brandnew brother DS-740D scanner,
when connecting the scanner to a USB3.0 port on a MSI GE63 7RD laptop
with Ubuntu 18.04 LTS, mouse and keyboard connected to USB are dead afterwards.
touchpad and keyboard directly on the machine are still working.
On Win
Same issue on my new HP Laptop 15s-fq2000nb (https://support.hp.com/be-
fr/document/c07043807), and I confirm that the issue is still there and
the PC is unusable while the Wifi is on.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-
** Summary changed:
- compilation due to "peermem" module
+ compilation errors due to "peermem" module
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1960256
Title:
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed f
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed f
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed f
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed f
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed f
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed f
@sebastian-berner or @kai-szymanski - please confirm that this fixes
your cifs issue.
--
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/1959665
Title:
linux-image-5.4.0-97.110 freezes by ac
This bug is awaiting verification that the linux-azure/5.4.0-1069.72
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 exists, c
Same thing, hardware is an Intel NUC NUC10i5FNK. OS: Ubuntu Server
20.04.3 LTS. Kiosk machine, when I select 5.13.0-28 to boot, it just
freezes at loading ramdisk. 5.11.0-46-generic works just fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
All autopkgtests for the newly accepted linux-meta (5.13.0.30.40) for impish
have finished running.
The following regressions have been reported in tests triggered by the package:
initramfs-tools/0.140ubuntu6 (amd64)
casper/1.465 (amd64)
systemd/248.3-1ubuntu8.2 (armhf)
libvirt/unknown (amd64)
** Changed in: hwe-next
Status: In Progress => Fix Released
--
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/1956373
Title:
Fix for rare (~1%) s0ix failures o AMD systems
** Information type changed from Private Security to Public
--
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/1956886
Title:
package linux-modules-5.13.0-23-generic (not installed) failed t
Public bug reported:
Installed with the following:
apt-get install --no-install-recommends nvidia-driver-470 nvidia-
modprobe libnvidia-cfg1-470 libnvidia-common-470 libnvidia-compute-470
libnvidia-decode-470 libnvidia-encode-470 libnvidia-extra-470 libnvidia-
fbc1-470 libnvidia-gl-470 libnvidia-
All ubuntu_kernel_selftests.ftrace:ftracetest tests completed
successfully with bionic:linux 4.15.0-169.177:
https://autopkgtest.ubuntu.com/results/autopkgtest-
bionic/bionic/s390x/l/linux/20220207_154815_bf623@/log.gz
** Tags removed: verification-needed-bionic
** Tags added: verification-done-b
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
--
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/1960213
Title:
Kernel Panic on linux-image-5.15.0-18-generic
Status in linux p
This bug was for 20.04 GA kernel plain Ubuntu - hence verification on
linux-ibm-5.4/5.4.0-1014 does not apply here.
However, I'm updating the tags to verification-done-bionic, just to unblock the
process.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
Yo
This bug was for 20.04 GA kernel plain Ubuntu - hence verification on
linux-ibm-5.4/5.4.0-1014 does not apply here.
However, I'm updating the tags to verification-done-bionic, just to unblock the
process.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
Yo
This bug was for 20.04 GA kernel plain Ubuntu - hence verification on
linux-ibm-5.4/5.4.0-1014 does not apply here.
However, I'm updating the tags to verification-done-bionic, just to unblock the
process.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
Yo
This bug is awaiting verification that the linux-
ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem st
This bug is awaiting verification that the linux-
ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem st
This bug is awaiting verification that the linux-
ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem st
This bug is awaiting verification that the linux-
ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem st
This bug is awaiting verification that the linux-
ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem st
This bug is awaiting verification that the linux-
ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem st
This bug is awaiting verification that the linux-
ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem st
This bug is awaiting verification that the linux-
ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem st
This bug is awaiting verification that the linux-
ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem st
/etc/default/grub and adding
GRUB_CMDLINE_LINUX="nvidia-drm.modeset=1"
sudo upgrade-grub
Thank you! Finally that worked ! (also with nvidia-driver-470)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
Public bug reported:
After a normal day's operations, the monitors switch off after an hour
or so. Every morning since Impish, upon waking up and unlocking the
system: 2 of the monitors wake, the rest remain in sleep mode. The
only recourse is to do a graceful poweroff and cold boot. There is a
I've just tried 5.4.0-99.112 it still doesn't work (I mean the camera [lsusb:
Bus 002 Device 005: ID 041e:4095 Creative Technology, Ltd Live! Cam Sync HD
[VF0770]). I will not report the bug again. Nothing happens. I roll back to
5.4.0-91
I can't find any hardware problem so the onlu solution i
Maybe it has already been fixed in 5.13.0-28.31 but I'm currently at
5.13.0-28.38
--
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/1806396
Title:
lis3lv02d: unknown sensor type 0x0 in HP x
This bug is awaiting verification that the linux/5.13.0-30.33 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-impish' to 'verification-done-impish'. If the
problem still exists, change
** Description changed:
There is a new more efficient debug format enabled via
CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need
packaging in the .ddeb before we can enable this. Evaluate whether the
other tooling we have will handle it before doing so.
--
* all
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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/1958155
Title:
Pod traffic not taking advantage of interf
Problem can be reproduced with 5.13.0-28.31~20.04.1 as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1958494
Title:
After upgrade to linux-image-5.13.0-27-generic,
Hi,
The reason I raised it as a security issue is because the issue came up
after I connected to public wifi. It resolves itself sometimes but when I
connect to wifi again the cursor freezes up and I have to use a mouse. The
touchpad issue might not be a security risk but I believe it is a symptom
** Description changed:
There is a new more efficient debug format enabled via
CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need
packaging in the .ddeb before we can enable this. Evaluate whether the
other tooling we have will handle it before doing so.
+
+ --
+
+ * all
** Package changed: ubuntu => linux-signed (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1960213
Title:
Kernel Panic on linux-image-5.15.0-18-generic
Status in linux-si
You have been subscribed to a public bug:
Hello. Get a Kernel Panic on linux-image-5.15.0-18-generic
The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957012
On 5.13.0-29-generic boot successfully.
Laptop: Lenovo
Model: 20RA002SRT
Stack trace in attached images.
** Affects: linu
@bonej079 I've tried every kernel from the 5.4 line and can confirm that
Creative Live! Cam Sync HD (VF0770) doesn't work on any of them after
5.4.0-91. Once I run the system using 5.4.0-91 it works like a charm so
no hardware failure for sure.
--
You received this bug notification because you ar
This bug was fixed in the package linux - 5.4.0-99.112
---
linux (5.4.0-99.112) focal; urgency=medium
* focal/linux: 5.4.0-99.112 -proposed tracker (LP: #1959817)
* linux-image-5.4.0-97.110 freezes by accessing cifs shares (LP: #1959665)
- Revert "cifs: To match file servers,
Only a few 5.11 kernels have AUFS config enabled and focal:linux-
hwe-5.11 is not one of them, so the fix cannot be verified with this
kernel. However, this fix has been cherry-picked by focal:linux-
oracle-5.11 and focal:linux-riscv-5.11 by versions which were already
promoted to -updates:
https:
** Tags added: verification-done-focal
--
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/1958153
Title:
[SRU][F] Add firmware of MT7922
Status in linux-firmware package in Ubuntu:
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
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/1958151
Title:
[SRU][I/J/OEM-5.13/OEM-5.14] Ad
Changing nomination from hirsute/linux to focal/linux-hwe-5.11 as
Hirsute has reached EOL.
** Also affects: linux-hwe-5.11 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.11 (Ubuntu)
Status: New => Invalid
** Changed in: linux-hwe-5.11 (Ubuntu Hirsute)
** Description changed:
Currently there is no support for TPLink (UB500) nano usb bluetooth
- adapter in Ubuntu 21.10. While checking it was found that
+ adapter in Ubuntu 21.10. While checking it was found that adding
+
https://github.com/torvalds/linux/commit/4fd6d490796171bf786090fee782e2521
*** This bug is a duplicate of bug 1958283 ***
https://bugs.launchpad.net/bugs/1958283
** This bug has been marked a duplicate of bug 1958283
linux-firmware missing renoir_ta
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-si
Public bug reported:
Currently there is no support for TPLink (UB500) nano usb bluetooth
adapter in Ubuntu 21.10. While checking it was found that
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
@juergh, thank you very much! Now, with this version of the firmware
everything works fine!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1958777
Title:
Noise before log
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24
---
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP:
#1959585)
* Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
- drm/am
The output was " no additional information collected"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1960129
Title:
kernelpanic on shutdown
Status in linux-signed-hwe-5.
Same here, cleared with 5.13.0-28 update.
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1958724
Title:
System Shutdown and resume hangs since Kernel linux-
imag
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1959921
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Please run 'apport-collect 1960129'.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1960129
Title:
kernelpanic on shutdown
Status in linux-signed-hwe-5.13 package in Ubu
** Package changed: linux (Ubuntu) => linux-hwe-5.13 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1960018
Title:
Boot Failure - linux-image-5.13.0-28-generic | regre
Can you try linux-firmware 1.187.26 from focal proposed?
https://launchpad.net/ubuntu/+archive/primary/+files/linux-
firmware_1.187.26_all.deb
** Package changed: linux (Ubuntu) => linux-hwe-5.13 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which
Can you try linux-firmware 1.187.26 from focal proposed?
https://launchpad.net/ubuntu/+archive/primary/+files/linux-
firmware_1.187.26_all.deb
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.l
Can you try linux-firmware 1.187.26 from focal proposed?
https://launchpad.net/ubuntu/+archive/primary/+files/linux-
firmware_1.187.26_all.deb
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.l
85 matches
Mail list logo
