I have the same problem on Slackware64 15.0 with 6.7.2
Also see
https://gitlab.freedesktop.org/drm/intel/-/issues/4458#note_2273700
** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4458
https://gitlab.freedesktop.org/drm/intel/-/issues/4458
--
You received this bug
Hi Roxana,
Do We get the kernel source tree link where we can check our included
patches for confirmation?
--
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/2045233
Title:
You have an unsupported DKMS module installed. Please remove it:
$ dkms remove nvidia/390.157
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Error! Bad return status for module build on kernel: 6.5.0-17-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.157/build/make.log for more information.
dkms autoinstall on 6.5.0-17-generic/x86_64 failed for nvidia(10)
Error! One or more modules failed to install during autoinstall.
Refer to
*** This bug is a duplicate of bug 2048183 ***
https://bugs.launchpad.net/bugs/2048183
Uninstall linux-laptop-tools-common. You should not install any of the
linux-laptop packages unless you're on a Lenovo X13s arm64 laptop.
** This bug has been marked a duplicate of bug 2048183
Don't
Might be related? On first attempt in the updater GUI in Ubuntu 23.10
(latest STS stable version), I got
linux-image-nvidia-6.5.0-17-generic: constructing .ko files
./BUILD: 10: make: not found
./BUILD: 11: make: not found
./BUILD: 12: make: not found
./BUILD: 13: make: not found
./BUILD: 14:
Private bug reported:
This below patch needs to be part of the Ubuntu 24.04 and other OS
versions which supports Intel Sierra Forrest and Granite Rapids Server
Processors.
When both CONFIG_RAS_CEC and CONFIG_ACPI_EXTLOG are enabled, Linux does
not clear the status word of the BIOS supplied error
All autopkgtests for the newly accepted linux-meta-azure-5.15
(5.15.0.1056.64~20.04.45) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/245.4-4ubuntu3.23 (arm64)
Please visit the excuses page listed below and investigate
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-18.18~22.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-jammy-linux-
hwe-6.5' to
** Attachment added: "Information from 6.2.0.33 kernel"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2052676/+attachment/5745180/+files/output-6.2.0-33-generic.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "Information from 6.5.0.17 kernel"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2052676/+attachment/5745179/+files/output-6.5.0-17-generic.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
IPv6 SLAAC using 6.5.0.17-generic does not work, running on Linux mint
6.3 Edge. This problem was also seen on kernel 6.5.0.15 and 6.5.0.14
generic kernels.
The same system running on 6.2.0.33-generic works without any issues.
** Affects: linux-signed-hwe-6.5 (Ubuntu)
Hi Andrea,
I'm having some trouble with this bug, particularly on jammy-hwe.
You see, is_rust_module.sh seems to have returned again.
I see you removed it in 4f2dbd4037a697c6d96eb3d8867253e2c8d6f8d0 (ubuntu-mantic)
but if you look at 0eec6d2a63d86ac94dc8fa7c56820a0972ccbe1f (ubuntu-mantic),
Do we have any updates when we will see this released for Ubuntu 22.04?
We are seeing an increase in inquires.
--
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/2049220
Title:
Integrated laptop screen is now detected and functions since upgrading
to kernel and hwe 6.5.0-17.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2050103
Title:
Integrated
I identified a similar bug today when installing nvidia-
fabricmanager-535 on a noble dev build for arm64 that may be related:
https://bugs.launchpad.net/ubuntu/+source/fabric-
manager-535/+bug/2052663
--
You received this bug notification because you are a member of Kernel
Packages, which is
Changed status to 'Fix Released' as multiple reports have been made that
this issue no longer occurs on kernel 6.5.0-17-generic.
** Changed in: linux-meta-hwe-6.5 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages,
All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1056.52) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
digimend-dkms/10-4 (amd64, arm64)
Please visit the excuses page listed below and investigate the failures,
** Summary changed:
- smb1: wsize blocks of bytes followed with binary zeros on copy, destroying
data
+ smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Confirming that this is also fixed for me in 6.5.0-17-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048935
Title:
Right speaker broken on Dell XPS 13 Plus 9320
AFAIKT this bug is resolved in 6.5.0-17-generic, thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048701
Title:
[i915] Screen freeze, kernel crash
Status in
Hi, we are using the generic kernel. Are
linux-bluefield/5.15.0-1035.37
linux-raspi/5.15.0-1046.49
linux-azure/5.15.0-1056.64
relevant in our case?
** Changed in: linux (Ubuntu)
Status: Confirmed => Opinion
** Changed in: linux (Ubuntu)
Status: Opinion => Confirmed
** Changed
Hi, we are using the generic kernel. Are
linux-bluefield/5.15.0-1035.37
linux-raspi/5.15.0-1046.49
linux-azure/5.15.0-1056.64
relevant in our case?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi, we are using the generic kernel. Are
linux-bluefield/5.15.0-1035.37
linux-raspi/5.15.0-1046.49
linux-azure/5.15.0-1056.64
relevant in our case?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
/20240207.1/noble-live-server-arm64+largemem.iso)
Ubuntu Noble Numbat (development branch) (GNU/Linux 6.6.0-14-generic aarch64)
(iso link:
https://cdimage.ubuntu.com/ubuntu-server/daily-live/20240207/noble-live-server-arm64.iso)
CPU/GPU: Nvidia Grace/Hopper
lsb_release -rd:
No LSB modules
Public bug reported:
Impact:
In AppArmor mediation, detached mounts are appearing as / when
applying mount mediation, which is incorrect and leads to bad
AppArmor policy being generated.
In addition, the move_mount mediation is not being advertised to
userspace, which denies the applications
Affecting my Lenovo P15(20YQ-003WUS) also. Very similar errors logged by
the kernel.(available if you need them)
09:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz
(rev 1a)
09:00.0 0280: 8086:2725 (rev 1a)
--
You received this bug notification because you are a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta-hwe-6.5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
after turning OFF all HW features of the LANIC.
only CRC calculation remains in the LANIC.
I have not seen the effect in wireshark again.
I assume the LANIC was adding TCP segments together.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Issue confirmed on 5.4.0-170.
** Attachment added: "20240207_103433.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5745140/+files/20240207_103433.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Same with Linux 6.5.0-17-generic kernel update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049242
Title:
CIFS Mounts Keep Load Average at n+1
Status in
I experienced the same behaviour on
Operating System: Ubuntu 23.10
Kernel: Linux 6.5.0-15-generic
Architecture: x86-64 (Intel N100 4CPU)
And the following mount options:
///paperless /share/smb/paperless cifs
credentials=/root/.smbcredentials,multichannel,iocharset=utf8 0 0
Fixed for me with new kernel Ubuntu 22.04
Linux XPS-9320 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan
16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5
After more research (including getting different symptoms with kernel
6.8-rc3), this appears to be the amdgpu scatter/gather bug:
https://community.frame.work/t/responded-screen-flashing-partially-
white-on-framework-13-amd-ubuntu-22-04/40626/2
I've applied the `amdgpu.sg_display=0` kernel
This is s390x-specific only and does not affect gcp.
Hence I'm adjusting the tag to potentially unblock the process.
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: verification-done
--
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/2048919
Title:
[UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
anymore
Status in
This is s390x specific only and does not impact gcp.
--
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/2048919
Title:
[UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
Attached: a photograph of the displays after exiting display sleep but
before unlocking. If it's relevant, the affected display is attached to
the front right port of an AMD Framework laptop (USB 3.2 gen 2) using a
device recognised by lsusb as `Bus 001 Device 002: ID 0bda:5442 Realtek
This occurred after a fresh reboot this morning, after letting my
displays go to sleep for ~5 minutes. dmesg log also attached. The
IO_PAGE_FAULT entries begin shortly after moving my mouse to turn the
displays back on.
** Attachment added: "dmesg log after getting this issue."
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
>From LP: #2052632
log_check/kernel_tainted tests will fail on AmpereOne based machines
like c3a-standard-4 for focal:linux 5.4.0-168.186 and newer.
The warning was introduced with upstream commit
f41cab7a4653 arm64: Add AMPERE1 to the Spectre-BHB affected list
that came with upstream stable
Public bug reported:
Erreur lors des mises a jour. semble concerner les drivers Nvidia.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-17-generic 6.5.0-17.17
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion:
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug was fixed in the package nvidia-graphics-drivers-545 -
545.29.06-0ubuntu5
---
nvidia-graphics-drivers-545 (545.29.06-0ubuntu5) noble; urgency=medium
*
debian/dkms_nvidia/patches/buildfix_kernel_6.8-nv_drm_ioctls-DRM_UNLOCKED-is-now-the-default-behavi.patch,
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
l-f landed in noble
** Changed in: linux-firmware (Ubuntu Noble)
Status: In Progress => Fix Released
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in
l-f landed in noble
** Changed in: linux-firmware (Ubuntu Noble)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049758
Title:
DP
This bug is awaiting verification that the linux-raspi/5.4.0-1102.114
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-raspi' to 'verification-done-focal-
linux-raspi'. If
This bug was fixed in the package nvidia-graphics-drivers-470 -
470.223.02-0ubuntu2
---
nvidia-graphics-drivers-470 (470.223.02-0ubuntu2) noble; urgency=medium
*
debian/dkms_nvidia/patches/buildfix_kernel_6.8-nv_drm_ioctls-DRM_UNLOCKED-is-now-the-default-behavi.patch,
This bug is awaiting verification that the linux-raspi/5.4.0-1102.114
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-raspi' to 'verification-done-focal-
linux-raspi'. If
Public bug reported:
Please add the following packages to i386 seed:
- nvidia-graphics-drivers-550-server
The other one:
- nvidia-graphics-drivers-550 is already included.
such that beta driver can be packaged and built for i386.
** Affects: nvidia-graphics-drivers-535-server (Ubuntu)
linux-oem-22.04d 6.5.0.1013.15 in jammy-updates contains the fix.
https://changelogs.ubuntu.com/changelogs/pool/main/l/linux-
oem-6.5/linux-oem-6.5_6.5.0-1013.14/changelog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 2047389 ***
https://bugs.launchpad.net/bugs/2047389
linux-oem-22.04d 6.5.0.1013.15 in jammy-updates contains the fix.
https://changelogs.ubuntu.com/changelogs/pool/main/l/linux-
oem-6.5/linux-oem-6.5_6.5.0-1013.14/changelog
--
You received this bug
This bug is awaiting verification that the linux-raspi/5.4.0-1102.114
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-raspi' to 'verification-done-focal-
linux-raspi'. If
kernel 6.5.0-17-generic has just arrived in 23.10 (Mantic) and that
seems to clear the issue.
mount/unmount an external btrfs filesystem no longer produces the
messages.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in
This bug is awaiting verification that the linux-raspi/5.4.0-1102.114
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-raspi' to 'verification-done-focal-
linux-raspi'. If
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49
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-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug was fixed in the package linux - 5.4.0-171.189
---
linux (5.4.0-171.189) focal; urgency=medium
* focal/linux: 5.4.0-171.189 -proposed tracker (LP: #2048282)
* Packaging resync (LP: #1786013)
- [Packaging] remove helper scripts
- [Packaging] update annotations
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-bluefield' to
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49
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-raspi' to 'verification-done-jammy-
linux-raspi'. If
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
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-bluefield' to
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33
---
linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966)
* Jammy update: v6.1.63 upstream stable release (LP: #2046577)
- Restore "UBUNTU:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33
---
linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966)
* Jammy update: v6.1.63 upstream stable release (LP: #2046577)
- Restore "UBUNTU:
This bug was fixed in the package linux - 5.4.0-171.189
---
linux (5.4.0-171.189) focal; urgency=medium
* focal/linux: 5.4.0-171.189 -proposed tracker (LP: #2048282)
* Packaging resync (LP: #1786013)
- [Packaging] remove helper scripts
- [Packaging] update annotations
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33
---
linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966)
* Jammy update: v6.1.63 upstream stable release (LP: #2046577)
- Restore "UBUNTU:
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-bluefield' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-bluefield' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-bluefield' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-bluefield' to
This bug was fixed in the package linux - 5.4.0-171.189
---
linux (5.4.0-171.189) focal; urgency=medium
* focal/linux: 5.4.0-171.189 -proposed tracker (LP: #2048282)
* Packaging resync (LP: #1786013)
- [Packaging] remove helper scripts
- [Packaging] update annotations
This bug was fixed in the package linux - 5.4.0-171.189
---
linux (5.4.0-171.189) focal; urgency=medium
* focal/linux: 5.4.0-171.189 -proposed tracker (LP: #2048282)
* Packaging resync (LP: #1786013)
- [Packaging] remove helper scripts
- [Packaging] update annotations
This bug is awaiting verification that the linux-oracle/5.4.0-1117.126
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-oracle' to 'verification-done-
focal-linux-oracle'.
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49
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-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49
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-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-bluefield' to
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49
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-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33
---
linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966)
* Jammy update: v6.1.63 upstream stable release (LP: #2046577)
- Restore "UBUNTU:
This bug is awaiting verification that the linux-oracle/5.4.0-1117.126
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-oracle' to 'verification-done-
focal-linux-oracle'.
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33
---
linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966)
* Jammy update: v6.1.63 upstream stable release (LP: #2046577)
- Restore "UBUNTU:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33
---
linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966)
* Jammy update: v6.1.63 upstream stable release (LP: #2046577)
- Restore "UBUNTU:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1033.33
---
linux-oem-6.1 (6.1.0-1033.33) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1033.33 -proposed tracker (LP: #2051966)
* Jammy update: v6.1.63 upstream stable release (LP: #2046577)
- Restore "UBUNTU:
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49
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-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-bluefield' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-bluefield' to
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49
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-raspi' to 'verification-done-jammy-
linux-raspi'. If
1 - 100 of 231 matches
Mail list logo
