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
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
@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
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.sourcewar
** 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 Ubu
** 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
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 se
** 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
** 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 ar
** 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 1
** 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
** 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/gd
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
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 verificat
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:
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
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/b
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
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 U
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/
@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 autop
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 notificat
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
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: verifica
** 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/gd
** 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.
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.laun
** 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
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
--
** 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
S
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
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. The
** 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
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
> 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 e
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/
> 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.
> Yo
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)
Ass
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
39 matches
Mail list logo
