⇦ | thunar [universe]
Last updated on: 2018-04-27 01:33 [UTC]

Hints for thunar in universe

Thunar.desktop ⚙ amd64

Warnings

  • metainfo-validation-issue
    Validation of the metainfo file found a problem: Found invalid tag: 'updatecontact'. Non-standard tags must be prefixed with "x-".
  • metainfo-validation-issue
    Validation of the metainfo file found a problem: The screenshot does not contain any images.
  • metainfo-validation-issue
    Validation of the metainfo file found a problem: The component ID is not a reverse domain-name. Please update the ID and that of the accompanying .desktop file to follow the latest version of the Desktop-Entry and AppStream specifications and avoid future issues.
  • metainfo-validation-issue
    Validation of the metainfo file found a problem: The component is missing a name (<name/> tag).

Hints

  • metainfo-validation-hint
    Validation of the metainfo file yielded the following hint: The id tag for "Thunar.desktop" still contains a 'type' property, probably from an old conversion.

thunar-settings.desktop ⚙ amd64

Hints

  • description-from-package
    This component gets its description from the package it is located in.
    This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.
    Please consider writing a metainfo file for this component to take the long description upstream. In future, components without metainfo file might be dropped from the metadata entirely. You can consult the XML quickstart guides for more information on how to write a metainfo file.

Thunar-bulk-rename.desktop ⚙ amd64

Hints

  • description-from-package
    This component gets its description from the package it is located in.
    This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.
    Please consider writing a metainfo file for this component to take the long description upstream. In future, components without metainfo file might be dropped from the metadata entirely. You can consult the XML quickstart guides for more information on how to write a metainfo file.