Skip to main content

Where an upstream finding goes

DeskOS measures things on purpose: a boot check, a session assertion, a scan, a re-pin. When the cause is upstream, the finding belongs to that project, with the measurement attached.

Rules​

  • A person files it. An agent may draft the report; a human sends it.
  • Attach the measurement: run, digest, check and output. "It does not work" is not a report.
  • One finding, one venue. If two projects are involved, say which part is whose.
  • Our own bugs stay here. The GDM login logo was ours: the plan wrote the key to the distro database and GDM reads system-db:gdm (#247).

The venues​

FindingVenueWhat we can attachFiled
bootc install and first bootbootc-dev/bootcthe first-boot check and its summary; the composefs finding that /run/ostree-booted is absent on a bootc host (#177)no
Fedora image modeFedora bootc docsthe Fedora example build and its weekly check; a released-compose re-pinno
AlmaLinux atomic desktopAlmaLinux/atomic-desktopthe AlmaLinux example build and boot in examples-weekly.ymlno
CentOS Stream and alternative imagesthe Alternative Images SIG in the CentOS GitLab groupa base re-review and its scan; a package only CRB carries, so a composed image cannot install it (virt-manager on stream10)no
GNOME and the login screengitlab.gnome.org/GNOME/gdma greeter behaviour reproduced in the VM, with the digest and the database it readno
Flatpak preinstallthe Flatpak trackerthe preinstall unit the plan emits and what first boot observedno

Nothing in the table has been filed. That is the state, not a plan.

What the measurements support​

  • A host without /run/ostree-booted. Detection for a bootc host that is not ostree, with the digest and the bootc status --json output that identifies it.
  • First-boot setup suppressed by an existing account. The Ubuntu root cause, GDM counting users through AccountsService and a uid-1000 account hiding the wizard, is in research-notes.md with the reproduction.
  • A base whose only copy of a tool is in CRB. What an image-based workstation should do when a requirement lives in an unsupported repository; our answer is that the organization decides.

Not a promise​

This page is not a roadmap of upstream work and does not promise to file anything. A finding nobody reports is still a finding; this page keeps it where a report would start.