2.2.6-1ubuntu1.1 works well on Intel RaptorLake DELL SKU 0C11 as 23.10
** Attachment added: "721293778.446208.mp4"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038263/+attachment/5717731/+files/721293778.446208.mp4
--
You received this bug notification because you are a member of
For Noble
** Patch added: "alsa-ucm-conf_1.2.9-1ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5717724/+files/alsa-ucm-conf_1.2.9-1ubuntu4.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is
For Mantic
** Patch added: "alsa-ucm-conf_1.2.9-1ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5717676/+files/alsa-ucm-conf_1.2.9-1ubuntu4.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is
The attachment "alsa-ucm-conf_1.2.6.3-1ubuntu1.9.debdiff" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove
For Lunar
** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu9.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5717628/+files/alsa-ucm-conf_1.2.6.3-1ubuntu9.3.debdiff
--
You received this bug notification because you are a member of Kernel
Packages,
for Jammy
** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu1.9.debdiff"
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5717627/+files/alsa-ucm-conf_1.2.6.3-1ubuntu1.9.debdiff
--
You received this bug notification because you are a member of Kernel
Packages,
I don't use ceph but I'm seeing this spammed across my Ubuntu 23.10
machines. Is it a false alarm then?
--
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/2037214
Title:
This bug is awaiting verification that the linux-gcp/6.5.0-1009.9 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-gcp' to 'verification-done-mantic-
linux-gcp'. If the
This bug is awaiting verification that the linux-gcp/5.4.0-1118.127
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-gcp' to 'verification-done-focal-
linux-gcp'. If the
I have identified the cause of the fio/glusterfs crash and the EXT4-fs
errors: The test procedure runs fio write tests on /dev/sda (which is
in fact the rootfs itself). I modified Phil's launch script to create a
smaller 10GB boot disk for the rootfs but also create a 50GB "junk" disk
(/dev/sdb)
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1007.7
---
linux-oem-6.5 (6.5.0-1007.7) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1007.7 -proposed tracker (LP: #2041654)
* Support speaker mute hotkey for Cirrus CS35L41 HDA codec (LP: #2039151)
- ALSA: hda:
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1007.7
---
linux-oem-6.5 (6.5.0-1007.7) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1007.7 -proposed tracker (LP: #2041654)
* Support speaker mute hotkey for Cirrus CS35L41 HDA codec (LP: #2039151)
- ALSA: hda:
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1007.7
---
linux-oem-6.5 (6.5.0-1007.7) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1007.7 -proposed tracker (LP: #2041654)
* Support speaker mute hotkey for Cirrus CS35L41 HDA codec (LP: #2039151)
- ALSA: hda:
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package mutter - 45.0-3ubuntu3.1
---
mutter (45.0-3ubuntu3.1) mantic; urgency=medium
* Cherry pick 4 commits to fix SIGKILL on lockscreen. (LP: #2034619)
* Drop kms-impl-device-Inhibit-deadline-timer-on-amdgpu.patch
-- Mario Limonciello Thu, 26 Oct
Related But.. and fixed in this
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2042092
Title:
CIFS module is not
Public bug reported:
It is always disconnected, I tried with Shell and Blueman, but both are
not good.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux
installing r8168-dkms seems to better the result, but not completely
solve it.
Suggested here: https://askubuntu.com/q/1488178
Afterwards download is 920 mbit and upload 400 mbit, should be 980/980
mbit.
--
You received this bug notification because you are a member of Kernel
Packages, which
** Summary changed:
- Processor turbo dsiabled/throttled after suspend
+ Processor turbo disabled/throttled after suspend
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1738534
Title:
This bug report has not seen any further follow-up for 2+ years. Closing
it. If it is still not fixed please re-open this issue.
** Changed in: thermald (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
These are the same patches that have been applied to the 5.19 and 6.2
kernels to enable GDS. NVIDIA is requesting they be applied to the 6.5
kernel which is used for Grace enablement.
** Affects: linux-nvidia-6.5 (Ubuntu)
Importance: Undecided
Status: New
--
Same issue here with Thinkpad P13s Gen 2 (AMD) with 23.10 installed just
moments ago
I'm also unable to install the fixes on a fresh installation:
sudo apt install -t mantic-proposed mutter
Reading package lists... Done
E: The value 'mantic-proposed' is invalid for APT::Default-Release as such a
I have switched to Debian and downloaded the latest kernel from
kernel.org. As the current kernel on Debian was 6.1.0-13, I have
selected the 6.1.62 kernel source. I have followed the steps and Quinten
written earlier, except the patching steps as it is not needed anymore
and after installing the
Public bug reported:
Updating from Linux 5.15.0-88-generic to 5.15.0-90-generic breaks
ethernet support.
In my setup, the ethernet port is inside a Thunderbolt Dell WD19TB
docking station.
On 5.15.0-88 the ethernet device works and is shown with ip and on dmesg
logs :
$ sudo dmesg
...
27 [
Public bug reported:
On Ubuntu 22.04.3 LTS (jammy jellyfish) we mount a DFS file service
using CIFS with kerberos authentication. After the kernel upgrade from
5.15.0-86-generic to 5.15.0-88-generic (exact version: 5.15.0-88.98)
this stopped working. The mount seems to have worked, but files and
** Description changed:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2029281
+
+ == firmware-sof ==
+
+ [Impact]
+
+ Missing soundwire firmware support for Intel MTL deivces.
+
+ [Fix]
+
+ Depends on sof-bin v2.7.1 release from
Attach proposed debdiff for Noble. Note while this change actually
contains two binary patches that cannot be renederred correctly by
debdiff, it's also pushed to
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2029281 for further
inspection.
Need sponsor for uploading.
** Patch added:
** Tags added: originate-from-2012814
--
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/2029281
Title:
Soundwire support for Dell SKU0C87 devices
Status in HWE Next:
New
Status
*** This bug is a duplicate of bug 2029281 ***
https://bugs.launchpad.net/bugs/2029281
While the required kernel commits for ALC713 has been in oem-6.5 kernel,
there is no more work to do except firmware-sof SRU that is also a part
of 2029281. Mark as duplicate and move private bug binding
Turn Mantic/Jammy to TRIAGED as there are already revisions in -proposed
pocket. To SRU for Noble first.
** Changed in: firmware-sof (Ubuntu)
Status: Incomplete => In Progress
** Changed in: firmware-sof (Ubuntu Jammy)
Status: Incomplete => Triaged
** Changed in: firmware-sof
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2023201
Title:
Add support of Smart Amplifier IC ALC1319D
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
** Also affects: canonical-kernel-snaps/jammy
Importance: Undecided
Status: New
** Changed in: canonical-kernel-snaps/jammy
Status: New => Fix Committed
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu Jammy)
Status:
yeah, after update kernel everything okay. Thanks!
--
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/2034477
Title:
Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
> I've tried install Fedora 39 from bootable ISO and there are not working
> mouse and keyboard in installation area. Lenovo V15 G4 AMN
This is expected, F39's images use 6.5.6 as kernel and the fixes for
this are only available in 6.5.10 and later.
So you need to either install 6.5.10 for your
I've tried install Fedora 39 from bootable ISO and there are not working
mouse and keyboard in installation area.
Lenovo V15 G4 AMN
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
Need sponsors for Mantic SRU.
--
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/2031412
Title:
Support mipi camera on Intel Meteor Lake platform
Status in HWE Next:
New
Status
Add debdiff for ivsc-driver/mantic since it's landed in Noble already.
This is identical to that in ivsc-driver/noble except for the version
string. It's a version bump, as we need this for linux-oem-6.5 builds
that tracks ivsc-driver/mantic.
** Patch added:
Add debdiff for ipu6-drivers/mantic since it's landed in Noble already.
This is identical to that in ipu6-drivers/noble except for the version
string. It's a version bump, as we need this for linux-oem-6.5 builds
that tracks ipu6-drivers/mantic.
** Patch added: "SRU ipu6-drivers/mantic"
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.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-jammy-linux-xilinx-zynqmp'
to
Public bug reported:
aster: Ubuntu desktop 20.04.6
Device: Advantech ARK-3534
Kernel: 5.15.0-67-generic x86_6
Steps to repro:
1. Execute Checkbox
2. View the Suspend Test
Failure symptom:
Attachments
suspend/1_xrandr_screens_after_suspend.tar.gz_auto
Failure rate:
100%
Note:
When using
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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/2041668
** Changed in: linux-lowlatency (Ubuntu Hirsute)
Status: New => Won't Fix
** Changed in: linux-lowlatency (Ubuntu Groovy)
Status: New => Won't Fix
** Changed in: linux-lowlatency (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are
I can confirm too, i'm just waiting for the latest kernels to show up in
mainline, so i can install them and have them signed. So that virtualbox
will finally worrk too.
It's been an honor to test along you people!!
Happy patching. :)
--
You received this bug notification because you are a
** Tags removed: verification-needed-mantic
** Tags added: verification-done-mantic
--
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/2038263
Title:
Add SoF topology support on
** Tags added: kern-8499
--
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/2042999
Title:
BT/WiFi coex stability issue on RTL8851BE/RTL8852BE
Status in HWE Next:
New
Status in
This bug was fixed in the package linux-gke - 5.15.0-1046.51
---
linux-gke (5.15.0-1046.51) jammy; urgency=medium
* jammy/linux-gke: 5.15.0-1046.51 -proposed tracker (LP: #2038024)
* Kernel configs deviate from generic kernel (LP: #2040120)
- [Configs] Revert configs to
** Description changed:
+ It seems to suspend fine (when closing lid), but when opening lid it
+ tries to startup... LEDs are blinking (as the HDD is activated), after
+ some time it is working hard because the fan starts running faster and
+ faster. No reaction on any keys. Tried the power
69 matches
Mail list logo
