-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Domain has failed to start: 'NoneType' object has no attribute 'count' #5772
Domain has failed to start: 'NoneType' object has no attribute 'count' #5772
Comments
No more None dsthosts or port ranges. fixes QubesOS/qubes-issues#5772
No more None dsthosts or port ranges. fixes QubesOS/qubes-issues#5772
Firewall rule cannot be missing value in declaration (e.g. 'dsthost=' is not a valid rule). fixes QubesOS/qubes-issues#5772
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Qubes OS version
R4.0
Affected component(s) or functionality
domU qube, Qube Manager qube settings and
qvm-firewall
.Brief summary
Affected domU qube fails to start. It is no longer possible to edit or list the firewall rules of this qube via
qvm-firewall
and it is not possible to open the qube settings (Qube Manager) for this qube.To Reproduce
Add a firewall rule to $qube which specifies the destination host as empty via
qvm-firewall
,e.g.
qvm-firewall $qube add accept dsthost=
, and then reboot Qubes.Expected behavior
qvm-firewall
refusing to create this rule.Actual behavior
qvm-firewall
creating the rule.Additional context
The Qube Manager prevents the user from creating such a firewall rule.
After the qube fails to start, a notification displays this message:
Solutions you've tried
Delete the rules that prevent the affected qube from starting by directly editing
/var/lib/qubes/appvms/$qube/firewall.xml
in dom0. This solves all issues described in the brief summary above.Relevant documentation you've consulted
https://qubes-os.org/doc/firewall
The text was updated successfully, but these errors were encountered: