On Thu, Feb 22, 2018 at 12:51:33PM +0100, Andreas Beckmann wrote:
> the seccomp changes cause man to fail in my armhf qemu pbuilder
> sid chroot (on an amd64 host):
>    dh_installman
> qemu: Unsupported syscall: 383
> /usr/bin/man: can't load seccomp filter: Bad address
> /usr/bin/man: command exited with status 2: /usr/lib/man-db/manconv -f 
> UTF-8:ISO-8859-1 -t UTF-8//IGNORE
> dh_installman: man -l --recode UTF-8 
> ./debian/nvidia-cuda-mps/usr/share/man/man1/nvidia-cuda-mps-control.1 > 
> debian/nvidia-cuda-mps/usr/share/man/man1/nvidia-cuda-mps-control.1.dh-new 
> returned exit code 3
> dh_installman: Aborting due to earlier error

I'm somewhat inclined to disable the seccomp filter if running under
qemu-user, as it's going to be pretty hard to make it work.  What do you
think?  And do you know of a way for a program to detect that it's
running under qemu-user?

Colin Watson                                       [cjwat...@debian.org]

Reply via email to