Hints for gnome-system-monitor in main
gnome-system-monitor.desktop ⚙ amd64
Warnings
-
asv-cid-desktopapp-is-not-rdns
gnome-system-monitor.appdata.xml:4
- gnome-system-monitor.desktop
The component ID is not a reverse domain-name. Please update the ID to avoid future issues and be compatible with all AppStream implementations. You may also consider to update the name of the accompanying .desktop file to follow the latest version of the Desktop-Entry specification and use a rDNS name for it as well. In any case, do not forget to mention the new desktop-entry in a <launchable/> tag for this component to keep the application launchable from software centers and the .desktop file data associated with the metainfo data. -
internal-unknown-tag
The generator emitted a tag 'internal-unknown-tag' which is unknown. This is a bug in the metadata generator, please file a bugreport. -
internal-unknown-tag
The generator emitted a tag 'internal-unknown-tag' which is unknown. This is a bug in the metadata generator, please file a bugreport. -
internal-unknown-tag
The generator emitted a tag 'internal-unknown-tag' which is unknown. This is a bug in the metadata generator, please file a bugreport.
Hints
-
asv-cid-missing-affiliation-gnome
gnome-system-monitor.appdata.xml:4
- gnome-system-monitor.desktop
The component is part of the GNOME project, but its ID does not start with GNOME's reverse-DNS name ("org.gnome"). -
asv-url-not-secure
gnome-system-monitor.appdata.xml:541
- http://www.gnome.org/friends/
Consider using a secure (HTTPS) URL for this web link.
gnome-system-monitor-kde.desktop ⚙ amd64
Hints
-
description-from-package
This software component gets its description from the package it is located in.
This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.
Please consider to either hide this .desktop file from AppStream by adding aX-AppStream-Ignore=true
field to its .desktop file, or to write a MetaInfo file for this component to take the long description upstream. In future, components without MetaInfo file might be dropped from the metadata entirely. You can consult the XML quickstart guides for more information on how to write a MetaInfo file.