*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Mandb recently started to apply seccomp policy to its subprocesses.
Unfortunatelly, the seccom policy is badly written, so that
mandb for foreign architectures (i386 or x32) crashes.
* What exactly did you do (or not do) that was effective (or
Install man-db:i386 or man-db:x32 on an amd64 system, try to view some
manpage and you'll get crashes.
The bug also happens if you use man-db:amd64, but /bin/sh is pointing
to i386 or x32 shell (i.e. if you install dash:i386 or dash:x32 and
make it a default shell).
* What was the outcome of this action?
man with any man page fails with SIGSYS signals.
* What outcome did you expect instead?
mandb should work.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: buster/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32
Kernel: Linux 4.15.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=cs_CZ.utf8, LC_CTYPE=cs_CZ.utf8 (charmap=UTF-8),
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages man-db depends on:
ii bsdmainutils 11.1.2
ii debconf [debconf-2.0] 1.5.65
ii dpkg 184.108.40.206
ii groff-base 1.22.3-10
ii libc6 2.26-6
ii libgdbm5 1.14.1-4
ii libpipeline1 1.5.0-1
ii libseccomp2 2.3.1-2.1
ii zlib1g 1:1.2.8.dfsg-5
man-db recommends no packages.
Versions of packages man-db suggests:
pn apparmor <none>
pn groff <none>
ii less 487-0.1
ii lynx [www-browser] 2.8.9dev16-3
ii w3m [www-browser] 0.5.3-36
-- Configuration Files:
/etc/manpath.config changed [not included]
-- debconf information: