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 upAfter having assigned an non-existing TemplateVM to an AppVM, Qubes VM Manager fails and does not allow to assign an existing TemplateVM #2495
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Dec 8, 2016
Member
Ok, it sounds like the real problem is that fedora-23 was still selectable as a TemplateVM in Qubes Manager even after you removed it. AFAIK, that shouldn't be possible.
$ sudo rm ~/.local/share/applications/fedora-23-* (pls. fix the wrong number 21 in your example on https://www.qubes-os.org/doc/templates/ !)
It's not "wrong." It's just an example. You're not supposed to copy that command verbatim; rather, it's an instance serving to illustrate the command.
|
Ok, it sounds like the real problem is that
It's not "wrong." It's just an example. You're not supposed to copy that command verbatim; rather, it's an instance serving to illustrate the command. |
andrewdavidwong
added
bug
C: qubes-manager
labels
Dec 8, 2016
andrewdavidwong
added this to the Release 3.2 updates milestone
Dec 8, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Wikinaut
Dec 8, 2016
It's not "wrong." It's just an example. You're not supposed to copy that command verbatim; rather, it's an instance serving to illustrate the command.
This is clear to me, but in your examples on https://www.qubes-os.org/doc/templates/ , in the section directly above, you use "$ sudo yum remove qubes-template-fedora-23 [sic]". The two examples should use the same version number (in my view).
Wikinaut
commented
Dec 8, 2016
•
This is clear to me, but in your examples on https://www.qubes-os.org/doc/templates/ , in the section directly above, you use "$ sudo yum remove qubes-template-fedora-23 [sic]". The two examples should use the same version number (in my view). |
added a commit
to QubesOS/qubes-doc
that referenced
this issue
Dec 8, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarta
Jul 13, 2018
It should not be possible in R4.0 (assigning the template will just fail), and the documentation has already been improved. I'm closing this one.
marmarta
commented
Jul 13, 2018
|
It should not be possible in R4.0 (assigning the template will just fail), and the documentation has already been improved. I'm closing this one. |
Wikinaut commentedDec 7, 2016
•
edited
Edited 1 time
-
Wikinaut
edited Dec 7, 2016 (most recent)
Qubes OS version (e.g.,
R3.2):R3.2
Affected TemplateVMs (e.g.,
fedora-23, if applicable):Affected: Qubes VM-Manager
Dom0 OSError Errno 2 file not found: /var/lib/qubes/vm-templates/fedora-23/apps.templatesAfter having successfully
by performing these steps
How to reproduce:
I intentionally assigned
fedora-23(remember: I deleted that intentionally) because this was still selectable in the Qubes VM Manager - to one of my AppVM "TestVM".Now, of course, I cannot start that "TestVM".
Problem/Bug
Reassigning an existing template in Qubes VM Manager is impossible.
Suggested solution
Fix the error message and code behaviour, and let user allow to assign an existing TemplateVM.