[GH-ISSUE #666] --trace breaks tar unpacking #454

Closed
opened 2026-05-05 05:54:03 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @thomasjfox on GitHub (Jul 30, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/666

when you run tar with the new tar.profile, tar won't extract any file if --trace is given.
This might be an easy reproducer to debug this issue,
may be #561 is related to this.

Originally created by @thomasjfox on GitHub (Jul 30, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/666 when you run tar with the new tar.profile, tar won't extract any file if --trace is given. This might be an easy reproducer to debug this issue, may be #561 is related to this.
Author
Owner

@thomasjfox commented on GitHub (Jul 30, 2016):

plain tar archives seem fine, the trouble starts when a compressor like bzip2 is used (=forked).

<!-- gh-comment-id:236390850 --> @thomasjfox commented on GitHub (Jul 30, 2016): plain tar archives seem fine, the trouble starts when a compressor like bzip2 is used (=forked).
Author
Owner

@thomasjfox commented on GitHub (Jul 30, 2016):

hmm, during my testing --tracelog was broken but now it works.

--trace probably messes up the stdout <-> stdin pipe tar uses for the compressor subprocesses.

<!-- gh-comment-id:236392117 --> @thomasjfox commented on GitHub (Jul 30, 2016): hmm, during my testing --tracelog was broken but now it works. --trace probably messes up the stdout <-> stdin pipe tar uses for the compressor subprocesses.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#454
No description provided.