Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign updisp VMs created when importing from 3.2 #3850
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Didn't you just file this as #3846? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Duplicate of #3273 |
andrewdavidwong
marked this as
a duplicate of
#3273
Apr 25, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
andrewdavidwong
Apr 25, 2018
Member
This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.
|
This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you. |
andrewdavidwong
closed this
Apr 25, 2018
andrewdavidwong
added
the
duplicate
label
Apr 25, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
qubesissues commentedApr 24, 2018
Qubes OS version:
4.0
Affected component(s):
Qube Manager
Steps to reproduce the behavior:
Import Qubest from 3.2
Expected behavior:
The VM from 3.2 will be imported as a Qube in 4.0
Actual behavior:
The VM is imported as a Qube and also another Qube called disp- exists.
General notes:
Can I delete these disp Qubes? Why are they there?