Repository navigation
Improve UX and documentation of services #4842
Description
Qubes OS version:
R4.0
Affected component(s) or functionality:
sys-firewall and qubes-firewall service
Steps to reproduce the behavior:
Check the services of sys-firewall and see that qubes-firewall is not enabled.
Despite this, sys-firewall still seems to work correctly as a FirewallVM.
Expected or desired behavior:
Either qubes-firewall is enabled in sys-firewall, or the documentation about qubes-firewall is updated to explain why it is not needed, or qubes-firewall is deprecated.
Actual behavior:
sys-firewall still seems to work correctly as a FirewallVM even without qubes-firewall being enabled.
General notes:
I have consulted the following relevant documentation:
http://dev.qubes-os.org/projects/core-admin-client/en/latest/manpages/qvm-features.html
http://dev.qubes-os.org/projects/core-admin-client/en/latest/manpages/qvm-service.html
https://dev.qubes-os.org/projects/core-admin-client/en/latest/manpages/qvm-prefs.html
https://dev.qubes-os.org/projects/core-admin-client/en/latest/manpages/qvm-create.html
https://www.qubes-os.org/doc/config-files/
https://www.qubes-os.org/doc/firewall/
Activity
marmarek commentedon Feb 24, 2019
Works as intended - service not listed means "use default value".
This is also included in
qvm-servicemanual you linked:Although indeed could be better exposed.
andrewdavidwong commentedon Feb 24, 2019
Ok, Thanks. Filing as a UX issue.
[-]qubes-firewall service not enabled in sys-firewall[/-][+]Improve UX and documentation of qubes services[/+][-]Improve UX and documentation of qubes services[/-][+]Improve UX and documentation of services[/+]alimirjamali commentedon Jun 11, 2024
I wonder if this issue is still valid. Marmarta added this text to
Servicestab of Settings GUI around 5 years ago:The improvement happened few months after the issue filing (Dec 14, 2019). The explanation text appears at the bottom of Window. Here is a recent screenshot:

andrewdavidwong commentedon Jun 12, 2024
Closing as completed. If anyone believes this issue is not yet completed, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen it. Thank you.