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

The Qube Settings GUI displays information in a misleading way #3565

Closed
andrewdavidwong opened this Issue Feb 10, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@andrewdavidwong
Member

andrewdavidwong commented Feb 10, 2018

Qubes OS version:

R4.0


In #3561 (comment), @awokd wrote:

the Qube Setting GUI is a bit buggy. If I use it to view anon-whonix's default_dispvm on the advanced tab, it claims it's set to the qubes-prefs' default_dispvm, even though it's actually using the value in qvm-prefs anon-whonix default_dispvm. I think there might be a similar issue out there too about the kernel value on this tab.
Also, hitting the drop-down for dispvm only lists default and (none), when I'd expect it to list all templates where template_for_dispvms = true.


Related issues:

#3561

@andrewdavidwong andrewdavidwong added this to the Release 4.0 milestone Feb 10, 2018

@marmarta marmarta referenced this issue in QubesOS/qubes-manager Feb 10, 2018

Merged

Fixed incorrect default dispvm settings #66

@marmarta

This comment has been minimized.

Show comment
Hide comment
@marmarta

marmarta Feb 10, 2018

You're completely right on the default dispvm thing - hopefully, I've fixed it. Although I'm not sure about the kernel thing - it uses the property_get_default of the current vm for the 'kernel' property, which I think is the desired behavior?

You're completely right on the default dispvm thing - hopefully, I've fixed it. Although I'm not sure about the kernel thing - it uses the property_get_default of the current vm for the 'kernel' property, which I think is the desired behavior?

@awokd

This comment has been minimized.

Show comment
Hide comment
@awokd

awokd Feb 10, 2018

I remembered wrong, I was thinking of the virt mode on that tab: #3517
Kernel is working properly.

awokd commented Feb 10, 2018

I remembered wrong, I was thinking of the virt mode on that tab: #3517
Kernel is working properly.

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Feb 10, 2018

Automated announcement from builder-github

The package qubes-manager-4.0.14-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.14-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 Feb 10, 2018

Closed

manager v4.0.14 (r4.0) #404

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Feb 27, 2018

Automated announcement from builder-github

The package qubes-manager-4.0.15-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.15-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