⇦ | gjacktransport [main]
Last updated on: 2024-10-07 20:14 [UTC]

Hints for gjacktransport in main

gjackclock.desktop ⚙ amd64

Errors

  • icon-too-small
    Only a very small icon ('gjacktransport_gjackclock.png', 32x32px) could be located. Please try to supply a bigger icon (at least 64x64px) in the Freedesktop icon path (/usr/share/icons/hicolor/%size%/apps/).
  • icon-not-found
    The icon 'gjackclock' 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)
    • On Debian and Ubuntu, the icon is a symlink. The generator cannot read symlinks on these distributions - make the icon a real file.
    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.

Warnings

  • no-metainfo
    This software component is missing a MetaInfo file to provide metadata.
    We currently took some data from its desktop-entry file and the long description of 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.
    Additionally, a lot of software with desktop-entry files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be tagged accordingly via MetaInfo files.
    Please consider to either hide this desktop-entry file from AppStream by adding a X-AppStream-Ignore=true field to it, or to write a MetaInfo file for this component and send it upstream.
    Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software may vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers) in a future distribution release.
    You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug with the upstream author of this software component.

gjacktransport.desktop ⚙ amd64

Errors

  • icon-too-small
    Only a very small icon ('gjacktransport_gjacktransport.png', 32x32px) could be located. Please try to supply a bigger icon (at least 64x64px) in the Freedesktop icon path (/usr/share/icons/hicolor/%size%/apps/).
  • icon-not-found
    The icon 'gjacktransport' 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)
    • On Debian and Ubuntu, the icon is a symlink. The generator cannot read symlinks on these distributions - make the icon a real file.
    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.

Warnings

  • no-metainfo
    This software component is missing a MetaInfo file to provide metadata.
    We currently took some data from its desktop-entry file and the long description of 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.
    Additionally, a lot of software with desktop-entry files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be tagged accordingly via MetaInfo files.
    Please consider to either hide this desktop-entry file from AppStream by adding a X-AppStream-Ignore=true field to it, or to write a MetaInfo file for this component and send it upstream.
    Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software may vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers) in a future distribution release.
    You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug with the upstream author of this software component.