Multiple entries in VM list show up when cloning fails

[ktprograms]

Describe the issue
Due to an earlier crash, one of my VMs (call it A.utm) got moved to A 2.utm (but it's still called A in the VM list). When I now try to clone A, I got an error that it couldn't be moved since A 2.utm already exists. After that (I did it again to see if it was a fluke), I now have 2 more VMs called A in the VM list.

Configuration

• UTM Version: 4.0.9
• macOS Version: 12.5.1
• Mac Chip (Intel, M1, ...): M1

[ktprograms]

I also had this similar thing happen a different way:
I cloned a VM, and after that both have the same name. I then clicked edit on the clone, but didn't change the name. Then, I either clicked cancel or save (can't remember which) and it gave an error that " 2.utm" couldn't be created as it already exists, and then after quitting and reopening the app I had three VMs (seemingly one "ghost" vm from the failed save)

[osy]

Forgot to close it with 05bb6d3

[ktprograms]

Thanks, will test this with the next release.

[ktprograms]

Yeah, seems to correctly use the "- 2" name in the UI.