I can reproduce this, somewhat, using remote connections. Can you verify that this happens to you connecting remotely, that is libvirt is not on the same host as virt-manager?
However, restarting libvirt on the server is not necessary (for me) - I can simply close and restart virt-manager on the client. Can you also confirm (or deny) that?
Thanks for taking the time to report this bug.
I can reproduce this, somewhat, using remote connections. Can you verify that this happens to you connecting remotely, that is libvirt is not on the same host as virt-manager?
However, restarting libvirt on the server is not necessary (for me) - I can simply close and restart virt-manager on the client. Can you also confirm (or deny) that?