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

Hints for unity-control-center in universe

unity-appearance-panel.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.

unity-display-panel.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.

unity-datetime-panel.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.

unity-wacom-panel.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.

unity-keyboard-panel.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.

unity-control-center.desktop ⚙ amd64

Warnings

  • 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.

Hints

  • metainfo-validation-hint
    Validation of the metainfo file yielded the following hint: Found invalid tag: 'kudos'. This tag is a GNOME-specific extension to AppStream and is not supported by all implementations.
  • metainfo-validation-hint
    Validation of the metainfo file yielded the following hint: The component ID [unity-control-center.desktop] contains a hyphen/minus. Using a hyphen is strongly discouraged, to keep interoperability with other tools such as D-Bus. Ideally, replace any hyphens with an underscore ('_')

unity-region-panel.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.

unity-bluetooth-panel.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.

unity-power-panel.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.

unity-online-accounts-panel.desktop ⚙ amd64

Warnings

  • category-name-invalid
    The category name OnlineAccounts is invalid. The software can not be shown in this category.

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.

unity-sound-panel.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.

unity-network-panel.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.

unity-screen-panel.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.

unity-info-panel.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.

unity-user-accounts-panel.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.

unity-color-panel.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.

unity-mouse-panel.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.

unity-screen-sharing-panel.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.

general ⚙ amd64

Warnings

  • legacy-metainfo-directory
    The AppStream metainfo file 'unity-control-center.appdata.xml' was found in a legacy path.
    Please install metainfo files into /usr/share/metainfo, as the old path will not be recognized anymore in the future.

unity-universal-access-panel.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.