[Touch-packages] [Bug 2052951] [NEW] ncurses/i386 autopkgtest failure
Public bug reported: ncurses fails to pass its autopkgtests on i386: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/i386/n/ncurses/20240212_101858_8f6ad@/log.gz ** Affects: ncurses (Ubuntu) Importance: Undecided Status: New ** Description changed: - ncurses fails to pass it's autopkgtests on i386: + ncurses fails to pass its autopkgtests on i386: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/i386/n/ncurses/20240212_101858_8f6ad@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/2052951 Title: ncurses/i386 autopkgtest failure Status in ncurses package in Ubuntu: New Bug description: ncurses fails to pass its autopkgtests on i386: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/i386/n/ncurses/20240212_101858_8f6ad@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/2052951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052951] Re: ncurses/i386 autopkgtest failure
This test is new in the latest proposed version, and is incompatible with cross-arch Ubuntu i386 autopkgtest, so the following patch just disables it. ** Patch added: "1-6.4+20240113-1ubuntu1.diff" https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/2052951/+attachment/5745955/+files/1-6.4+20240113-1ubuntu1.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/2052951 Title: ncurses/i386 autopkgtest failure Status in ncurses package in Ubuntu: New Bug description: ncurses fails to pass its autopkgtests on i386: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/i386/n/ncurses/20240212_101858_8f6ad@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/2052951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052951] Re: ncurses/i386 autopkgtest failure
@juliank Testing was done by running autopkgtest locally against the source package only (-B, --no-built-binaries), I didn't rebuild the binaries. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/2052951 Title: ncurses/i386 autopkgtest failure Status in ncurses package in Ubuntu: New Bug description: ncurses fails to pass its autopkgtests on i386: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/i386/n/ncurses/20240212_101858_8f6ad@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/2052951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040113] [NEW] gdb crashes upon `run` on some arm64 machines
Public bug reported: gdb 13.1 shipped in lunar, is affected by a bug where it crashes upon `run` on some arm64 machines (confirmed on Apple M-series, both under hypervisor and bare metal, everything else with PAC should also be affected). It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- patches/20230316103904.1947447-1-luis.mach...@arm.com/. Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth-registers.patch`. ** Affects: gdb (Ubuntu) Importance: Low Status: New ** Changed in: gdb (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2040113 Title: gdb crashes upon `run` on some arm64 machines Status in gdb package in Ubuntu: New Bug description: gdb 13.1 shipped in lunar, is affected by a bug where it crashes upon `run` on some arm64 machines (confirmed on Apple M-series, both under hypervisor and bare metal, everything else with PAC should also be affected). It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- patches/20230316103904.1947447-1-luis.mach...@arm.com/. Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth-registers.patch`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040113] Re: gdb crashes upon `run` on some arm64 machines
** Patch added: "aarch64-pauth-registers.patch" https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+attachment/5712292/+files/aarch64-pauth-registers.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2040113 Title: gdb crashes upon `run` on some arm64 machines Status in gdb package in Ubuntu: New Bug description: gdb 13.1 shipped in lunar, is affected by a bug where it crashes upon `run` on some arm64 machines (confirmed on Apple M-series, both under hypervisor and bare metal, everything else with PAC should also be affected). It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- patches/20230316103904.1947447-1-luis.mach...@arm.com/. Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth-registers.patch`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu
** Also affects: mesa (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Noble) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Mantic: New Status in mesa source package in Noble: Confirmed Bug description: This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu
This integrates the patch for this bug from upstream. ** Patch added: "1-23.2.1-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2038834/+attachment/5717150/+files/1-23.2.1-1ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Mantic: New Status in mesa source package in Noble: Confirmed Bug description: This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu
** Description changed: - This was reported by someone else upstream and is already fixed by - https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. + + [ Impact ] + * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs + + * This was reported by someone else upstream and is already fixed by +https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. + + [ Test Plan ] + + * I've tested the patch on an affected macOS host running Ubuntu in UTM with +OpenGL enabled on both Mantic and Noble VMs. + + * Anyone else can do the same on an affected host by simply installing the +patched package and booting to the desktop. + + [ Where problems could occur ] + + * This patch fixes an upstream mesa regression which caused libvirglrendrer to +crash on the host side. + + * This makes a non-working use case work, VirGL on affected hosts cannot +regress as it simply didn't work before. + + * Risk of breakage is mainly from other packages possible affected by a mesa +rebuild. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Mantic: New Status in mesa source package in Noble: Confirmed Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040113] Re: gdb crashes upon `run` on some arm64 machines
** Also affects: gdb (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2040113 Title: gdb crashes upon `run` on some arm64 machines Status in gdb package in Ubuntu: New Status in gdb source package in Lunar: New Bug description: gdb 13.1 shipped in lunar, is affected by a bug where it crashes upon `run` on some arm64 machines (confirmed on Apple M-series, both under hypervisor and bare metal, everything else with PAC should also be affected). It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- patches/20230316103904.1947447-1-luis.mach...@arm.com/. Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth-registers.patch`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040113] Re: gdb crashes upon `run` on some arm64 machines
** Description changed: - gdb 13.1 shipped in lunar, is affected by a bug where it crashes upon - `run` on some arm64 machines (confirmed on Apple M-series, both under - hypervisor and bare metal, everything else with PAC should also be - affected). + [ Impact ] - It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- - patches/20230316103904.1947447-1-luis.mach...@arm.com/. + * gdb 13.1 as shipped in lunar is affected by a bug where it crashes upon `run` +on some arm64 machines (confirmed on Apple M-series, both under hypervisor +and bare metal, everything else with PAC should also be affected). - Debian bookworm's gdb_13.1-3 also includes the same patch as - `aarch64-pauth-registers.patch`. + * It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- +patches/20230316103904.1947447-1-luis.mach...@arm.com/. + + * Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth- +registers.patch`. + + [ Test Plan ] + + * This diff is confirmed to fix gdb 13.1 in lunar on my arm64 laptop. + + * This could be tested by running any program under lunar's gdb +on any ARM64 PAC machine. + + [ Where problems could occur ] + + * Problems aren't particularly likely as the exact patch was included in the +last Debian stable. + + * In theory, a gdb rebuild could possibly cause breakage. ** Patch added: "1-13.1-2ubuntu2.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+attachment/5719723/+files/1-13.1-2ubuntu2.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2040113 Title: gdb crashes upon `run` on some arm64 machines Status in gdb package in Ubuntu: New Status in gdb source package in Lunar: New Bug description: [ Impact ] * gdb 13.1 as shipped in lunar is affected by a bug where it crashes upon `run` on some arm64 machines (confirmed on Apple M-series, both under hypervisor and bare metal, everything else with PAC should also be affected). * It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- patches/20230316103904.1947447-1-luis.mach...@arm.com/. * Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth- registers.patch`. [ Test Plan ] * This diff is confirmed to fix gdb 13.1 in lunar on my arm64 laptop. * This could be tested by running any program under lunar's gdb on any ARM64 PAC machine. [ Where problems could occur ] * Problems aren't particularly likely as the exact patch was included in the last Debian stable. * In theory, a gdb rebuild could possibly cause breakage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu
** Changed in: mesa (Ubuntu Noble) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Mantic: New Status in mesa source package in Noble: Fix Released Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2041830] Re: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset
** Changed in: gdb (Ubuntu) Assignee: (unassigned) => Mate Kukri (mkukri) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2041830 Title: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset Status in gdb package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdb. This problem was most recently seen with package version 14.0.50.20230907-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e052ff0ad61743594bf64a85ca1e18b6e353025d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2041830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu
Hi @sergiodj, I believe it was already uploaded, and is currently in the unapproved queue: https://launchpadlibrarian.net/697888277/mesa_23.2.1-1ubuntu3_23.2.1-1ubuntu3.1.diff.gz The difference to noble is purely the version number being ubuntu3.1 instead of ubuntu4. Mate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Mantic: New Status in mesa source package in Noble: Fix Released Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040113] Re: gdb crashes upon `run` on some arm64 machines
I can confirm that upgrading from 13.1-2ubuntu2 to 13.1-2ubuntu2.1 makes gdb functional on my ARM64 machine. Every program I've tried to debug previously crashed gdb immediately upon `run`. Appears to be fully functional now on a variety of binaries. ** Tags removed: verification-needed verification-needed-lunar ** Tags added: verification-done verification-done-lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2040113 Title: gdb crashes upon `run` on some arm64 machines Status in gdb package in Ubuntu: Fix Released Status in gdb source package in Lunar: Fix Committed Bug description: [ Impact ] * gdb 13.1 as shipped in lunar is affected by a bug where it crashes upon `run` on some arm64 machines (confirmed on Apple M-series, both under hypervisor and bare metal, everything else with PAC should also be affected). * It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- patches/20230316103904.1947447-1-luis.mach...@arm.com/. * Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth- registers.patch`. [ Test Plan ] * This diff is confirmed to fix gdb 13.1 in lunar on my arm64 laptop. * This could be tested by running any program under lunar's gdb on any ARM64 PAC machine. [ Where problems could occur ] * Problems aren't particularly likely as the exact patch was included in the last Debian stable. * In theory, a gdb rebuild could possibly cause breakage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040113] Re: gdb crashes upon `run` on some arm64 machines
The regression above was due to a flaky test, and seems not to be a real regression. It has passed when re-running. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2040113 Title: gdb crashes upon `run` on some arm64 machines Status in gdb package in Ubuntu: Fix Released Status in gdb source package in Lunar: Fix Committed Bug description: [ Impact ] * gdb 13.1 as shipped in lunar is affected by a bug where it crashes upon `run` on some arm64 machines (confirmed on Apple M-series, both under hypervisor and bare metal, everything else with PAC should also be affected). * It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- patches/20230316103904.1947447-1-luis.mach...@arm.com/. * Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth- registers.patch`. [ Test Plan ] * This diff is confirmed to fix gdb 13.1 in lunar on my arm64 laptop. * This could be tested by running any program under lunar's gdb on any ARM64 PAC machine. [ Where problems could occur ] * Problems aren't particularly likely as the exact patch was included in the last Debian stable. * In theory, a gdb rebuild could possibly cause breakage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2041830] Re: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset
I cannot re-produce this unfortunately. If someone manages to and could describe the conditions that lead to this and/or attach a core file, it could perhaps move forward. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2041830 Title: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset Status in gdb package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdb. This problem was most recently seen with package version 14.0.50.20230907-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e052ff0ad61743594bf64a85ca1e18b6e353025d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2041830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2041830] Re: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset
I couldn't reproduce the TeamViewer crash in the first place. I've also tried running TeamViewer under gdb, but it works fine for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2041830 Title: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset Status in gdb package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdb. This problem was most recently seen with package version 14.0.50.20230907-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e052ff0ad61743594bf64a85ca1e18b6e353025d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2041830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044269] [NEW] gdb broken on armhf
Public bug reported: Trying to step through an armhf program in gdb throws the following internal error: ``` /build/gdb-U0UiMP/gdb-14.0.50.20230907/gdb/displaced-stepping.c:283: internal-error: copy_insn_closure_by_addr: Assertion `buffer.copy_insn_closure.get () != nullpt r' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. - Backtrace - 0xab234d ??? 0xdb2a93 ??? 0xdb2cf5 ??? 0xf16145 ??? 0xb29e4f ??? 0xa7d24d ??? 0xa7d3b5 ??? 0xb272a3 ??? 0xb2798b ??? 0xd64943 ??? 0xd653f1 ??? 0xd7beed ??? 0xd6525f ??? 0xd7800f ??? 0xd66105 ??? 0xb8dddf ??? 0xbdfcd1 ??? 0xbf1243 ??? 0xa7ffeb ??? 0xf17031 ??? 0xc26291 ??? 0xc284a9 ??? 0xa125c1 ??? 0x40c33699 __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 0x40c3373d __libc_start_main_impl ./csu/libc-start.c:360 - /build/gdb-U0UiMP/gdb-14.0.50.20230907/gdb/displaced-stepping.c:283: internal-error: copy_insn_closure_by_addr: Assertion `buffer.copy_insn_closure.get () != nullpt r' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) Quit ``` ** Affects: gdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2044269 Title: gdb broken on armhf Status in gdb package in Ubuntu: New Bug description: Trying to step through an armhf program in gdb throws the following internal error: ``` /build/gdb-U0UiMP/gdb-14.0.50.20230907/gdb/displaced-stepping.c:283: internal-error: copy_insn_closure_by_addr: Assertion `buffer.copy_insn_closure.get () != nullpt r' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. - Backtrace - 0xab234d ??? 0xdb2a93 ??? 0xdb2cf5 ??? 0xf16145 ??? 0xb29e4f ??? 0xa7d24d ??? 0xa7d3b5 ??? 0xb272a3 ??? 0xb2798b ??? 0xd64943 ??? 0xd653f1 ??? 0xd7beed ??? 0xd6525f ??? 0xd7800f ??? 0xd66105 ??? 0xb8dddf ??? 0xbdfcd1 ??? 0xbf1243 ??? 0xa7ffeb ??? 0xf17031 ??? 0xc26291 ??? 0xc284a9 ??? 0xa125c1 ??? 0x40c33699 __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 0x40c3373d __libc_start_main_impl ./csu/libc-start.c:360 - /build/gdb-U0UiMP/gdb-14.0.50.20230907/gdb/displaced-stepping.c:283: internal-error: copy_insn_closure_by_addr: Assertion `buffer.copy_insn_closure.get () != nullpt r' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) Quit ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2044269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044269] Re: gdb broken on armhf
This is armhf gdb running in an lxc container on an arm64 kernel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2044269 Title: gdb broken on armhf Status in gdb package in Ubuntu: New Bug description: Trying to step through an armhf program in gdb throws the following internal error: ``` /build/gdb-U0UiMP/gdb-14.0.50.20230907/gdb/displaced-stepping.c:283: internal-error: copy_insn_closure_by_addr: Assertion `buffer.copy_insn_closure.get () != nullpt r' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. - Backtrace - 0xab234d ??? 0xdb2a93 ??? 0xdb2cf5 ??? 0xf16145 ??? 0xb29e4f ??? 0xa7d24d ??? 0xa7d3b5 ??? 0xb272a3 ??? 0xb2798b ??? 0xd64943 ??? 0xd653f1 ??? 0xd7beed ??? 0xd6525f ??? 0xd7800f ??? 0xd66105 ??? 0xb8dddf ??? 0xbdfcd1 ??? 0xbf1243 ??? 0xa7ffeb ??? 0xf17031 ??? 0xc26291 ??? 0xc284a9 ??? 0xa125c1 ??? 0x40c33699 __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 0x40c3373d __libc_start_main_impl ./csu/libc-start.c:360 - /build/gdb-U0UiMP/gdb-14.0.50.20230907/gdb/displaced-stepping.c:283: internal-error: copy_insn_closure_by_addr: Assertion `buffer.copy_insn_closure.get () != nullpt r' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) Quit ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2044269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043713] Re: armhf autopkgtests fail due to TestApportValgrind.test_valgrind_min_installed
It is sort of a known issue, you need a no change rebuild when dpkg 1.22.1ubuntu3 hits proposed. That is libselinux needs a rebuild. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043713 Title: armhf autopkgtests fail due to TestApportValgrind.test_valgrind_min_installed Status in apport package in Ubuntu: New Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 638s === FAILURES === 638s TestApportValgrind.test_valgrind_min_installed 638s 638s self = 638s 638s def test_valgrind_min_installed(self): 638s """Valgrind is installed and recent enough.""" 638s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 638s (ret, out, err) = self._call(cmd) 638s > self.assertEqual(err, "") 638s E AssertionError: "==2474== Invalid write of size 4\n==2474[1064 chars]= \n" != '' 638s E Diff is 1134 characters long. Set self.maxDiff to None to see it. 638s 638s tests/integration/test_apport_valgrind.py:43: AssertionError This could be related to valgrind functionality being different on armhf, it could also be related to integer sizes internally on armhf. I haven't looked too deeply into it. [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043713] Re: armhf autopkgtests fail due to TestApportValgrind.test_valgrind_min_installed
@adrien-n based on the errors it looks like the current libselinux was built with the bad flag too -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043713 Title: armhf autopkgtests fail due to TestApportValgrind.test_valgrind_min_installed Status in apport package in Ubuntu: New Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 638s === FAILURES === 638s TestApportValgrind.test_valgrind_min_installed 638s 638s self = 638s 638s def test_valgrind_min_installed(self): 638s """Valgrind is installed and recent enough.""" 638s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 638s (ret, out, err) = self._call(cmd) 638s > self.assertEqual(err, "") 638s E AssertionError: "==2474== Invalid write of size 4\n==2474[1064 chars]= \n" != '' 638s E Diff is 1134 characters long. Set self.maxDiff to None to see it. 638s 638s tests/integration/test_apport_valgrind.py:43: AssertionError This could be related to valgrind functionality being different on armhf, it could also be related to integer sizes internally on armhf. I haven't looked too deeply into it. [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043713] Re: armhf autopkgtests fail due to TestApportValgrind.test_valgrind_min_installed
Ive asked an upload of a rebuild of libselinux on IRC: code.launchpad.net/~mkukri/ubuntu/+source/libselinux/+git/libselinux/+merge/456199 along with the other packages we had affected. There should be someone on it. And after that goes up, this should be fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043713 Title: armhf autopkgtests fail due to TestApportValgrind.test_valgrind_min_installed Status in apport package in Ubuntu: New Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 638s === FAILURES === 638s TestApportValgrind.test_valgrind_min_installed 638s 638s self = 638s 638s def test_valgrind_min_installed(self): 638s """Valgrind is installed and recent enough.""" 638s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 638s (ret, out, err) = self._call(cmd) 638s > self.assertEqual(err, "") 638s E AssertionError: "==2474== Invalid write of size 4\n==2474[1064 chars]= \n" != '' 638s E Diff is 1134 characters long. Set self.maxDiff to None to see it. 638s 638s tests/integration/test_apport_valgrind.py:43: AssertionError This could be related to valgrind functionality being different on armhf, it could also be related to integer sizes internally on armhf. I haven't looked too deeply into it. [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044506] Re: issues on armhf with -fstack-clash-protection
We were seeing various autopkgtest failures related to the packages above. Mostly stemming from the fact that valgrind throws errors when running binaries compiled with the -fstack-clash-protection option. There are earlier reports of this at: https://bugzilla.redhat.com/show_bug.cgi?id=1522678 ** Also affects: libxml2 (Ubuntu) Importance: Undecided Status: New ** Also affects: libarchive (Ubuntu) Importance: Undecided Status: New ** Also affects: gnutls28 (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Red Hat Bugzilla #1522678 https://bugzilla.redhat.com/show_bug.cgi?id=1522678 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/2044506 Title: issues on armhf with -fstack-clash-protection Status in gnutls28 package in Ubuntu: New Status in libarchive package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in libxml2 package in Ubuntu: New Bug description: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/2044506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu
The autopkgtest regression above are due to armhf autopkgtest runner faults. The tests have been re-triggered and should succeed. Confirmed to fix VirGL graphics acceleration on my previously affected machine. ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Mantic: Fix Committed Status in mesa source package in Noble: Fix Released Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2041830] Re: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset
** Changed in: gdb (Ubuntu) Assignee: Mate Kukri (mkukri) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2041830 Title: /usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset Status in gdb package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdb. This problem was most recently seen with package version 14.0.50.20230907-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e052ff0ad61743594bf64a85ca1e18b6e353025d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2041830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043713] Re: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4
** Changed in: apport (Ubuntu) Status: New => In Progress ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Mate Kukri (mkukri) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043713 Title: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4 Status in apport package in Ubuntu: In Progress Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 517s === FAILURES === 517s TestApportValgrind.test_valgrind_min_installed 517s 517s self = 517s 517s def test_valgrind_min_installed(self): 517s """Valgrind is installed and recent enough.""" 517s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 517s (ret, out, err) = self._call(cmd) 517s > self.assertEqual(err, "") 517s E AssertionError: "==2567== Invalid write of size 4\n==2567[1064 chars]= \n" != '' 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4843040: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7e4 is on thread 1's stack 517s E - ==2567== 64 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F96: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a758 is on thread 1's stack 517s E - ==2567== 160 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x484958C: selinuxfs_exists (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7bc is on thread 1's stack 517s E - ==2567== 48 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F0E: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a690 is on thread 1's stack 517s E - ==2567== 16 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842E62: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a6a0 is on thread 1's stack 517s E - ==2567== 8 bytes below stack pointer 517s E - ==2567== 517s 517s tests/integration/test_apport_valgrind.py:45: AssertionError 517s === warnings summary === This is caused by -fstack-clash-protection. Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1522678 [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043713] Re: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4
It should be fixed by the last libselinux upload which has migrated, but keeping it "In Progress" until a successful autopkgtest run of apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043713 Title: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4 Status in apport package in Ubuntu: In Progress Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 517s === FAILURES === 517s TestApportValgrind.test_valgrind_min_installed 517s 517s self = 517s 517s def test_valgrind_min_installed(self): 517s """Valgrind is installed and recent enough.""" 517s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 517s (ret, out, err) = self._call(cmd) 517s > self.assertEqual(err, "") 517s E AssertionError: "==2567== Invalid write of size 4\n==2567[1064 chars]= \n" != '' 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4843040: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7e4 is on thread 1's stack 517s E - ==2567== 64 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F96: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a758 is on thread 1's stack 517s E - ==2567== 160 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x484958C: selinuxfs_exists (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7bc is on thread 1's stack 517s E - ==2567== 48 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F0E: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a690 is on thread 1's stack 517s E - ==2567== 16 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842E62: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a6a0 is on thread 1's stack 517s E - ==2567== 8 bytes below stack pointer 517s E - ==2567== 517s 517s tests/integration/test_apport_valgrind.py:45: AssertionError 517s === warnings summary === This is caused by -fstack-clash-protection. Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1522678 [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043713] Re: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4
** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043713 Title: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4 Status in apport package in Ubuntu: Fix Released Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 517s === FAILURES === 517s TestApportValgrind.test_valgrind_min_installed 517s 517s self = 517s 517s def test_valgrind_min_installed(self): 517s """Valgrind is installed and recent enough.""" 517s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 517s (ret, out, err) = self._call(cmd) 517s > self.assertEqual(err, "") 517s E AssertionError: "==2567== Invalid write of size 4\n==2567[1064 chars]= \n" != '' 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4843040: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7e4 is on thread 1's stack 517s E - ==2567== 64 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F96: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a758 is on thread 1's stack 517s E - ==2567== 160 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x484958C: selinuxfs_exists (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7bc is on thread 1's stack 517s E - ==2567== 48 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F0E: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a690 is on thread 1's stack 517s E - ==2567== 16 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842E62: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a6a0 is on thread 1's stack 517s E - ==2567== 8 bytes below stack pointer 517s E - ==2567== 517s 517s tests/integration/test_apport_valgrind.py:45: AssertionError 517s === warnings summary === This is caused by -fstack-clash-protection. Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1522678 [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038834] [NEW] GPU acceleration via VirGL is broken in qemu
Public bug reported: This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Milestone: None => ubuntu-23.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in mesa package in Ubuntu: New Bug description: This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2038834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu
** Changed in: mesa (Ubuntu) Milestone: ubuntu-23.10 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in mesa package in Ubuntu: New Bug description: This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2038834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2084460] Re: [SRU] Please enable frame-pointer on Noble
nspr in noble is a build1 of the Debian package. The only delta between noble and oracular are the frame pointer changes, this patch is a backport of the oracular changes as nspr - `2:4.35-1.1ubuntu1~24.04`. Please see my dev PPA for a test build: https://launchpad.net/~mkukri/+archive/ubuntu/dev/+packages ** Description changed: [ Impact ] In order to help developers with profiling, Ubuntu enabled frame- pointers for packages in the main archive. https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame- pointers-by-default The `Affects` packages were missed due to the packaging issues. These have been fixed on Oracular and can now be ported to Noble. [ Test Plan ] Look at the DW_AT_producer in the associated debug ELF file for flags. -fno-omit-frame-pointer should be present after the fix. The following scripts can be used as a reference https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c + The nspr package comes with a build time test-suite that should ensure + some level of functionality from the re-built library. + + override_dh_auto_test: + ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),) + $(MAKE) -C nspr/pr/tests + $(MAKE) -C nspr/lib/tests + # Skip gethost because it needs DNS, and thus networking. + # Skip fdcach, peek and vercheck because they fail. + # Skip socket because it freezes. + # Skip getproto because it fails on some buildds. + # Skip nblayer because it freezes on armel. + cd nspr/pr/tests && grep -v '^\(fdcach\|gethost\|getproto\|nblayer\|peek\|socket\|vercheck\)$$' ./runtests.sh | sh - $(CURDIR)/nspr/dist + cd nspr/lib/tests && LD_LIBRARY_PATH=$(CURDIR)/nspr/dist/bin$(addprefix :,$(LD_LIBRARY_PATH)) ./base64t + cd nspr/lib/tests && LD_LIBRARY_PATH=$(CURDIR)/nspr/dist/bin$(addprefix :,$(LD_LIBRARY_PATH)) ./string + endif + + [ Where problems could occur ] No source changes are made. The packaging fixes have enabled other security hardening flags. This could have unintended effects. [ Other Info ] changes in dpkg have been made to make sure frame-pointers are not enabled on s390x and ppc64el. Bug reference with similar SRU - https://bugs.launchpad.net/ubuntu/+source/authbind/+bug/2081707 ** Patch added: "nspr_4.35-1.1ubuntu1~24.04.diff" https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2084460/+attachment/5828201/+files/nspr_4.35-1.1ubuntu1~24.04.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nspr in Ubuntu. https://bugs.launchpad.net/bugs/2084460 Title: [SRU] Please enable frame-pointer on Noble Status in nspr package in Ubuntu: New Bug description: [ Impact ] In order to help developers with profiling, Ubuntu enabled frame- pointers for packages in the main archive. https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame- pointers-by-default The `Affects` packages were missed due to the packaging issues. These have been fixed on Oracular and can now be ported to Noble. [ Test Plan ] Look at the DW_AT_producer in the associated debug ELF file for flags. -fno-omit-frame-pointer should be present after the fix. The following scripts can be used as a reference https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c The nspr package comes with a build time test-suite that should ensure some level of functionality from the re-built library. override_dh_auto_test: ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),) $(MAKE) -C nspr/pr/tests $(MAKE) -C nspr/lib/tests # Skip gethost because it needs DNS, and thus networking. # Skip fdcach, peek and vercheck because they fail. # Skip socket because it freezes. # Skip getproto because it fails on some buildds. # Skip nblayer because it freezes on armel. cd nspr/pr/tests && grep -v '^\(fdcach\|gethost\|getproto\|nblayer\|peek\|socket\|vercheck\)$$' ./runtests.sh | sh - $(CURDIR)/nspr/dist cd nspr/lib/tests && LD_LIBRARY_PATH=$(CURDIR)/nspr/dist/bin$(addprefix :,$(LD_LIBRARY_PATH)) ./base64t cd nspr/lib/tests && LD_LIBRARY_PATH=$(CURDIR)/nspr/dist/bin$(addprefix :,$(LD_LIBRARY_PATH)) ./string endif [ Where problems could occur ] No source changes are made. The packaging fixes have enabled other security hardening flags. This could have unintended effects. [ Other Info ] changes in dpkg have been made to make sure frame-pointers are not enabled on
[Touch-packages] [Bug 2084460] [NEW] [SRU] Please enable frame-pointer on Noble Edit
Public bug reported: [ Impact ] In order to help developers with profiling, Ubuntu enabled frame- pointers for packages in the main archive. https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame- pointers-by-default The `Affects` packages were missed due to the packaging issues. These have been fixed on Oracular and can now be ported to Noble. [ Test Plan ] Look at the DW_AT_producer in the associated debug ELF file for flags. -fno-omit-frame-pointer should be present after the fix. The following scripts can be used as a reference https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c [ Where problems could occur ] No source changes are made. The packaging fixes have enabled other security hardening flags. This could have unintended effects. [ Other Info ] changes in dpkg have been made to make sure frame-pointers are not enabled on s390x and ppc64el. Bug reference with similar SRU - https://bugs.launchpad.net/ubuntu/+source/authbind/+bug/2081707 ** Affects: nspr (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nspr in Ubuntu. https://bugs.launchpad.net/bugs/2084460 Title: [SRU] Please enable frame-pointer on Noble Edit Status in nspr package in Ubuntu: New Bug description: [ Impact ] In order to help developers with profiling, Ubuntu enabled frame- pointers for packages in the main archive. https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame- pointers-by-default The `Affects` packages were missed due to the packaging issues. These have been fixed on Oracular and can now be ported to Noble. [ Test Plan ] Look at the DW_AT_producer in the associated debug ELF file for flags. -fno-omit-frame-pointer should be present after the fix. The following scripts can be used as a reference https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c [ Where problems could occur ] No source changes are made. The packaging fixes have enabled other security hardening flags. This could have unintended effects. [ Other Info ] changes in dpkg have been made to make sure frame-pointers are not enabled on s390x and ppc64el. Bug reference with similar SRU - https://bugs.launchpad.net/ubuntu/+source/authbind/+bug/2081707 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2084460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2084460] Re: [SRU] Please enable frame-pointer on Noble
** Summary changed: - [SRU] Please enable frame-pointer on Noble Edit + [SRU] Please enable frame-pointer on Noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nspr in Ubuntu. https://bugs.launchpad.net/bugs/2084460 Title: [SRU] Please enable frame-pointer on Noble Status in nspr package in Ubuntu: New Bug description: [ Impact ] In order to help developers with profiling, Ubuntu enabled frame- pointers for packages in the main archive. https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame- pointers-by-default The `Affects` packages were missed due to the packaging issues. These have been fixed on Oracular and can now be ported to Noble. [ Test Plan ] Look at the DW_AT_producer in the associated debug ELF file for flags. -fno-omit-frame-pointer should be present after the fix. The following scripts can be used as a reference https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c [ Where problems could occur ] No source changes are made. The packaging fixes have enabled other security hardening flags. This could have unintended effects. [ Other Info ] changes in dpkg have been made to make sure frame-pointers are not enabled on s390x and ppc64el. Bug reference with similar SRU - https://bugs.launchpad.net/ubuntu/+source/authbind/+bug/2081707 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2084460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2100783] Re: systemd-boot does not support an externally provided initrd on UKI
The overall security model of the CA on which we would sign such UKIs already allows loading external initrds without a UKI being used. This would be for the simple convenience of being able to use the stub purely as a (temporary) mechanism for signing dtbs and the kernel together, not to provide any of the added security of regular systemd- stub. And since you won't weaken the security of the CA itself, and because such an initrd-less UKI will have different TPM hashes as the one that relies on the verified initrd, I don't see any real security argument here other than systemd wishing to distance itself from unsigned initrds fully. If that is the only argument remaning, we should probably ship the patched (and stripped down) stub in package called "definitely-not- systemd-stub" and actually give us the ability to ship signed dtbs in 25.10 timeframe. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2100783 Title: systemd-boot does not support an externally provided initrd on UKI Status in systemd package in Ubuntu: Won't Fix Bug description: We would like to boot arm and riscv using systemd-ukify, but the EFI stub in systemd-boot that is used by systemd-ukify to make the UKI only supports embedded initrd's. We would like to be able to externally provide the initrd. This is important for secure boot, as this way on kernel updates the UKI can be signed and provided as a package while the initrd can be generated by update-initramfs locally, as there are still many things changing initramfs-hooks locally. The patch was rejected upstream: https://github.com/systemd/systemd/pull/35978 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2100783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2099811] Re: Os-prober segmentation fault one message for each partition on same PC
> The grub file system drivers have a huge number of security issues and we should run them isolated, they should be using user namespaces, mount namespaces to hide / or have it all readonly, and like empty network namespaces so they can't phone home. No doubt about that, but in a perfect world eliminating os-prober might be more desirable :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2099811 Title: Os-prober segmentation fault one message for each partition on same PC Status in apparmor package in Ubuntu: Confirmed Status in os-prober package in Ubuntu: Confirmed Bug description: Reporting this bug on os-prober, my bug https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2099662 was incorrectly attributed to grub corrado@corrado-n3-pp-0223:~$ sudo os-prober [sudo] password for corrado: find: Failed to restore initial working directory: /home/corrado: Permission denied Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault corrado@corrado-n3-pp-0223:~$ Attaching related journal ProblemType: Bug DistroRelease: Ubuntu 25.04 Package: os-prober 1.83ubuntu2 ProcVersionSignature: Ubuntu 6.12.0-15.15-generic 6.12.11 Uname: Linux 6.12.0-15-generic x86_64 ApportVersion: 2.31.0+git20250220-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Feb 23 15:46:27 2025 InstallationDate: Installed on 2025-02-23 (0 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250223) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: os-prober UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2099811/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2099811] Re: Os-prober segmentation fault one message for each partition on same PC
Im gonna set this public if this is just an apparmor rule issue. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2099811 Title: Os-prober segmentation fault one message for each partition on same PC Status in apparmor package in Ubuntu: New Status in os-prober package in Ubuntu: Confirmed Bug description: Reporting this bug on os-prober, my bug https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2099662 was incorrectly attributed to grub corrado@corrado-n3-pp-0223:~$ sudo os-prober [sudo] password for corrado: find: Failed to restore initial working directory: /home/corrado: Permission denied Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault corrado@corrado-n3-pp-0223:~$ Attaching related journal ProblemType: Bug DistroRelease: Ubuntu 25.04 Package: os-prober 1.83ubuntu2 ProcVersionSignature: Ubuntu 6.12.0-15.15-generic 6.12.11 Uname: Linux 6.12.0-15-generic x86_64 ApportVersion: 2.31.0+git20250220-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Feb 23 15:46:27 2025 InstallationDate: Installed on 2025-02-23 (0 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250223) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: os-prober UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2099811/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2104316] Re: 25.04 beta TPMFDE: first boot failure
> This makes sense because other systems boot after all. Is this "borked hooking" only in newer systemds? (because Noble TPM FDE installs apparently work with plucky ovmf) Hmm I am not sure, I'll look into this in more detail as part of fixing this bug properly after edk2 workaround is done. > You marked the edk2 task as invalid, but this sounds like you think we should make a change to edk2? (even if it's not a bug in edk2, per se) Yes I will upload edk2 to work around it today, I marked as Invalid because I dont consider this an edk2 bug per se. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2104316 Title: 25.04 beta TPMFDE: first boot failure Status in Gadget snap for Personal Computers using Intel or AMD processors: New Status in Ubuntu: New Status in edk2 package in Ubuntu: Invalid Status in grub2 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 25.04 beta hybrid TPMFDE: first boot failure Using virt-manager, creating a VM, adjusting the firmware for UEFI (.ms), and adding a TPM (default settings), the resulting system appears to install but fails on first boot. The screen shows TianoCore along with BdsDxe: loading Booot0003... BdsDxe: starting Booot0003... If I repeat this test with ubuntu 24.04.2 boot makes it boots as expected, showing this prior to continuing to the desktop: BdsDxe: loading Booot0003... BdsDxe: starting Booot0003... /EndEntire /EndEntire On 24.04.2, if I hit escape during the /EndEntire bit, I can see the Grub menu offering the "Run Ubuntu Core" option, which never seems to work on the 25.04 beta install. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-pc/+bug/2104316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2104316] Re: 25.04 beta TPMFDE: first boot failure
Two possible causes: - UKIs don't work with mem attribute protocol + secure boot enabled, this is likely due to systemd's borked hooking of the SEC ARCH 2 protocol pointer, which i assume is in protected memory... - grub page faults when running chainloader on kernel.efi , or linux + boot on kernel.efi, the exact cause of this is unclear right now. but probably because systemd-stub incorrectly marks itself as NX_COMPAT despite not being so. Both of these things need to be investigated. I think we should get rid of the mem attribute protocol in ubuntu's edk2 until these are fixed. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Changed in: grub2 (Ubuntu) Assignee: (unassigned) => Mate Kukri (mkukri) ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Mate Kukri (mkukri) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2104316 Title: 25.04 beta TPMFDE: first boot failure Status in Gadget snap for Personal Computers using Intel or AMD processors: New Status in Ubuntu: New Status in edk2 package in Ubuntu: New Status in grub2 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 25.04 beta hybrid TPMFDE: first boot failure Using virt-manager, creating a VM, adjusting the firmware for UEFI (.ms), and adding a TPM (default settings), the resulting system appears to install but fails on first boot. The screen shows TianoCore along with BdsDxe: loading Booot0003... BdsDxe: starting Booot0003... If I repeat this test with ubuntu 24.04.2 boot makes it boots as expected, showing this prior to continuing to the desktop: BdsDxe: loading Booot0003... BdsDxe: starting Booot0003... /EndEntire /EndEntire On 24.04.2, if I hit escape during the /EndEntire bit, I can see the Grub menu offering the "Run Ubuntu Core" option, which never seems to work on the 25.04 beta install. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-pc/+bug/2104316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2104316] Re: 25.04 beta TPMFDE: first boot failure
GRUB issue is that peimage tries to write relocations addends to read- only sections after setting them read only But i suspect fixing that will make the GRUB problem be the same as the firmware direct boot problem, so we nicely caught two bugs here. ** Changed in: edk2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2104316 Title: 25.04 beta TPMFDE: first boot failure Status in Gadget snap for Personal Computers using Intel or AMD processors: New Status in Ubuntu: New Status in edk2 package in Ubuntu: Invalid Status in grub2 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 25.04 beta hybrid TPMFDE: first boot failure Using virt-manager, creating a VM, adjusting the firmware for UEFI (.ms), and adding a TPM (default settings), the resulting system appears to install but fails on first boot. The screen shows TianoCore along with BdsDxe: loading Booot0003... BdsDxe: starting Booot0003... If I repeat this test with ubuntu 24.04.2 boot makes it boots as expected, showing this prior to continuing to the desktop: BdsDxe: loading Booot0003... BdsDxe: starting Booot0003... /EndEntire /EndEntire On 24.04.2, if I hit escape during the /EndEntire bit, I can see the Grub menu offering the "Run Ubuntu Core" option, which never seems to work on the 25.04 beta install. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-pc/+bug/2104316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2104316] Re: 25.04 beta TPMFDE: first boot failure
This still needs a grub2 upload and systemd stub change to properly fix so i wouldnt remove, edk2 is only a workaround. ** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2104316 Title: 25.04 beta TPMFDE: first boot failure Status in Gadget snap for Personal Computers using Intel or AMD processors: New Status in edk2 package in Ubuntu: Fix Released Status in grub2 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 25.04 beta hybrid TPMFDE: first boot failure Using virt-manager, creating a VM, adjusting the firmware for UEFI (.ms), and adding a TPM (default settings), the resulting system appears to install but fails on first boot. The screen shows TianoCore along with BdsDxe: loading Booot0003... BdsDxe: starting Booot0003... If I repeat this test with ubuntu 24.04.2 boot makes it boots as expected, showing this prior to continuing to the desktop: BdsDxe: loading Booot0003... BdsDxe: starting Booot0003... /EndEntire /EndEntire On 24.04.2, if I hit escape during the /EndEntire bit, I can see the Grub menu offering the "Run Ubuntu Core" option, which never seems to work on the 25.04 beta install. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-pc/+bug/2104316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
