mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3371] Support simplification: improving --debug and stdout #2118
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#2118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @matu3ba on GitHub (Apr 20, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3371
Disabled commands in /usr/bin/ or list of whitelist commandsare not emittedThese got to very long threads, because retrieving the setup from user might also be nontrivial.
fixed by new issue template
#3333 #3312
If there is
warning/Warning/WARNINGinside program output, print everything to stdout. Currently this seems only to be printed on--debug. #3360If possible extend to
error/Error/ERROR.I guess this is due to programs emitting no proper status code. If previous messages should be collected, a circular buffer for length limitation could be used.
@matu3ba commented on GitHub (Apr 20, 2020):
The other option would be to ask users to report the wrong status code, because that is a bug of the program #3360
@matu3ba commented on GitHub (Apr 26, 2020):
Closing due to updated issue template, which asks for the output of
--debugand emits everything.