More safeguards for a VM that started in a weird way
If for any reason adding a VM failed, Qube Manager will attempt to add it on the next state event it receives. references QubesOS/qubes-issues#5066
This commit is contained in:
		
							parent
							
								
									492b8705b6
								
							
						
					
					
						commit
						8c1a9e5120
					
				@ -596,6 +596,8 @@ class VmManagerWindow(ui_qubemanager.Ui_VmManagerWindow, QtGui.QMainWindow):
 | 
				
			|||||||
            self.vms_in_table[vm.qid].info_widget.update_vm_state()
 | 
					            self.vms_in_table[vm.qid].info_widget.update_vm_state()
 | 
				
			||||||
        except exc.QubesPropertyAccessError:
 | 
					        except exc.QubesPropertyAccessError:
 | 
				
			||||||
            return  # the VM was deleted before its status could be updated
 | 
					            return  # the VM was deleted before its status could be updated
 | 
				
			||||||
 | 
					        except KeyError:  # adding the VM failed for some reason
 | 
				
			||||||
 | 
					            self.on_domain_added(None, None, vm)
 | 
				
			||||||
 | 
					
 | 
				
			||||||
        if vm == self.get_selected_vm():
 | 
					        if vm == self.get_selected_vm():
 | 
				
			||||||
            self.table_selection_changed()
 | 
					            self.table_selection_changed()
 | 
				
			||||||
 | 
				
			|||||||
		Loading…
	
		Reference in New Issue
	
	Block a user