You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whonix is quite verbose and sometimes information is not important at all. One specific example, which is complicating automated testing is when whonix shows a dialog just to inform that some repo is enabled. This is unnecessary.
Steps to Reproduce
Install workstation on a clean Qubes system.
Expected Behavior
No unactionable information is shown to the user.
Actual Behavior
Comments
This may end up being an upstream "issue", but if there is anyway we can suppress this, it would be a very nice addition.
The text was updated successfully, but these errors were encountered:
Turns out we can (and probably should) hide these messages via a config file in /etc/systemcheck.d/. Something like this would suppress all systemcheck non-actionable messages (for SD users):
systemcheck_skip_functions+=" check_apt_repository"# Skip info about enabled derivative repository
systemcheck_skip_functions+=" check_operating_system"# Skip OS updates check (already ensured in SD updater)
systemcheck_skip_functions+=" donate"
One thing to consider, though, is that because we're installing it in whonix-gateway-17, sys-whonix may end up also being affected.
Found another instance where it only mentions the derivative repository, but not donate button and the update check. And this time it showed as the system booted up for the first time and not when doing the sys-whonix configuartion step.
Description
Whonix is quite verbose and sometimes information is not important at all. One specific example, which is complicating automated testing is when whonix shows a dialog just to inform that some repo is enabled. This is unnecessary.
Steps to Reproduce
Install workstation on a clean Qubes system.
Expected Behavior
No unactionable information is shown to the user.
Actual Behavior
Comments
This may end up being an upstream "issue", but if there is anyway we can suppress this, it would be a very nice addition.
The text was updated successfully, but these errors were encountered: