MR for jammy/mantic/noble. The MR contains the required tplg binary and the
patch file.
https://code.launchpad.net/~mschiu77/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/461948
https://code.launchpad.net/~mschiu77/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/461950
*** This bug is a duplicate of bug 2028165 ***
https://bugs.launchpad.net/bugs/2028165
** This bug has been marked a duplicate of bug 2028165
nvidia-dkms-* FTBS with linux 6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage
** Description changed:
[Impact]
- We found some laptops from Dell and HP with Intel MTL platform suffer the
same MIC-Mute led not working problem just like lp:2049569.
+ We found some laptops from Lenovo and HP with Intel MTL platform suffer the
same MIC-Mute led not working problem just
Private bug reported:
On DELL PowerEdge system when Ubuntu 24.04 OS is Installed Observed ACPI
Error: Aborting method \_SB.PMI0._GHL due to previous error
(AE_NOT_EXIST) (20230628/psparse-529) in dmesg logs.
Steps to Reproduce: -
1. Install Ubuntu 24.04 OS.
2. Boot to Ubuntu 24.04 OS and check
Public bug reported:
[Impact]
Headphone mic is lost after resume from S3 or reboot with plugin.
[Fix]
Restore the headphone mic detect logic for ALC897 after lost power.
[Test]
Tested on hardware, the headphone mic appears as plugin after boot or
resume from S3, and works fine.
[Where problems
Private bug reported:
On Dell PowerEdge system when Ubuntu 24.04 OS is Installed observed
"ACPI BIOS Error (bug): Could not resolve symbol [\_SB.SCK3.C165],
AE_NOT_FOUND (20230628/dswload2-162)" in dmesg logs.
Steps to Reproduce: -
1. Install Ubuntu 24.04 OS.
2. Boot to Ubuntu 24.04 OS and
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => Portia Stephens
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
** Tags removed: verification-needed-jammy-linux-oem-6.1
** Tags added: verification-done-jammy-linux-oem-6.1
--
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/2054487
Title:
There
** Information type changed from Public Security to Private Security
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
Random pointers although I'm not sure those are identical to my issue:
https://www.reddit.com/r/archlinux/comments/199am0a/thinkpad_t14_suspend_broken_in_kernel_670/
https://discussion.fedoraproject.org/t/random-resume-after-suspend-issue-on-thinkpad-t14s-amd-gen3-radeon-680m-ryzen-7/103452
--
Multiple suspends in a row worked without an external monitor connected,
but after connecting it the machine failed to suspend/resume.
** Attachment added: "failed_on_suspend_after_connecting_monitor.log"
Public bug reported:
I had a similar issue before:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718
However, I haven't seen the issue with later kernels until getting
6.8.0-11.11+1 recently.
* 6.8.0-11 - fails to suspend/resume for the second time although the first
kernel log when trying suspend/resume twice in a row. The machine got
frozen while the power LED is still on in the second suspend and there
is no second "PM: suspend entry (s2idle)" in the kernel log.
** Attachment added: "failed_on_second_suspend.log"
Public bug reported:
---Problem Description---
Issues with HVCS and hotplugging issues.
When working on Canonical bug 2023243, it was discovered that mkvterm
was not working for multiple reasons. This bug will cover the issues
found in HVCS, and hotplugging issues found when drmgr writes the
You have been subscribed to a public bug:
---Problem Description---
Issues with HVCS and hotplugging issues.
When working on Canonical bug 2023243, it was discovered that mkvterm
was not working for multiple reasons. This bug will cover the issues
found in HVCS, and hotplugging issues found
I can confirm the fix after applying latest firmware!
ISSUE: I was getting intermittent internet dropping (for 5 to 10
seconds) between my MAC OS and my 22.04 Ubuntu server (no lost of
connection from Ubuntu or Mac to internet)
HARDWARE: Motherboard: MSI MPG X670E CARBON WIFI (mt7921e wifi)
*** This bug is a duplicate of bug 2046844 ***
https://bugs.launchpad.net/bugs/2046844
Hi cipricus,
This is a security feature working as intended. Ubuntu recently decided
to disable unprivileged access to user namespaces. You can find more
information it about it here:
Is there a way I can track this issue?
--
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/2052840
Title:
Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed
-62
** Tags removed: verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy-linux-bluefield
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2051871
Title:
** Changed in: shim-signed (Ubuntu Cosmic)
Status: Triaged => Won't Fix
** Changed in: shim-signed (Ubuntu Bionic)
Status: Triaged => Fix Released
** Changed in: linux-signed (Ubuntu Cosmic)
Status: Triaged => Won't Fix
** Changed in: linux-meta (Ubuntu Cosmic)
Public bug reported:
* intro
In bug 2053155 "Add DPLL and syncE support" below:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2053155
It requires using a yaml spec file, dpll.yaml, and a python script, cli.py, to
verify the correctness.
ex:
$ sudo ./tools/net/ynl/cli.py --spec
AFAICT; these initramfs-tools package changes would cover it:
* hooks/framebuffer can be totally removed.
* scripts/init-top/framebuffer should probably stay
* conf/initramfs.conf needs FRAMEBUFFER=y added to it
--
You received this bug notification because you are a member of Kernel
Plymouth only gets added to the initrd when LUKS is enabled or you mark
another reason for needing the framebuffer.
So the suggestion I have from comment #49 is to mark needing the
framebuffer by default, and then stop including any DRM modules because
simpledrm is built into the kernel.
--
You
Public bug reported:
[Impact]
Some improvement are made to qat which makes it
more resilient and able to handle reset in a
better way.
There is an upstream patch set that improve this
but it's applied to linux-next and scheduled for 6.9.
We should apply the patch set to the Noble 6.8 kernel,
It's a bit unclear to me what change we need now to take advantage of
simpledrm? Comment #49 state getting plymouth in the initrd but that should
already be the case today or luks encryption wouldn't be working no?
what change would trigger the include of extra drm modules?
--
You received
There is no 'kernel-package' in Ubuntu 22.04 so moving...
** Package changed: kernel-package (Ubuntu) => linux-meta-hwe-6.5
(Ubuntu)
** Tags added: jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
** Changed in: linux (Ubuntu Noble)
Status: New => 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/2056126
Title:
hwmon: (coretemp) Fix core count limitation
Status
You have been subscribed to a public bug:
This only happens to me when I connect my USB-C docking station to my
laptop. The laptop doesn't really turn off and goes crazy. To solve this
I have seen that disconnecting the battery from the BIOS settings solves
the problem. If I don't do this the
** Description changed:
- All details are to be found in my previous bug report [Tabs of non-
- flatpak Firefox (and non-flatpak Firefox-based browsers) crash in
- Kubuntu
- 24.04](https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190).
+ All details are to be found in my previous bug
Public bug reported:
I can not install the gpu driver without an error.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-390 390.157-0ubuntu0.22.04.2
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
ApportVersion:
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~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
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~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
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~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
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~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
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~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
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~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
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~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
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~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
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~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
This bug was fixed in the package linux-oracle - 6.5.0-1018.18
---
linux-oracle (6.5.0-1018.18) mantic; urgency=medium
* mantic/linux-oracle: 6.5.0-1018.18 -proposed tracker (LP: #2054120)
* Provide an arm64 linux-oracle 64k kernel variant (LP: #2052469)
- [Packaging]
This bug was fixed in the package linux-oracle-6.5 -
6.5.0-1018.18~22.04.1
---
linux-oracle-6.5 (6.5.0-1018.18~22.04.1) jammy; urgency=medium
* jammy/linux-oracle-6.5: 6.5.0-1018.18~22.04.1 -proposed tracker
(LP: #2054122)
[ Ubuntu: 6.5.0-1018.18 ]
* mantic/linux-oracle:
This bug was fixed in the package linux - 5.4.0-173.191
---
linux (5.4.0-173.191) focal; urgency=medium
* focal/linux: 5.4.0-173.191 -proposed tracker (LP: #2052135)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2024.02.05)
This bug was fixed in the package linux - 5.4.0-173.191
---
linux (5.4.0-173.191) focal; urgency=medium
* focal/linux: 5.4.0-173.191 -proposed tracker (LP: #2052135)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2024.02.05)
This bug was fixed in the package linux - 5.4.0-173.191
---
linux (5.4.0-173.191) focal; urgency=medium
* focal/linux: 5.4.0-173.191 -proposed tracker (LP: #2052135)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2024.02.05)
This bug was fixed in the package linux - 5.4.0-173.191
---
linux (5.4.0-173.191) focal; urgency=medium
* focal/linux: 5.4.0-173.191 -proposed tracker (LP: #2052135)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2024.02.05)
This bug was fixed in the package linux - 5.4.0-173.191
---
linux (5.4.0-173.191) focal; urgency=medium
* focal/linux: 5.4.0-173.191 -proposed tracker (LP: #2052135)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2024.02.05)
This bug was fixed in the package linux - 5.4.0-173.191
---
linux (5.4.0-173.191) focal; urgency=medium
* focal/linux: 5.4.0-173.191 -proposed tracker (LP: #2052135)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2024.02.05)
This bug is very old, if it is still an issue please update the bug with
information from a supported release.
** Changed in: kwin (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Package changed: crun (Ubuntu) => linux-meta-hwe-6.5 (Ubuntu)
--
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/2052961
Title:
Error: OCI runtime error: crun: chmod :
You have been subscribed to a public bug:
There appears to be a regression due to a "change in the kernel" in
which, as of "commit 5d1f903f75a80daa4dfb3d84e114ec8ecbf29956 in the
kernel, present in a release since Linux 6.6 doesn't allow anymore to
change the mode of a symlink, so just ignore the
This bug is very old, if it is still an issue please update the bug with
information from a supported release.
** Changed in: kwin (Ubuntu)
Status: Confirmed => Incomplete
** No longer affects: plasma-desktop (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Package changed: ubuntu => linux (Ubuntu)
** Tags added: mantic
--
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/2054456
Title:
Possible regression: Some wireless Logitech devices
buntu 6.5.0-21.21~22.04.1-generic 6.5.8
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+attachment/5753222/+files/version.log
** Description changed:
On one Lenovo machine, using a hwe-22.04 kernel, I get several messages
from UBSAN while
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+attachment/5753221/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
On one Lenovo machine, using a hwe-22.04 kernel, I get several messages
from UBSAN while booting. Previously, on the non-hwe kernel for Jammy,
the screen went black shortly after logging in, and that doesn't seem to
happen any more, so there is improvement, but it seems still
You have been subscribed to a public bug:
I'm on Ubuntu 23.10. Kernel 6.5.0-17-generic.
I believe I am experiencing this bug, which appears to have been fixed
once, some years ago: https://bugzilla.kernel.org/show_bug.cgi?id=208935
Here's what happens in my syslog while pairing my Logitech
Public bug reported:
All details are to be found in my previous bug report [Tabs of non-
flatpak Firefox (and non-flatpak Firefox-based browsers) crash in
Kubuntu
24.04](https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190).
Given that simply reverting to kernel 6.5.0-17-generic fixes
Accidentally changed status whilst examining status list - currently
unable to revert the change!
** 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.
81 matches
Mail list logo
