Skip to content
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

Create new qube: Template has network by default #9174

Closed
deeplow opened this issue Apr 29, 2024 · 8 comments · Fixed by QubesOS/qubes-desktop-linux-manager#221
Closed

Create new qube: Template has network by default #9174

deeplow opened this issue Apr 29, 2024 · 8 comments · Fixed by QubesOS/qubes-desktop-linux-manager#221
Assignees
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: manager/widget diagnosed Technical diagnosis has been performed (see issue comments). good first issue This is a recommended issue for first-time contributors. P: major Priority: major. Between "default" and "critical" in severity. pr submitted A pull request has been submitted for this issue.

Comments

@deeplow
Copy link

deeplow commented Apr 29, 2024

How to file a helpful issue

The problem you're addressing (if any)

When we create a new template qube (e.g. via clone), this is what the settings look like when one clicks on the template tab (notice the network part)

The solution you'd like

When clicking the template tab No network connection should be the default option. This probably is not the case due to the network connection being "saved" from the previous (default) tab which are app qubes.

The value to a user, and who that user might be

Foot-shooting prevention.

Completion criteria checklist

(This section is for developer use only. Please do not modify it.)

@deeplow deeplow added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement labels Apr 29, 2024
@andrewdavidwong andrewdavidwong added C: manager/widget T: bug needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. affects-4.2 This issue affects Qubes OS 4.2. and removed T: enhancement labels Apr 30, 2024
@marmarta marmarta added the good first issue This is a recommended issue for first-time contributors. label Oct 2, 2024
@andrewdavidwong andrewdavidwong added P: major Priority: major. Between "default" and "critical" in severity. and removed P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. labels Oct 4, 2024
@alimirjamali
Copy link

alimirjamali commented Oct 4, 2024

OK. The question is if this has to be fixed at admin.vm.Create core API level or at GUI end level.
p.s.: The answer is at GUI level. Creating a Template via Admin API does not associate a netvm to the Template

Sub-tasks:

  • Fix the legacy Qt based Qubes Manager's Create Qubes VM (i.e. qubes-vm-create)
  • Fix the new GTK based Create New Qube (i.e. qubes-new-qube)

@marmarek
Copy link
Member

marmarek commented Oct 4, 2024

The answer is at GUI level

Yes, the GUI needs to show accurate info before creating the qube.

alimirjamali added a commit to alimirjamali/qubes-manager that referenced this issue Oct 4, 2024
Select (None) for `Template` and `Networking` if user selects
`TemplateVM` for `Type` in Create new qube dialog.

related: QubesOS/qubes-issues#9174
@alimirjamali
Copy link

PR for sub-task 1 is submitted.

Review priority: low

It changes the ComboBoxes for Template & Networking to (none) if you select TemplateVM in the 1st combo box. It also locks the Template ComboBox to (none) if TemplateVM is selected. They are reverted to their default value if user selects another type. Here is the video:

qubes-vm-create.mp4

@marmarek
Copy link
Member

marmarek commented Oct 4, 2024

I don't think locking is appropriate, it's a valid choice to make network-connected template if one really wants that (for example it's kinda-necessary for Windows to be able to install updates there).

Anyway, for the old create qube dialog, I would prefer to simply remove it (and make qubes manager use the new one). Focus on the new one.

@alimirjamali
Copy link

I don't think locking is appropriate, it's a valid choice to make network-connected template if one really wants that (for example it's kinda-necessary for Windows to be able to install updates there).

Locking is done only for the middle ComboBox (the Template: ComboBox). Not for Networking.

Anyway, for the old create qube dialog, I would prefer to simply remove it (and make qubes manager use the new one). Focus on the new one.

Sure. Will be done soon.

@marmarek
Copy link
Member

marmarek commented Oct 4, 2024

Locking is done only for the middle ComboBox (the Template: ComboBox). Not for Networking.

Ah, okay, makes sense.

@alimirjamali
Copy link

alimirjamali commented Oct 4, 2024

Development notes:
Type change detection could be done via CreateNewQube._type_selected. The button_name for Templates is qube_type_template. Doing it via self.network_selector.network_none.set_active(True) is insufficient as it results on the Template netvm to be None instead of being unset. This behaviour will be changed only for new Templates.

@alimirjamali
Copy link

PR for sub-task 2 (main task) is submitted

Review priority: low

Video:

qubes-new-qube.mp4

@andrewdavidwong andrewdavidwong added diagnosed Technical diagnosis has been performed (see issue comments). pr submitted A pull request has been submitted for this issue. and removed needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. labels Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: manager/widget diagnosed Technical diagnosis has been performed (see issue comments). good first issue This is a recommended issue for first-time contributors. P: major Priority: major. Between "default" and "critical" in severity. pr submitted A pull request has been submitted for this issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants