Current /lib/firmware disk usage for different series:
326Mbionic
695Mfocal
914Mjammy
879Mlunar
After replacing duplicates with symlinks:
309Mbionic
663Mfocal
878Mjammy
843Mlunar
Even for Bionic we can shave off almost 20MB, so nominating for all
series.
** Also
** Tags added: kern-6734
--
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/2019072
Title:
600+ duplicate or duplicated firmware files exist.
Status in Linux Firmware:
New
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-oracle (Ubuntu)
** No longer affects: linux-oracle (Ubuntu Jammy)
** No longer affects: linux-oracle (Ubuntu Kinetic)
** No longer affects: linux-oracle (Ubuntu Lunar)
** No longer
Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2936
** Bug watch added: github.com/canonical/cloud-init/issues #2936
https://github.com/canonical/cloud-init/issues/2936
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
Ubuntu frequently fails to boot up, it hangs between GRUB and login
splash screen. I need to force turn off the computer and restart
repeatedly to get it success. Sometimes I need to select older kernel to
succeed, sometimes selecting older kernel doesn't help.
ProblemType:
Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2858
** Bug watch added: github.com/canonical/cloud-init/issues #2858
https://github.com/canonical/cloud-init/issues/2858
--
You received this bug notification because you are a member of Kernel
Packages, which is
All autopkgtests for the newly accepted linux-meta-azure-fde-5.15
(5.15.0.1038.45~20.04.1.17) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
** Tags added: patch
--
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/2019011
Title:
[UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5
driver
Status in linux
Hi, Vineeth.
These packages are for the 20.04 LTS Kernel.
BR,
pprincipeza
--
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/2019011
Title:
[UBUNTU 20.04] [HPS] Kernel panic with
--- Comment From vineeth.vija...@ibm.com 2023-05-10 15:31 EDT---
Hi,
Thank you very much for the quick support.
Is this kernel (5.4.0.149) and the package attached corresponds to 20.04 or
20.04 HWE ?
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672298/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672296/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672297/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672295/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672294/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672293/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672292/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672291/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672290/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672289/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672288/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672287/+files/Lsusb.txt
--
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/2019143
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672286/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672285/+files/Lspci.txt
--
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/2019143
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672283/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672284/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672282/+files/CRDA.txt
--
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/2019143
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/2019143/+attachment/5672281/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected mantic wayland-session
** Description changed:
hallo,
since i upgraded to mantic, i cant start xdg-desktop-portal.service`
systemctl --user status xdg-desktop-portal.service
× xdg-desktop-portal.service - Portal service
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2019143
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
hallo,
since i upgraded to mantic, i cant start xdg-desktop-portal.service`
systemctl --user status xdg-desktop-portal.service
× xdg-desktop-portal.service - Portal service
Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static)
Active: failed
The change requires the backport of one additional patch (both are
provided above).
We created a test kernel with those changes for validation and you can
find the debian packages at
https://people.canonical.com/~mhcerri/lp2019011/s390x_debs.tgz
Please let us know if the test kernel works as
** Patch added:
"0002-net-mlx5-Fix-handling-of-entry-refcount-when-command.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019011/+attachment/5672246/+files/0002-net-mlx5-Fix-handling-of-entry-refcount-when-command.patch
--
You received this bug notification because you are a
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Patch added:
"0001-net-mlx5-cmdif-Avoid-skipping-reclaim-pages-if-FW-is.patch"
This change was made by a bot.
** 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/2019140
Title:
package linux-tools-common
Public bug reported:
ramslab@ramslab:~$ sudo apt-get check
[sudo] password for ramslab:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet
verified that there are no build issues with jammy or kinetic and
everything is building as expected, marking verification-passed
** Tags removed: verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-jammy verification-done-kinetic
--
You received this bug
** Changed in: linux (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: linux (Ubuntu Kinetic)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed => In Progress
** Changed
** Tags added: sru-20230417
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2006716
Title:
5 failures reported in net:fcnal-test.sh on Jammy
Status in ubuntu-kernel-tests:
Public bug reported:
SRU Justification
[Impact]
Intel has introduced support for their new Emerald Rapids CPU.
It was backported to Jammy in #lp2015372 and in #lp2015855.
The remaining feature needed to fully support EMR is PPIN (the Protected
Processor Inventory/Identification Number).
This
As this change doesent have reproducers and was verified by the GKE team
I will mark it verified in kinetic and jammy.
** Tags removed: verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-jammy verification-done-kinetic
--
You received this bug notification
Fix sent to ML
https://lists.ubuntu.com/archives/kernel-team/2023-May/139327.html
--
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/2016269
Title:
conntrack mark is not advertised via
** 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/2019000
Title:
Use new annotations model
Status in linux
Both focal and bionic passed glibc tests for linux-kvm:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/g/glibc/20230428_090153_8d77a@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/g/glibc/20230428_162353_fc51a@/log.gz
Marking as verified.
**
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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' to 'verification-
done-jammy'. If the problem
Also, please enable
CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING on the cloud
kernels - especially I am interested in the Azure one. Same reason as
above - the other options are already enabled there.
--
You received this bug notification because you are a member of Kernel
Packages,
** Description changed:
On an openstack KVM guest VM the following kernel message is displayed:
"XSAVE consistency problem: size 2560 != kernel_size 0" (see further
traces collected through "ubuntu-bug linux" command)
As a result, the avx feature isn't enabled in the kernel, failing
@blindbO
hello!
I meet the same problem , my computer is same with you , and also is ubuntu
23.04.
but when I compile the https://github.com/Kvalme/uvc , there is an error occur.
"fatal error: linux/usb/uvc.h: no such file or directory"
and i also put the "uvc" directory into the
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2019108/+attachment/5672189/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2019108/+attachment/5672188/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Description changed:
On an openstack KVM guest VM the following kernel message is displayed:
"XSAVE consistency problem: size 2560 != kernel_size 0" (see further
traces collected through "ubuntu-bug linux" command)
As a result, the avx feature isn't enabled in
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2019108/+attachment/5672185/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2019108/+attachment/5672190/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2019108/+attachment/5672187/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2019108/+attachment/5672186/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
> If, due to the nature of the issue you have encountered, you are
unable to run this command, please add a comment stating that fact and
change the bug status to 'Confirmed'
I'm running a vm image optimized for use within cloudfoundry (see
https://bosh.io/stemcells/#ubuntu-jammy) for Jammy 22.04
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2019108/+attachment/5672184/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
+ SRU justification sent to ML:
+
+ [Impact]
+ There was a commit 95fcb42e5f20
+ ("netfilter: ctnetlink: fix compilation warning after data race fixes in ct
mark")
+ that introduces a regression where the "mark" variable is no longer
+ dumped in netlink netfilter
This looks similar to the following kernel thread
https://lore.kernel.org/lkml/a60333b9-6b42-4730-6509-cf1a0cd5c...@citrix.com/T/
> Apparently "size 832 != kernel_size 0" so let the debugging continue...
[...]
> So we've actually found and fixed the issue, but XSAVE and therefore
automatically
Tested with 5.15.0-72.79:
[ Test Case ]
* Boot testing passed
* IBM tested functionality indirectly through derivative IBM kernel that got
same patch
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2019108
and then change the status of the bug to 'Confirmed'.
If, due to the
** 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/2018438
Title:
Jammy update: v5.15.99 upstream stable
Public bug reported:
On an openstack KVM guest VM the following kernel message is displayed:
"XSAVE consistency problem: size 2560 != kernel_size 0" (see further
traces collected through "ubuntu-bug linux" command)
As a result, the avx feature isn't enabled in the kernel, failing some
programs
thanks for sharing https://7dstierlister.com/7ds-tier-list-jp/
--
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/1628204
Title:
linux: 4.4.0-41.61 -proposed tracker
Status in Kernel SRU
** Tags added: lookout-canyon oem-priority originate-from-2000203
** Tags added: originate-from-2011689
** Tags added: originate-from-2012910
** Tags added: originate-from-2013018
** Tags added: originate-from-2013020
** Tags added: originate-from-2013028
** Tags added:
I narrowed this issue down to *not* being downstream, and I narrowed
this down to a particular commit, along with a script that replicates
the issue. I hope this information is helpful.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2623
** Bug watch added: github.com/canonical/cloud-init/issues #2623
https://github.com/canonical/cloud-init/issues/2623
--
You received this bug notification because you are a member of Kernel
Packages, which is
@Robie, let me check it,
I SRUed for L/K/J/OEM-6.1 and got ACKed.
https://lists.ubuntu.com/archives/kernel-team/2023-April/138680.html
i verified on machines, one equipped mute-led and another is w/o.
Is there any issues you are facing?
--
You received this bug notification because you are a
Also is there any testing being done to ensure that other use cases of
alsa-ucm-conf haven't regressed?
--
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/2015972
Title:
Dell:
I see this is verified against the proposed kernel for Jammy. But Lunar
and Kinetic look like they have been tested only against locally patched
kernels, rather than the Ubuntu archive. I would expect SRU
verifications for hardware enablements to be tested exclusively against
the Ubuntu archive
In response to #11, I installed the mainline software
(https://github.com/bkw777/mainline) and installed kernel 6.2.14, the newest of
version 6.2, and restarted with this new kernel version. Unfortunately, kernel
6.2.14 does not fix the suspend issue.
I remind you that I made this test with
> While this works as expected on Jammy, ...
Do we need to test it for jammy, then?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2013209
Title:
expoline.o is packaged
Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2586
** Bug watch added: github.com/canonical/cloud-init/issues #2586
https://github.com/canonical/cloud-init/issues/2586
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-bionic verification-done-focal
verification-done-jammy verification-done-kinetic
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Low
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Low
** Changed in:
Fedora's individual binary firmware xz compression plans seem to be a
success. They kept going and divided the package into many different
firmware packages.
https://packages.fedoraproject.org/pkgs/linux-firmware/
https://packages.fedoraproject.org/pkgs/linux-firmware/intel-gpu-
1 - 100 of 105 matches
Mail list logo
