Description of problem: After upgrade virt-manager 1.4.1-1.fc25 on fedora 25 if I try to open a the console of any existent VM I receive an error Errore nell'avvio dei dettagli: 'nome-mv' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 820, in _show_vm_helper details = self._get_details_dialog(uri, vm.get_connkey()) File "/usr/share/virt-manager/virtManager/engine.py", line 797, in _get_details_dialog obj = vmmDetails(conn.get_vm(connkey)) File "/usr/share/virt-manager/virtManager/details.py", line 395, in __init__ self.console = vmmConsolePages(self.vm, self.builder, self.topwin) File "/usr/share/virt-manager/virtManager/console.py", line 128, in __init__ self._change_title() File "/usr/share/virt-manager/virtManager/console.py", line 291, in _change_title "connection-name": self.vm.conn.get_pretty_desc(), KeyError: 'nome-mv' Version-Release number of selected component (if applicable): virt-manager-1.4.1-1.fc25.noarch virt-manager-common-1.4.1-1.fc25.noarch How reproducible: Open details/console of any VM, powered on or off Steps to Reproduce: 1. Start Virt Manager 2. Create new vm 3. after wizard try to start vm Actual results: Errore nell'avvio dei dettagli: 'nome-mv' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 820, in _show_vm_helper details = self._get_details_dialog(uri, vm.get_connkey()) File "/usr/share/virt-manager/virtManager/engine.py", line 797, in _get_details_dialog obj = vmmDetails(conn.get_vm(connkey)) File "/usr/share/virt-manager/virtManager/details.py", line 395, in __init__ self.console = vmmConsolePages(self.vm, self.builder, self.topwin) File "/usr/share/virt-manager/virtManager/console.py", line 128, in __init__ self._change_title() File "/usr/share/virt-manager/virtManager/console.py", line 291, in _change_title "connection-name": self.vm.conn.get_pretty_desc(), KeyError: 'nome-mv' Expected results: Open VM details as usual Additional info: Workaround: rename /usr/share/locale/it/LC_MESSAGES/virt-manager.mo and restart virt-manager
*** This bug has been marked as a duplicate of bug 1433800 ***