This seems pretty minor, I don't notice it really affecting usability of Discover, but I don't know exactly what to look for.
At the end of the output of appstreamcli status, there's this line, which might indicate the reason for this message:
appstreamcli status
Error while loading the metadata pool: Many components have been recognised as invalid. See debug output for details.
By "see debug output", I think it means appstreamcli status --verbose, which spits out tons of output. I'm not sure exactly what to look for here, but there's quite a few lines that say No component found in desktop-entry file: <thing>.desktop
appstreamcli status --verbose
No component found in desktop-entry file: <thing>.desktop
And later on, there's a few warnings:
WARNING: Ignored component 'google-noto-sans': The component is invalid. WARNING: Ignored component 'google-noto-sans-sinhala-vf': The component is invalid. WARNING: Ignored component 'google-noto-sans-gurmukhi': The component is invalid. WARNING: Ignored component 'google-noto-sans-mono': The component is invalid.
This was all done in a pretty clean fedora 34 VM.
These are packaging bugs on those fonts, please file it on them in the Red Hat Bugzilla, please.
How should I do the bug reports? Like, is there any more detail I can give besides filing them on product:Fedora component:google-noto-sans or whatever, and just saying "Appstream says the component is invalid"? I'm not sure where to go to find any more detail
That's pretty much what you should do.
Apparently there is no component of the Fedora product that matches those component names, since apparently those packages don't exist (try dnf info google-noto-sans, no matches are found), so I'm not sure what to do now
dnf info google-noto-sans
Each package has the URL to their bug tracker in the package itself.
rpm -qi <packagename> will reveal it for you.
rpm -qi <packagename>
For example: rpm -qi google-noto-sans-fonts will give you the following info:
rpm -qi google-noto-sans-fonts
Name : google-noto-sans-fonts Version : 20181223 Release : 9.fc34 Architecture: noarch Install Date: Sat 10 Apr 2021 07:41:09 PM EDT Group : Unspecified Size : 34132926 License : OFL Signature : RSA/SHA256, Tue 26 Jan 2021 05:44:44 PM EST, Key ID 1161ae6945719a39 Source RPM : google-noto-fonts-20181223-9.fc34.src.rpm Build Date : Tue 26 Jan 2021 04:03:29 PM EST Build Host : buildhw-x86-10.iad2.fedoraproject.org Packager : Fedora Project Vendor : Fedora Project URL : https://github.com/googlei18n/noto-fonts/ Bug URL : https://bugz.fedoraproject.org/google-noto-fonts Summary : Sans font Description : Noto fonts aims to remove tofu from web by providing fonts for all Unicode supported scripts. Its design goal is to achieve visual harmonization between multiple scripts. Noto family supports almost all scripts available in Unicode. Noto Sans font.
https://bugzilla.redhat.com/show_bug.cgi?id=1830709#c4 If I'm reading things correctly, it looks like this bug has been fixed, but the fix has been pushed to Fedora 35...
That update has been pushed to f34, which fixes this bug for me.
Metadata Update from @eiglow: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.