This bug is awaiting verification that the linux-nvidia/6.8.0-1028.31
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-noble-linux-nvidia' to 'verification-done-
noble-linux-nvidia'. If
This bug is awaiting verification that the linux-nvidia/6.8.0-1028.31
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-noble-linux-nvidia' to 'verification-done-
noble-linux-nvidia'. If
All autopkgtests for the newly accepted
linux-restricted-modules-lowlatency-hwe-6.8 (6.8.0-60.63.1~22.04.1) for jammy
have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-470/unknown (amd64)
Please visit the excuses page
All autopkgtests for the newly accepted linux-meta-gke (6.8.0-1025.29) for
noble have finished running.
The following regressions have been reported in tests triggered by the package:
dpdk-kmods/unknown (arm64)
fwts/unknown (arm64)
glibc/2.39-0ubuntu8.4 (amd64)
glibc/unknown (arm64)
lxc/unknown (
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.4.0-1146.156) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/unknown (i386)
Please visit the excuses page listed below and invest
All autopkgtests for the newly accepted linux-restricted-modules-azure
(5.4.0-1151.158) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/unknown (amd64, i386)
Please visit the excuses page listed below a
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1129.142~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-linux-
raspi-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1129.142~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-linux-
raspi-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1129.142~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-linux-
raspi-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1129.142~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-linux-
raspi-5.4' to 'verification-done-bionic
All autopkgtests for the newly accepted linux-meta-aws (6.11.0-1014.15) for
oracular have finished running.
The following regressions have been reported in tests triggered by the package:
fwts/unknown (amd64)
glibc/unknown (amd64)
lxc/unknown (amd64, arm64)
snapd/unknown (arm64)
zfs-linux/unknown
This bug is awaiting verification that the linux-gke/6.8.0-1025.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-noble-linux-gke' to 'verification-done-noble-
linux-gke'. If the prob
All autopkgtests for the newly accepted linux-meta-aws (6.8.0-1029.31) for
noble have finished running.
The following regressions have been reported in tests triggered by the package:
dkms/unknown (amd64)
dpdk-kmods/unknown (arm64)
fwts/unknown (amd64, arm64)
glibc/unknown (amd64, arm64)
zfs-linu
Public bug reported:
my wifi card details:
```
root@lap01:~# lspci | grep -i network
:00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi
(rev 01)
root@lap01:~# lspci -n | grep 14.3
:00:14.3 0280: 8086:51f0 (rev 01)
```
modules related:
```
root@lap01:~# lsmod | gre
please ignore rtw88_core in lsmod output.
(it is my working dongle).
--
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/2109375
Title:
Intel Corporation Alder Lake-P PCH CNVi WiFi (
This bug is awaiting verification that the linux-aws/6.8.0-1029.31
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-noble-linux-aws' to 'verification-done-noble-
linux-aws'. If the prob
Public bug reported:
Ν//Α
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.8.0-58-generic 6.8.0-58.60
ProcVersionSignature: Ubuntu 6.8.0-57.59-generic 6.8.12
Uname: Linux 6.8.0-57-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3.5
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Committed => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packa
All autopkgtests for the newly accepted linux-meta (5.15.0.140.135) for jammy
have finished running.
The following regressions have been reported in tests triggered by the package:
acpi-call/unknown (arm64, ppc64el, s390x)
adv-17v35x/unknown (amd64, arm64, ppc64el, s390x)
apparmor/unknown (arm64,
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
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
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
You're welcome, but can you verify that that firmware is actually
working with the 6.14 so I can start the process of adding it to the
linux-firmware package?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https:
The autopkgtests for apt/noble have passed; per the documented test plan
> To validate the APT change on noble, we must rely on the test suite as
we won't have a noble->oracular upgrade bug causing it, most likely.
I am hence setting this to verification-done-noble.
** Tags removed: verification
** Changed in: linux (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Oracular)
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.
https://bugs.lau
** Changed in: linux (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Oracular)
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.
https://bugs.lau
This bug is awaiting verification that the linux/5.15.0-140.150 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' to 'verification-done-jammy-linux'. If
the problem still ex
This bug is awaiting verification that the linux/5.15.0-140.150 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' to 'verification-done-jammy-linux'. If
the problem still ex
This bug is awaiting verification that the linux/5.15.0-140.150 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' to 'verification-done-jammy-linux'. If
the problem still ex
This bug is awaiting verification that the linux/5.15.0-140.150 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' to 'verification-done-jammy-linux'. If
the problem still ex
This bug is awaiting verification that the linux/5.15.0-140.150 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' to 'verification-done-jammy-linux'. If
the problem still ex
** Also affects: nvidia-graphics-drivers-550 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-550 (Ubuntu Plucky)
Status: New => Invalid
** Changed in: nvidia-graphics-drivers-550 (Ubuntu Oracular)
Status: New => Invalid
** Summary changed
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2102663
Title:
nvidia-kernel
** Also affects: nvidia-graphics-drivers-570 (Ubuntu Questing)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-570 in Ubuntu.
https://bugs.launchpad.net/bugs/2107759
Titl
@fuchanglin Intel released firmware for this card but it requires a 6.14
kernel. We'll soon have an HWE 6.14 kernel in Noble. In the meantime, you can
either install the plucky kernel from:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/30614565
or the latest mainl
** Changed in: linux-firmware (Ubuntu)
Status: Expired => Won't Fix
--
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/1638862
Title:
[Dell Latitude E5460] bluetooth is not s
Public bug reported:
Description:
On a laptop with a MediaTek MT7922 Wi-Fi card (driver mt7921e, firmware
00-20240219103337), I cannot obtain a global IPv6 address.
The system sends Router Solicitations (RS), but never receives Router
Advertisements (RA), so IPv6 autoconfiguration (SLAAC
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
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/2106491
78 matches
Mail list logo
