linux-oem-6.1 has the issue.
--
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/2007516
Title:
XPS 9320 screen flicker on UHD panel 3840x2400
Status in linux package in Ubuntu:
Public bug reported:
[Impact]
[Fix]
[Test]
[Where problems could occur]
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects:
All autopkgtests for the newly accepted linux-meta-oem-5.17 (5.17.0.1028.26)
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
dahdi-linux/1:2.11.1~dfsg-1ubuntu12~22.04.1 (amd64)
Please visit the excuses page listed below and
Thanks cking, I have trouble finding a machine stably reproducing this
issue.
I will run >100 times test on V0.15.04 and V0.15.03. If V0.15.04 is much
more stable, we can switch to V0.15.04 to avoid this issue.
Many thanks.
--
You received this bug notification because you are a member of
please test newer kernels, like oem-6.0, oem-6.1..
--
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/2007516
Title:
XPS 9320 screen flicker on UHD panel 3840x2400
Status in linux package
For the relevant kernels running:
sudo apt purge linux-image-5.15.0-xx-generic linux-modules-5.15.0-xx-
generic linux-modules-extra-5.15.0-xx-generic
Or using this utility: https://git.launchpad.net/linux-purge
Then the leftover directories are correctly removed.
But I don't think you should
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 2007516
and then change the status of the bug to 'Confirmed'.
If, due to the
** Also affects: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-intel-iotg (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-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/2007328
Title:
[ADL-N] HDMI port
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-meta-hwe-5.19 (Ubuntu)
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages,
** Also affects: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg-5.15 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg (Ubuntu Focal)
Importance: Undecided
Status: New
** Also
** Also affects: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in:
Upload the apport log.
** Attachment added: "oemlogs-TRBA-DVT2-C5-20230216143637+0800.apport.gz"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007516/+attachment/5647661/+files/oemlogs-TRBA-DVT2-C5-20230216143637+0800.apport.gz
** Tags added: jellyfish-tentacool
--
** Changed in: linux-intel-iotg (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-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/2006914
Title:
Raptor Lake S/P
** Tags added: kern-5726
--
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/2007369
Title:
Intel AX210 wifi card "Failed to run INIT ucode: -110" after linux-
firmware upgraded
Public bug reported:
The screen flicker after ubuntu jammy upgrade kernel to 5.19.
The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in
5.19 kernel.
I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config
can omit the issue.
** Affects: linux-meta-hwe-5.19
** Changed in: linux-intel-iotg (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/1996609
Title:
AX210 (8086:6020) WLAN init failed
** Also affects: linux-raspi (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: linux-raspi (Ubuntu)
Status: New => Invalid
** Changed in: linux-raspi (Ubuntu Kinetic)
Status: New => Confirmed
** Changed in: linux-raspi (Ubuntu Kinetic)
Importance:
All autopkgtests for the newly accepted linux-meta-aws (5.15.0.1031.29) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/249.11-0ubuntu3.6 (arm64)
Please visit the excuses page listed below and investigate the failures,
After sending the original report, I reverted to using the older
5.4.0-136-generic kernel. That was a week ago, and there have been no
freezes while using the older kernel. This confirms that the freezes are
indeed specific to the 5.4.0-137-generic kernel.
--
You received this bug notification
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/2007486
Title:
The network adapter sometimes
Public bug reported:
Kubuntu 22.04.1 LTS. Honor MagicBook 15 BMH-WFQ9HN.
The network adapter may randomly disconnect. It is not possible to enable it
via the "ip link set ip" command, it gives the following error:
sudo ip link set wlp1s0 up
RTNETLINK answers: Cannot send after transport
Can also confirm that this also happened to me as well. And my
motherboard is a MSI MS-7984.
** Attachment added: "Screenshot from 2023-02-16 16-10-20.png"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/2007439/+attachment/5647560/+files/Screenshot%20from%202023-02-16%2016-10-20.png
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bcmwl (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/2007439
Try deleting/disabling colour profiles completely. Now that you mention
it, I have seen this bug reported a couple of times over the years.
See bug 1803840, bug 1785764, bug 938751
** Package changed: linux (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19
(5.19.0-1020.21~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.15.0-1031.35) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-oem-5.17
(5.17.0-1028.29) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19
(5.19.0-1020.21~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19
(5.19.0-1021.22~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.15.0-1031.35) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-oem-5.17
(5.17.0-1028.29) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19
(5.19.0-1021.22~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the
debdiff for jammy
** Patch added: "pulseaudio_15.99.1+dfsg1-1ubuntu2.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2007331/+attachment/5647523/+files/pulseaudio_15.99.1+dfsg1-1ubuntu2.1.debdiff
--
You received this bug notification because you are a member of
debdiff for kinetic
** Patch added: "pulseaudio_16.1+dfsg1-1ubuntu3.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2007331/+attachment/5647522/+files/pulseaudio_16.1+dfsg1-1ubuntu3.1.debdiff
--
You received this bug notification because you are a member of Kernel
debdiff for lunar
** Patch added: "pulseaudio_16.1+dfsg1-2ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2007331/+attachment/5647521/+files/pulseaudio_16.1+dfsg1-2ubuntu3.debdiff
--
You received this bug notification because you are a member of Kernel
The feature not working for snaps is unsurprising but also an important
one for us to track.
Please either create a new bug for that or reopen and reword this bug to
be about snapped apps only.
** Changed in: mutter (Ubuntu)
Status: Incomplete => Invalid
** Changed in:
If you're willing to try a new kernel then also consider:
sudo apt install linux-generic-hwe-22.04-edge
Just in case the bug is already fixed in kernel 5.19.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6221
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6221
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6221
Importance: Unknown
Status: Unknown
--
You received this bug
This bug is awaiting verification that the linux-gcp/5.15.0-1030.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' to 'verification-done-jammy'. If the
problem still exists,
** Changed in: linux (Ubuntu Xenial)
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/2002889
Title:
5.15.0-58.64 breaks xen bridge networking
I have found that the rapid cyan lines disappear when I swap the color
profile from the default to the "test:blue" profile. The default profile
still retains the issue but the computer screen is less distracting
while using the blue. I have not opened the PC yet, but this does work
as a temporary
Well, no occurrences since my last post on Jan 19. Seems that something
changed for the better.
--
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/1910866
Title:
nvme drive fails after some
The fix for the getattr issue in comment #26-#39 has now landed in
upstream 6.2 and be part of the final release.
--
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/1991691
Title:
cannot
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 directly
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/2007439
Title:
bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module
failed to
Public bug reported:
on Mac Mini 2014. Booted into Ubuntu from external HDD. directed here
from software updater
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux
Using the patch that Jay mentioned above, as well as following his
direction in getting the kernel compiled, after 5 reboots this appears
to resolve the issue.
from watching this reboot many times both with the stock kernel and the
upstream intel driver, i can see that this acts more like the
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: Don Brace (bracedon) => Jeff Lane (bladernr)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Jeff,
Downloaded 22.04.2 daily from today. Still no smartpqi driver update.
Hopefully we will make 2/23.
--
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/1998643
Title:
smartpqi:
Thanks!
Yours,
Carsten
On Wed, Feb 15, 2023 at 9:30 PM Mario Limonciello
<2006...@bugs.launchpad.net> wrote:
>
> The commit is in linux-firmware upstream:
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
> firmware.git/commit/?id=c7a57ef688f7d99d8338a5d8edddc8836ff0e6de
>
> --
>
let me know if you need any more info
[ 2471.643770] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:0020f7fe, in
minetest [8885]
[ 2471.644400] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on
rcs0
[ 2471.747293] i915 :00:02.0: [drm] *ERROR* rcs0 reset request timed out:
The commit is in linux-firmware upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=c7a57ef688f7d99d8338a5d8edddc8836ff0e6de
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
git://git.launchpad.net/~timg-tpi/ubuntu/+source/linux/+git/jammy jammy-
Fix-accessing-freed-irq-affinity_hint-lp2007417
--
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/2007417
the updated stress-ng is available from the stress-ng ppa:
https://launchpad.net/~colin-king/+archive/ubuntu/stress-ng/
--
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/1999731
Title:
git://git.launchpad.net/~timg-tpi/ubuntu/+source/linux/+git/kinetic
kinetic-Fix-accessing-freed-irq-affinity_hint-lp2007417
--
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/2007417
Public bug reported:
SRU Justification
[Impact]
Memory can be accessed after being freed.
[Fix]
commit 18a048370b06a3a521219e9e5b10bdc2178ef19c ('net: mana: Fix
accessing freed irq affinity_hint')
[Test Plan]
Microsoft tested
[Other Info]
SF: #00354216
** Affects: linux-azure (Ubuntu)
@Daniel, Plugging one monitor directly into the Laptop's HDML worked
(with a lesser refresh rate).
And disabling the in-build monitor allowed both external monitors to
have the same refresh rate.
So finally I have 2 external monitors, 1 connected to Laptop's HDMI, 2nd
connected to HDMI in the
stress-ng V0.15.04 has been released with a fix for this issue.
--
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/1999731
Title:
disk stress test failing with code 7
Status in Stress-ng:
The verification of the Stable Release Update for linux-signed-
lowlatency-hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
The verification of the Stable Release Update for linux-lowlatency-
hwe-5.19 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
This bug was fixed in the package linux-hwe-5.19 - 5.19.0-32.33~22.04.1
---
linux-hwe-5.19 (5.19.0-32.33~22.04.1) jammy; urgency=medium
* jammy/linux-hwe-5.19: 5.19.0-32.33~22.04.1 -proposed tracker (LP:
#2004157)
* Packaging resync (LP: #1786013)
- [Packaging] update
** Changed in: linux-bluefield (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1914389
Title:
Integrate fixes for some
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
--
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/1921506
Title:
i2c-mlx.c: sync up with upstream
Status in
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
--
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/1968751
Title:
Devlink wasn't enabled from common config
** Changed in: linux-bluefield (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1975820
Title:
remove offload_pickup sysctl
Verified on J-oem-5.17, test passed without any issue.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
Public bug reported:
RM linux-bluefield from jammy-proposed, shipped in PPA instead
Please RM linux-bluefield kernel from jammy-proposed
shipped in the ppa instead for now.
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects:
** Tags added: sru-20230130
--
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/2006453
Title:
Fix selftests/ftracetests/Meta-selftests in Focal
Status in linux package in Ubuntu:
Invalid
** Also affects: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-intel-iotg (Ubuntu
** Also affects: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-intel-iotg (Ubuntu
@cjwatson thanks alot for chiming in on the issue. I added Launchpad,
because I was unsure what part Launchpad has in the massaging of
dependencies on the Debian import, and if something could be done there.
Unfortunately even if the host had a 5.15 kernel, there is no 5.15
package in Lunar.
The
1) changed -1ubuntu1~22.04.0 to -1~ubuntu22.04.0 because
-1ubuntu1~22.04.0 is higher version that is in lunar:
$ dpkg --compare-versions 2.13.8-1ubuntu1~22.04.0 lt 2.13.8-1 && echo "sru
version is lower than devel" || echo "sru version is HIGHER than devel"
sru version is HIGHER than devel
$
the liveapatch service builders are ephemeral and private - as unique
one is setup for every kernel abi build, with matching build-
dependencies, and potentially contains embargoed security updates code.
livepatches are consumed via livepatch clients, with an optional onprem
server. More
corrado@corrado-x-kinetic:~$ ls /lib/modules
5.19.0-23-generic 5.19.0-28-generic 5.19.0-29-generic 5.19.0-31-generic
corrado@corrado-x-kinetic:~$ sudo apt autoremove --purge
[sudo] password for corrado:
Reading package lists... Done
Building dependency tree... Done
Reading state information...
We plan to switch the buildd host system from Ubuntu 20.04 to 22.04
fairly soon, which would result in using a 5.15 kernel instead of 5.4.
Would that be enough to fix this problem?
** Project changed: launchpad => launchpad-buildd
--
You received this bug notification because you are a member
@Douglas
Please follow message #19, download, compile and install the patched usbvideo
driver.
The patch is working perfectly (with zoom, chees, skyupe, goggle meet,...)
Don't know when it will be included in the official kernel...
BR
Giuliano
--
You received this bug notification because you
Is the PPA with the backported kpatch tool (that can be used with jammy)
public?
--
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/1639924
Title:
Kernel livepatch support for for s390x
*** This bug is a duplicate of bug 1973098 ***
https://bugs.launchpad.net/bugs/1973098
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
The next issue that is still to resolve is around UBSAN -
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003374 it appears that
kpatch is currently incompatible with our kernel configuration that
enables UBSAN.
--
You received this bug notification because you are a member of Kernel
Packages,
This bug was fixed in the package bcmwl -
6.30.223.271+bdcom-0ubuntu10~22.04.1
---
bcmwl (6.30.223.271+bdcom-0ubuntu10~22.04.1) jammy; urgency=medium
* Backport dkms support for HWE kernels.
bcmwl (6.30.223.271+bdcom-0ubuntu10) lunar; urgency=medium
* debian/dkms.conf.in,
1 - 100 of 129 matches
Mail list logo
