For those using mirror mode, bug 2051074 might finally provide an
explanation.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/1968040
Title:
[i915] Blanked screen doesn't wake
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
** Package changed: linux-signed (Ubuntu) => slurm-wlm (Ubuntu)
** Changed in: slurm-wlm (Ubuntu)
Status: Confirmed => Invalid
** Summary changed:
- cgroup2 broken since 5.15.0-90-generic?
+ load_ebpf_prog() fails for long bpf() logs
--
You received this bug notification because you
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1021.21 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1021.21 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-nvidia-tegra' to
All autopkgtests for the newly accepted linux-meta-oracle (5.4.0.1117.110) 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 the failures,
Okay, this is caused by
commit 9c67dde401ea0ceb0c159428d0775948108343fb (HEAD)
Author: Lionel Landwerlin
Date: Tue May 23 10:00:20 2023 +0300
intel: reduce minimum memory alignment on Gfx12.5
as we're missing kernel support for it in oem 6.1:
commit
** Description changed:
+ [Impact]
+
+ OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
+ (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
+ gpu on boot, causing a blank screen with no GDM running (with wayland,
+ and fallback to X failed too).
+
+
** Summary changed:
- Firefox/brave browser causes GPU reset
+ Firefox/brave browser causes GPU reset and Gnome-shell crash
--
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/2045584
Title:
Public bug reported:
We observed a kernel trace on a KVM hypervisor servers during live
migrating an instance:
```
[...]
Jan 23 10:58:53 fra-az1-comp-22 kernel: [ cut here ]
Jan 23 10:58:53 fra-az1-comp-22 kernel: WARNING: CPU: 75 PID: 1082578 at
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-kvm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
** Description changed:
[Impact]
OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
(gfx12.5). Mesa 23.2 started using that, so it broke initializing the
gpu on boot, causing a blank screen with no GDM running (with wayland,
and fallback to X failed too).
Public bug reported:
A few hours after upgrading a machine serving as VM hypervisor running
OpenStack Nova + libvirt from linux kernel 6.2.0-37-generic to
6.5.0-14-generic we observed kernel traces and quick disintegration of
the system and its various processes.
While the TCP connection itself
In Noble we have to wait for 2.5.6 because of:
https://github.com/intel/thermal_daemon/issues/428
** Bug watch added: github.com/intel/thermal_daemon/issues #428
https://github.com/intel/thermal_daemon/issues/428
--
You received this bug notification because you are a member of Kernel
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1021.21 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1021.21 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1021.21 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-nvidia-tegra' to
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mesa (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.1 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.1 (Ubuntu)
This is a big issue as its a crash and I was wondering how to get it
prioritized as no one seems to be looking at it. I am new to this so I
just wanted to understand how to get some attention.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
So turns out this is not a kernel bug after all. As @hedrick mentioned
it is indeed related to the bpf logs. I suppose kernel 5.15 just
produces longer logs here than the newer kernels.
Here is the original bug report for Slurm
https://bugs.schedmd.com/show_bug.cgi?id=17210 that includes a patch.
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1021.21 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-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1008.8 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-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1008.8 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-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1021.21 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-nvidia-tegra' to
On Noble, i just got a new thermald package : 2.5.5-1
and after a reboot, the log now is:
journalctl -b | grep thermald
janv. 24 10:22:54 ub64 systemd[1]: Starting thermald.service - Thermal Daemon
Service...
janv. 24 10:22:54 ub64 thermald[990]: 24 CPUID levels; family:model:stepping
Hi Michael,
There were actually 2 issues reported in this bug
1.duplicate dax id devices
2.CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=y
1st issue is got resolved, and 2nd issue you have mentioned in Bugzilla
is no longer disabled.
To reconfigure dax-devices we have to make offline/disable online
*** This bug is a duplicate of bug 1950878 ***
https://bugs.launchpad.net/bugs/1950878
** This bug has been marked a duplicate of bug 1950878
Enable ptp_kvm module for time synchronization
--
You received this bug notification because you are a member of Kernel
Packages, which is
no need to land the dkms in jammy
** Package changed: Ubuntu Noble => usbio-drivers (Ubuntu Noble)
** Changed in: usbio-drivers (Ubuntu Noble)
Status: In Progress => Fix Released
** Changed in: usbio-drivers (Ubuntu Jammy)
Status: Confirmed => Invalid
--
You received this bug
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug exists on Kubuntu 23.10 as well,
and,
Fix:
Run `sudo apt install dptfxtract`
... DOES work,
on it as well.
Kernel: 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in
I started having this problem today. I'm not on ubuntu I'm on suse tumbleweed.
I'm posting this here because it was the 1st google hit and it might help
someone. I can reproduce this problem.
I have an LG Xboom external bluetooth speaker. My magic trackpad will stop
responding when the speaker is
Here is a comparison of the network captures between an Ubuntu Server
23.10 client and Ubuntu Server 22.04.3 LTS client. The difference noted
is consistent with when the bug reproduces - that is, Windows 10, Ubuntu
Server 23.10, and latest arch all have the SetInfo by itself and the bug
does not
Hi, we are using the generic kernel - we recently tested the
5.15.0.94-generic. Is it the linux-ibm-gt-fips relevant in our case?
--
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/2045385
This bug was fixed in the package nvidia-graphics-drivers-525-server -
525.147.05-0ubuntu2
---
nvidia-graphics-drivers-525-server (525.147.05-0ubuntu2) noble; urgency=medium
* End of support for 525 series, transition to 535. LP: #2049635
-- Dimitri John Ledkov Tue, 23 Jan 2024
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Jammy)
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.
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: High => Medium
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
**
# VERIFICATION JAMMY
This verification is using a jammy 5.15.0-1055 kernel on a focal machine.
To reproduce this issue a special azure instance is required and currently I
have access to a focal vm.
root@jo-twosla:/home/ubuntu# uname -rv
5.15.0-1055-azure #63~20.04.1-Ubuntu SMP Thu Jan 18
Update:
This appears to be linked to the Night Light.
When Night Light is off:
• The brightness stays at whatever I set it to with xrandr. But, the
computer still boots at 100% brightness, and missing the brightness
controls.
When Night Light is on:
• The brightness resets to 100% every 60
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
** Changed in: linux (Ubuntu Jammy)
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.launchpad.net/bugs/2050044
Title:
Jammy update: v5.15.141 upstream stable
Skipped "io_uring/fdinfo: lock SQ thread while retrieving thread
cpu/pid" as it is already applied as CVE-2023-46862 (cross-checked both
patches look identical).
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-46862
** Changed in: linux (Ubuntu Jammy)
Status: In Progress
** Changed in: linux (Ubuntu Jammy)
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.launchpad.net/bugs/2050849
Title:
Jammy update: v5.15.142 upstream stable
Hi, we are using the generic kernel - we recently tested the
5.15.0.94-generic. Is it the linux-ibm-gt-fips relevant in our case?
--
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/2045387
** Changed in: linux (Ubuntu Jammy)
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.launchpad.net/bugs/2036239
Title:
Intel E810-XXV - NETDEV WATCHDOG: (ice):
Hi, we are using the generic kernel - we recently tested the
5.15.0.94-generic. Is it the linux-ibm-gt-fips relevant in our case?
--
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/2045386
Public bug reported:
Il m'est impossible d'installer le package nvidia-driver-390
390.157-0ubuntu0.22.04.2
Code retour: Failed to install/upgrade: problèmes de dépendances - laissé non
configuré
Je rencontre désormais un problème d'affichage de l'écran
Cette erreur me bloque donc d'autres
** Changed in: netplan.io (Ubuntu Noble)
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/2049924
Title:
WireGuard broken on Noble ppc64el
Status in The
So I've got more investigation results. I no longer think it is the Last
Access difference that is relevant, but rather differences in the SMB
request pattern from the client that triggers buggy server behavior.
First, the updated results:
1. To reproduce, The file must be non-empty. The issue
@Luca
You can ignore the message about testing linux-ibm-gt-fips.
--
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/2045387
Title:
Add ODM driver f81604 usb-can
Status in HWE Next:
New
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1048.56+fips1 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-gcp-fips' to
@anthonywang, what about linux-intel-iotg?
--
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/2045387
Title:
Add ODM driver f81604 usb-can
Status in HWE Next:
New
Status in linux package
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
According to Dell DM's comment, ODM has done the validation with this proposed
linux-firmware package. Please kindly refer to the attachment and below, thanks.
-
Hi Michael,
ODM has done the validation with this proposed linux-firmware package.
Top on the x88 manifest, and via online update
** Tags added: originate-from-2051090
** Tags added: originate-from-2051089
--
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/2046504
Title:
Fix AMDGPU display on lower resolution
verified l-f/jammy-proposed version 20220329.git681281e4-0ubuntu3.25,
mantic-proposed version 20230919.git3672ccab-0ubuntu2.6.
** Tags added: verification-done-jammy verification-done-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Lunar kernel reaches EOL, so set "won't fix" for L kernel.
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
** Changed in: linux-gcp (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-gcp (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
** Changed in: linux-gcp (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-gcp (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
crash log attached
** Attachment added: "nvidia-kernel-source-390.0.crash"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5742049/+files/nvidia-kernel-source-390.0.crash
--
You received this bug notification because you are a member of Kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2019869
Title:
nvidia-dkms-390: better support for kernel 6.2
Status in nvidia-graphics-drivers-390 package in
does not install 22.04 kernel 6.5.0-14-generic
make.log attatched
** Attachment added: "make.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5742048/+files/make.log
--
You received this bug notification because you are a member of Kernel
** Merge proposal linked:
https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-rootfs/+merge/459380
--
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/2045586
Title:
Here's my workaround then https://code.launchpad.net/~mwhudson/livecd-
rootfs/+git/livecd-rootfs/+merge/459380
--
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/2045586
Title:
I have mt7921e with ASIC revision 79220010. For me in addition to mDNS /
IPv6 no longer working I was also unable to see Wi-Fi 5 GHz networks in
the U-NII-2A band.
A similar fix applies here, I upgraded my firmware to the files from the
following commits:
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1013.14
---
linux-oem-6.5 (6.5.0-1013.14) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1013.14 -proposed tracker (LP: #2049407)
* Mute/mic LEDs no function on HP ZBook (LP: #2048729)
- ALSA: hda/realtek: fix
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1013.14
---
linux-oem-6.5 (6.5.0-1013.14) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1013.14 -proposed tracker (LP: #2049407)
* Mute/mic LEDs no function on HP ZBook (LP: #2048729)
- ALSA: hda/realtek: fix
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1013.14
---
linux-oem-6.5 (6.5.0-1013.14) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1013.14 -proposed tracker (LP: #2049407)
* Mute/mic LEDs no function on HP ZBook (LP: #2048729)
- ALSA: hda/realtek: fix
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1013.14
---
linux-oem-6.5 (6.5.0-1013.14) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1013.14 -proposed tracker (LP: #2049407)
* Mute/mic LEDs no function on HP ZBook (LP: #2048729)
- ALSA: hda/realtek: fix
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1013.14
---
linux-oem-6.5 (6.5.0-1013.14) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1013.14 -proposed tracker (LP: #2049407)
* Mute/mic LEDs no function on HP ZBook (LP: #2048729)
- ALSA: hda/realtek: fix
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1013.14
---
linux-oem-6.5 (6.5.0-1013.14) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1013.14 -proposed tracker (LP: #2049407)
* Mute/mic LEDs no function on HP ZBook (LP: #2048729)
- ALSA: hda/realtek: fix
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1013.14
---
linux-oem-6.5 (6.5.0-1013.14) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1013.14 -proposed tracker (LP: #2049407)
* Mute/mic LEDs no function on HP ZBook (LP: #2048729)
- ALSA: hda/realtek: fix
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1013.14
---
linux-oem-6.5 (6.5.0-1013.14) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1013.14 -proposed tracker (LP: #2049407)
* Mute/mic LEDs no function on HP ZBook (LP: #2048729)
- ALSA: hda/realtek: fix
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1013.14
---
linux-oem-6.5 (6.5.0-1013.14) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1013.14 -proposed tracker (LP: #2049407)
* Mute/mic LEDs no function on HP ZBook (LP: #2048729)
- ALSA: hda/realtek: fix
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1013.14
---
linux-oem-6.5 (6.5.0-1013.14) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1013.14 -proposed tracker (LP: #2049407)
* Mute/mic LEDs no function on HP ZBook (LP: #2048729)
- ALSA: hda/realtek: fix
Public bug reported:
[ Impact ]
* The Ubuntu.md has incorrect Ubuntu release and kernel version
information which may impact any tools that use this information to
determine the Ubuntu release.
[ Test Plan ]
* cat Ubuntu.md and check to make sure it is correct
[ Where problems could occur ]
I tracked this down to a bunch of edge-cases in Fujitsu's UEFI
implementation, the Linux kernel, and efibootmgr.
The method of restoring access by doing a CMOS-reset (shorting the
CL1_CL2 test point) and flashing the BIOS [1] was already known, but I
also created a tool [2] that is supposed to
I tracked this down to a bunch of edge-cases in Fujitsu's UEFI
implementation, the Linux kernel, and efibootmgr.
The method of restoring access by doing a CMOS-reset (shorting the
CL1_CL2 test point) and flashing the BIOS [1] was already known, but I
also created a tool [2] that is supposed to
I tracked this down to a bunch of edge-cases in Fujitsu's UEFI
implementation, the Linux kernel, and efibootmgr.
The method of restoring access by doing a CMOS-reset (shorting the
CL1_CL2 test point) and flashing the BIOS [1] was already known, but I
also created a tool [2] that is supposed to
** Summary changed:
- Ubuntu.md in Mantic is out of date
+ Update Ubuntu.md
** Description changed:
[ Impact ]
- * The Ubuntu.md has incorrect Ubuntu release and kernel version
+ * The Ubuntu.md has incorrect Ubuntu release and kernel version
information which may impact any tools that
Public bug reported:
Just got a system notification after installing the regular update.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-kernel-common-545 545.23.08-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
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/2049927
** Changed in: fabric-manager-450 (Ubuntu)
Status: New => Invalid
** Changed in: fabric-manager-470 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
** Changed in: fabric-manager-525 (Ubuntu)
Status: New => Fix Released
** Changed in: libnvidia-nscq-450 (Ubuntu)
Status: New => Invalid
** Changed in: libnvidia-nscq-470 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
Best lead I have is that when this happens, top shows
kworker/u64:78-events_unbound as the CPU hog during the event.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe in Ubuntu.
https://bugs.launchpad.net/bugs/2048924
Title:
This bug was fixed in the package livecd-rootfs - 24.04.21
---
livecd-rootfs (24.04.21) noble; urgency=medium
* live-build/functions: avoid losetup -P as it appears to race with udev and
do it a bit more by-hand instead. (LP: #2045586)
-- Michael Hudson-Doyle Thu, 25 Jan
Possibly related to bug 2011575 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6470
** Tags added: amdgpu cursor
** Summary changed:
- Distorted mouse poitner in the remote window
+ [amdgpu] Distorted mouse pointer in the remote window
** Bug watch added:
1 - 100 of 115 matches
Mail list logo
