-
-
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
implement dom0 -> right click -> VM settings / easy way to configure updatevm setting #1165
Comments
It is possible: menu "system" -> global settings. But indeed it isn't Best Regards, |
Maybe "settings" for dom0 should simply open global settings? |
Sounds good to me.
|
Instead of generic menu with almost everything grayed-out, now context menu for dom0 has only Global Settings, Logs and update. fixes QubesOS/qubes-issues#1165
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Has this been reverted? Is there a regression here? The right click menu in QVMM on dom0 shows most grayed out for me. Only update, qubes windows tools installation and logs is clickable. Please re-open. //cc @marmarta |
yes, it has been long reverted, I think. We could add global config there, but I'm not sure if it's that easy to find... Global Settings are linked in System menu and toolbar in manager, and I think it's a generally more reasonable place. |
And I think it's better to think about stuff like "how updates are made" from perspective of global settings rather than from perspective of "dom0 settings", especially as with introduction of gui domain it gets more and more complex to look at those settings from dom0 perspective. |
Currently
dom0 -> right click -> VM settings
is grayed out. Would it make sense to implement that?To my knowledge, there is currently no way to set dom0 updatevm, i.e.
qubes-prefs --set updatevm whonix-gw
by using the gui.This is related to...
high-level target: templates should default update over Tor
:#1159
If #1159 is not going to be implemented, this ticket could be closed or set to "patches welcome".
The text was updated successfully, but these errors were encountered: