⇦ | simon [xenial]
Last updated on: 2016-11-16 10:55:26 UTC

Hints for simon in xenial

simon/0.4.1-0ubuntu9: ksimond.desktop ⚙ amd64 ⚙ armhf ⚙ i386 ⚙ s390x ⚙ arm64 ⚙ ppc64el ⚙ powerpc

Errors

  • metainfo-no-summary
    Component does not contain a short summary. Ensure that the components metainfo file has a summary tag, or that its .desktop file has a Comment= field set. Especially applications by KDE often use the GenericName field for a short summary, instead of the Comment field (which is not its intended use case).
    More information can be found in the Desktop Entry specification.

Hints

  • description-from-package
    This component gets its description from the package it is located in.
    This has several disadvantages, like missing localization, possibly too short descriptions, too technical descriptions for users of software centers, etc.
    Please consider writing a metainfo file for this component. In the near future, components without metainfo file might be dropped from the metadata. You can consult the XML quickstart guide for more information on how to write a metainfo file.

simon/0.4.1-0ubuntu9: simond.desktop ⚙ amd64 ⚙ armhf ⚙ i386 ⚙ s390x ⚙ arm64 ⚙ ppc64el ⚙ powerpc

Errors

  • metainfo-no-summary
    Component does not contain a short summary. Ensure that the components metainfo file has a summary tag, or that its .desktop file has a Comment= field set. Especially applications by KDE often use the GenericName field for a short summary, instead of the Comment field (which is not its intended use case).
    More information can be found in the Desktop Entry specification.

Hints

  • description-from-package
    This component gets its description from the package it is located in.
    This has several disadvantages, like missing localization, possibly too short descriptions, too technical descriptions for users of software centers, etc.
    Please consider writing a metainfo file for this component. In the near future, components without metainfo file might be dropped from the metadata. You can consult the XML quickstart guide for more information on how to write a metainfo file.

simon/0.4.1-0ubuntu9: ssc.desktop ⚙ amd64 ⚙ armhf ⚙ i386 ⚙ s390x ⚙ arm64 ⚙ ppc64el ⚙ powerpc

Errors

  • icon-not-found
    The icon 'ssc' was not found in the archive. This issue can have multiple reasons:
    • The icon is not present in the archive.
    • The icon is in a wrong directory.
    • The icon is not available in a suitable size (at least 64x64px)
    To make the icon easier to find, place it in /usr/share/icons/hicolor/<size>/apps and ensure the Icon= value of the .desktop file is set correctly.
  • gui-app-without-icon
    The GUI application (application which has a .desktop file for the XDG menu and Type=Application) with AppStream-ID 'ssc.desktop' has been found, but we could not find a matching icon.

simon/0.4.1-0ubuntu9: sam.desktop ⚙ amd64 ⚙ armhf ⚙ i386 ⚙ s390x ⚙ arm64 ⚙ ppc64el ⚙ powerpc

Errors

  • metainfo-no-summary
    Component does not contain a short summary. Ensure that the components metainfo file has a summary tag, or that its .desktop file has a Comment= field set. Especially applications by KDE often use the GenericName field for a short summary, instead of the Comment field (which is not its intended use case).
    More information can be found in the Desktop Entry specification.

Hints

  • description-from-package
    This component gets its description from the package it is located in.
    This has several disadvantages, like missing localization, possibly too short descriptions, too technical descriptions for users of software centers, etc.
    Please consider writing a metainfo file for this component. In the near future, components without metainfo file might be dropped from the metadata. You can consult the XML quickstart guide for more information on how to write a metainfo file.

simon/0.4.1-0ubuntu9: simon.desktop ⚙ amd64

Hints

  • description-from-package
    This component gets its description from the package it is located in.
    This has several disadvantages, like missing localization, possibly too short descriptions, too technical descriptions for users of software centers, etc.
    Please consider writing a metainfo file for this component. In the near future, components without metainfo file might be dropped from the metadata. You can consult the XML quickstart guide for more information on how to write a metainfo file.

simon/0.4.1-0ubuntu9: sscd.desktop ⚙ amd64 ⚙ armhf ⚙ i386 ⚙ s390x ⚙ arm64 ⚙ ppc64el ⚙ powerpc

Errors

  • icon-not-found
    The icon 'sscd' was not found in the archive. This issue can have multiple reasons:
    • The icon is not present in the archive.
    • The icon is in a wrong directory.
    • The icon is not available in a suitable size (at least 64x64px)
    To make the icon easier to find, place it in /usr/share/icons/hicolor/<size>/apps and ensure the Icon= value of the .desktop file is set correctly.
  • gui-app-without-icon
    The GUI application (application which has a .desktop file for the XDG menu and Type=Application) with AppStream-ID 'sscd.desktop' has been found, but we could not find a matching icon.

simon/0.4.1-0ubuntu9: afaras.desktop ⚙ amd64 ⚙ armhf ⚙ i386 ⚙ s390x ⚙ arm64 ⚙ ppc64el ⚙ powerpc

Errors

  • metainfo-no-summary
    Component does not contain a short summary. Ensure that the components metainfo file has a summary tag, or that its .desktop file has a Comment= field set. Especially applications by KDE often use the GenericName field for a short summary, instead of the Comment field (which is not its intended use case).
    More information can be found in the Desktop Entry specification.

Hints

  • description-from-package
    This component gets its description from the package it is located in.
    This has several disadvantages, like missing localization, possibly too short descriptions, too technical descriptions for users of software centers, etc.
    Please consider writing a metainfo file for this component. In the near future, components without metainfo file might be dropped from the metadata. You can consult the XML quickstart guide for more information on how to write a metainfo file.