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

qvm-prefs -D SOMEVM template fails with confusing error #8928

Closed
DemiMarie opened this issue Feb 9, 2024 · 3 comments · Fixed by QubesOS/qubes-core-admin#633
Closed

qvm-prefs -D SOMEVM template fails with confusing error #8928

DemiMarie opened this issue Feb 9, 2024 · 3 comments · Fixed by QubesOS/qubes-core-admin#633
Assignees
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: core diagnosed Technical diagnosis has been performed (see issue comments). P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. pr submitted A pull request has been submitted for this issue. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. ux User experience

Comments

@DemiMarie
Copy link

How to file a helpful issue

Qubes OS release

R4.2

Brief summary

qvm-prefs -D SOMEVM template fails with the confusing error message Cannot unset template. This does not make sense because a default template is set, meaning that I am asking Qubes OS to set the template to whatever the default TemplateVM is. For qvm-refs SOMEVM template '' the error message would be correct.

Steps to reproduce

See above.

Expected behavior

Operation should succeed, or the error should explain why the operation is not allowed.

Actual behavior

Confusing error message.

@DemiMarie DemiMarie added T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. C: core P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. labels Feb 9, 2024
@marmarek
Copy link
Member

marmarek commented Feb 9, 2024

Template property is not allowed to have "default" value (as in - "D" flag in qvm-prefs, meaning automatically following whatever the default is). Theoretically, qvm-prefs -D SOMEVM template could set the template to whatever is the default value right now. That would be convenient for the user, I think, but on the other hand, it would be inconsistent (as it won't follow future changes to the default template property).
I'm not sure whether it's better to improve the error message, or implement the alternative behavior from above... @marmarta any opinion?

@andrewdavidwong andrewdavidwong added ux User experience 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. labels Feb 9, 2024
@marmarta
Copy link
Member

marmarta commented Jul 1, 2024

I'd improve the error message, otherwise it does get inconsistent. (and, if possible, I would put in the error message something like "You cannot set the template value to default. Did you mean to set the template to fedora-foo, which is the default template? y/N"?

@andrewdavidwong andrewdavidwong added diagnosed Technical diagnosis has been performed (see issue comments). and removed needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. labels Jul 1, 2024
alimirjamali added a commit to alimirjamali/qubes-core-admin that referenced this issue Nov 9, 2024
@alimirjamali
Copy link

I submitted a PR to propose a change to error message which hopefully could be a good compromise.

Review priority: Low

@andrewdavidwong andrewdavidwong added the pr submitted A pull request has been submitted for this issue. label Nov 10, 2024
alimirjamali added a commit to alimirjamali/qubes-core-admin that referenced this issue Nov 10, 2024
alimirjamali added a commit to alimirjamali/qubes-core-admin that referenced this issue Nov 10, 2024
alimirjamali added a commit to alimirjamali/qubes-core-admin that referenced this issue Nov 10, 2024
alimirjamali added a commit to alimirjamali/qubes-core-admin that referenced this issue Nov 10, 2024
marmarek pushed a commit to QubesOS/qubes-core-admin that referenced this issue Dec 8, 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: core diagnosed Technical diagnosis has been performed (see issue comments). P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. pr submitted A pull request has been submitted for this issue. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. ux User experience
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants