RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1435806 - Busted italian translation breaks virt-manager
Summary: Busted italian translation breaks virt-manager
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 1442982 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-24 20:48 UTC by Cole Robinson
Modified: 2017-08-01 21:04 UTC (History)
8 users (show)

Fixed In Version: virt-manager-1.4.1-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 21:04:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2072 0 normal SHIPPED_LIVE virt-manager bug fix and enhancement update 2017-08-01 18:36:34 UTC

Description Cole Robinson 2017-03-24 20:48:42 UTC 
See this fedora bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1433800

it.po mixed up a python format string, which heavily breaks the app. There were a couple other less common translation format errors as well.

You can either cherry pick these 4 commits below, or just copy it.po and ko.po from upstream git and make a single commit out of those changes:

commit f5d709d9d06929d68e2090f0c52e41a55e30293e
Author: Cole Robinson <crobinso>
Date:   Mon Mar 20 16:43:58 2017 -0400

    Update italian translation from zanata

commit c66098f3b63d53dec514cf59266f57d32960a3ea
Author: Cole Robinson <crobinso>
Date:   Mon Mar 20 16:45:47 2017 -0400

    Fix busted italian translation, again (bug 1433800)

commit 452a693e0ad6b7d535890264916de3b69710f279
Author: Cole Robinson <crobinso>
Date:   Tue Mar 21 19:26:59 2017 -0400

    Update some translations

commit 6b5106eae6e5f3f34d705de35e6baf0ef7feb02e
Author: Cole Robinson <crobinso>
Date:   Tue Mar 21 19:28:36 2017 -0400

    Fix format errors in it.po and ko.po
Comment 2 Cole Robinson 2017-04-18 14:05:35 UTC 
*** Bug 1442982 has been marked as a duplicate of this bug. ***
Comment 5 zhoujunqin 2017-04-26 03:29:29 UTC 
I can reproduce this issue with build:
virt-manager-1.4.0-2.el7.noarch

Steps:
1. Set system language to it_IT.
# export LANG=it_IT.UTF-8
# echo $LANG
it_IT.UTF-8

2. Launch virt-manager.
# virt-manager

3. Create new vm

4. After wizard try to start installation, meet 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 798, in _get_details_dialog
    obj = vmmDetails(conn.get_vm(connkey))
  File "/usr/share/virt-manager/virtManager/details.py", line 363, 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'

Then try to verify this bug with new build:
libvirt-3.2.0-3.el7.x86_64
virt-manager-1.4.1-2.el7.noarch
qemu-kvm-rhev-2.8.0-6.el7.x86_64

Steps as above, no error prompt, guest can be installed successfully.

@Pavel, my verification for this bug just covered virt-manager UI usage, now there is no error while starting guest installation.
And i also noticed that there are some update for translation, shall we need cover this part or let Globalization and localization testing workmates to do it, thanks.
Waiting for your feedback.
Comment 6 Pavel Hrdina 2017-04-26 09:46:41 UTC 
This bug is about the error during installation, it should not happen.  So it can be moved to VERIFIED.  There is a separate Bug 1375044 to work on translation that will be handled by globalization and localization team.
Comment 7 zhoujunqin 2017-04-26 10:37:59 UTC 
(In reply to Pavel Hrdina from comment #6)
> This bug is about the error during installation, it should not happen.  So
> it can be moved to VERIFIED.  There is a separate Bug 1375044 to work on
> translation that will be handled by globalization and localization team.

Thanks for your feedback, Pavel.
So move this bug from ON_QA to VERIFIED
Comment 8 errata-xmlrpc 2017-08-01 21:04:33 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2072
Note You need to log in before you can comment on or make changes to this bug.