Bug#889608: Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

2018-02-04 Thread intrigeri
Ben Caradoc-Davies: >> Ben Caradoc-Davies wrote: >>> And what I would like to know is how the fscking apparmor module got >>> loaded in the first place, given that I have the apparmor service >>> masked: >>> # ls -al /etc/systemd/system/apparmor.service >>> lrwxrwxrwx 1 root root 9 Dec 8 11:24 >>>

Bug#889608: Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

2018-02-04 Thread Ben Caradoc-Davies
On 05/02/18 13:40, Axel Beckert wrote: Control: merge 889608 -1 Hi Ben, thanks for the bug report. Ben Caradoc-Davies wrote: under man-db 2.8.0-1 amd64 all man pages fail to display with: $ man man man: command exited with status 4: /usr/lib/man-db/zsoelim | /usr/lib/man- db/manconv -f UTF-8:ISO

Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

2018-02-04 Thread Ben Caradoc-Davies
Rebooting restores man page rendering, even with 2.8.0-1, but reinstalling causes the bug to reappear. It looks like root can view man pages but an unprivileged user cannot. Kind regards, -- Ben Caradoc-Davies Director Transient Software Limited New Zealand

Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

2018-02-04 Thread Axel Beckert
Control: merge 889608 -1 Hi Ben, thanks for the bug report. Ben Caradoc-Davies wrote: > under man-db 2.8.0-1 amd64 all man pages fail to display with: > > $ man man > man: command exited with status 4: /usr/lib/man-db/zsoelim | /usr/lib/man- > db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | p

Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

2018-02-04 Thread Ben Caradoc-Davies
And what I would like to know is how the fscking apparmor module got loaded in the first place, given that I have the apparmor service masked: # ls -al /etc/systemd/system/apparmor.service lrwxrwxrwx 1 root root 9 Dec 8 11:24 /etc/systemd/system/apparmor.service -> /dev/null Yet: # aa-statu

Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

2018-02-04 Thread Ben Caradoc-Davies
With 2.8.0-1, I see AppArmor messages in the systemd journal for "man man": Feb 05 13:09:30 ripley audit[30186]: AVC apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="/usr/bin/man" name="/usr/bin/preconv" pid=30186 comm="man" requested_mask="x" denied_mask="x" fsuid=1000

Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

2018-02-04 Thread Ben Caradoc-Davies
Package: man-db Version: 2.8.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, under man-db 2.8.0-1 amd64 all man pages fail to display with: $ man man man: command exited with status 4: /usr/lib/man-db/zsoelim | /usr/lib/man- db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//I