Linux workstation

openSUSE Leap 16.0 native package

lightdm-gtk-greeter-branding-upstream

Upstream branding of lightdm-gtk-greeter

Packages / openSUSE Leap 16.0 / System/X11/Displaymanagers / lightdm-gtk-greeter-branding-upstream

[Source: lightdm-gtk-greeter]

Package: lightdm-gtk-greeter-branding-upstream (2.0.8-bp160.1.1)

[Project overview: lightdm-gtk-greeter]

External Resources:

Homepage: [github.com]

Similar packages:

Upstream branding of lightdm-gtk-greeter

This package provides the upstream look and feel for lightdm-gtk-greeter.

Other Packages Related to lightdm-gtk-greeter-branding-upstream:

  • enh: packageand(lightdm-gtk-greeter:branding-upstream)

    Package not available

Download lightdm-gtk-greeter-branding-upstream

ArchitecturePackage SizeInstalled SizeFiles
noarch15 KiB2.9 KiB[list of files]

Package file paths (2)

Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.

  • /etc/lightdm
  • /etc/lightdm/lightdm-gtk-greeter.conf

Field source: openSUSE Leap 16.0 OSS revision leap-16-0-oss-multiarch:271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c

Use this package

OpenFactory can boot this operating system in a browser VM, or start a build that includes the native package name from this record.

Try openSUSE Leap 16.0 in the browserBuild an image that includes lightdm-gtk-greeter-branding-upstream

Versions, suites, and repositories

Each row is recorded package-index metadata for one version, architecture, suite, and repository. Names, URLs, and sizes are source-reported; a link is a potentially mutable retrieval location, not an OpenFactory redistribution claim or proof that OpenFactory retained the artifact bytes.

VersionReleaseArchitectureRepositoryPackage sizeInstalled sizePublisher repository artifact
2.0.8-bp160.1.1leap-16.0 / ossnoarchopenSUSE Leap 16.0 · OSS · multi-architecture15 KiB2.9 KiBnoarch/lightdm-gtk-greeter-branding-upstream-2.0.8-bp160.1.1.noarch.rpm

Field source: openSUSE Leap 16.0 OSS revision leap-16-0-oss-multiarch:271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c

Checksums and observation dates

For an APT source, signature verification authenticates the repository metadata chain and the Packages index containing this source-reported artifact digest. It does not certify package safety.

2.0.8-bp160.1.1 / noarchObserved Sep 1, 2026 to Sep 1, 2026

Verification status: Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.

Source-reported sha512: e8741f87362f3f03acc18fd885a3faea38324dd907daa27eafea3836c58d042b51dcf70411190a525083188617bc111f199e356c15ea8aa3b2853744714102ba

Field source: openSUSE Leap 16.0 OSS revision leap-16-0-oss-multiarch:271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c

Catalog record completeness

The completeness score measures metadata coverage, not software quality, security, compatibility, or suitability.

Summary and description
25/25
Artifact path and source digest
25/25
Dependency metadata
15/15
Package-file index
15/15
Homepage
5/5
License text
5/5
Source package or maintainer
10/10

Recorded total: 100/100

Field source: openSUSE Leap 16.0 OSS revision leap-16-0-oss-multiarch:271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c. The cross-OS mapping is catalog-derived from the source-reported homepage; it does not establish authorship or publisher identity

Sources and provenance

Field-source links above resolve here. Each source entry names the metadata publisher, trust tier, exact snapshot revision, signature result, and observation time; catalog-derived mappings are labeled separately.

  • openSUSE Leap 16.0 OSSSep 1, 2026

    Authoritative source; repository metadata signature verified, revision leap-16-0-oss-multiarch:271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c

    Signature verification covers the configured repository metadata chain. It does not certify that the package is safe or suitable.

    Repository-signature verification record
    Signed-object SHA-256
    271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c
    Signer fingerprint
    AD485664E901B867051AB15F35A2F86E29B700A4
    Keyring revision
    opensuse-project-signing-key.asc
    SHA-256 b5745739ebfb95b25b8e810f9bcb847fe750ccda598bd85f02f0e974599a6d7e
    Tool and policy
    gpgv (GnuPG) 2.4.9
    openfactory-software-catalog-signature-v1
    Verification time
    Sep 1, 2026
    Signed Release → package-index hash linkage

    Path: Not recorded
    Expected SHA-256: Not recorded
    Observed SHA-256: Not recorded
    Result: match verified