Files
punktfunk/docs-site/content/docs/hyprland.md
T
enricobuehlerandClaude Opus 5 d383161723
ci / rust (push) Failing after 2m31s
ci / docs-site (push) Successful in 1m22s
ci / web (push) Successful in 1m48s
docker / builders (--build-arg FEDORA_VERSION=44, ci/fedora-rpm.Dockerfile, punktfunk-fedora44-rpm, -f44) (push) Successful in 1m1s
ci / rust-arm64 (push) Successful in 2m2s
docker / builders (ci/android-ci.Dockerfile, punktfunk-android-ci) (push) Successful in 11s
docker / builders (ci/arch-ci.Dockerfile, punktfunk-arch-ci) (push) Successful in 9s
docker / builders (ci/fedora-rpm.Dockerfile, punktfunk-fedora-rpm) (push) Successful in 9s
docker / builders (ci/rust-ci-noble.Dockerfile, punktfunk-rust-ci-noble) (push) Successful in 9s
docker / builders (ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 9s
docker / builders-arm64cross (push) Successful in 20s
docker / apps (., web/Dockerfile, punktfunk-web) (push) Canceled after 36s
docker / apps (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Canceled after 36s
docker / deploy-docs (push) Canceled after 0s
docs: the docs catch up with five releases of shipped work
~1150 feat/fix commits landed since v0.19 and the docs drifted badly. This is a
full sweep of every page against the code as shipped: ~280 verified corrections,
nine new pages, and one deletion.

The worst of what was wrong: the quickstart's five-minute path could not work
(`serve` never started the web console, so step 3 had no PIN to read); every
packaged Linux host runs `serve --gamestream` while security.md told readers to
leave GameStream off; HDR was documented as Windows-only; `PUNKTFUNK_SECURE_DDA`
was documented as a working knob that nothing reads; `PUNKTFUNK_INPUT_BACKEND`
listed a `uinput` value that does not exist and named libei for KDE instead of
kwin; README linked three pages deleted on 2026-07-05; and the rpm-ostree update
command pointed at a script no package installs.

Completeness: about half of what shipped since v0.19 had no page at all. New:
support-matrix (what works where, from 217 verified capability cells), input
(mouse/touch/pen — and the in-stream chords, so the docs finally say how to get
your mouse back), client-settings, profiles-and-links, game-library, clipboard,
wake-on-lan, hdr, uninstall. Updating existed but had zero inbound links.

status.md is gone: its facts moved into the support matrix, its shell stays as a
redirect so the public URL does not 404. roadmap.md is themes now, not a feature
checklist — checkboxes are what rotted.

Debian is no longer claimed. The .deb's Depends resolve against Ubuntu images,
nothing in CI builds or tests Debian, and Debian 12 is below the glibc 2.39
floor. The `debian` in the repo URL is the package format.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-07-31 17:37:06 +02:00

5.7 KiB
Raw Blame History

title, description
title description
Hyprland Configure a Punktfunk host on a Hyprland session — headless output via hyprctl, capture via xdg-desktop-portal-hyprland.

Hyprland is a first-class backend. The host adds a per-client headless output at the client's exact mode with hyprctl, captures it through the xdg-desktop-portal-hyprland (xdph) ScreenCast portal (zero-copy dmabuf), and injects input via the wlroots virtual pointer/keyboard protocols — which Hyprland still implements even after dropping wlroots in v0.42.

This is a distinct backend from Sway / wlroots: Hyprland has its own IPC (hyprctl) and its own portal (xdph), so it is auto-detected and driven separately.

This page assumes the package is already installed — see Arch, Ubuntu, or Fedora.

New here? Read Security & Safe Use first — a streaming host is remote control of the machine, so keep it on a trusted LAN or VPN and require pairing.

host.env

The host auto-detects a Hyprland session, so the starter ~/.config/punktfunk/host.env is one line:

PUNKTFUNK_VIDEO_SOURCE=virtual
# GPU zero-copy capture→encode is ON by default; auto-falls back to CPU. Set PUNKTFUNK_ZEROCOPY=0 to force CPU.

To force the backend (CI/testing — note that pinning turns live-session auto-detection off, so the host stops following session switches):

PUNKTFUNK_COMPOSITOR=hyprland
PUNKTFUNK_INPUT_BACKEND=wlr

See Configuration for the full reference.

How it works

  • Video — the host runs hyprctl output create headless PF-1 and applies a monitor rule for the client's exact mode. Outputs are named, so there's no before/after diffing. The rule uses hyprctl keyword monitor … (the hyprlang config manager — the default on every release, 0.55 included) and falls back to the Lua hyprctl eval 'hl.monitor{…}' only if you've opted into the Lua config manager. The host confirms the output actually adopted the mode before streaming.
  • Capture — it captures that output through the xdg-desktop-portal-hyprland (xdph) ScreenCast portal. To pick the output without a GUI on a headless host, the host writes a managed ~/.config/hypr/xdph.conf pointing xdph's custom_picker_binary at a small shim that selects the new output automatically — no interactive picker dialog to answer.
  • Input — mouse and keyboard are injected via the wlroots virtual pointer and virtual keyboard protocols (Hyprland kept them). Gamepads and audio are compositor-independent.

For how long the virtual output lives, and extend-vs-exclusive topology, see Virtual displays.

Requirements

  • A running Hyprland session (the hyprctl/xdph contracts are verified on 0.55.4; older releases share the same hyprctl surface).

  • xdg-desktop-portal-hyprland (xdph) installed and running — the host captures through its ScreenCast portal, and steers its custom picker. Without it there is no video.

  • ScreenCast routed to xdph — only if another portal backend (gtk, wlr) is installed alongside it. xdg-desktop-portal picks one implementation per interface, and if it hands ScreenCast to the wrong backend the host steers an xdph picker nobody is reading. Pin it for your session by creating ~/.config/xdg-desktop-portal/hyprland-portals.conf (the name is your session's desktop — XDG_CURRENT_DESKTOP, which is Hyprland here — lowercased):

    [preferred]
    default=gtk
    org.freedesktop.impl.portal.ScreenCast=hyprland
    

    Then systemctl --user restart xdg-desktop-portal. On a box with only xdph installed there is nothing to choose between, so you can skip this.

Troubleshooting: black / no video (headless output at 0×0)

A headless output only gets a framebuffer once the compositor can allocate one. On some GPU/driver combinations (notably NVIDIA, and in nested test setups) that GBM/dmabuf allocation fails and the output stays 0×0 — you'll see GBM: Failed to allocate a GBM buffer: bo null in the Hyprland log (cf. Sunshine #4197). The host detects this and fails the session with a clear error rather than streaming a blank surface. If you hit it, capture the Hyprland log (hyprctl instance dir → hyprland.log) and check your GPU's GBM support; running Hyprland as a real session (not nested) is the supported configuration.

Permission system

Hyprland's permission system (ecosystem.enforce_permissions, 0.49+, off by default) can deny direct screencopy and virtual-input clients — and denial is silent: capture goes to black frames and input is dropped, with no error. If you've enabled it, grant the host explicitly in your Hyprland config:

ecosystem {
    enforce_permissions = true
}

permission = /usr/bin/punktfunk-host, screencopy, allow
permission = /usr/bin/punktfunk-host, virtual-pointer, allow
permission = /usr/bin/punktfunk-host, virtual-keyboard, allow

The host logs a warning at startup when it detects enforcement is on. (Adjust the binary path to where your package installed punktfunk-host.)

Start the host

With the backend selected, start the host from inside your Hyprland session:

systemctl --user enable --now punktfunk-host
journalctl --user -u punktfunk-host -f

This unit runs serve --gamestream, so it serves stock Moonlight clients as well as the native ones. For a native-only host, see What the unit starts.

Bring up the console and pair

Enable the web console, read its login password, and arm PIN pairing — see The Web Console. Then connect a client.