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 upqvm-clone ProxyVM with '_' char in name produces menu & VM Manager error #3301
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Related: #2422 |
andrewdavidwong
added
bug
C: core
labels
Nov 10, 2017
andrewdavidwong
modified the milestones:
Release 4.0,
Release 3.2 updates
Nov 10, 2017
added a commit
to marmarta/qubes-manager
that referenced
this issue
Jul 13, 2018
marmarta
referenced this issue
in QubesOS/qubes-manager
Jul 13, 2018
Merged
Fixed VM name validation in GUI tools (Create VM, Settings, Manager) (R3.2) #112
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
qubeling commentedNov 9, 2017
•
edited
Edited 1 time
-
qubeling
edited Nov 9, 2017 (most recent)
Qubes OS version:
Qubes release 3.2 (R3.2)
Affected TemplateVMs:
ProxyVM built on debian-8 TemplateVM
Steps to reproduce the behavior:
Expected behavior:
ProxyVM deletes, removing the Applications menu shortcut with it.
Actual behavior:
ProxyVM persists in Applications menu; is not listed in VM Manager, cannot be removed from command-line (A VM with the name 'vpn_1' does not exist in the system error message) as it is quite obviously already gone.
Trying to open programs in the stuck ProxyVM predictably does nothing.
General notes:
Was cloning one of my VPN ProxyVMs and in my haste accidentally produced an underscore instead of hyphen. After experiencing related bug below (1), I removed the entire ProxyVM in order to start the cloning again. However post-removal it is still visible in the applications menu, even though it is not present either in qvm or in the GUI VM Manager. Minor, but incredibly annoying.
Could be mitigated entirely by adding a block of the underscore in qvm-clone as it does block it in GUI renaming.
Related issues:
(1) Went into VM Manager to rename, would not allow me to make a modification. The field was activated as normal, though trying to backspace did not yield results.