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

Firewall rules GUI disables itself #3289

Closed
mirrorway opened this Issue Nov 7, 2017 · 5 comments

Comments

Projects
None yet
5 participants
@mirrorway

mirrorway commented Nov 7, 2017

Qubes OS version: R4.0-rc2

Affected TemplateVMs:


Steps to reproduce the behavior:

  1. Create a Fedora VM with netvm := sys-firewall.
  2. Open VM settings, click "Limit outgoing internet connections to..."
  3. Close VM settings.
  4. Re-open VM settings.

Expected behavior:

Can add/modify rules a la Qubes R3.2

Actual behavior:

Firewall setting is grayed out with
"Firewall has been modified manually - please use qvm-firewall for any further configuration."

Other comments

You can make the firewall tab visible again by using qvm-firewall to delete all but the accept-all rule.

@mirrorway mirrorway changed the title from Disabled firewall rules tab to Firewall rules GUI disabled Nov 7, 2017

@mirrorway mirrorway changed the title from Firewall rules GUI disabled to Firewall rules GUI disables itself. Nov 7, 2017

@mirrorway mirrorway changed the title from Firewall rules GUI disables itself. to Firewall rules GUI disables itself Nov 7, 2017

@marmarek marmarek added this to the Release 4.0 milestone Nov 7, 2017

@marmarta marmarta referenced this issue in QubesOS/qubes-manager Nov 17, 2017

Merged

Fixed bug with firewall GUI settings #48

@mannp

This comment has been minimized.

Show comment
Hide comment
@mannp

mannp Nov 20, 2017

Hi @marmarek which repo would this change be in, as I have the same bug and am up to date with the testing repo and still have the bug.

Is it only in unstable?

mannp commented Nov 20, 2017

Hi @marmarek which repo would this change be in, as I have the same bug and am up to date with the testing repo and still have the bug.

Is it only in unstable?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Nov 20, 2017

Member

It's not built yet, you'll notification here when it's done.

Member

marmarek commented Nov 20, 2017

It's not built yet, you'll notification here when it's done.

@mannp

This comment has been minimized.

Show comment
Hide comment
@mannp

mannp Nov 20, 2017

ok cool thanks.

mannp commented Nov 20, 2017

ok cool thanks.

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Nov 21, 2017

Automated announcement from builder-github

The package qubes-manager-4.0.9-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

Automated announcement from builder-github

The package qubes-manager-4.0.9-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@qubesos-bot qubesos-bot referenced this issue in QubesOS/updates-status Nov 21, 2017

Closed

manager v4.0.9 (r4.0) #307

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Dec 11, 2017

Automated announcement from builder-github

The package qubes-manager-4.0.9-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

Automated announcement from builder-github

The package qubes-manager-4.0.9-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment