Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_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!
https://wiki.archlinux.org/title/Bug_reporting_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!
FS#53175 - [pax-utils] pspax returns Bad system call
Attached to Project:
Community Packages
Opened by trendkiller (trendkiller) - Monday, 06 March 2017, 10:38 GMT
Last edited by Timothy Redaelli (tredaelli) - Tuesday, 07 March 2017, 14:46 GMT
Opened by trendkiller (trendkiller) - Monday, 06 March 2017, 10:38 GMT
Last edited by Timothy Redaelli (tredaelli) - Tuesday, 07 March 2017, 14:46 GMT
|
DetailsSince pax-utils 1.2.2, pspax returns a "Bad system call" error.
I don't think it's a kernel issue, since linux-grsec is still at version 4.9 |
This task depends upon
Closed by Timothy Redaelli (tredaelli)
Tuesday, 07 March 2017, 14:46 GMT
Reason for closing: Fixed
Additional comments about closing: Removed seccomp usage in 1.2.2-2
Tuesday, 07 March 2017, 14:46 GMT
Reason for closing: Fixed
Additional comments about closing: Removed seccomp usage in 1.2.2-2
Comment by Doug Newgard (Scimmia) -
Monday, 06 March 2017, 15:53 GMT
Does it work with the standard kernel?