Alright, I checked with Chris Chiu, he confirms that all the tests
kernels that he provided don't have -fcf-protection=none. However, we
still don't think that touching this compiler option is a proper fix for
the bug, more likely it's just hiding the problem, so we could still
have a potential
** Summary changed:
- [EHL][TGL][ADL][ICX-D] Enable Time Coordinated Compute interface driver
+ [EHL][TGL][ADL][ICX] Enable Time Coordinated Compute interface driver
** Description changed:
Description
Time Coordinated Compute (TCC)
Pseudo SRAM interface support on top of Cache Allocation
** Summary changed:
- [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver
+ [EHL][TGL][ADL][ICX-D] Enable Time Coordinated Compute interface driver
** Description changed:
Description
Time Coordinated Compute (TCC)
Pseudo SRAM interface support on top of Cache Allocation
@kaihengfeng
I just switched to linux-oem-20.04d (5.14.0.1007.7) and, wow, it works like a
charm. The Wi-Fi 6 throughput is impressive.
Thanks a bunch!
Régis
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
** Changed in: blueman (Ubuntu)
Status: New => Incomplete
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
** Changed in: ubuntu-mate
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Summary changed:
- With Nvidia-470 there is no option to use Wayland on the login screen
+ With the Nvidia driver installed there is no option to use Wayland on the
login screen
** Tags added: jammy
** Also affects: nvidia-graphics-drivers-495 (Ubuntu)
Importance: Undecided
Run
apport-collect 1950410
** Tags removed: hirsute
** Tags added: impish
** Also affects: blueman (Ubuntu)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux-hwe-5.11 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-hwe-5.11 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
After validating that I didn't seem to get issues with 20.04.2 I fully
replaced 20.04.3 with the previous version.
I can edit the grub config, but would that impact a live disk? If yes, I
can try editing grub, loading into the .2 version on a live disk, and
play around until I see an issue.
Also
** Changed in: linux
Status: Confirmed => 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/1912052
Title:
[Acer Spin 5 - SP513-54N] External headset microphone not
The above change is in upstream:
https://lore.kernel.org/alsa-
devel/20211104155726.2090997-1-pe...@perex.cz/
--
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/1912052
Title:
[Acer Spin
** 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/1945967
Title:
rtw89 kernel module for
*** This bug is a duplicate of bug 1813733 ***
https://bugs.launchpad.net/bugs/1813733
Chiming in that I also experience this issue on my Razer Blade 17 (2021)
running ElementaryOS 6 (5.11.0-38-generic).
--
You received this bug notification because you are a member of Kernel
Packages,
At first this looks like a hardware fault to me. It looks like what
happens when I replace a laptop screen and it doesn't get a clean
electrical connection. The same can happen if it has received some bumps
and intermittently loses connections on some pins.
However there's a chance this is a
You have been subscribed to a public bug:
(Initial post on ask ubuntu, copy pasted:
https://askubuntu.com/questions/1359955/intense-screen-flickering-
vertical-rainbow-bars-display-problems-on-ubuntu-20)
Starting today (Aug 24) I observed intense screen flickering and tearing
on my Ubuntu
Semih, that's not this bug, it's a completely different bug in a
different driver. You should open a new bug by running:
ubuntu-bug linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 1950385
and then change the status of the bug to 'Confirmed'.
If, due to the
** Package changed: 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/1950385
Title:
HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel
Status in
You have been subscribed to a public bug:
Focal Fossa 20.04.1
HP lt4120 Snapdragon X5 LTE USB modem stopped working from kernel 5.10.x. It is
not seen by Network Manager. Everything worked with 5.8.x kernel. I can't use
newer kernel if I want work over HP lt4120 Snapdragon X5 LTE modem.
I can't
** 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/1950381
Title:
Adding landlock to CONFIG_LSM in 5.13 kernels
Status
i can confirm that the kernel linked by randomdave above works
perfectly.
so there is your working kernel, bisect away.
(can also confirm the 5.15 kernel still has the bug, every ubuntu kernel
since 5.11 has the bug, apart from the unofficial one linked by
randomdave 2 replies above.)
--
You
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539348/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539347/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539346/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539352/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539344/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539350/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539351/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539349/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539354/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539345/+files/Lsusb.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/1950389
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539355/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539342/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539343/+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/1950389
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539353/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539341/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1950389/+attachment/5539340/+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/1950389
apport information
** Tags added: apport-collected
** Description changed:
In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update.
For example, if you press Fn+F3 it's the same as pressing F3.
That was the update (from the /var/log/apt/history.log file):
Tests are now passing.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
--
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/192
Title:
test_utils_testsuite from
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 1950389
and then change the status of the bug to 'Confirmed'.
If, due to the
Does this fix also work for Impish Indri (21.10) because I noticed the
same issue but I was not able to fix the issue by manually changing the
line within /usr/share/initramfs-tools/scripts/zfs.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: "The result of executing `dmidecode -t system`"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+attachment/5539317/+files/dmidecode.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Attachment added: "The result of executing `dmesg`"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+attachment/5539316/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
$ lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
$ apt-cache policy linux-image-generic-hwe-20.04
linux-image-generic-hwe-20.04:
Instalados: 5.11.0.40.44~20.04.18
Candidato: 5.11.0.40.44~20.04.18
Tabla de versión:
*** 5.11.0.40.44~20.04.18 500
500
Public bug reported:
In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update.
For example, if you press Fn+F3 it's the same as pressing F3.
That was the update (from the /var/log/apt/history.log file):
Start-Date: 2021-11-09 19:14:19
Commandline: apt full-upgrade
Install:
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
The issue seems to have been resolved for me with 5.13.0-7620, while it
was still broken with 5.13.0-7614. I realize these are System76 specific
kernels, but maybe the trend is the same for the corresponding 5.13.0-20
and 5.13.0-14.
--
You received this bug notification because you are a member
** Changed in: amd
Status: Fix Committed => 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/1941893
Title:
Improve performance and idle power consumption
** Changed in: amd
Status: Fix Committed => 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/1945361
Title:
[Yellow Carp] USB4 interdomain communication
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre
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 1950381
and then change the status of the bug to 'Confirmed'.
If, due to the
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre
Public bug reported:
Since Landlock[1] is enabled in ubuntu 5.13 kernels[2], I wonder if it
should be added to CONFIG_LSM[3] so that the feature is usable without
having to override the lsm parameter on the kernel command line (and
reboot).
Upstream seems to have it enabled since it was merged
All autopkgtests for the newly accepted linux-meta (5.11.0.41.42) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
sysdig/0.27.1-0.2 (armhf)
systemd/247.3-3ubuntu3.6 (armhf)
Please visit the excuses page listed below and
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1947453
Title:
[amdgpu] wayland black screen with white flashes,
resolved with latest proposed kernel - 5.13.0.22.33
--
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/1947453
Title:
[amdgpu] wayland black screen with white flashes, display corruption,
All autopkgtests for the newly accepted linux-meta (5.13.0.22.33) for impish
have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/248.3-1ubuntu8 (ppc64el)
diffoscope/180 (armhf)
Please visit the excuses page listed below and investigate
Just upgraded my Lenovo L13 Yoga machine to Ubuntu 21.10. Affected by
the same bug, had to revert to kernel 5.11.
--
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/1945590
Title:
Thinkpad
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
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/1947164
Title:
ebpf: bpf_redirect fails with ip6
All autopkgtests for the newly accepted linux-meta (4.15.0.163.152) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/237-3ubuntu10.52 (armhf)
Please visit the excuses page listed below and investigate the failures,
I'm not sure it's relevant but I'm already on (K)ubuntu 21.10, kernel
5.13.0.20 and the problem is still there. Unless you are looking
specifically for feedback from HWE kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I'm experiencing the problem on radeon driver too. Only way to run
without any error is setting power_dpm_state to "battery" (or setting
power_dpm_force_performance_level to "low").
It gives gpu fault error:
[ 173.274091] radeon :01:00.0: WB enabled
[ 173.274093] radeon :01:00.0: fence
** 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/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre
Public bug reported:
Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on
20.04, I found that my screen won't work if my laptop goes idle (screen
off) or wakes up from suspend. Reverting to 5.11 resolves this for me.
This seems to be a common issue across many distributions and
The kernel Chris Chiu compiled here:
https://people.canonical.com/~mschiu77/lp1941773/I/
works with my Lenovo ThinkPad E15 Gen 2, AMD Ryzen 7 4700u with radeon graphics
× 8 (AMD Renoir graphic).
In another thread (https://www.mail-archive.com/ubuntu-
b...@lists.ubuntu.com/msg5949850.html)
Kernel panic still happening in linux-image-5.13.0-21-generic.
--
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/1945531
Title:
kernel panic at boot
Status in Ubuntu MATE:
Confirmed
Public bug reported:
[SRU Justification]
[Impact]
Microsoft has asked to backport cifs patches up through v5.15-rc3 from
git://git.samba.org/sfrench/cifs-2.6.git 5.11-backport. Two patches have
been added since the original request (LP: #1947027).
[Test Case]
Connect to a SAMBA server
[Where
Same here, no change with Kernel 5.15 (Lenovo ThinkPad E15 Gen 2, AMD Ryzen 7
4700u with radeon graphics × 8 (AMD Renoir graphic)).
@Andrea I might not send my hardware, but is there any other information I can
give that might help to identify the error?
--
You received this bug notification
** Also affects: linux-meta-azure (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Hirsute)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Also affects:
@aseligmann
Backporting sounds like too much effort for now indeed. At least it is good to
know that I'm not the only one experiencing these issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu.
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux-aws (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.
This bug is awaiting verification that the linux/5.13.0-22.22 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,
This bug is awaiting verification that the linux/5.11.0-41.45 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-hirsute' to 'verification-done-hirsute'. If the
problem still exists,
SRU request submitted to the Ubuntu kernel team mailing list for impish,
hirsute and focal:
https://lists.ubuntu.com/archives/kernel-team/2021-November/thread.html#125581
Changing status to 'In Progress' for impish, hirsute and focal.
** Changed in: linux (Ubuntu Impish)
Status: New => In
This bug is awaiting verification that the linux/4.15.0-163.171 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 still exists,
This bug is awaiting verification that the linux/5.4.0-91.102 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, change
This bug is awaiting verification that the linux/4.15.0-163.171 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 still exists,
This bug is awaiting verification that the linux/5.4.0-91.102 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, change
This bug is awaiting verification that the linux/5.13.0-22.22 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,
This bug is awaiting verification that the linux/5.4.0-91.102 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, change
This bug is awaiting verification that the linux/4.15.0-163.171 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 still exists,
This bug is awaiting verification that the linux/5.11.0-41.45 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-hirsute' to 'verification-done-hirsute'. If the
problem still exists,
This bug is awaiting verification that the linux/4.15.0-163.171 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 still exists,
This bug is awaiting verification that the linux/5.11.0-41.45 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-hirsute' to 'verification-done-hirsute'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-22.22 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,
This bug is awaiting verification that the linux/4.15.0-163.171 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 still exists,
This bug is awaiting verification that the linux/5.13.0-22.22 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,
This bug is awaiting verification that the linux/5.4.0-91.102 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, change
This bug is awaiting verification that the linux/5.4.0-91.102 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, change
This bug is awaiting verification that the linux/5.11.0-41.45 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-hirsute' to 'verification-done-hirsute'. If the
problem still exists,
This bug is awaiting verification that the linux/5.11.0-41.45 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-hirsute' to 'verification-done-hirsute'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-22.22 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,
This bug is awaiting verification that the linux/5.11.0-41.45 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-hirsute' to 'verification-done-hirsute'. If the
problem still exists,
This bug is awaiting verification that the linux/4.15.0-163.171 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 still exists,
This bug is awaiting verification that the linux/4.15.0-163.171 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 still exists,
This bug is awaiting verification that the linux/4.15.0-163.171 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 still exists,
This bug is awaiting verification that the linux/4.15.0-163.171 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 still exists,
This bug is awaiting verification that the linux/5.4.0-91.102 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, change
1 - 100 of 163 matches
Mail list logo
