⇦ | rss-glx [main]
Last updated on: 2024-12-18 02:13 [UTC]

Hints for rss-glx in main

lattice.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    lattice.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

fieldlines.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    fieldlines.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

spirographx.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    spirographx.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

skyrocket.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    skyrocket.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

euphoria.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    euphoria.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

biof.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    biof.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

pixelcity.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    pixelcity.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

hufo_smoke.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    hufo_smoke.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

sundancer2.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    sundancer2.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

helios.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    helios.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

cyclone.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    cyclone.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

lorenz.desktop ⚙ amd64

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.
    More information can be found in the Desktop Entry specification and the MetaInfo specification.

Warnings

  • asv-desktop-entry-category-invalid
    lorenz.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

busyspheres.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    busyspheres.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

flocks.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    flocks.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

hyperspace.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    hyperspace.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

drempels.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    drempels.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

matrixview.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    matrixview.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

colorfire.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    colorfire.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

plasma.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    plasma.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

hufo_tunnel.desktop ⚙ amd64

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.
    More information can be found in the Desktop Entry specification and the MetaInfo specification.

Warnings

  • asv-desktop-entry-category-invalid
    hufo_tunnel.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

flux.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    flux.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

solarwinds.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    solarwinds.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

feedback.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    feedback.desktop - Screensaver
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.