** Changed in: cryptsetup (Ubuntu Focal)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054390
Title:
Refine proc mounts entries traversal
To manage notific
Hi Heitor,
As referenced in the corresponding bug report [1], the ZFS-related logic should
ideally be backported to Focal.
However, the reason for not doing so remains unclear.
Since the issue is unrelated to the reported bug, addressing it as part of this
fix might not be appropriate.
[1] http
** Description changed:
[Impact]
The shell's read builtin iterates through /proc/mounts one line at a time.
This becomes problematic when LDAP automount maps generate a large number of
entries in /proc/mounts. It can lead to timeout issues, especially when
iterating through the entries twic
Public bug reported:
[Impact]
The IPv6 configuration is being cleared even though `KeepConfiguration` is set
to `yes`, causing the iSCSI backend system to hang during shutdown.
[Fix]
Systemd upstream has addressed this issue.
https://github.com/systemd/systemd/pull/34989
[Test Plan]
1. Set up a
The systemd-networkd code has undergone significant refinement. Based on
Oracle's requirements, we are only backporting the changes to Noble and
Oracular.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
(Ubuntu Jammy)
Assignee: (unassigned) => Chengen Du (chengendu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103840
Title:
VMware VMs experience 100% CPU usage when the latency-performance
Jammy, Noble, and Oracular have been successfully verified on Oracle
Cloud, and the UBSAN warning is no longer present.
Jammy: Linux jammy-ipv6-bm 5.15.0-138-generic #148-Ubuntu SMP PREEMPT_DYNAMIC
Fri Mar 14 19:05:48 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Noble: Linux noble-ipv6-bm 6.8.0-58-gen
The commits have already been included in Noble, Oracular, and Plucky.
** Changed in: tuned (Ubuntu Noble)
Status: New => Fix Released
** Changed in: tuned (Ubuntu Oracular)
Status: New => Fix Released
** Changed in: tuned (Ubuntu Plucky)
Status: New => Fix Released
--
You
Commit #0ec40e036019 (plugin_cpu: latency can now be specified as
cstate) is not included in Focal. The "force_latency" setting in Focal
only supports a single numeric value.
** Changed in: tuned (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are
[Noble]
Preparation for Network Configuration Serialization/Deserialization
lp2098183-0001: Refactor network code to minimize conflicts during merging.
lp2098183-0002: Introduce new JSON dispatch flags for better logic control.
lp2098183-0003: Add macros for automatically defining a dis
@enr0n
First of all, I sincerely appreciate you taking the time to review these
patches. I acknowledge that this patch set is quite large and resembles a
feature backport. However, the reason for backporting it stems from a request
by one of our customers. We have discussed the challenges of bac
Public bug reported:
[Impact]
The "force_latency=cstate.id:1|3" setting in the latency-performance profile
forces the CPU to remain in C-state 0 to achieve the desired latency.
This prevents the CPU from entering deeper idle states, causing the kernel to
switch the idle method to IDLE_POLL.
As a
** Changed in: systemd (Ubuntu Noble)
Status: Incomplete => In Progress
** Changed in: systemd (Ubuntu Oracular)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
The proposed package in Focal has been successfully verified according
to the test plan, and the results align with expectations.
root@focal:~# apt policy cryptsetup-initramfs
cryptsetup-initramfs:
Installed: 2:2.2.2-3ubuntu2.5
Candidate: 2:2.2.2-3ubuntu2.5
Version table:
*** 2:2.2.2-3ubunt
The fix has already been included in Plucky.
** Description changed:
[Impact]
The IPv6 configuration is being cleared even though `KeepConfiguration` is
set to `yes`, causing the iSCSI backend system to hang during shutdown.
[Fix]
Systemd upstream has addressed this issue.
https://g
Hi Nick, I’ve followed your suggestions and submitted the PRs. Please
take a look when you have a chance. Thanks!
** Changed in: systemd (Ubuntu Focal)
Status: Incomplete => Triaged
** Changed in: systemd (Ubuntu Jammy)
Status: Incomplete => Triaged
--
You received this bug notifi
Thanks! I wasn't aware of this. If all stable releases will include the
bug fix after the upstream release, then filing this bug may not be
necessary. I really appreciate all your assistance with this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I would like to share some preliminary findings regarding this issue.
According to the customer's description, the problem persists in mainline
v6.12.16 but appears to be resolved in v6.12.17.
On the Ubuntu side, a noticeable performance degradation has been observed in
kernel version v6.8.0-40.
** Description changed:
[Impact]
The IPv6 configuration is being cleared even though `KeepConfiguration` is
set to `yes`, causing the iSCSI backend system to hang during shutdown.
[Fix]
Systemd upstream has addressed this issue.
https://github.com/systemd/systemd/pull/34989
[Tes
The only remaining step is to confirm that VMware VMs are not affected
by the same issue. We are currently waiting for the test environment to
proceed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/210
@babyphilip has tested the VMware VMs and confirmed that the issue has
been resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103840
Title:
VMware VMs experience 100% CPU usage when the laten
** Attachment added: "Screenshot from 2025-04-23 09-22-41.png"
https://bugs.launchpad.net/ubuntu/+source/tuned/+bug/2103840/+attachment/5873724/+files/Screenshot%20from%202025-04-23%2009-22-41.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Attachment added: "Screenshot from 2025-04-23 09-22-02.png"
https://bugs.launchpad.net/ubuntu/+source/tuned/+bug/2103840/+attachment/5873725/+files/Screenshot%20from%202025-04-23%2009-22-02.png
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done v
a) Is this bug only present in vmware guests? No other systems?
So far, only VMware virtual machines have been affected by this issue. No other
systems have been reported to encounter it at this time.
b) What is the impact of this change on non-vmware guests?
The impact depends on the value of
/
Debdiff for Oracular
** Patch added: "lp2107301-cloud-init-oracular.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2107301/+attachment/5871619/+files/lp2107301-cloud-init-oracular.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Also affects: cloud-init (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubunt
Debdiff for Jammy
** Patch added: "lp2107301-cloud-init-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2107301/+attachment/5871617/+files/lp2107301-cloud-init-jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Debdiff for Plucky
** Patch added: "lp2107301-cloud-init-plucky.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2107301/+attachment/5871620/+files/lp2107301-cloud-init-plucky.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Debdiff for Focal
** Patch added: "lp2107301-cloud-init-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2107301/+attachment/5871616/+files/lp2107301-cloud-init-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Debdiff for Noble
** Patch added: "lp2107301-cloud-init-noble.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2107301/+attachment/5871618/+files/lp2107301-cloud-init-noble.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Changed in: cloud-init (Ubuntu Focal)
Assignee: (unassigned) => Chengen Du (chengendu)
** Changed in: cloud-init (Ubuntu Jammy)
Assignee: (unassigned) => Chengen Du (chengendu)
** Changed in: cloud-init (Ubuntu Noble)
Assignee: (unassigned) => Chengen Du (chengendu)
*
Public bug reported:
[Impact]
When `modprobe --remove ena` is executed, the kernel triggers a udev remove
event.
This causes cloud-init to refetch the datasource information, expecting the NIC
to be gone.
However, since IMDS updates asynchronously, cloud-init's hotplug logic may wait
and retry
Thanks for your review. After reviewing the code, I believe that
Oracular also requires the 0009-network-json-add-missing-entries-for-
route-propertie.patch. I am currently working on this and will update
the test plan accordingly. Your assistance with this issue is greatly
appreciated.
--
You re
I’ve reviewed the commits between v6.7.6 and v6.7.7 but haven’t found
anything particularly suspicious. From my perspective, it would be
reasonable to bisect the commits between these two versions to identify
the problematic one, and then confirm any related fixes accordingly.
Please let me know i
All proposed versions have been verified and confirmed to behave as
expected.
[Focal]
root@focal:~# apt policy open-iscsi
open-iscsi:
Installed: 2.0.874-7.1ubuntu6.5
Candidate: 2.0.874-7.1ubuntu6.5
Version table:
*** 2.0.874-7.1ubuntu6.5 500
500 http://archive.ubuntu.com/ubuntu foca
** Changed in: grub2 (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098641
Title:
grub 2.06 prob fat fs fail.
To manage notifications about this bug
Debdiff for grub2 in Jammy
** Patch added: "lp2098641-grub2-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2098641/+attachment/5860956/+files/lp2098641-grub2-jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Noble and later versions already include the patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098641
Title:
FAT filesystem probing fails if a file's timestamp exceeds 2038
To manage notificati
Debdiff for grub2-unsigned in Jammy
** Patch added: "lp2098641-grub2-unsigned-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2098641/+attachment/5860957/+files/lp2098641-grub2-unsigned-jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Changed in: grub2 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: grub2-unsigned (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20986
** Also affects: grub2-unsigned (Ubuntu)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-bluefield (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2-unsigned (Ubun
** Description changed:
[Impact]
If any file's timestamp under `/boot/efi` exceeds 2038, the FAT filesystem
probe will fail, and the system will drop into the GRUB shell.
[Fix]
There is an upstream patch that fixes this issue:
https://git.savannah.gnu.org/cgit/grub.git/commit/grub-c
Debdiff for Noble
** Patch added: "lp2098183-systemd-noble.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2098183/+attachment/5864619/+files/lp2098183-systemd-noble.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: systemd (Ubuntu Oracular)
Assignee: (unassigned) => Chengen Du (chengendu)
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Chengen Du (chengendu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Debdiff for Oracular
** Patch added: "lp2098183-systemd-oracular.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2098183/+attachment/5864620/+files/lp2098183-systemd-oracular.debdiff
** Changed in: systemd (Ubuntu Noble)
Status: New => In Progress
** Changed in: system
** Description changed:
[Impact]
The IPv6 configuration is being cleared even though `KeepConfiguration` is
set to `yes`, causing the iSCSI backend system to hang during shutdown.
[Fix]
Systemd upstream has addressed this issue.
https://github.com/systemd/systemd/pull/34989
[Tes
I apologize for not attaching the IPv4 result, even though I had already
verified it.
[Focal]
root@focal:~# apt policy open-iscsi
open-iscsi:
Installed: 2.0.874-7.1ubuntu6.5
Candidate: 2.0.874-7.1ubuntu6.5
Version table:
*** 2.0.874-7.1ubuntu6.5 500
500 http://archive.ubuntu.com/ubu
Public bug reported:
[Impact]
A mount point was originally used by the old volume group.
After replacing it with a new volume group and deactivating the old one, the
mount point, now belonging to the new volume group, gets unmounted accidentally.
[Fix]
A patch set has been introduced to fix this
The patched fix has already been included in Noble, Oracular, and
Plucky.
** Also affects: systemd (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importan
Debdiff for Focal
** Patch added: "lp2100252-systemd-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2100252/+attachment/5860701/+files/lp2100252-systemd-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
d in: systemd (Ubuntu Jammy)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Chengen Du (chengendu)
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Chengen Du (chengendu)
--
You received this bug notification becau
** Summary changed:
- grub 2.06 prob fat fs fail.
+ FAT filesystem probing fails if a file's timestamp exceeds 2038
** Description changed:
- I found this issue on Ubuntu 22.04.5 LTS, but it's a general issue for
grub-2.06.
- This is my setup information：
- nvme0n1
- ├─nvme0n1p1 v
gcc-14 (Ubuntu Questing)
Status: New => Won't Fix
** Changed in: gcc-9 (Ubuntu Focal)
Assignee: (unassigned) => Chengen Du (chengendu)
** Changed in: gcc-11 (Ubuntu Jammy)
Assignee: (unassigned) => Chengen Du (chengendu)
** Changed in: gcc-13 (Ubuntu Noble)
The partial test results have been updated. The test environment for the
first check item appears to be broken, and we are currently seeking
assistance to resolve the issue.
[Noble]
> apt policy systemd
systemd:
Installed: 255.4-1ubuntu8.7
Candidate: 255.4-1ubuntu8.7
Version table:
*** 255.
The issue exists in Focal's gcc-9 package, but it will be addressed only
under Ubuntu Pro support.
** Changed in: gcc-9 (Ubuntu Focal)
Status: New => Won't Fix
** Also affects: ubuntu-pro
Importance: Undecided
Status: New
** Also affects: ubuntu-pro/20.04
Importance: Undecide
The proposed packages for Noble and Oracular have been tested, and all
results are as expected.
[Noble]
> apt policy systemd
systemd:
Installed: 255.4-1ubuntu8.7
Candidate: 255.4-1ubuntu8.7
Version table:
*** 255.4-1ubuntu8.7 100
100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packa
** Description changed:
- This bug-report is to request patching of the GCC bug 118976 in the
- Ubuntu gcc packages to avoid correctness issues, especially in 24.04 and
- 22.04 LTS releases.
+ [Impact]
+ This issue affects SVE vectorization on arm64 platforms, specifically in
cases where bitwise-
Debdiff for Oracular
** Patch added: "lp2101084-gcc-14-oracular.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/2101084/+attachment/5881337/+files/lp2101084-gcc-14-oracular.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Debdiff for Jammy
** Patch added: "lp2101084-gcc-11-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/2101084/+attachment/5881335/+files/lp2101084-gcc-11-jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Debdiff for Noble
** Patch added: "lp2101084-gcc-13-noble.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/2101084/+attachment/5881336/+files/lp2101084-gcc-13-noble.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Focal will not be fixed as it has reached the end of standard support.
** Changed in: systemd (Ubuntu Focal)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100252
The jammy-proposed version has been verified, and the normal behavior
remains unchanged.
root@cifs-client-jammy:~# uname -a
Linux cifs-client-jammy 5.15.0-144-generic #157-Ubuntu SMP Mon Jun 16 07:33:10
UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
root@cifs-client-jammy:~# mount | grep dfs
//dfs-serve
The proposed package for Noble has been tested, and all results are as
expected.
> apt policy systemd
systemd:
Installed: 255.4-1ubuntu8.9
Candidate: 255.4-1ubuntu8.9
Version table:
*** 255.4-1ubuntu8.9 100
100 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu
noble-proposed/main am
** Summary changed:
- wait-network-online timing out on ipv6 only VMs
+ systemd-networkd-wait-online service times out in IPv6-only environments
** Description changed:
- On VMs with IPv6 only networking, systemd-networkd-wait-online times out
- during boot. To reproduce, get the latest questing
** Also affects: systemd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Questin
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Chengen Du (chengendu)
** Changed in: systemd (Ubuntu Oracular)
Assignee: (unassigned) => Chengen Du (chengendu)
** Changed in: systemd (Ubuntu Plucky)
Assignee: (unassigned) => Chengen Du (chengendu)
** C
Public bug reported:
[Impact]
When refresh_cache_worker attempts to refresh DFS referrals, it may access
uninitialized data, leading to a general protection fault caused by a NULL
pointer dereference.
[Fix]
There is an upstream commit that addresses this issue:
From 41f10081a92a0ed280008218a8e
The situation seems a bit unusual at this point. Perhaps you could try
rebuilding version 6.7.7 using your approach to confirm whether the
issue still persists? Please feel free to share any other thoughts you
may have or let me know if there’s anything I can assist with, @ecanepa.
--
You receive
** Description changed:
[Impact]
In an iSCSI boot scenario within an IPv6-only environment, the link remains
in the "configuring" state when the DHCPv6-assigned address conflicts with an
already configured address.
Although network connectivity works as expected, this condition causes the
On a bare metal machine from Oracle Cloud using iSCSI boot in an
IPv6-only environment, the initial DHCPv6 setup is performed by iPXE to
boot the system. Subsequently, systemd attempts to perform its own
DHCPv6 configuration, but this process fails due to a mismatch in prefix
length.
Specifically,
Thanks to @ecanepa for the thorough analysis. He has identified a potentially
relevant configuration—CONFIG_INTEL_IOMMU_DEFAULT_ON—which may be contributing
to the performance issue. A similar problem has been reported in [1].
We’ve reviewed your environment and confirmed that
CONFIG_INTEL_IOMMU
The proposed package for Noble has been tested, and all results are as
expected.
[Noble]
> apt policy systemd
systemd:
Installed: 255.4-1ubuntu8.10
Candidate: 255.4-1ubuntu8.10
Version table:
*** 255.4-1ubuntu8.10 100
100 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu
noble-propo
** Merge proposal linked:
https://code.launchpad.net/~chengendu/ubuntu/+source/systemd/+git/systemd/+merge/487924
** Merge proposal linked:
https://code.launchpad.net/~chengendu/ubuntu/+source/systemd/+git/systemd/+merge/487923
** Merge proposal linked:
https://code.launchpad.net/~che
** Description changed:
[Impact]
The IPv6 configuration is being cleared even though `KeepConfiguration` is
set to `yes`, causing the iSCSI backend system to hang during shutdown.
[Fix]
Systemd upstream has addressed this issue.
https://github.com/systemd/systemd/pull/34989
[Tes
** Description changed:
[Impact]
The IPv6 configuration is being cleared even though `KeepConfiguration` is
set to `yes`, causing the iSCSI backend system to hang during shutdown.
[Fix]
Systemd upstream has addressed this issue.
https://github.com/systemd/systemd/pull/34989
[Tes
We’ve taken note of this issue and have been working with the upstream
maintainer [1] to address it.
The next step will be to backport the fix, and we will schedule time to work on
it accordingly.
[1] https://github.com/systemd/systemd/pull/37916
--
You received this bug notification because y
101 - 176 of 176 matches
Mail list logo
