Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1705583

Summary: org.gnome.baobab.gschema.xml not valid against DTD
Product: Red Hat Enterprise Linux 8 Reporter: Martin Krajnak <mkrajnak>
Component: baobabAssignee: Ondrej Holy <oholy>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0CC: jkoten
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: baobab-3.28.0-2.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:14:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
custom validation script none

Description Martin Krajnak 2019-05-02 14:02:06 UTC
Created attachment 1561673 [details]
custom validation script

Description of problem:
Based on the discussion with cgarnch. the file org.gnome.baobab.gschema.xml, 
located in /usr/share/glib-2.0/schemas should be valid against this DTD schema:

https://gitlab.gnome.org/GNOME/glib/blob/master/gio/gschema.dtd

which is not a case.

Version-Release number of selected component (if applicable):
baobab-3.28.0-1.el8.x86_64

How reproducible:
always

Actual results:
Around 500 errors: 
.
.
.
/org.gnome.baobab.gschema.xml:581:0:ERROR:VALID:DTD_UNKNOWN_ATTRIBUTE: No declaration for attribute lang of element description

Expected results:
There should be no errors

Additional info:
I am attaching script in python3 I used for validation.

Comment 1 Ondrej Holy 2019-05-03 09:01:55 UTC
The following commit should fix this:
https://gitlab.gnome.org/GNOME/baobab/commit/80f7e1c144103d52a877f2d42db6a427867591f6

Comment 2 Martin Krajnak 2019-05-06 10:48:25 UTC
(In reply to Ondrej Holy from comment #1)
> The following commit should fix this:
> https://gitlab.gnome.org/GNOME/baobab/commit/
> 80f7e1c144103d52a877f2d42db6a427867591f6

Yes, I can confirm that I tested the schema after path and it passes validation.

Comment 4 Martin Krajnak 2019-07-09 12:54:21 UTC
no erorrs in 
baobab-3.28.0-2.el8.x86_6

Comment 6 errata-xmlrpc 2019-11-05 22:14:04 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/RHSA-2019:3553