since the libseccomp uploads to b/e/x-proposed also have this bug marked in their changelog, it's showing up in the pending srus page as not verified yet for the x/b/e libseccomp uploads. As mentioned in the description, the initial problem only occurred in focal, but just for verification purposes:
eoan: ubuntu@lp1877633-e:~$ dpkg -l |grep libseccomp ii libseccomp2:amd64 2.4.1-0ubuntu0.19.10.3 amd64 high level interface to Linux seccomp filter ubuntu@lp1877633-e:~$ scmp_sys_resolver -a aarch64 getrlimit 163 ubuntu@lp1877633-e:~$ dpkg -l |grep seccomp ii libseccomp2:amd64 2.4.3-1ubuntu3.19.10.2 amd64 high level interface to Linux seccomp filter ii seccomp 2.4.3-1ubuntu3.19.10.2 amd64 helper tools for high level interface to Linux seccomp filter ubuntu@lp1877633-e:~$ scmp_sys_resolver -a aarch64 getrlimit 163 bionic: ubuntu@lp1877633-b:~$ dpkg -l |grep seccomp ii libseccomp2:amd64 2.4.1-0ubuntu0.18.04.2 amd64 high level interface to Linux seccomp filter ii seccomp 2.4.1-0ubuntu0.18.04.2 amd64 helper tools for high level interface to Linux seccomp filter ubuntu@lp1877633-b:~$ scmp_sys_resolver -a aarch64 getrlimit 163 ubuntu@lp1877633-b:~$ dpkg -l |grep seccomp ii libseccomp2:amd64 2.4.3-1ubuntu3.18.04.2 amd64 high level interface to Linux seccomp filter ii seccomp 2.4.3-1ubuntu3.18.04.2 amd64 helper tools for high level interface to Linux seccomp filter ubuntu@lp1877633-b:~$ scmp_sys_resolver -a aarch64 getrlimit 163 xenial: ubuntu@lp1877633-x:~$ dpkg -l|grep seccomp ii libseccomp2:amd64 2.4.1-0ubuntu0.16.04.2 amd64 high level interface to Linux seccomp filter ii seccomp 2.4.1-0ubuntu0.16.04.2 amd64 helper tools for high level interface to Linux seccomp filter ubuntu@lp1877633-x:~$ scmp_sys_resolver -a aarch64 getrlimit 163 ubuntu@lp1877633-x:~$ dpkg -l|grep seccomp ii libseccomp2:amd64 2.4.3-1ubuntu3.16.04.2 amd64 high level interface to Linux seccomp filter ii seccomp 2.4.3-1ubuntu3.16.04.2 amd64 helper tools for high level interface to Linux seccomp filter ubuntu@lp1877633-x:~$ scmp_sys_resolver -a aarch64 getrlimit 163 ** Tags added: verification-done verification-done-bionic verification-done-eoan verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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