[Bug 2069352] Re: aws: Backport linear memory map change
** Changed in: linux-aws (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069352 Title: aws: Backport linear memory map change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2069352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069828] Re: Revert removal of unminimize call in server builds
** Summary changed: - Revert removal of yes /usr/local/sbin/unminimize call in server builds + Revert removal of unminimize call in server builds -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069828 Title: Revert removal of unminimize call in server builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2069828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069828] [NEW] Revert removal of yes /usr/local/sbin/unminimize call in server builds
Public bug reported: There was a change made by me in https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd- rootfs/+merge/466388 as part of LP: #2066905 to remove references to LXD in the unminimize scripts but I also removed the calls to `unminimize` in error. This still needs to run but without any references to LXD which no longer needs to be `unminimized` via snap installation. [ Impact ] The server images no longer have a non minimized layer as it is never unminimized. [ Test Plan ] * Successfully build server daily image and ensure that the multiple layers are present. [ Where problems could occur ] * If the server image does not build, if LXD snap continues to be installed or if the unminimized layer is not as expected. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Oracular) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069828 Title: Revert removal of yes /usr/local/sbin/unminimize call in server builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2069828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
Adding `block-proposed-noble` tag as the changes in https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd- rootfs/+merge/466388 actually remove all of unminimize calls - not just the lxd specific changes. I will create bug to track this. ** Tags added: block-proposed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
I have created a test noble minimal cloud image with the -proposed livecd-rootfs 24.04.71 and also successfully confirmed that `unminimize` no longer attempts to install the LXD snap. I built the cloud image in launchpad and tested using qemu. Marking as verification-done ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063203] Re: Build ubuntu-core-desktop images
Based on vorlon's comments above and so as not to delay SRU I am marking this as verified ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063203 Title: Build ubuntu-core-desktop images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2063203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069352] Re: aws: Backport linear memory map change
** Description changed: SRU Justification: [Impact] AWS discovered an issue of long EC2 instance launch times on the upcoming R8g instance types. [Fix] They have identified the following fixes that address this issue: * https://patchew.org/linux/20240412131908.433043-1-ryan.robe...@arm.com/20240412131908.433043-2-ryan.robe...@arm.com/ * https://patchew.org/linux/20240412131908.433043-1-ryan.robe...@arm.com/20240412131908.433043-3-ryan.robe...@arm.com/ They would like this fixced in the jammy, and noble kernels. For reference, here are the links to the above patches in 6.10-rc3: * arm64: mm: Don't remap pgtables per-cont(pte|pmd) block https://github.com/torvalds/linux/commit/5c63db59c5f89925add57642be4f789d0d671ccd * arm64: mm: Batch dsb and isb when populating pgtables https://github.com/torvalds/linux/commit/1fcb7cea8a5f7747e02230f816c2c80b060d9517 + AWS has requested only the first two patches of the series of three patches be back ported. + [Test Plan] - AWS test. + I have tested this, as has AWS. [Where problems could occur] + With the reordering of tlb invalidation and memory barriers, there is some risk, but this chance for regressions on this change is fairly small as the scope is fairly narrow. [Other info] SF# 00387444 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069352 Title: aws: Backport linear memory map change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2069352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069352] Re: aws: Backport linear memory map change
** Changed in: linux-aws (Ubuntu Noble) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux-aws (Ubuntu Jammy) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux-aws (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Noble) 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/2069352 Title: aws: Backport linear memory map change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2069352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069352] [NEW] aws: Backport linear memory map change
Public bug reported: SRU Justification: [Impact] AWS discovered an issue of long EC2 instance launch times on the upcoming R8g instance types. [Fix] They have identified the following fixes that address this issue: * https://patchew.org/linux/20240412131908.433043-1-ryan.robe...@arm.com/20240412131908.433043-2-ryan.robe...@arm.com/ * https://patchew.org/linux/20240412131908.433043-1-ryan.robe...@arm.com/20240412131908.433043-3-ryan.robe...@arm.com/ They would like this fixced in the jammy, and noble kernels. For reference, here are the links to the above patches in 6.10-rc3: * arm64: mm: Don't remap pgtables per-cont(pte|pmd) block https://github.com/torvalds/linux/commit/5c63db59c5f89925add57642be4f789d0d671ccd * arm64: mm: Batch dsb and isb when populating pgtables https://github.com/torvalds/linux/commit/1fcb7cea8a5f7747e02230f816c2c80b060d9517 [Test Plan] AWS test. [Where problems could occur] [Other info] SF# 00387444 ** Affects: linux-aws (Ubuntu) Importance: Undecided Assignee: Philip Cox (philcox) Status: Fix Released ** Affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069352 Title: aws: Backport linear memory map change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2069352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045560] Re: TCP memory leak, slow network (arm64)
@nklya The 6.5 and 6.8 based jammy kernels have received this patch as well. The 6.2 based jammy kernel is no longer supported so it will not be receiving these patches. The way that the jammy 6.5/6.8 kernels work are, they are backports of the newer series kernels. So, for noble (24.04) for example, the noble 6.8 kernel has been back ported to jammy and is the jammy 6.8 based kernel. So, when changes go in to the noble 6.8 kernel, they automatically make it into the jammy 6.8 kernel. So this was targeted to noble and mantic, with the understanding that the changes would end up in the jammy 6.8 and 6.5 based kernel backports. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: TCP memory leak, slow network (arm64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067516] Re: [aws] Backport CMA pool per numa functionality for 22.04 and 20.04
** Description changed: - SRU Justification: [Impact] We discovered a network packets per second (PPS) performance issue in one of our upcoming EC2 instance platform on Graviton.The issue is addressed by setting a value for the numa_cma parameter. While this parameter is supported in 24.04, the parameter is not available in 22.04 or 20.04 today, which could impact customers running 22.04 or 20.04 on the new EC2 platform. [Fix] We are requesting the the following changes be backported to 22.04 and 20.04 for ARM: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/noble/commit/kernel/dma/contiguous.c?id=22e4a348f87c59df2c02f1efb7ba9a56b622c7b8 https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/noble/commit/kernel/dma/contiguous.c?id=bf29bfaa54901a4bdee2a18cd10eb951a884a5f9 EC2 Nitro team is only asking for the change in ARM, however we will leave to Canonical's discretion to make the same changes in x86. - We also request Canonical set kernel params to "numa_cma=1:32M" for all - OSes that support this parameter - 24.04, 22.04 and 20.04. + Also requested to add this fix for NUMA node overrides for AWS EC2 ENA + adapaters: + https://github.com/torvalds/linux/commit/2dc8b1e7177d4f49f492ce648440caf2de0c366 + + + We also request Canonical set kernel params to "numa_cma=1:32M" for all OSes that support this parameter - 24.04, 22.04 and 20.04. [Test Plan] aws tested [Where problems could occur] [Other info] sf# 00385923 ** Also affects: linux-aws (Ubuntu Noble) Importance: Undecided Status: New ** No longer affects: linux-aws (Ubuntu Focal) ** Description changed: SRU Justification: [Impact] We discovered a network packets per second (PPS) performance issue in one of our upcoming EC2 instance platform on Graviton.The issue is addressed by setting a value for the numa_cma parameter. While this parameter is supported in 24.04, the parameter is not available in 22.04 or 20.04 today, which could impact customers running 22.04 or 20.04 on the new EC2 platform. [Fix] We are requesting the the following changes be backported to 22.04 and 20.04 for ARM: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/noble/commit/kernel/dma/contiguous.c?id=22e4a348f87c59df2c02f1efb7ba9a56b622c7b8 https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/noble/commit/kernel/dma/contiguous.c?id=bf29bfaa54901a4bdee2a18cd10eb951a884a5f9 EC2 Nitro team is only asking for the change in ARM, however we will leave to Canonical's discretion to make the same changes in x86. Also requested to add this fix for NUMA node overrides for AWS EC2 ENA adapaters: https://github.com/torvalds/linux/commit/2dc8b1e7177d4f49f492ce648440caf2de0c366 + We also request Canonical set kernel params to "numa_cma=1:32M" for all + OSes that support this parameter - 24.04, 22.04 and 20.04. - We also request Canonical set kernel params to "numa_cma=1:32M" for all OSes that support this parameter - 24.04, 22.04 and 20.04. + + Focal only needs this via the 5.15 based backport kernel, and not the 5.4 based focal kernel. [Test Plan] aws tested [Where problems could occur] [Other info] sf# 00385923 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067516 Title: [aws] Backport CMA pool per numa functionality for 22.04 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2067516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067516] [NEW] [aws] Backport CMA pool per numa functionality for 22.04 and 20.04
Public bug reported: SRU Justification: [Impact] We discovered a network packets per second (PPS) performance issue in one of our upcoming EC2 instance platform on Graviton.The issue is addressed by setting a value for the numa_cma parameter. While this parameter is supported in 24.04, the parameter is not available in 22.04 or 20.04 today, which could impact customers running 22.04 or 20.04 on the new EC2 platform. [Fix] We are requesting the the following changes be backported to 22.04 and 20.04 for ARM: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/noble/commit/kernel/dma/contiguous.c?id=22e4a348f87c59df2c02f1efb7ba9a56b622c7b8 https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/noble/commit/kernel/dma/contiguous.c?id=bf29bfaa54901a4bdee2a18cd10eb951a884a5f9 EC2 Nitro team is only asking for the change in ARM, however we will leave to Canonical's discretion to make the same changes in x86. We also request Canonical set kernel params to "numa_cma=1:32M" for all OSes that support this parameter - 24.04, 22.04 and 20.04. [Test Plan] aws tested [Where problems could occur] [Other info] sf# 00385923 ** Affects: linux-aws (Ubuntu) Importance: Undecided Assignee: Philip Cox (philcox) Status: Fix Released ** Affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067516 Title: [aws] Backport CMA pool per numa functionality for 22.04 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2067516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045223] Re: Fail to boot VM with console=hvc0 in VM kernel cmdline and qemu cmd -serial stdio
** Changed in: ubuntu Assignee: Philip Cox (philcox) => Thibf (thibf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045223 Title: Fail to boot VM with console=hvc0 in VM kernel cmdline and qemu cmd -serial stdio To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2045223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062373] Re: 24.04 TPM backed FDE regression following shim 15.8 update
** Also affects: cloud-images Importance: Undecided Status: New ** Changed in: cloud-images Assignee: (unassigned) => Gauthier Jolly (gjolly) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062373 Title: 24.04 TPM backed FDE regression following shim 15.8 update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2062373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064280] Re: Hyperv desktop images no longer building in Noble
Now in noble unapproved queue https://launchpad.net/ubuntu/noble/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064280 Title: Hyperv desktop images no longer building in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
Now in noble unapproved queue https://launchpad.net/ubuntu/noble/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045560] Re: TCP memory leak, slow network (arm64)
The review for this change has been sent out. It is: https://lists.ubuntu.com/archives/kernel-team/2024-May/151087.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: TCP memory leak, slow network (arm64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066903] Re: Noble+ no longer seed LXD snap so this does not need to be installed when running unminimize
** Description changed: The LXD snap is no longer seeded in non minimal images since Noble+ so the unminimize logic related to LXD snap @ https://git.launchpad.net/ubuntu/+source/unminimize/tree/unminimize?h=applied/ubuntu/noble#n108 is no longer required. lxd-installer can remain installed. This applies for Noble+ so requires SRU back to Noble + + [ Impact ] + + Attempting to install LXD snap on unminimize when this is no longer + required. + + [ Test Plan ] + + * Build cloud minimal image and confirm unminimize does not install LXD + snap + + [ Where problems could occur ] + + * If LXD snap continues to be installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066903 Title: Noble+ no longer seed LXD snap so this does not need to be installed when running unminimize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unminimize/+bug/2066903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
** Description changed: The LXD snap is no longer seeded in any images since Noble+ so the unminimize logic in https://git.launchpad.net/livecd-rootfs/tree/live- build/auto/build?h=ubuntu/noble#n290 and https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- server/hooks/01-unminimize.chroot_early?h=ubuntu/noble#n17 is no longer required. lxd-installer can remain installed. This applies for Noble+ so requires SRU back to Noble [ Impact ] Attempting to install LXD snap on unminimize when this is no longer required. Due to how daily server image builds upgrade to packages from -proposed this is also causing server image build failures - see https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017 - [ Test Plan ] - * Successfully build server daily image - * Build cloud minimal image and confirm unminimize does not install LXD snap - + * Successfully build server daily image + * Build cloud minimal image and confirm unminimize does not install LXD snap [ Where problems could occur ] - * If the server image built does not build or if LXD snap continues to - be seeded + * If the server image built does not build or if LXD snap continues to + be installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
** Description changed: The LXD snap is no longer seeded in any images since Noble+ so the unminimize logic in https://git.launchpad.net/livecd-rootfs/tree/live- build/auto/build?h=ubuntu/noble#n290 and https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- server/hooks/01-unminimize.chroot_early?h=ubuntu/noble#n17 is no longer required. lxd-installer can remain installed. This applies for Noble+ so requires SRU back to Noble + + [ Impact ] + + Attempting to install LXD snap on unminimize when this is no longer + required. + + Due to how daily server image builds upgrade to packages from -proposed + this is also causing server image build failures - see + https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017 + + + [ Test Plan ] + + * Successfully build server daily image + * Build cloud minimal image and confirm unminimize does not install LXD snap + + + [ Where problems could occur ] + + * If the server image built does not build or if LXD snap continues to + be seeded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064280] Re: Hyperv desktop images no longer building in Noble
For context the image @jibel tested was https://partner- images.canonical.com/hyper-v/desktop/oracular/20240522/ @jibel I will start SRU to noble now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064280 Title: Hyperv desktop images no longer building in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] [NEW] LXD snap no longer seeded in non any images so does not need special handling in unminimize logic
Public bug reported: The LXD snap is no longer seeded in non minimal images since Noble+ so the unminimize logic in https://git.launchpad.net/livecd- rootfs/tree/live-build/auto/build?h=ubuntu/noble#n290 and https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- server/hooks/01-unminimize.chroot_early?h=ubuntu/noble#n17 is no longer required. lxd-installer can remain installed. This applies for Noble+ so requires SRU back to Noble ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Summary changed: - LXD snap no longer seeded in non minimal images so does not need special handling in unminimize logic + LXD snap no longer seeded in non any images so does not need special handling in unminimize logic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in non any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066903] [NEW] Noble+ no longer seed LXD snap so this does not need to be installed when running unminimize
Public bug reported: The LXD snap is no longer seeded in non minimal images since Noble+ so the unminimize logic related to LXD snap @ https://git.launchpad.net/ubuntu/+source/unminimize/tree/unminimize?h=applied/ubuntu/noble#n108 is no longer required. lxd-installer can remain installed. This applies for Noble+ so requires SRU back to Noble ** Affects: unminimize (Ubuntu) Importance: Undecided Status: New ** Affects: unminimize (Ubuntu Noble) Importance: Undecided Status: New ** Affects: unminimize (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: unminimize (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: unminimize (Ubuntu Noble) Importance: Undecided Status: New ** Description changed: The LXD snap is no longer seeded in non minimal images since Noble+ so the unminimize logic related to LXD snap @ https://git.launchpad.net/ubuntu/+source/unminimize/tree/unminimize?h=applied/ubuntu/noble#n108 is no longer required. lxd-installer can remain installed. + + This applies for Noble+ so requires SRU back to Noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066903 Title: Noble+ no longer seed LXD snap so this does not need to be installed when running unminimize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unminimize/+bug/2066903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed
@sdeziel thank you for debugging. +1 on moving to `/usr/sbin/lxd` instead of `/sbin/lxd` if possible thus removing the need for any livecd-rootfs changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061017 Title: lxd-installer: permission error not handled and lxd snap not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062929] Re: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel
Jammy livecd-rootfs 2.765.42 has now been uploaded to SRU queue @ https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062929 Title: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062929] Re: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel
Mantic livecd-rootfs 23.10.60 has now been uploaded to SRU queue @ https://launchpad.net/ubuntu/mantic/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062929 Title: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed
Full failing build log @ https://launchpadlibrarian.net/731241044/buildlog_ubuntu_noble_amd64_ubuntu- server-live_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061017 Title: lxd-installer: permission error not handled and lxd snap not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed
The changes proposed here in Noble lxd-installer 4ubuntu0.1 have caused server builds to fail ``` Invoking LXD so that it can be installed by the lxd-installer's script.. Unable to trigger the installation of the LXD snap. Please make sure you're a member of the 'lxd' system group. ``` This is being triggered during build @ https://git.launchpad.net/livecd- rootfs/tree/live-build/auto/build?h=ubuntu/noble#n291 I have added `block-proposed-noble` to this bug until resolved. ** Tags added: block-proposed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061017 Title: lxd-installer: permission error not handled and lxd snap not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045560] Re: TCP memory leak, slow network (arm64)
Two patches are actually needed for this fix. From the 6.8.y stable
branch, the following two patches cherry-pick and build clean on the
generic ubuntu mantic (6.5), and noble (6.8) kernels. I will perform
some more testing and send these out for review.
The two patches are:
d2fa3493811ecd49f1581940111ccf475fa5cd38net: fix
sk_memory_allocated_{add|sub} vs softirqs
e830c804e26733fb09219cb9b92f167715c3b8a0net: make SK_MEMORY_PCPU_RESERV
tunable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045560
Title:
TCP memory leak, slow network (arm64)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045560/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045560] Re: TCP memory leak, slow network (arm64)
I've looked at this issue in some detail now. The initial memory leak was introduced in linux kernel version v6.0, and the fix was introduced in the v6.9 kernel version. This means that the 6.5, and 6.8 based ubuntu kernels will contain this memory leak. I will submit a fix for the generic 6.8, and generic 6.5 kernels so all ubuntu kernels will receive the fix. For reference: The commit that introduces this issue is 3cd3399dd7a84ada85cb839989cdf7310e302c7d https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=3cd3399dd7a84ada85cb839989cdf7310e302c7d And the commit I will be working with to provide the fix is the stable backport to the 6.8.y stable kernel which is: d2fa3493811ecd49f1581940111ccf475fa5cd38 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d2fa3493811ecd49f1581940111ccf475fa5cd38 ** Package changed: linux-signed-aws-6.2 (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux (Ubuntu Noble) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: TCP memory leak, slow network (arm64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045560] Re: TCP memory leak, slow network (arm64)
** Changed in: linux-signed-aws-6.2 (Ubuntu) Assignee: (unassigned) => Philip Cox (philcox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: TCP memory leak, slow network (arm64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
Note to get the vendor id right you need to look at vmware.log - there will be 3 vendors in it and pick the one you want. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060992] Re: aws: Support hibernation on Graviton
** Changed in: linux-aws (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060992 Title: aws: Support hibernation on Graviton To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2060992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060992] Re: aws: Support hibernation on Graviton
** Summary changed: - aws: Guest kernel support for clean boot on demand + aws: Support hibernation on Graviton ** Description changed: SRU Justification: [Impact] + This change contains two parts, the first is adding support for + - KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call + + And the second part is: +- Guest kernel support for clean boot on demand + + + For KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call: + + PSCI v1.3 adds support for SYSTEM_OFF2 which is analogous to ACPI S4 + state. + + This will allow hosting environments to determine that a guest is + hibernated rather than just powered off, and ensure that they preserve + the virtual environment appropriately to allow the guest to resume + safely (or bump the hardware_signature in the FACS to trigger a clean + reboot instead). + + + For Guest kernel support for clean boot on demand: + + The FACS field in the ACPI table is optional, but can be used communicate the hardware_signature field. If this field changes on resuming from a hibernation a clean reboot should happen rather than the resume from hibernation. On hardware reduced platforms[0] this field may exist but it is not exposed currently. [Fix] - Expose this field even on hardware reduced platforms. - https://lore.kernel.org/lkml/20240312134148.727454-1-dw...@infradead.org + The changes for KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call come from: + https://lore.kernel.org/lkml/20240312135958.727765-1-dw...@infradead.org + + + The changes for Guest kernel support for clean boot on demand come from: + https://lore.kernel.org/lkml/20240312134148.727454-1-dw...@infradead.org + [Test Plan] AWS test. [Where problems could occur] If on hardware reduced platforms that incorrectly support/advertise the FACS field, hibernation may break if it returns a hardware signature that changes. [Other info] SF# 00383181 [0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms. https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html ** Changed in: linux-aws (Ubuntu Jammy) Assignee: (unassigned) => Philip Cox (philcox) ** Description changed: SRU Justification: [Impact] - This change contains two parts, the first is adding support for - - KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call + This change contains two parts, the first is adding support for + - KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call And the second part is: -- Guest kernel support for clean boot on demand - + - Guest kernel support for clean boot on demand For KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call: PSCI v1.3 adds support for SYSTEM_OFF2 which is analogous to ACPI S4 state. This will allow hosting environments to determine that a guest is hibernated rather than just powered off, and ensure that they preserve the virtual environment appropriately to allow the guest to resume safely (or bump the hardware_signature in the FACS to trigger a clean reboot instead). - For Guest kernel support for clean boot on demand: - - The FACS field in the ACPI table is optional, but can be used communicate the hardware_signature field. If this field changes on resuming from a hibernation a clean reboot should happen rather than the resume from hibernation. + The FACS field in the ACPI table is optional, but can be used + communicate the hardware_signature field. If this field changes on + resuming from a hibernation a clean reboot should happen rather than the + resume from hibernation. On hardware reduced platforms[0] this field may exist but it is not exposed currently. [Fix] The changes for KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call come from: - https://lore.kernel.org/lkml/20240312135958.727765-1-dw...@infradead.org + https://lore.kernel.org/lkml/20240312135958.727765-1-dw...@infradead.org + + The changes for Guest kernel support for clean boot on demand come from: + https://lore.kernel.org/lkml/20240312134148.727454-1-dw...@infradead.org - The changes for Guest kernel support for clean boot on demand come from: - https://lore.kernel.org/lkml/20240312134148.727454-1-dw...@infradead.org + Latest patches have been picked from: +- noble/mantic: https://git.infradead.org/users/dwmw2/linux.git/shortlog/refs/heads/psci-hibernate-6.8 + + + - jammy: https://git.infradead.org/users/dwmw2/linux.git/shortlog/refs/heads/psci-hibernate-5.15 [Test Plan] AWS test. [Where problems could occur] If on hardware reduced platforms that incorrectly support/advertise the FACS field, hibernation may break if it returns a hardware signature that changes. [Other info] SF# 00383181 [0]: See Section 4.1 of the ACPI spec for i
[Bug 2061006] Re: aws: KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call
*** This bug is a duplicate of bug 2060992 *** https://bugs.launchpad.net/bugs/2060992 ** This bug has been marked a duplicate of bug 2060992 aws: Guest kernel support for clean boot on demand -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061006 Title: aws: KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2061006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061006] Re: aws: KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call
** Also affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-aws (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/2061006 Title: aws: KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2061006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060992] Re: aws: Guest kernel support for clean boot on demand
** Also affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-aws (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/2060992 Title: aws: Guest kernel support for clean boot on demand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2060992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
** Changed in: livecd-rootfs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064580] Re: Please update the package to 20240320.00
The xenial and bionic target is the ESM repos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064580 Title: Please update the package to 20240320.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064580] [NEW] Please update the package to 20240320.00
Public bug reported: Following on from previous similar package update requests @ LP: #2020762, LP: #1996735, LP: #1938553 and LP: #1911689 this bug is a request to update the google-osconfig-agent to the upstream version `20240320.00` @ https://github.com/GoogleCloudPlatform/osconfig/releases/tag/20240320.00 This package has an SRU exception @ https://wiki.ubuntu.com/StableReleaseUpdates#google-osconfig-agent including an ageing exception detailed @ https://wiki.ubuntu.com/google- osconfig-agent-Updates There is some urgency in landing these changes to accommodate planned infrastructure changes on the Google Compute Platform. [Impact] This package is provided by Google for installation within guests that run on Google Compute Engine. It is part of a collection of tools and daemons, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating this package to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of this package is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/google-osconfig-agent-Updates The updated package is not built for armhf and riscv64 due to upstream regressions but the package is not used on those architectures thus please release the SRU without the armhf and risc64 binaries. The package does not build for powerpc on Xenial, but this is OK since it is not used on powerpc either. ** Affects: google-osconfig-agent (Ubuntu) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Focal) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Noble) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064580 Title: Please update the package to 20240320.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064280] [NEW] Hyperv desktop images no longer building in Noble
Public bug reported: We have not built Hyperv desktop images since Jammy and with the re- introduction of HyperV for Noble we have encountered build issues caused by refactoring and removals of code assumed to be redundant but the HyperV desktop images were actually using these code paths. In bbedffe6 we split the building of cloud images and non cloud to using an ddisk-image-uefi.binary and disk-image-uefi-non-cloud.binary respectively. In e38264ca there was a change which meant that any attempt to build hyperv images would result in incorrect disk size and incorrect disk label. A change in 76d79466 changed the logic of how the image size for amd64 images were being set. This overrode the sizes set for the desktop images incorrectly. A change in 8fb21808 also removed many of the dependencies that the hyperv images require. This removal has been restored in this commit by adding them expliciltly in the hyperv hook. With Ubutnu 24.04+ cloud-init was introduced to desktop images. This is not required for HyperV images and can be disabled. This bug is to track the work to restore functioning Hyperv desktop image builds [ Impact ] Unable to build HyperV Desktop image. [ Test Plan ] * Successfully build image * Launch through Windows HyperV manager successfully without any errors or warning. [ Where problems could occur ] * If the image built does not launch in hyperv manager or has errors or warnings. [ Other Info ] * There is work required to migrate oem-config to the new provisioning stack but this is out of scope of this bug. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Assignee: Philip Roche (philroche) Status: New ** Also affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Noble) Assignee: (unassigned) => Philip Roche (philroche) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064280 Title: Hyperv desktop images no longer building in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061121] Re: Mantic preseeding of LXD using incorrect track/channel
Verification done for Mantic now. * Successfully built image with LXD preseeded with these changes * confirmed LXD is preseeded/installed and works as expected. * Confirmed that preseeding other snap like google-cloud-cli for example in the GCE images continues to preseed as expected. ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic ** Also affects: livecd-rootfs (Ubuntu Oracular) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061121 Title: Mantic preseeding of LXD using incorrect track/channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2061121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061121] Re: Mantic preseeding of LXD using incorrect track/channel
This issue affects Oracular/24.10 too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061121 Title: Mantic preseeding of LXD using incorrect track/channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2061121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063365] Re: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52
This happens too with Ubuntu Core 24 during console-conf WiFi configuration, and provides a less-than-nice experience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063365 Title: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
I was able to get something working on my win 11 i9-13900H discrete RTX2000 laptop. I used: mks.enable3d = "TRUE" mks.enableDX12Renderer = "TRUE" mks.enableDX11Renderer = "FALSE" mks.dx12.vendorID = "0x17AA" and I also had to do: settings->system->dislay->graphics entries for both vmware.exe and vmware-vmx.exe (its in a subdirectory) Both entries specify that vmware must run only on RTX2000 and not the cpu GPU. Still seeing MESA: error: ZINK: failed to choose pdev glx: failed to create drisw screen but that might be known? I dont think linux will be stable until you back off mesa to not have that error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
Also tried virtualbox this morning on a different win 11 machine with an nvidia laptop gpu and same thing. No 3D acceleration is not stable on vmware (crashes after a while) With 3D acceleration black screens really fast on vmware and virtualbox (which uses the vmware driver by default) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
Microsoft Windows [Version 10.0.22631.3447] Processor AMD Ryzen 7 3700X 8-Core Processor, 3600 Mhz, 8 Core(s), 16 Logical Processor(s) System ModelX570 AORUS PRO WIFI RTX 2070 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
vmware 17.5 win 11 not fixed with todays iso. mesa is 24.0.5. Can see gui without enable 3d acceleration, but black screen and have to task manager kill with 3d acceleration. rtx 2070 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063482] Re: mpv should be configured with hwdec=yes or hwdec=auto-safe rather than hwdec=vaapi
In fact just putting `hwdec` by itself into the config file implies `hwdec=yes` so that's even more concise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063482 Title: mpv should be configured with hwdec=yes or hwdec=auto-safe rather than hwdec=vaapi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/2063482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063482] [NEW] mpv should be configured with hwdec=yes or hwdec=auto-safe rather than hwdec=vaapi
Public bug reported: (mpv dev here) mpv has long recommended that users who want hardware decoding start by using `hwdec=auto-safe`. This goes through a set of hwdecs that we consider to be safe, and it will keep trying if the first one doesn't work. So we recommend that Ubuntu uses `hwdec=auto-safe` or `hwdec=yes` (both do the same thing now) in the config file vs `hwdec=vaapi`. This will produce better results on nvidia hardware and also enable the fallback logic which will generally increase the chances of successfully enabling hardware decoding. ** Affects: mpv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063482 Title: mpv should be configured with hwdec=yes or hwdec=auto-safe rather than hwdec=vaapi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/2063482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063442] [NEW] needrestart on Ubuntu 24.04 is restarting google-guest-agent startup and shutdown scrips on reinstall but they should not be restarted
Public bug reported:
The recent change in Ubuntu 24.04 and needrestart which results in
services being restarted automatically , details @
https://discourse.ubuntu.com/t/noble-numbat-release-
notes/39890#services-restart-on-unattended-upgrade-26, has resulted in
unexpected behaviour on Google GCE ubuntu 24.04 images where if the
google-guest-agent package is reinstalled then needrestart will restart
the `google-startup-scripts.service` and `google-shutdown-
scripts.service` but these should only be run during the lifetime of the
instance and should not be restarted.
It can be worked around by setting `NEEDRESTART_SUSPEND=1` prior to any
re-install as per the needrestart man pages @
https://manpages.ubuntu.com/manpages/noble/man1/needrestart.1.html?&_ga=2.32620542.1557010342.1713949275-1490161839.1713949275#environment
or by appending to the needrestart configuration `echo
"\$nrconf{override_rc}{qr(^google-(shutdown|startup)-scripts\.service$)}
= 0;" >> /etc/needrestart/conf.d/google-guest-agent.conf` which will
disable this behaviour for any future google-guest-agent upgrade or
reinstall.
This bug is to track the work of getting this added to the packaged
`/etc/needrestart/needrestart.conf` configuration.
Similar to the work done for cloud-init @
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2059337
** Affects: needrestart (Ubuntu)
Importance: Undecided
Status: New
** Affects: needrestart (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: needrestart (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063442
Title:
needrestart on Ubuntu 24.04 is restarting google-guest-agent startup
and shutdown scrips on reinstall but they should not be restarted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2063442/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063315] Re: Suspend & Resume functionality broken/timesout in GCE
** Also affects: linux-gcp (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063315 Title: Suspend & Resume functionality broken/timesout in GCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2063315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression with new apparmor profiles/features
** Changed in: snapd (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-gcp (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-ibm (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-oracle (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression with new apparmor profiles/features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060992] Re: aws: Guest kernel support for clean boot on demand
** Also affects: linux-aws (Ubuntu Noble) Importance: Undecided Assignee: Philip Cox (philcox) Status: New ** Also affects: linux-aws (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Mantic) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux-aws (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Noble) 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/2060992 Title: aws: Guest kernel support for clean boot on demand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2060992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061006] Re: aws: KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call
** Also affects: linux-aws (Ubuntu Noble) Importance: Undecided Assignee: Philip Cox (philcox) Status: New ** Also affects: linux-aws (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Mantic) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux-aws (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Noble) 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/2061006 Title: aws: KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2061006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062373] Re: 24.04 TPM backed FDE regression following snapd 2.62 update
I have removed references to desktop FDE from the description. Thank you for testing. ** Description changed: Azure testing has reported an issue following update of the nullboot package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed included the vendoring of snapd 2.62. This has caused a regression and TPM backed FDE instances no longer boot as expected. - There are reports that this is affecting desktop TPM backed FDE too. + ~~ There are reports that this is affecting desktop TPM backed FDE too. + ~~ ** Description changed: Azure testing has reported an issue following update of the nullboot package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed included the vendoring of snapd 2.62. This has caused a regression and TPM backed FDE instances no longer boot as expected. - ~~ There are reports that this is affecting desktop TPM backed FDE too. - ~~ + ~~There are reports that this is affecting desktop TPM backed FDE too.~~ ** Description changed: Azure testing has reported an issue following update of the nullboot package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed included the vendoring of snapd 2.62. This has caused a regression and TPM backed FDE instances no longer boot as expected. - - ~~There are reports that this is affecting desktop TPM backed FDE too.~~ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062373 Title: 24.04 TPM backed FDE regression following snapd 2.62 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2062373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062373] Re: 24.04 TPM backed FDE regression following snapd 2.62 update
This is a 24.04 release blocking bug as it is a regression and results in a failure to boot for TPM backed FDE instances. ** Description changed: Azure testing has reported an issue following update of the nullboot package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed included the vendoring of snapd 2.62. + This has caused a regression and TPM backed FDE instances no longer boot + as expected. - This has caused a regression and TPM backed FDE instances no longer boot as expected. + There are reports that this is affecting desktop TPM backed FDE too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062373 Title: 24.04 TPM backed FDE regression following snapd 2.62 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2062373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062373] [NEW] 24.04 TPM backed FDE regression following snapd 2.62 update
Public bug reported: Azure testing has reported an issue following update of the nullboot package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed included the vendoring of snapd 2.62. This has caused a regression and TPM backed FDE instances no longer boot as expected. There are reports that this is affecting desktop TPM backed FDE too. ** Affects: nullboot (Ubuntu) Importance: Undecided Status: New ** Affects: shim (Ubuntu) Importance: Undecided Status: New ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Affects: nullboot (Ubuntu Noble) Importance: Undecided Status: New ** Affects: shim (Ubuntu Noble) Importance: Undecided Status: New ** Affects: snapd (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Also affects: nullboot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062373 Title: 24.04 TPM backed FDE regression following snapd 2.62 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2062373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062024] Re: armhf doesn't build disk-image-uefi
** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062024 Title: armhf doesn't build disk-image-uefi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-ibm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features
** Also affects: chrony (Ubuntu) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Also affects: chrony (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061851] [NEW] linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features
Public bug reported: * Canonical Public Cloud discovered that `chronyc -c sources` now fails with `506 Cannot talk to daemon` with the latest kernels. We are seeing this in linux-azure and linux-gcp kernels (6.8.0-1005.5) * Disabling AppArmor (`sudo systemctl stop apparmor`) completely results in no regression and `chronyc -c sources` returns as expected * Disabling the apparmor profile for `chronyd` only results in no regression and `chronyc -c sources` returns as expected * There are zero entries in dmesg when this occurs * There are zero entries in dmesg when this occurs if the apparmor profile for `chronyd` is placed in complain mode instead of enforce mode * We changed the time server from the internal GCP metadata.google.internal to the ubuntu time server ntp.ubuntu.com with no change in behaviour We also noted issues with DNS resolution in snaps like `google-cloud-cli` in GCE images. * Disabling apparmor completely for snaps too (`sudo systemctl stop snapd.apparmor`) results in no regression and calling the snaps returns as expected. The same issues are present in azure kernel `linux-azure` `6.8.0-1005.5` and the -proposed `6.8.0-25.25` generic kernel. This is a release blocker for Noble release ** Affects: chrony (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Affects: chrony (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: snapd (Ubuntu Noble) Importance: Undecided Status: New ** Tags: block-proposed block-proposed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061121] Re: Mantic preseeding of LXD using incorrect track/channel
This does not affect Noble as we no longer preseed LXD in >=Noble ** Also affects: livecd-rootfs (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Mantic) Assignee: (unassigned) => Philip Roche (philroche) ** Description changed: Recent Mantic cloud image builds fail - see https://launchpad.net/~cloudware/+livefs/ubuntu/mantic/cpc/+build/604087 build log for an example. ``` + UBUNTU_STORE_ARCH=amd64 SNAPPY_STORE_NO_CDN=1 snap download --cohort=MSAqIDE3MTI5MDgwNDcgNWIzNmM3MmIwYjVmNDIyMjQ5Y2NmY2JhNjA4MjAyNTliYzAyNjA4NWYzMjA1MWNlN2U3Y2Y3NjE5NzgwMmZkMQ== --channel=stable/ubuntu-23.10 lxd Fetching snap "lxd" store_download.go:142: no host system xdelta3 available to use deltas error: cannot download snap "lxd": no snap revision available as specified ``` The was due to the default track now pointing to "5.21" instead of "latest". That change was made 20240411 which corresponds to when we started seeing failures. - The long term solution is to pressed from "latest/" for all snaps and no + The long term solution is to preseed from "latest/" for all snaps and no longer assume that "latest/" is the default. - [ Impact ] All image with preseeding of the LXD snap will fail [ Test Plan ] - * Successfully build image with LXD preseeded with these changes - * confirm LXD is preseeded/installed and works as expected. - * Confirm that preseeding other snap like google-cloud-cli for example in the GCE images continues to preseed as expected. + * Successfully build image with LXD preseeded with these changes + * confirm LXD is preseeded/installed and works as expected. + * Confirm that preseeding other snap like google-cloud-cli for example in the GCE images continues to preseed as expected. [ Where problems could occur ] - * If other snaps are also preseeded they might not be preseeded as + * If other snaps are also preseeded they might not be preseeded as expected. This is covered in the test plan. [ Other Info ] - * A temporary workaround has been made to point + * A temporary workaround has been made to point 5.21/stable/ubuntu-23.10 to the 5.19 LXD snap but this will expire in one month. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061121 Title: Mantic preseeding of LXD using incorrect track/channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2061121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061121] [NEW] Mantic preseeding of LXD using incorrect track/channel
Public bug reported: Recent Mantic cloud image builds fail - see https://launchpad.net/~cloudware/+livefs/ubuntu/mantic/cpc/+build/604087 build log for an example. ``` + UBUNTU_STORE_ARCH=amd64 SNAPPY_STORE_NO_CDN=1 snap download --cohort=MSAqIDE3MTI5MDgwNDcgNWIzNmM3MmIwYjVmNDIyMjQ5Y2NmY2JhNjA4MjAyNTliYzAyNjA4NWYzMjA1MWNlN2U3Y2Y3NjE5NzgwMmZkMQ== --channel=stable/ubuntu-23.10 lxd Fetching snap "lxd" store_download.go:142: no host system xdelta3 available to use deltas error: cannot download snap "lxd": no snap revision available as specified ``` The was due to the default track now pointing to "5.21" instead of "latest". That change was made 20240411 which corresponds to when we started seeing failures. The long term solution is to pressed from "latest/" for all snaps and no longer assume that "latest/" is the default. [ Impact ] All image with preseeding of the LXD snap will fail [ Test Plan ] * Successfully build image with LXD preseeded with these changes * confirm LXD is preseeded/installed and works as expected. * Confirm that preseeding other snap like google-cloud-cli for example in the GCE images continues to preseed as expected. [ Where problems could occur ] * If other snaps are also preseeded they might not be preseeded as expected. This is covered in the test plan. [ Other Info ] * A temporary workaround has been made to point 5.21/stable/ubuntu-23.10 to the 5.19 LXD snap but this will expire in one month. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061121 Title: Mantic preseeding of LXD using incorrect track/channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2061121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061006] [NEW] aws: KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call
Public bug reported: SRU Justification: [Impact] PSCI v1.3 adds support for SYSTEM_OFF2 which is analogous to ACPI S4 state. This will allow hosting environments to determine that a guest is hibernated rather than just powered off, and ensure that they preserve the virtual environment appropriately to allow the guest to resume safely (or bump the hardware_signature in the FACS to trigger a clean reboot instead). [Fix] This adds support for it to KVM, and to the guest hibernate code. https://lore.kernel.org/lkml/20240312135958.727765-1-dw...@infradead.org [Test Plan] AWS tested. [Where problems could occur] If the final spec of the PSCI v1.3 changes, there may be changes required to this patch series. [Other Info] SF# 00383181 ** Affects: linux-aws (Ubuntu) Importance: Undecided Assignee: Philip Cox (philcox) Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061006 Title: aws: KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2061006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060992] Re: aws: Guest kernel support for clean boot on demand
** Description changed: SRU Justification: [Impact] The FACS field in the ACPI table is optional, but can be used communicate the hardware_signature field. If this field changes on resuming from a hibernation a clean reboot should happen rather than the resume from hibernation. On hardware reduced platforms[0] this field may exist but it is not exposed currently. [Fix] Expose this field even on hardware reduced platforms. https://lore.kernel.org/lkml/20240312134148.727454-1-dw...@infradead.org [Test Plan] AWS test. [Where problems could occur] - If on hardware reduced platforms that incorrectly support/advertise the FACS field, hibernation may break if it returns a hardware signature that changes. + If on hardware reduced platforms that incorrectly support/advertise the FACS field, hibernation may break if it returns a hardware signature that changes. + [Other info] + SF# 00383181 [0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms. https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060992 Title: aws: Guest kernel support for clean boot on demand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2060992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060992] [NEW] aws: Guest kernel support for clean boot on demand
Public bug reported: SRU Justification: [Impact] The FACS field in the ACPI table is optional, but can be used communicate the hardware_signature field. If this field changes on resuming from a hibernation a clean reboot should happen rather than the resume from hibernation. On hardware reduced platforms[0] this field may exist but it is not exposed currently. [Fix] Expose this field even on hardware reduced platforms. https://lore.kernel.org/lkml/20240312134148.727454-1-dw...@infradead.org [Test Plan] AWS test. [Where problems could occur] If on hardware reduced platforms that incorrectly support/advertise the FACS field, hibernation may break if it returns a hardware signature that changes. [0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms. https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html ** Affects: linux-aws (Ubuntu) Importance: Undecided Assignee: Philip Cox (philcox) Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060992 Title: aws: Guest kernel support for clean boot on demand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2060992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060558] [NEW] AppArmor profile `unconfined_restrictions` missing for noble 6.8 kernel
Public bug reported: A recent update to the Noble introduced AppArmor new profile `unconfined_restrictions` [1]. This is not reflected in the snap preseeding code and need to be updated. Currently any snaps preseeded are not seeded correctly resulting in a longer boot time. [1] https://discourse.ubuntu.com/t/spec-unprivileged-user-namespace-restrictions-via-apparmor-in-ubuntu-23-10/37626/2 ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Assignee: Catherine Redfield (catred) Status: New ** Affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Assignee: Catherine Redfield (catred) Status: New ** Also affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Noble) Assignee: (unassigned) => Philip Roche (philroche) ** Changed in: livecd-rootfs (Ubuntu Noble) Assignee: Philip Roche (philroche) => Catherine Redfield (catred) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060558 Title: AppArmor profile `unconfined_restrictions` missing for noble 6.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2060558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054688] Re: Update ena to 2.10.x or later
I am looking in to this. ** Changed in: linux-aws (Ubuntu) Assignee: (unassigned) => Philip Cox (philcox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054688 Title: Update ena to 2.10.x or later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2054688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059730] Re: Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs
Verified Focal: This exact proposed version of livecd-rootfs has been used in cloud image build for many weeks now and has met all of the steps listed in the test plan. GCE daily minimal image daily-ubuntu-minimal-2004-focal-v20240405`` being one such image with snaps and built using this version of livecd- rootfs. Steps: 1. Launch `daily-ubuntu-minimal-2004-focal-v20240405` from project `ubuntu-os-cloud-devel` in GCE ``` gcloud compute instances create $(petname) --zone=europe-west1-d --image=daily-ubuntu-minimal-2004-focal-v20240405 --image-project=ubuntu-os-cloud-devel ``` 4. logged in and ran `sudo snap debug seeding` ``` ubuntu@usable-mullet:~$ sudo snap debug seeding seeded: true preseeded: true image-preseeding: 5.744s seed-completion: 3.278s ``` 5. and just to double check, yes there are snaps ``` ubuntu@usable-mullet:~$ snap list Name Version Rev Tracking Publisher Notes core20 20240111 2182 latest/stable canonical✓ base google-cloud-cli 471.0.0 229 latest/stable/… google-cloud-sdk✓ classic snapd 2.61.2 21184 latest/stable canonical✓ snapd ``` ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059730 Title: Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2059730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
Verified Focal: This exact proposed version of livecd-rootfs has been used in cloud image build for many weeks now and has met all of the steps listed in the test plan. GCE daily minimal image daily-ubuntu-minimal-2004-focal-v20240405`` being one such image with snaps and built using this version of livecd- rootfs. Steps: 1. Launch `daily-ubuntu-minimal-2004-focal-v20240405` from project `ubuntu-os-cloud-devel` in GCE ``` gcloud compute instances create $(petname) --zone=europe-west1-d --image=daily-ubuntu-minimal-2004-focal-v20240405 --image-project=ubuntu-os-cloud-devel ``` 4. logged in and ran `sudo snap debug seeding` ``` ubuntu@usable-mullet:~$ sudo snap debug seeding seeded:true preseeded: true image-preseeding: 5.744s seed-completion: 3.278s ``` 5. and just to double check, yes there are snaps ``` ubuntu@usable-mullet:~$ snap list Name Version RevTracking Publisher Notes core2020240111 2182 latest/stablecanonical✓ base google-cloud-cli 471.0.0 229latest/stable/… google-cloud-sdk✓ classic snapd 2.61.221184 latest/stablecanonical✓ snapd ``` ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058409] Re: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found
Pressing enter multiple times as @jakobpinggera mentioned also worked for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058409 Title: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/context/+bug/2058409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
Focal livecd-rootfs `2.664.53` with these proposed changes now in upload queue https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059730] Re: Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs
Focal livecd-rootfs `2.664.53` with these proposed changes now in upload queue https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059730 Title: Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2059730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051727] Re: tcp: Add memory barrier to tcp_push()
** Tags removed: verification-needed-focal-linux-aws verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux-aws-fips verification-needed-mantic-linux-aws ** Tags added: verification-passed-focal-linux-aws verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux-aws-fips verification-passed-mantic-linux-aws -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051727 Title: tcp: Add memory barrier to tcp_push() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054699] Re: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux verification-needed-jammy-linux-aws-fips verification-needed-mantic-linux ** Tags added: verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux verification-passed-jammy-linux-aws-fips verification-passed-mantic-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054699 Title: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056475] Re: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation
** Tags removed: verification-needed-focal-linux-aws verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux-aws-fips verification-needed-mantic-linux-aws ** Tags added: verification-passed-focal-linux-aws verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux-aws-fips verification-passed-mantic-linux-aws -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056475 Title: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2056475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053069] Re: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing
** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux verification-needed-jammy-linux-aws-fips ** Tags added: verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux verification-passed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053069 Title: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052827] Re: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold
** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux verification-needed-jammy-linux-aws-fips ** Tags added: verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux verification-passed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052827 Title: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052817] Re: cpufreq: intel_pstate: Enable HWP IO boost for all servers
** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux verification-needed-jammy-linux-aws-fips ** Tags added: verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux verification-passed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052817 Title: cpufreq: intel_pstate: Enable HWP IO boost for all servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053251] Re: performance: Scheduler: ratelimit updating of load_avg
** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux verification-needed-jammy-linux-aws-fips verification-needed-mantic-linux ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-jammy-linux verification-done-jammy-linux-aws-fips verification-done-mantic-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053251 Title: performance: Scheduler: ratelimit updating of load_avg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
MP with catred's proposed changes @ https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd- rootfs/+merge/463488 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059730] Re: Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs
MP with catred's proposed changes @ https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd- rootfs/+merge/463488 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059730 Title: Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2059730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056344] Re: "apt-get install software-properties-gtk" command produces an error: /usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197: SyntaxWarning: invalid escape sequence
The backslash is being treated as an escape character for the enclosing string. Needs to be replaced with two backslashes to produce an actual backslash IN the regex. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056344 Title: "apt-get install software-properties-gtk" command produces an error: /usr/lib/python3/dist- packages/softwareproperties/gtk/DialogMirror.py:197: SyntaxWarning: invalid escape sequence '\.' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2056344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2042101] Re: "intel_ish_ipc 0000:00:1d.0: enable ose_gpe failed" when suspend/resume over 255 times Edit
** Changed in: linux-intel-iotg (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2042101 Title: "intel_ish_ipc :00:1d.0: enable ose_gpe failed" when suspend/resume over 255 times Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2042101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
Now uploaded to Jammy queue @ https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056475] Re: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation
** Changed in: linux-aws (Ubuntu Focal) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux-aws (Ubuntu Jammy) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux-aws (Ubuntu Mantic) Assignee: (unassigned) => Philip Cox (philcox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056475 Title: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2056475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056475] Re: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation
** Changed in: linux-aws (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056475 Title: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2056475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057965] Re: google-startup-scripts runs before cloud-init finished network setup
** Also affects: google-guest-agent (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: google-guest-agent (Ubuntu Noble) Importance: Undecided Status: Confirmed ** Also affects: google-guest-agent (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: google-guest-agent (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: google-guest-agent (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: google-guest-agent (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057965 Title: google-startup-scripts runs before cloud-init finished network setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2057965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057965] Re: google-startup-scripts runs before cloud-init finished network setup
@holmanb > google-startup-scripts.service starts well after the network is online You are correct. I have updated the bug description now. > due to configuration via cloud-init not being fully completed, apt sources for example, when startup scripts are run ** Description changed: - New GCP dailies are failing startup-script tests, due to network not - being fully set up when startup scripts are run. The failure can be - reproduced as follows: + New GCP dailies are failing startup-script tests, due to configuration + via cloud-init not being fully completed, apt sources for example, when + startup scripts are run. The failure can be reproduced as follows: Using startup_script.sh: #!/bin/bash cp /etc/apt/sources.list /tmp/startup-sources.list - $ gcloud compute instances create startup-test --image daily-ubuntu-2204-jammy-v20240314 --image-project ubuntu-os-cloud-devel --metadata-from-file=startup-script=startup_script.sh [...] $ ssh [INSTANCE IP] > diff /tmp/startup-sources.list /etc/apt/sources.list 0a1,8 > ## Note, this file is written by cloud-init on first boot of an instance > ## modifications made here will not survive a re-bundle. > ## if you wish to make changes you can: > ## a.) add 'apt_preserve_sources_list: true' to /etc/cloud/cloud.cfg > ## or do the same in user-data > ## b.) add sources in /etc/apt/sources.list.d > ## c.) make changes to template file /etc/cloud/templates/sources.list.tmpl - > + > 3,4c11,12 < deb http://archive.ubuntu.com/ubuntu/ jammy main restricted < # deb-src http://archive.ubuntu.com/ubuntu/ jammy main restricted --- > deb http://us-central1.gce.archive.ubuntu.com/ubuntu/ jammy main restricted > # deb-src http://us-central1.gce.archive.ubuntu.com/ubuntu/ jammy main restricted 8,9c16,17 < deb http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted < # deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted --- [...] - - On earlier images (such as ubuntu-2204-jammy-v20240307 in ubuntu-os-cloud) do not show this behaviour. The change is due to a change in ubuntu-pro 31 (see https://github.com/canonical/ubuntu-pro-client/blob/dfe1f1ed4678c50240d4e251f41d33bb4034135e/debian/changelog#L40 for details) that removes a systemd ordering on cloud-config.service. As side effect of this change was the removal of cloud-config.service (and ubuntu-advantage.service) from systemd's critical chain. + On earlier images (such as ubuntu-2204-jammy-v20240307 in ubuntu-os- + cloud) do not show this behaviour. The change is due to a change in + ubuntu-pro 31 (see https://github.com/canonical/ubuntu-pro- + client/blob/dfe1f1ed4678c50240d4e251f41d33bb4034135e/debian/changelog#L40 + for details) that removes a systemd ordering on cloud-config.service. + As side effect of this change was the removal of cloud-config.service + (and ubuntu-advantage.service) from systemd's critical chain. On v20240307 (startup scripts execute correctly): catred@startup-test-control:~$ systemd-analyze critical-chain google-startup-scripts.service The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. google-startup-scripts.service +18.262s └─multi-user.target @28.480s - └─ubuntu-advantage.service @28.480s - └─cloud-config.service @27.372s +1.095s - └─snapd.seeded.service @20.048s +7.312s - └─snapd.service @12.469s +7.555s - └─basic.target @11.558s - └─sockets.target @11.540s - └─snap.lxd.daemon.unix.socket @24.376s - └─sysinit.target @10.825s - └─cloud-init.service @8.432s +2.267s - └─systemd-networkd-wait-online.service @6.467s +1.935s - └─systemd-networkd.service @6.347s +112ms - └─network-pre.target @6.328s - └─cloud-init-local.service @4.309s +2.006s - └─systemd-remount-fs.service @1.829s +68ms - └─systemd-fsck-root.service @1.587s +160ms - └─systemd-journald.socket @1.292s - └─system.slice @1.068s - └─-.slice @1.068s - + └─ubuntu-advantage.service @28.480s + └─cloud-config.service @27.372s +1.095s + └─snapd.seeded.service @20.048s +7.312s + └─snapd.service @12.469s +7.555s + └─basic.target @11.558s + └─sockets.target @11.540s + └─snap.lxd.daemon.unix.socket @24.376s + └─sysinit.target @10.825s + └─cloud-init.service @8.432s +2.267s + └─systemd-networkd-wait-online.service @6.467s +1.935s + └─systemd-networkd.service @6.347s +112ms + └─network-pre.target @6.328s +
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
Test plan updated for Jammy too ** Description changed: After the kernel roll to linux-gcp-5.15 to version 5.15.0-1051.59_20.04.1 the public cloud team pre publication test were failing on our snap_preseed_optimized test which checks to ensure that snaps are preseeded correctly This test checks the output of `snap debug seeding` to assert `seed- completion` is present and not empty. `` ❯ snap debug seeding seeded:true preseeded: true image-preseeding: 39.367s seed-completion: 1.335s ``` If `/var/lib/snapd/seed/seed.yaml` exists it also asserts that `preseeded` is present and not empty. With the recent kernel update this test is failing which indicates a kernel feature mismatch between the running kernel and the feature set hard-coded in livecd-rootfs for this image. Boot will be slowed by ~200ms until this is resolved in livecd-rootfs. This solution is to add a 5.15 apparmor configuration to the focal branch of livecd-rootfs The issue is also present with the recent 5.15 kernels in Jammy. Related bugs LP: #2031943 and LP: #2045384 [ Impact ] Boot will be slowed by ~200ms until this is resolved in livecd-rootfs [ Test Plan ] - * build any focal cloud image with HWE 5.15 kernel + * for focal build any cloud image with preseeded snaps with HWE 5.15 kernel + * for jammy build any cloud image with preseeded snaps with up to date 5.15 kernel * boot * run `snap debug preseed` * assert the test described above passes [ Where problems could occur ] * Similar patches already exist for later releases 6.2, 6.5 kernel etc. and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057559] Re: Rename the ubuntu-advantage-tools package
Subscribing ubuntu-release as per FFE policy. This bug affects noble cloud image release ** Also affects: update-manager (Ubuntu Noble) Importance: Wishlist Assignee: Calvin Mwadime Makokha (calvinmwadime) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057559 Title: Rename the ubuntu-advantage-tools package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2057559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057651] Re: Rename the ubuntu-advantage-tools package
Subscribing ubuntu-release as per FFE policy. This bug affects noble cloud image release ** Also affects: wsl-pro-service (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057651 Title: Rename the ubuntu-advantage-tools package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2057651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057671] Re: Rename the ubuntu-advantage-tools package
Subscribing ubuntu-release as per FFE policy. This bug affects noble cloud image release ** Also affects: software-properties (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057671 Title: Rename the ubuntu-advantage-tools package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2057671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057674] Re: Rename the ubuntu-advantage-tools package
Subscribing ubuntu-release as per FFE policy. This bug affects noble cloud image release ** Also affects: ubuntu-advantage-desktop-daemon (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057674 Title: Rename the ubuntu-advantage-tools package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/2057674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057705] [NEW] package firefox 123.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Public bug reported: ==> Checking connectivity with the snap store ==> Installing the firefox snap 2024-03-12T20:49:44Z INFO Waiting for automatic snapd restart... error: cannot perform the following tasks: - Run hook connect-plug-host-hunspell of snap "firefox" (run hook "connect-plug-host-hunspell": cannot perform operation: mount --rbind /home /tmp/snap.rootfs_b1St4v//home: Permission denied) dpkg: error processing archive /tmp/apt-dpkg-install-p02kAs/00-firefox_1snap1-0ubuntu2_amd64.deb (--unpack): new firefox package pre-installation script subprocess returned error exit status 1 Please restart all running instances of firefox, or you will experience problems. Preparing to unpack .../01-fonts-droid-fallback_6.0.1r16-1.1build1_all.deb ... Unpacking fonts-droid-fallback (1:6.0.1r16-1.1build1) over (1:6.0.1r16-1.1) ... Preparing to unpack .../02-fonts-kacst_2.01+mry-15_all.deb ... Unpacking fonts-kacst (2.01+mry-15) over (2.01+mry-14) ... Preparing to unpack .../03-fonts-kalapi_1.0-4_all.deb ... Unpacking fonts-kalapi (1.0-4) over (1.0-3) ... Preparing to unpack .../04-fonts-lato_2.0-2.1_all.deb ... Unpacking fonts-lato (2.0-2.1) over (2.0-2) ... ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/firefox.0.crash' Preparing to unpack .../05-fonts-smc-anjalioldlipi_7.1.2-2_all.deb ... Unpacking fonts-smc-anjalioldlipi (7.1.2-2) over (7.1.2-1) ... Preparing to unpack .../06-fonts-smc-rachana_7.0.2-1build1_all.deb ... Unpacking fonts-smc-rachana (7.0.2-1build1) over (7.0.2-1) ... Preparing to unpack .../07-fonts-smc-dyuthi_3.0.2-2_all.deb ... Unpacking fonts-smc-dyuthi (3.0.2-2) over (3.0.2-1) ... Preparing to unpack .../08-fonts-smc-chilanka_1.540-1_all.deb ... Unpacking fonts-smc-chilanka (1.540-1) over (1.400-1) ... Preparing to unpack .../09-fonts-smc-gayathri_1.110-2-1_all.deb ... Unpacking fonts-smc-gayathri (1.110-2-1) over (1.100-1) ... Preparing to unpack .../10-fonts-smc-karumbi_1.1.2-2_all.deb ... Unpacking fonts-smc-karumbi (1.1.2-2) over (1.1.2-1) ... Preparing to unpack .../11-fonts-smc-keraleeyam_3.0.2-2_all.deb ... Unpacking fonts-smc-keraleeyam (3.0.2-2) over (3.0.2-1) ... Preparing to unpack .../12-fonts-smc-manjari_2.000-3_all.deb ... Unpacking fonts-smc-manjari (2.000-3) over (1.710-1) ... Preparing to unpack .../13-fonts-smc_7.2_all.deb ... Unpacking fonts-smc (1:7.2) over (1:7.1) ... Errors were encountered while processing: /tmp/apt-dpkg-install-p02kAs/00-firefox_1snap1-0ubuntu2_amd64.deb Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 123.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-100.110~20.04.1-generic 5.15.143 Uname: Linux 5.15.0-100-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair blackmagic_io AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm4235 F pulseaudio /dev/snd/controlC0: lightdm4235 F pulseaudio BuildID: 20240304104836 CasperMD5CheckResult: unknown Channel: Unavailable Date: Tue Mar 12 20:50:53 2024 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2021-07-04 (982 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.11 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 123.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2024-03-12 (0 days ago) dmi.bios.date: 03/02/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4101 dmi.board.asset.tag: Default string dmi.board.name: Pro WS X570-ACE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd03/02/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSX570-ACE:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU
[Bug 2056671] [NEW] Gnome Shell Screencast does not capture mouse pointer
Public bug reported: Press the Print Screen button, select the Record Screen option and then press capture [1]. The screen recording works as expected however does not display the mouse cursor making it hard to use the screen capture for a tutorial without using a third-party capture device. The screen cast should capture the mouse pointer by default. Or [1] you include an option to show/hide the mouse pointer in the recording. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 12:04:47 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06b9] InstallationDate: Installed on 2024-03-10 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. OptiPlex 7040 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=6b60e9f2-5ca2-4299-85bd-4fb992af91dd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2022 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 096JG8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd07/14/2022:br1.24:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn096JG8:rvrA01:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble reproducible ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056671 Title: Gnome Shell Screencast does not capture mouse pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2056671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056475] [NEW] aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation
Public bug reported: SRU Justification: [Impact] In Ubuntu AMIs for x86 and Graviton based EC2 instances, the standard Ubuntu AMI comes without IRQ moderation enabled for ENA, which for our latest generation instances with networking heavy workloads is up to a 25% performance regression (i.e. NGINX in a load-balancing configuration). [Fix] The mainline Linux kernel will now support IRQ moderation by default for ENA in the 6.9 kernel release via this patch: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/amazon/ena?id=50d7a2660579889fba28b7e4543d4ce85aa2311b [Test Plan] AWS tested [Where problems could occur] By enabling adaptive coalescing, the default interrupt behaviour will by changed to be more adaptive, which shows improvements on heavy network workloads, but my change the behaviour and performance on other network workloads differently. Rather than handling the interrupts based off of a fixed amount of time elapsed, it will change to an adaptive based approach. There should be no negative impact on light workloads, and a positive impact on heavy work loads. If there is an impact though, this option can be disabled via the ethtool command. [Other Info] SF: 00380449 ** Affects: linux-aws (Ubuntu) Importance: Undecided Assignee: Philip Cox (philcox) Status: In Progress ** Affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: In Progress ** Affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux-aws (Ubuntu Mantic) Importance: Undecided Status: In Progress ** Affects: linux-aws (Ubuntu Noble) Importance: Undecided Assignee: Philip Cox (philcox) Status: In Progress ** Also affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Noble) Importance: Undecided Assignee: Philip Cox (philcox) Status: New ** Also affects: linux-aws (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Noble) 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/2056475 Title: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2056475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056078] Re: 6.8 Kernel AppArmor Feature Missing on Noble
Subscribing ubuntu-release as per FFE policy. This bug will block noble cloud image release ** Also affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056078 Title: 6.8 Kernel AppArmor Feature Missing on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2056078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051727] Re: tcp: Add memory barrier to tcp_push()
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051727 Title: tcp: Add memory barrier to tcp_push() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
