Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57557 - [man-db] man: tbl: Bad system call (core dumped)

Attached to Project: Arch Linux
Opened by John Sivak (jsivak) - Sunday, 18 February 2018, 00:55 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 01 March 2018, 07:26 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When issuing any "man" call I get the following:

man: tbl: Bad system call (core dumped)
man: nroff: Bad system call (core dumped)
man: preconv: Bad system call (core dumped)

followed by:

man: command exited with status 159: /usr/lib/man-db/zsoelim | /usr/lib/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | tbl | nroff -mandoc -rLL=126n -rLT=126n -Tutf8


Additional info:
* versions affected: man-db 2.8.0 and man-db 2.8.1-1

Steps to reproduce:

man man

Originally I though this was related to bug  FS#57436  (https://bugs.archlinux.org/task/57436 ), but when that bug was resolved with the relase of man-db 2.8.0-1, my issue didn't get resolved.

I found this Debian bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889608 and using:

MAN_DISABLE_SECCOMP=1 man man

then the man page works as expected.

I do not have any apparmor packages installed (that I'm aware of), so I'm not sure why this is impacting my system.



This task depends upon

Closed by  Andreas Radke (AndyRTR)
Thursday, 01 March 2018, 07:26 GMT
Reason for closing:  Fixed
Additional comments about closing:  2.8.2-1
Comment by Allan McRae (Allan) - Sunday, 18 February 2018, 02:23 GMT
Do you have groff installed?
Comment by John Sivak (jsivak) - Sunday, 18 February 2018, 04:15 GMT
Yes, version 1.22.3-7
Comment by Allan McRae (Allan) - Sunday, 18 February 2018, 04:54 GMT
Can you check the files with "pacman -Qk groff"?
Comment by John Sivak (jsivak) - Sunday, 18 February 2018, 06:05 GMT
/home/jsivak $ sudo pacman -Qk groff
groff: 624 total files, 0 missing files
Comment by Andreas Radke (AndyRTR) - Sunday, 18 February 2018, 08:24 GMT
Please ask at the man-db mailing list. Looks you hit another upstream bug here.
Comment by John Sivak (jsivak) - Sunday, 18 February 2018, 15:56 GMT
Thanks, I've replied to the closed issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889608 and will see how they want me to proceed.
Comment by loqs (loqs) - Sunday, 18 February 2018, 18:03 GMT
debian is another downstream packager of man-db like arch. As you are not using debian or man-db as built and packaged by debian would
expect them to refer you to upstream as AndyRTR already has. Upstream is http://www.nongnu.org/man-db/development.html
You might want to include the backtrace from the coredump or an strace of a run of man so upstream can see which system call is triggering seccomp.
Comment by Andreas Radke (AndyRTR) - Sunday, 18 February 2018, 18:51 GMT
loqs, it's ok here to post to the Debian tracker though upstream would be the better place. The Debian package maintainer is here the upstream developer in one person.

Loading...