Fatal crashpad/ptrace error on flatpak 1.16.5_1

[TeusLollo]

Is this a new report?

Yes

System Info

Void 6.18.21_1 x86_64 AuthenticAMD notuptodate rrrrmD

Package(s) Affected

flatpak-1.16.5_1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

This error on CachyOS seems related and implies this is not solely a Chromium-related issue, also happening due to flatpak-1.16.5_1 update:
brave/brave-browser#54387

This user suggests there are known problems with the most recent flatpak update:
brave/brave-browser#54345 (comment)

Expected behaviour

Running a flatpak-sandboxed application should not result in cascading crashpad errors eventually leading to process termination

Actual behaviour

Upon updating to flatpak-1.16.5_1, sandboxed app io.github.ungoogled_software.ungoogled_chromium (Which was already up-to-date, did not receive any update recently, and was otherwise working perfectly prior to flatpak update) was behaving strangely with random extension crashes, inability to enter menu options, and finally crashing to desktop after a few seconds

Running flatpak run io.github.ungoogled_software.ungoogled_chromium outputted a cascading linefeed of the following error:

ERROR:third_party/crashpad/crashpad/util/linux/scoped_ptrace_attach.cc:27] ptrace: Operation not permitted (1)

Juggling between sandbox options, restoring defaults, and otherwise messing with launching options did not yield any positive result

Running xdowngrade /var/cache/xbps/flatpak-1.16.4_1 fixed the error, and sandboxed app io.github.ungoogled_software.ungoogled_chromium returned to behaving normally.

Steps to reproduce

1. Update to flatpak-1.16.5_1
2. Run flatpak run io.github.ungoogled_software.ungoogled_chromium (Remember to close any Chromium instances first)
3. Enjoy linefeed cascade of ERROR:third_party/crashpad/crashpad/util/linux/scoped_ptrace_attach.cc:27] ptrace: Operation not permitted (1)
4. Process eventually crashes without user input

[Duncaen]

Pushed another update: 77bdf05

[TeusLollo]

Updating to flatpak-1.16.6 seems to have fixed the issue.

Anyone else is free to contribute, but I would be waiting a little bit before closing, since it's likely that several applications were affected