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:
Anaconda warnings like GtkWarning: Failed to set text from markup due to error parsing markup: Error on line 2 char 32: Element 'markup' was closed, but the currently open element is 'NAME' 

Version-Release number of selected component (if applicable):
13.21.251

How reproducible:
Non

Steps to Reproduce:
1.Install OS 
2.Reboot
3.Check anaconda log

Actual results:


Expected results:


Additional info:

Hello Lenovo,
Please attach the anaconda log from this issue.
Please confirm which releases this is being tested on.

Please confirm all steps used to recreate this issue.

Would you be able to confirm if this worked correctly on RHEL 6.7?

Thank You
Joe Kachuck

Created attachment 1145839 [details]
anaconda.log

Hi Joseph, 
Actually, I don't need to do any thing. The warnings are in the log file after install a fresh OS and finish the first boot.
I have the same warning on RHEL 6.7.

https://github.com/rhinstaller/anaconda/pull/823

https://github.com/rhinstaller/anaconda/pull/895

Retested with anaconda-13.21.261-1.el6, no gtk warnings are present in anaconda.log.

Moving to VERIFIED.

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://rhn.redhat.com/errata/RHBA-2017-0720.html