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.

Description of problem:
Failed to show vm's name and installation type when create a new guest via virt-manager

Version-Release number of selected component (if applicable):
virt-manager-1.1.0-1.el7.noarch
virt-install-1.1.0-1.el7.noarch
virt-manager-common-1.1.0-1.el7.noarch
kernel-3.10.0-153.el7.x86_64
libvirt-1.2.8-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Launch virt-manager.
2. Create a new vm by clicking: File---> New Virtual Machine or clicking "Create a new virtual machine" directly.

Actual results:
1. After clicking "New Virtual Machine", installation New VM window prompt(1/5), but cannot show vm's name and installation type. (Screenshot-1)
2. Click "Forward" button, we can see "Local install media(ISO image or CDROM)" installation type has been chosen by default(2/5).(Screenshot-2)
3. Also found on step 3/5, the Memory Unit is 1024 MiB and step 4/5 Storage Unit is 9.0 GiB (Screenshot-3), before unit is MB and GB.

Expected results:
1. Can showing vm's name and installation type successfully as before.(Screenshot-4)
2. Memory and Storage unit should changed to MB & GB.

Additional info:

Created attachment 935565 [details]
Screenshot-1

Created attachment 935566 [details]
Screenshot-2

Created attachment 935567 [details]
Screenshot-3

Created attachment 935569 [details]
Screenshot-4

unfortunately it is a pygobject issue.  There are similar errors in the UI caused by the same issue

*** This bug has been marked as a duplicate of bug 1138372 ***

After update package to latest build:
pygobject3-base-3.8.2-6.el7.x86_64
pygobject3-3.8.2-6.el7.x86_64
virt-manager-1.1.0-3.el7.noarch

Comment 0 issue has no long reproduced, virt-manager can show items showing correctly.
And about "2. Memory and Storage unit should changed to MB & GB." i have confirmed with dev, it made more precise, so GiB and MiB showing is correctly.

Result: virt-manager works well with new version.