Bugzilla – Bug 1072581
virt-manager fails to open VM window a second time: 'NoneType' object has no attribute 'change_run_text'
Last modified: 2017-12-13 15:32:42 UTC
Created attachment 752773 [details]
I'm using virt-manager to interact with a couple of libvirtd managed machines. This used to work fine when I was using only one machine, but as I added another machine I got seemingly spurious errors.
I nailed it down to opening the VM window a second time. First time it works OK, second time it fails with
summary=Error launching details: 'NoneType' object has no attribute 'change_run_text'
details=Error launching details: 'NoneType' object has no attribute 'change_run_text'
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 837, in _show_vm_helper
File "/usr/share/virt-manager/virtManager/details.py", line 653, in show
File "/usr/share/virt-manager/virtManager/details.py", line 1316, in refresh_vm_state
File "/usr/share/virt-manager/virtManager/details.py", line 1299, in change_run_text
AttributeError: 'NoneType' object has no attribute 'change_run_text'
The only workaround is to kill virt-manager and start it up again. It only works once per virtual machine, the second time it always fails with the same error.
A slightly simpler within virt-manager is to disconnect/connect from the 'QEMU/KVM' connection
A fix for this is available in the Factory virt-manager. Hopefully the next
Tumbleweed build will have it.
*** This bug has been marked as a duplicate of bug 1071825 ***
That was fast! Thanks for the rapid response.