-
Notifications
You must be signed in to change notification settings - Fork 558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: invalid --debug command line option
if quiet-by-default is set in firejail.config
#4168
Comments
I think the only way to make |
@rusty-snake I think this is going into the right direction of what I meant. Then I had some thoughts which arouse from working with firejai and some confusion about the messages I am confronted with. After reading through the code of I think the default (without setting anything in any profile, configuration file etc.) when you start firejail should be to show only errors. When you start firejail with --verbose you would see the usual firejail output starting with profile loading etc. This would spare the quiet settings in the profiles and the Errors (and maybe also information messages) from firejail should be prefixed with "firejail: " to differentiate from error messages coming from the sandboxed application. However that led me to the thought to route every message through a logger. A logger with debug, info and error levels would reflect the current level of implemented messages as far as I have seen it in the The first and obvious way would be to keep the current flags and think of them like The other way would be to introduce new flags Please consider, that I haven't read through all of the code and am no a fluent C programmer so it's likely that I may have overseen something and please correct me if I'm wrong. |
Fixed! There will be more fixes there, but we track them in #4275 |
Running
didn't work as long as
quiet-by-default yes
is set in the/etc/firejail/firejail.config
, what is very confusing.IMHO at least the error message should be different. Something likequite-by-default is set in the configuration
. I actually would love to see--debug
working even if thequiet-by-default
option is set toyes
in the configuration.Environment
The text was updated successfully, but these errors were encountered: