-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Moving, Deleting and Cloning a VM doesn't work correctly #5147
Comments
Can you try the latest v4.2.x beta? The move functionality has been re-worked. |
Thanks for the answer! I tried the new beta version (4.2.2), and it was actually a bit weird. Moving.VM.in.UTM.4.2.2.mp4Furthermore, I have tried the other options in the same right-click menu and I've noticed that the same bug seems to be implemented in other options as well (the behaviours I'll describe now are identical in the stable version 4.1.6 and beta version 4.2.2). Cloning.VM.in.UTM.4.2.2.mp4(You can see a different graphical bug in this video that the lower elements aren't displayed correctly after cloning; sometimes the same also happened with the last element when creating a new VM, but this isn't related to this issue and only happened in the 4.2.2 beta version and not in the 4.1.6 version.) And also when using the Delete function, the confirmation screens opens twice, each trying to delete it (after I pressed confirm the second time, an error message, saying that the VM couldn't be deleted (since it doesn't exist anymore), opens): Deleting.VM.in.UTM.4.2.2.mp4(I also noticed that the Delete button is weirdly the only German element in the menu while everything else is in English, and depending on whether it has been moved it even has two different translations: Löschen for non-moved and Entfernen for moved VMs.) Since it seems to be the same underlying bug implemented in these different options, should I rename my issue to also explicitly include those? Every other function works correctly though and doesn't open two screens. Funny enough, that includes the Share function (although it also opens a file system window): Sharing.VM.in.UTM.4.2.2.mp4 |
i have this issue too, but when moving it, it just has a loading icon infinitely, and when i do restart it, it cloned the vm into the directory it was supposed to move it to, and when trying to start it, i get an error: |
@KillzTheSpy2 did you try on 4.3.2 beta? |
im downloading it rn |
i just did, same issue |
when i go to move it, it becomes unresponsive and i have to force quit it |
There's a number of issues with SwiftUI on macOS 11 which has been fixed in macOS 12. We have workarounds for many such issues but certain things like double confirmation popups cannot really be fixed without significant rework. I believe the functionality still works but only if you accept one of the two confirmation (I can't remember which one). Can you see if that works for you? I think I am going to leave this as "won't fix" because it falls in the bucket of macOS 11 issues that would add complexity to the codebase in order to address. In the next major update to UTM, we're probably going to drop support for macOS 11. |
Describe the issue
When you right click on a VM and select "Move" to move the VM, a confirmation screen appears as expected. If you confirm to move, a file manager window should open to select where to move the VM to.
But instead, the confirmation screen opens a second time. If you confirm again, it closes and nothing happens. Only if you then click to run the VM, the file manager window opens and you can select where to move the VM to.
The moving works if you do this, but this window should just open directly after confirming to move the VM.
Here is a video showing the bug:
UTM.Move.VM.Bug.mp4
Configuration
No crash log or debug log since the app didn't crash and the issue isn't related to running a VM.
The text was updated successfully, but these errors were encountered: