⇦ | rss-glx [main]
Last updated on: 2026-02-23 14:12 [UTC]

Hints for rss-glx in main

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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>skyrocket.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>plasma.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>solarwinds.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 component's MetaInfo file has a <code>summary</code> tag, or that its .desktop file has a <code>Comment=</code> field set.<br/>More information can be found in the <a href="https://specifications.freedesktop.org/desktop-entry-spec/latest/localized-keys.html">Desktop Entry specification</a> and the <a href="https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Application.html#tag-dapp-summary">MetaInfo specification</a>.

Warnings

  • asv-desktop-entry-category-invalid
    <code>lorenz.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> for more information on how to write a MetaInfo file, or file a bug with the upstream author of this software component.

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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>lattice.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>hyperspace.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>spirographx.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>matrixview.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>flocks.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>sundancer2.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>busyspheres.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>euphoria.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>biof.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 component's MetaInfo file has a <code>summary</code> tag, or that its .desktop file has a <code>Comment=</code> field set.<br/>More information can be found in the <a href="https://specifications.freedesktop.org/desktop-entry-spec/latest/localized-keys.html">Desktop Entry specification</a> and the <a href="https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Application.html#tag-dapp-summary">MetaInfo specification</a>.

Warnings

  • asv-desktop-entry-category-invalid
    <code>hufo_tunnel.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>colorfire.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>hufo_smoke.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>drempels.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>fieldlines.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>flux.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>pixelcity.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>cyclone.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>feedback.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> 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 <code>Type=Application</code>), but we could not find a matching icon for this application.

Warnings

  • asv-desktop-entry-category-invalid
    <code>helios.desktop</code> - <em>Screensaver</em><br/>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 <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> for more information on how to write a MetaInfo file, or file a bug with the upstream author of this software component.