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

qubes-manager: "reset to defaults" option #1363

Open
andrewdavidwong opened this issue Oct 29, 2015 · 8 comments
Open

qubes-manager: "reset to defaults" option #1363

andrewdavidwong opened this issue Oct 29, 2015 · 8 comments
Labels
C: manager/widget P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.

Comments

@andrewdavidwong
Copy link
Member

It's standard in most GUI program to have a button which resets all options to their default settings, where "default" means roughly "how things would look on a fresh install."

@marmarek
Copy link
Member

What exactly do you have in mind? "Reset VM settings"? Or something more
global?

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

@marmarek marmarek added the T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. label Oct 29, 2015
@marmarek marmarek added this to the Release 4.0 milestone Oct 29, 2015
@andrewdavidwong
Copy link
Member Author

Qubes Manager --> System --> Qubes Global Settings

In this window, the user can change things like: minimal VM memory, dom0 memory boost, whether to keep DispVMs in memory, whether to check for dom0 updates, and whether to check for VM updates. A user might change some of those settings (being new to Qubes, not realizing that her custom choice is a bad idea), then later realize that she wants to revert to the defaults. But maybe she doesn't remember what the defaults are. It would be nice to have a button which sets everything to the defaults.

@fepitre
Copy link
Member

fepitre commented May 31, 2019

I would add something related to this: resetting default applications list in VM settings. @marmarta @marmarek do you think that would be reasonable to do?

@airelemental
Copy link

airelemental commented May 31, 2019

The default applications list is "show every application", so can't this be accomplished by clicking the ">>"?

One specific settings reset that might be useful, is resetting the firewall so it clears any qvm-firewall CLI modifications, allowing the firewall tab to be usable again.

@andrewdavidwong
Copy link
Member Author

The default applications list is "show every application", so can't this be accomplished by clicking the ">>"?

Are you sure? I thought the default was just a handful of common applications.

One specific settings reset that might be useful, is resetting the firewall so it clears any qvm-firewall CLI modifications, allowing the firewall tab to be usable again.

This is a separate issue: #4710

@andrewdavidwong andrewdavidwong added the P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. label Jun 1, 2019
@fepitre
Copy link
Member

fepitre commented Jun 1, 2019

The default applications list is "show every application", so can't this be accomplished by clicking the ">>"?

Are you sure? I thought the default was just a handful of common applications.

He is wrong and you are right. The default application list is what we provide in every builder-/template_scripts/appmenus_

@marmarta
Copy link
Member

@marmarek, what is the source of global defaults? or is there no simple answer to this one?

@marmarek
Copy link
Member

Those values being just properties of Qubes() object, can be reset by assigning qubesadmin.DEFAULT value - you can also try getting the default using property_get_default() method. But it may not work for some, like default_template which is basically the first template installed on the system that may not be present anymore at a later time. Similar case for default kernel. Some others have default value None, only set later by initial setup wizard (this is the case of default_netvm for example - which BTW really depends on the choice made in the initial-setup).
Settings modified directly in some config file (like qmemman parameters) don't have programmatic way of getting default values. In case of qmemman, removing them from the file will make it use defaults, but you won't know the actual value, unless you copy it from the qmemman source code...

In short: there is no simple way to get "default" values (understood as "values just after installation") for global settings. You can get some of them by copying logic that set them during installation, but for some it may still not be enough (like default template, which could be removed since then).

This is much easier for VM properties, where default values for most properties are actually meaningful, especially for "normal" AppVMs. There are still few corner cases - like 'netvm' property of a sys-net itself, but those applies to system VMs mostly. Those things again are set by the initial setup (through salt).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: manager/widget P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Development

No branches or pull requests

5 participants