This bug was fixed in the package linux-bluefield - 5.4.0-1064.70
---
linux-bluefield (5.4.0-1064.70) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1064.70 -proposed tracker (LP:
#2019657)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
[
This bug was fixed in the package linux-intel-iotg - 5.15.0-1030.35
---
linux-intel-iotg (5.15.0-1030.35) jammy; urgency=medium
* jammy/linux-intel-iotg: 5.15.0-1030.35 -proposed tracker (LP:
#2019028)
* net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable
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: bugnameltc-194783 severity-medium
** Tags added: bugnameltc-192677 severity-high
--
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/1927076
Title:
IPv6 TCP in
Since it's end of May 2023, bionic reached it's end of base support.
So can this bug be closed now as 'Won't Fix' or does it need to stay open (for
ESM/Pro matters)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux-intel-iotg - 5.15.0-1030.35
---
linux-intel-iotg (5.15.0-1030.35) jammy; urgency=medium
* jammy/linux-intel-iotg: 5.15.0-1030.35 -proposed tracker (LP:
#2019028)
* net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable
Public bug reported:
[Impact]
[Fix]
[Test Cases]
[Where problems could occur]
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: New
** Affects:
Public bug reported:
While testing J/xilinx, I noticed that the keyword we use to grep from
/proc/device-tree/compatible has to be changed into kv26 instead of k26
that we used for F/xilinx
J/xilinx:
$ cat /proc/device-tree/compatible
I see the original report is on a DigitalOcean Droplet, but I think this
should also reproduce in a local VM. Is there anything specific I need
to do to trigger the bug, Gabor?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
Ubuntu launch the Software Updater and I installed all the updates and
this error occurred
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
Uname:
Hi Andrei,
I have no idea what triggers it. The Droplet is a webserver, maybe
whenever someone requested a page. The warning did not happen
frequently, a few times in an hour, though this server is a test server,
probably does not see much traffic. Maybe Jamie has a better idea or
could give
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2006102
Title:
Mic Mute LED doesn't work on Soundwire
** Changed in: linux-aws (Ubuntu Lunar)
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/2021605
Title:
introduce do_lib_rust=true|false to
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of
For me this was a bare metal bionic install on a home personal, multi-
purpose, intranet server (rsyslog, apache, bind9, etc). The message was
triggered 480 times in ~6 hours and 15 minutes before I downgraded. I
didn't notice other issues. I looked at the logs and couldn't see a
pattern of 'cut
I did a test on focal platforms, I found this issue was not fixed yet.
By default user used oem kernel which is set by oem-meta packages, it
will be ok, but if the user select the generic kernel, then it will meet
black screen issue cause of missing nvidia driver.
Start-Date: 2023-05-31
** Also affects: linux-intel-iotg (Ubuntu)
Importance: Undecided
Status: New
--
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/1998194
Title:
Please add support for Qualcomm IPC
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2021986
Title:
package linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to
Public bug reported:
Newly installed kernel linux-image-5.19.0-43-generic 5.19.0.43.39 does
not boot with the following diagnostics:
-
error: cannot allocate kernel buffer.
error: you need to load the kernel first.
Press any key to continue...
Failed to boot both default and fallback
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/2021997
Title:
Regression. kernel
Created attachment 304349
patch_realtek_alc1220_record.diff
Hi all:
Basically, ASUS CROSSHAIR VI HERO only provides Windows version, not
Linux version.
You can try it, after entering the LINUX OS (ALC1220, 0x10ec1022, subsytem ID:
10438735)
"sudo su root" type root password
"hda-verb
** Tags added: oem-priority originate-from-2016873 somerville
** Tags added: originate-from-2000668
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2021949
Title:
Fix Monitor
** Merge proposal linked:
https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/443928
--
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/1950627
Title:
** Description changed:
[Impact]
+ Enabling CL1 (Controller Low Power) states during discovery of existing
tunnels established by the system firmware can interfere with the operation of
those tunnels.
+ The DisplayPort tunnel establishment timeout of 1.5 seconds can be
insufficient for some
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1065.60)
for focal have finished running.
The following regressions have been reported in tests triggered by the package:
acpi-call/unknown (arm64)
adv-17v35x/unknown (arm64)
bbswitch/unknown (arm64)
ddcci-driver-linux/unknown
Updated to 5.19.0-43, still no sound. Reverting to -38 works, -40, -41, -42 and
-43 all have no sound through HDMI.
Also, from my end:
- HDMI device is showing in GUI sound settings for both -38 and -43.
- "lspci" prints the same result.
- "cat /proc/asound/cards" prints the same for both -38 and
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1018.18
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
All autopkgtests for the newly accepted linux-meta-oem-6.0 (6.0.0.1018.18) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
backport-iwlwifi-dkms/9858-0ubuntu3.2 (amd64)
systemd/249.11-0ubuntu3.9 (amd64)
Please visit the excuses
Public bug reported:
Very slow startup
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
*** This bug is a duplicate of bug 2017227 ***
https://bugs.launchpad.net/bugs/2017227
Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.2.0-20-generic all
INCLUDEDIR=/lib/modules/6.2.0-20-generic/build/include
KVERSION=6.2.0-20-generic DKMS_BUILD=1(bad exit status: 2)
Hello? Has anyone worked on this bug? It's a simple patch:
https://bugzilla.kernel.org/show_bug.cgi?id=217242
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/2013390
Title:
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 2022001
and then change the status of the bug to 'Confirmed'.
If, due to the
>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'.
Cannot open application windows, as already stated in the bug
description, the window or the whole desktop crashes.
**
This bug was fixed in the package clamav - 0.103.8+dfsg-0ubuntu2
---
clamav (0.103.8+dfsg-0ubuntu2) mantic; urgency=medium
* Extend ifupdown script to support networkd-dispatcher.
- d/clamav-freshclam-ifupdown: Modernize some parts of
the script. Implement support for
** Tags added: jammy
** Package changed: ubuntu => linux (Ubuntu)
--
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/2022001
Title:
Kernel 5.19.0-42 onward crashes with VMSVGA + 3D
Hmm, while the Sound Blaster can now be seen for me in PulseAudio with
kernels 5.19.0-42 and 5.19.0-43, it's still not fully functioning
properly. It will not appear as a sink if the profile on the card is set
to anything but stereo output or duplex. I need my card to output 5.1
surround sound
36 matches
Mail list logo
