Qt doesn't cope with EPERM returned from statx(2)

[Zygmunt Krynicki]

The statx(2) system call is a relatively new addition and has not seen widespread use. As such the seccomp filer used by snapd to confine application processes does not currently permit it. While addressing the bug in snapd is in progress we wanted to contribute a fix to the package so that all snaps built with Qt from the Ubuntu archive will automatically benefit and behave correctly.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "Debdiff fixing the statx(2) under snap confinement (v2)" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

[Timo Jyrinki (timo-jyrinki)]

The upstream response might be similar to https://bugreports.qt.io/browse/QTBUG-70447 's "Please update your container manager's whitelist of syscalls."

[Simon Quigley (tsimonq2)]

Unsubscribing ~ubuntu-sponsors for now because upstream has rejected the patch.

If this was done in error, please resubscribe us.

Thank you!

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Nils Schimmelmann (nschimme)]

This bug is still preventing Qt apps from being run on Core18 snaps. I'm assuming we're blocked on https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250 ?