Skip to content

fix: enable PipeWire user units so GNOME screencast can start - #177

Merged
castrojo merged 3 commits into
projectbluefin:testingfrom
KiKaraage:fix/enable-pipewire
Sep 19, 2026
Merged

castrojo merged 3 commits into
projectbluefin:testingfrom
KiKaraage:fix/enable-pipewire

Conversation

@KiKaraage

@KiKaraage KiKaraage commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

Closes #176

Hummingbird's server user preset (dbus only + disable *) leaves PipeWire disabled, so xdg-desktop-portal logs "Failed to connect to PipeWire" and GNOME screencast fails with "Couldn't connect pipewire context".

  • user-preset/85-utah-desktop.preset enables pipewire.socket, pipewire-pulse.socket, wireplumber.service (socket-activated, Fedora default)
  • configure-services.sh enables the same three --global
  • just check gates the preset; desktop-contract skill records the policy

Assisted-by: Muse Spark 1.3 in OpenCode

Assisted-by: Muse Spark 1.3 in OpenCode
Assisted-by: Muse Spark 1.3 in OpenCode

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed — no findings from this perspective.

— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.78

@hanthor hanthor left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving — this is the right fix and it follows the conventions the repo already has. contract and kernel_cache are green; the four image builds are still running, and I will merge once they finish.

Why it is right, checked against the tree rather than the description:

  • scripts/configure-services.sh already guards every global user-unit enable with user_unit_exists, and this uses the same shape, in the same block, for the same reason.
  • Enabling the sockets and leaving the .service units to socket activation matches Fedora's own preset, so this does not invent a new policy for Utah.
  • The comment at scripts/configure-services.sh:88 states the rule this PR is applying: "The preset must agree or first-boot preset-all will undo the build-time enablement." A --global enable with nothing backing it in a user preset is exactly that failure.

Which is why the same file should probably carry two more lines. There is no user-preset/ anywhere on main — this PR creates the first one. So the two user units already enabled --global today, podman-auto-update.timer and ublue-user-setup.service, have precisely the bug you are fixing for PipeWire: nothing in a preset backs them, and if Hummingbird's user preset disables what it does not list, first-boot preset-all --global undoes them the same way it was undoing pipewire.socket. The difference is only that nobody has noticed, because neither has a symptom as visible as screencast failing.

If you are willing, adding

enable podman-auto-update.timer
enable ublue-user-setup.service

to the new preset (and the matching grep -q lines to just check) closes the whole class in one commit rather than leaving two-thirds of it for someone to rediscover. If you would rather keep this PR to the screencast fix, say so and I will open a follow-up issue instead — I will not hold the merge on it either way.

One thing worth a follow-up regardless: just check can only grep the preset text. scripts/verify-desktop-contract.py asserts system units with systemctl is-enabled, which is scope-blind to these, so nothing verifies the user units in the built image. systemctl --global is-enabled would make that a real in-image assertion rather than a file-content one.


Generated by Claude Code

@castrojo
castrojo merged commit 6519c83 into projectbluefin:testing Sep 19, 2026
14 checks passed
@hanthor

hanthor commented Sep 19, 2026

Copy link
Copy Markdown
Member

One thing worth flagging now that this is merged, @KiKaraage — nothing you did wrong, and no action needed from you.

This merged with testing as its base rather than main, and main is the repository's default and protected branch:

default_branch : main
main       a2cfbc261  protected=True
testing    6519c83a6  protected=False

So the fix currently lives only on testing, which is one commit ahead of main — that commit being this one:

commits on testing not on main: 1
  6519c83 fix: enable PipeWire user units so GNOME screencast can start (#177)
commits on main not on testing: 0

The route back to main is the automated promotion PR, #181. That is blocked at the moment, for a reason unrelated to this change: no :testing image tag has ever been created, because the ISO end-to-end matrix fails on the two gaming flavors, so the job that writes the tag never runs. I have written the full chain up on #181, and the fixes are in #162.

Practical upshot: your change is safe (it is in the promotion PR's diff and will land on main when that merges), but it will not appear on main or in a promoted image until #181 clears. If you send further PRs, targeting main avoids the detour.

Thanks for this one — the finding that Hummingbird's server user preset disables everything unlisted is the useful part, and it turned out to apply to two units beyond PipeWire that nothing had noticed.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants