Comment 6 for bug 837275

Well I verified that the version i had that was working was 0.9.1-1ubuntu2 and 0.9.1-1ubuntu3 doesn't. So the bug was introduced in http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/virt-manager/precise/revision/58/src/virtManager/domain.py

So this is probably different than Paul van Genderen's problem was.

Since I've been looking at this 0.9.1-1ubuntu4 has been released. While apt-get update+upgrade doesn't give it to me yet, looking at http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/virt-manager/precise/revision/59?start_revid=59 doesn't look likely to fix it.

Looking at the upstream code repos from http://virt-manager.org/scmrepo.html the code there that is relevant to this has changed significantly, but introduces a new version of this bug that causes the same problem. I'm going to go try to file a bug+patch up there.