Hello Mauricio, or anyone else affected,
Accepted dmidecode into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/dmidecode/3.3-3ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-
tests/commit/?id=6c4955b36b2806abb402ebafd1978245425581e2
** Summary changed:
- ubuntu_ftrace_smoke_test timeout on H/F-riscv
+ ubuntu_ftrace_smoke_test timeout on F-5.15/H/J/K-riscv
** Changed in: linux-riscv (Ubuntu)
This happens with the current 15 min timeout on J-riscv, K-riscv,
F-5.15-riscv
They're failing even with 30 min.
45 works.
** Tags added: 5.15 jammy kinetic sru-20220808
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubu
I also have this issue but on a Lenovo laptop with Ubuntu 22.04. It
doesn't seem to affect anything but happens on every boot despite
changing SecureBoot options.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
The verification of the Stable Release Update for kdump-tools 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 encount
This bug was fixed in the package kdump-tools - 1:1.6.10ubuntu2
---
kdump-tools (1:1.6.10ubuntu2) jammy; urgency=low
* debian/rules: Remove "ata_piix.prefer_ms_hyperv=0" (LP: #1978333)
-- Heather Lemon Fri, 10 Jun 2022
16:26:37 +
** Changed in: kdump-tools (Ubuntu Jammy)
kdump-tools (1:1.7) unstable; urgency=medium
[ Guilherme G. Piccoli ]
* kdump-tools.service: Start kdump service a bit earlier in boot.
[ Kellen Renshaw ]
* rules: Remove "ata_piix.prefer_ms_hyperv=0" (Closes: #1011960).
-- dann frazier Thu, 09 Jun 2022 15:29:58 -0600
** Changed in:
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 1988108
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1988108
Title:
kernal 5.15.0-46 error out of memory when boosting
Status in li
The verification of the Stable Release Update for linux-restricted-
modules-hwe-5.15 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
This bug was fixed in the package linux-restricted-modules-hwe-5.15 -
5.15.0-46.49~20.04.1+1
---
linux-restricted-modules-hwe-5.15 (5.15.0-46.49~20.04.1+1) focal; urgency=medium
* Miscellaneous Ubuntu changes (LP: #1988143)
- [packaging] revert drop nvidia 390
-- Alberto Milon
The verification of the Stable Release Update for thermald 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 thermald - 2.4.9-1ubuntu0.1
---
thermald (2.4.9-1ubuntu0.1) jammy; urgency=medium
* Add support for Raptor Lake CPUs. (LP: #1981525)
-- Dirk Su Wed, 13 Jul 2022 14:06:08 +0800
** Changed in: thermald (Ubuntu Jammy)
Status: Fix Committed
The verification of the Stable Release Update for lttng-modules 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 encou
This bug was fixed in the package lttng-modules -
2.13.1-1ubuntu0.22.04.1
---
lttng-modules (2.13.1-1ubuntu0.22.04.1) jammy; urgency=medium
* [ed1149ef] Backport upstream fix to handle removal of random.h
(LP: #1986921)
-- Stefan Bader Thu, 18 Aug 2022 10:13:02
+0200
** Cha
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 from
Hello 'nafeiy', we indeed wanted to pick this up in the next days.
Just notice that this is a development bug, opened at the Launchpad bug
tracking system, that is mainly used for development.
We will usually produce a patched 20.04/focal/5.4 test kernel, that we make a
available via a so called
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 from
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 from
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 from
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1988209
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages, which
This was visible in the terminal when I ran nvidia-settings:
ERROR: Unable to load info from any available system
(nvidia-settings:7822): GLib-GObject-CRITICAL **: 11:42:14.321: g_object_unref:
assertion 'G_IS_OBJECT (object)' failed
** Message: 11:42:14.326: PRIME: No offloading required. Abo
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 from
** Changed in: linux (Ubuntu Kinetic)
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/1988207
Title:
Kinetic update: v5.19.5 upstream stable re
I'm going to go ahead and close this given we are missing some
information and I've reported a similar bug (1988209) already.
** Changed in: nvidia-settings (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Its empty.
** Attachment added: "Screenshot from 2022-08-30 11-09-59.png"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1988209/+attachment/5612573/+files/Screenshot%20from%202022-08-30%2011-09-59.png
--
You received this bug notification because you are a member of Kernel
P
Public bug reported:
I just did a fresh install of Ubuntu 20.04.5 and the when launching
nvidia-settings the GUI does not display anything.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nvidia-settings 470.57.01-0ubuntu0.20.04.3
ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.
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 from
--- Comment From naf...@cn.ibm.com 2022-08-30 12:28 EDT---
@Canonical, I'd like to know that when will the fix be back ported to hwe-5.4
kernel? Will it be a new hotpatch like this one ?
https://launchpad.net/~canonical-support-eng/+archive/ubuntu/sf334332 or
something else. Thanks so m
** 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/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
Confirmed
S
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 1988198
and then change the status of the bug to 'Confirmed'.
If, due to the nature
This issue also exists for "Yeti Stereo Microphone" and "HD Pro Webcam
C920".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1002952
Title:
[meta-bug] Invalid extra "Digital output S/
Public bug reported:
Ubuntu 5.15.0-46.49-generic 5.15.39
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th
Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08)
Subsystem: Fujitsu Limited. Xeon E3-1200 v5/E3-1500 v5/6th Gen Core
Processor Host Bri
The bug seems to be unbeatable. Still happening on Ubuntu 22.04 LTS on a
Samsung NP550XDAE laptop. I'm using an integrated camera:
$ lsmod | grep uvcvideo
uvcvideo 106496 2
videobuf2_vmalloc 20480 1 uvcvideo
videobuf2_v4l2 32768 1 uvcvideo
videobuf2_common 77824
The bug is from 2017 without activity until now, from a desktop
perspective it isn't a rls issue, tagging a notfixing
** Tags removed: rls-kk-incoming
** Tags added: rls-kk-notfixing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
This bug report must stay open to prevent the LRM intel-iotg migrating
back in again.
** Changed in: linux-restricted-signatures-intel-iotg (Ubuntu)
Status: Fix Released => Triaged
** Changed in: linux-restricted-modules-intel-iotg (Ubuntu)
Status: Fix Released => Triaged
--
You r
I prepared a test kernel with the proposed patch (that was a clear
cherry pick for 5.15). Frank do you think you can help me validating the
test kernel?
You can find a tarball with the debian packages for the test kernel at:
https://kernel.ubuntu.com/~mhcerri/test/lp1984103/linux-unsigned-
debs-5
** Patch added: "0001-s390-qeth-cache-link_info-for-ethtool.patch"
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+attachment/5612535/+files/0001-s390-qeth-cache-link_info-for-ethtool.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is s
I no longer see this issue with the recent kernels.
--
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/1977929
Title:
Resume from suspend to ram doesn't work
Status in linux package in Ubun
> * disable Intel DMA remapping by default (LP: #1971699)
Doesn't this add a massive security issue, in that you can plug a
malicious thunderbolt peripheral into any Ubuntu laptop and read the
entire unencrypted RAM space? The IOMMU is there for a reason...
--
You received this bug notificatio
** Description changed:
+ [Impact]
+
+ * Linux-restricted-modules for the 390 drivers were disabled
+ temporarily back in January, however they were not re-enabled when
+ support for the new kernel was added.
+
+ * Including the 390 release in the ISO causes the 5.13 packages to be
+ pulled in
Yepp, it's all about kernel patches.
This bug was wrongly marked as affecting the ethtool (well, it affects the
ethtool, but not in the 'affects' send of Launchpad), which caused some
confusion.
I just changed that, pointing now to the kernel (which is "linux (Ubuntu)" in
the above affects secti
--- Comment From tsta...@de.ibm.com 2022-08-30 08:13 EDT---
(In reply to comment #12)
> canonical-kernel-team does not monitor or respond to userpsace ethtool
> package bugs; this bug should have gone to the server team triage.
This is a _kernel_ patch that fixes output used by ethtool.
-
...discussed this with the kernel team and it seems to be a bug in the
5.15 hwe lrm kernel packages. Apparently because of an error, the
nvidia-390 packages have not been prepared for this kernel. And since we
pull in 390 (and should), this causes the build infrastructure to pull
in the old 5.13 ke
** Tags removed: rls-incoming-jj rls-incoming-kk
--
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/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ethtool (Ubuntu)
** Changed in: ethtool (Ubuntu Jammy)
Assignee: Ubuntu Server (ubuntu-server) => (unassigned)
** Changed in: ethtool (Ubuntu Kinetic)
Assignee: Ubuntu Server (ubuntu-serve
Demoting packages to kinetic-proposed:
linux-restricted-modules-oem-5.17 5.17.0-1003.3+1 in kinetic
linux-restricted-signatures-oem-5.17 5.17.0-1003.3+1 in kinetic
linux-restricted-modules-intel-iotg 5.15.0-1004.6 in kinetic
linux-restricted-signatures-intel-iotg 5.1
** Description changed:
- Remove linux-intel-iotg from kinetic
+ v5.19 kernels are ready to migrate in kinetic.
- This kernel should not exist in kinetic-release, as it is jammy-only
- thing.
+ via new nvidia and LRM packages all kernels are entangled.
- At least for the time being.
+ intel-
** Summary changed:
- Remove linux-oem-5.17 from kinetic
+ Demote to proposed LRM portions of linux-oem-5.17
** No longer affects: linux-meta-oem-5.17 (Ubuntu)
** No longer affects: linux-oem-5.17 (Ubuntu)
** No longer affects: linux-signed-oem-5.17 (Ubuntu)
** Description changed:
- Remove l
@vorlon @apw
Then we must either respin or remove
linux-restricted-modules-oem-5.17
linux-restricted-signatures-oem-5.17
then linux-meta can migrate (with the oem packages transitionals) and
then we can remove the rest of the oem-5.17 packages.
** Changed in: linux-oem-5.17 (Ubuntu)
Stat
** Changed in: linux-restricted-modules-intel-iotg (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux-restricted-signatures-intel-iotg (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
** Tags added: bug-council
--
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/1922910
Title:
Unable to deploy HWE kernel with sub-arch set to xgene-uboot
Status in MAAS:
New
Status in lin
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed => Fix Committed
** Changed in: linux-oem-5.14 (Ubuntu Jammy)
Status: Fix Committed => Invalid
** Changed in: hwe-next
Status: Confirmed => In Progress
** Changed in: hwe-next
Status: In Progress => Fix Committed
** Changed in: hwe-next
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1980829
Title:
System freeze after resuming from suspend due t
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 1988120
and then change the status of the bug to 'Confirmed'.
If, due to the nature
56 matches
Mail list logo
