Skip to content

parity(dakota): kmscon for VT consoles #1237

Closed

Description

@hanthor

GNOME OS (gnome-build-meta kmscon.bst) replaces getty on the VTs with kmsconvt@ (font Adwaita Mono, gdm drop-in Conflicts=kmsconvt@tty1). Dakota runs kmsconvt@.service and disables getty@.service. Utah runs plain getty@.

Needs kmscon in the factory (new spec or Fedora recipe), then the presets and the gdm drop-in.

Part of #1236 (Dakota parity). Found by scanning ghcr.io/projectbluefin/dakota:testing against utah:testing.

Activity

  1. hivecommons-hive commented on Nov 14, 2026

    @hivecommons-hive
    Contributor

    🌱 Good first issue — bring your own coding agent

    Hi! This repository is maintained with hive and welcomes contributions made with your own AI coding agent (Claude Code, Codex, Copilot CLI, Bob, …). hosted-projectbluefin-knuckle-gjvq picked this issue as a good place to start because:

    • scoped to one package (ghcr.io/projectbluefin)
    • short, focused description

    How to land it (no waiting on a human):

    1. Claim it through the relay: open https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute?issue=projectbluefin%2Futah%231237 and sign in with GitHub. Claiming stamps the issue so hive leaves it to you.
    2. Fork or branch, make the change with your agent, and sign each commit with DCO (git commit -s).
    3. Open a PR whose description says Fixes #1237 — that closing keyword is how hive's contributor lane links the PR to your claim.
    4. Hive runs CI and merges green PRs from claimed contributors automatically.
    Paste this to your agent
    Fix #1237 in github.com/projectbluefin/utah (https://github.com/projectbluefin/utah/issues/1237). First open https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute?issue=projectbluefin%2Futah%231237 and claim the issue through the hive relay (sign in with GitHub). Work on a fork/branch; keep the change scoped to the issue; sign every commit with DCO (git commit -s); open a PR whose description contains the line 'Fixes #1237' so the hive's contributor lane can auto-merge it once CI is green. Read and follow https://github.com/projectbluefin/utah/blob/HEAD/AGENTS.md before changing code.
    

    Prefer not to drive the loop by hand? Run your own hive (we call them clankers) — a relay on your machine that claims, opens the PR and handles review fixes for you, and earns you a contributor profile and a leaderboard place: see https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute.

    If nobody claims it, hive may pick it up itself — claiming first prevents that. Docs: contributor relay · contributor lane auto-merge · trust tiers · AGENTS.md.

  2. added
    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    stage/stalledIn its current stage longer than expected
    on Nov 14, 2026
  3. hanthor commented on Nov 16, 2026

    @hanthor
    MemberAuthor

    Owner decision (2026-11-16, delegated): Adopt kmscon once the factory builds it (new spec).

  4. hanthor commented on Nov 16, 2026

    @hanthor
    MemberAuthor

    Factory side: kmscon is imported from Fedora Rawhide in projectbluefin/utah-packages#1099, armed for auto-merge.

  5. hanthor commented on Nov 16, 2026

    @hanthor
    MemberAuthor

    Update: the factory import PR is now consolidated into projectbluefin/utah-packages#1147 (armed for auto-merge).

  6. 29 remaining items

  7. Danathar commented on Nov 16, 2026

    @Danathar
    Contributor

    /triage accepted

  8. added
    triage/acceptedScope accepted; ready for work. Use `/triage accepted`.
    and removed on Nov 16, 2026
  9. removed
    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 17, 2026
  10. added a commit that references this issue on Nov 20, 2026
    3feebff
  11. added a commit that references this issue on Nov 20, 2026
    0913c62
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureA new capability.triage/acceptedScope accepted; ready for work. Use `/triage accepted`.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions