Hi Colin,
> Hmm. So I just dug out the VM that I'd been using to look into this,
> brought it up to date, and found that man works fine for me: this is a
> sid x32 chroot on a stretch amd64 base system running a 4.9.0-4-amd64
> kernel. So that means I'm sort of stalled on this for now: perhaps
On Wed, Apr 04, 2018 at 06:35:12PM +, Thorsten Glaser wrote:
> Hi Colin,
> >tglase@tglase:~ $ man ls
> >man: nroff: Bad system call
> > Manual page ls(1) line ?/? (END) (press h for help or q to quit)
>
> any progress on this? Can I disable the seccomp stuff locally,
> using a configuration
Hi Colin,
>tglase@tglase:~ $ man ls
>man: nroff: Bad system call
> Manual page ls(1) line ?/? (END) (press h for help or q to quit)
any progress on this? Can I disable the seccomp stuff locally,
using a configuration file or something? It’s kinda annoying
after a while, on my $dayjob desktop
On Wed, Feb 14, 2018 at 03:26:31AM +0100, Thorsten Glaser wrote:
> Hrm.…
>
> > Sure, it’s attached, and it seems really weird…
>
> … I had thought someone had defined NULL as just 0
> (although dalias makes a good argument for it) and
> it was passed as a too-short sentinel, but it uses
>
Hrm.…
> Sure, it’s attached, and it seems really weird…
… I had thought someone had defined NULL as just 0
(although dalias makes a good argument for it) and
it was passed as a too-short sentinel, but it uses
execve, so that was not it.
But I see a lot of seccomp stuff in there, which,
On Tue, Feb 13, 2018 at 09:55:36PM +0100, Thorsten Glaser wrote:
> tglase@tglase:~ $ man ls
> man: nroff: Bad system call
> Manual page ls(1) line ?/? (END) (press h for help or q to quit)
This test case works fine for me; perhaps there's something about x32
that matters here. Could you please
Package: man-db
Version: 2.8.1-1
Severity: grave
Justification: renders package unusable
-begin screenshot-
tglase@tglase:~ $ man ls
man: nroff: Bad system call
Manual page ls(1) line ?/? (END) (press h for help or q to quit)
-end screenshot-
This one works, though:
7 matches
Mail list logo
