Bug 1922533

Summary: Many international google-noto-*-fonts have invalid Appstream data
Product: [Fedora] Fedora Reporter: hank.johnson3002
Component: google-noto-fontsAssignee: Akira TAGOH <tagoh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: fonts-bugs, i18n-bugs, petersen, psatpute, pwu, tagoh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-05 07:29:02 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
List of google-noto-*-fonts packages with Appstream data issues
none
Example `appstreamcli status --verbose` with invalid font Appstream data none

Description hank.johnson3002 2021-01-30 01:48:53 UTC
Created attachment 1752196 [details]
List of google-noto-*-fonts packages with Appstream data issues

Description of problem:

Many international google-noto-*-fonts have invalid Appstream data. This causes warnings in applications using Appstream, like KDE Discover. It also makes many appstreamcli commands not work.

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

Most of them are version 20181223-8.fc33

How reproducible:

Should be easy

Steps to Reproduce:

1. sudo dnf install google-noto-sans-arabic fonts (I will attach a txt file with the full list of google-noto fonts with this issue)

Actual results:

Running `appstreamcli status` warns "Error while loading the metadata pool: Many components have been recognized as invalid. See debug output for details." Verbose output with `appstreamcli status --verbose` is attached in txt file.

Opening KDE Discover creates a warning that "Please make sure that Appstream is properly set up on your system".

Expected results:

Running `appstreamcli status` reports no errors. Opening KDE Discover shows no warning.

Additional info:

Removing the specified fonts fixes the issues. I tried force refreshing appstream cache, rebooting, reinstalling appstream data, etc.

TXT file with list of the violating fonts is attached.

Comment 1 hank.johnson3002 2021-01-30 01:52:44 UTC
Created attachment 1752197 [details]
Example `appstreamcli status --verbose` with invalid font Appstream data

Comment 2 Akira TAGOH 2021-04-05 07:29:02 UTC

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