enricobuehler
2f9e61d191
apple / swift (push) Failing after 45s
windows-msix / package (arm64, C:\Users\Public\ffmpeg-arm64, aarch64-pc-windows-msvc, C:\t-a64) (push) Successful in 1m15s
android / android (push) Successful in 4m56s
windows-host / package (push) Failing after 3m31s
windows-msix / package (x64, C:\Users\Public\ffmpeg, x86_64-pc-windows-msvc, C:\t) (push) Has been cancelled
windows / build (aarch64-pc-windows-msvc) (push) Has been cancelled
windows / build (x86_64-pc-windows-msvc) (push) Has been cancelled
rpm / build-publish (43, bazzite, punktfunk-fedora-rpm) (push) Has been cancelled
rpm / build-publish (44, fedora-44, punktfunk-fedora44-rpm) (push) Has been cancelled
arch / build-publish (push) Successful in 5m39s
release / apple (push) Has been cancelled
flatpak / build-publish (push) Has been cancelled
apple / screenshots (push) Has been skipped
docker / build-push (--build-arg FEDORA_VERSION=44, ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora44-rpm) (push) Has been cancelled
docker / build-push (., web/Dockerfile, punktfunk-web) (push) Has been cancelled
docker / build-push (ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora-rpm) (push) Has been cancelled
docker / build-push (ci, ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Has been cancelled
docker / build-push (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Has been cancelled
docker / deploy-docs (push) Has been cancelled
decky / build-publish (push) Has been cancelled
ci / web (push) Successful in 1m3s
ci / docs-site (push) Successful in 1m23s
ci / rust (push) Successful in 4m46s
ci / bench (push) Successful in 4m57s
deb / build-publish (push) Successful in 4m22s
Now that the per-capture worker subprocess makes an NVENC EGL/CUDA driver fault survivable (design/zerocopy-worker-isolation.md), the reason the NVENC zero-copy path stayed opt-in is gone. zerocopy::enabled() now defaults ON for both GPU backends (was ON VAAPI / OFF NVENC). Fallbacks are intact: VAAPI's one-shot CPU auto-downgrade (VAAPI-gated, never trips for NVENC) and NVENC's per-capture fallback + worker-death latch. Reframe the shipped host.env examples and setup guides to rely on the default rather than force PUNKTFUNK_ZEROCOPY=1 (an explicit =1 skips the VAAPI auto-downgrade). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
97 lines
3.5 KiB
Markdown
97 lines
3.5 KiB
Markdown
---
|
|
title: GNOME (Mutter)
|
|
description: Configure a punktfunk host for GNOME — host.env, the EGL/lock traps, and a headless session.
|
|
---
|
|
|
|
Configure a host running **GNOME**. The host drives GNOME's Mutter compositor to create a per-client
|
|
virtual display over D-Bus (`RecordVirtual`), zero-copy. This page assumes the host is already
|
|
installed — see [Ubuntu](/docs/ubuntu), [Fedora](/docs/fedora), or [Arch](/docs/arch).
|
|
|
|
> New here? Read [Security & Safe Use](/docs/security) first — a streaming host is remote control of
|
|
> the machine, so keep it on a trusted LAN or VPN and require pairing.
|
|
|
|
## host.env
|
|
|
|
Write `~/.config/punktfunk/host.env` with the GNOME settings. The host auto-detects the compositor
|
|
from your session, so the explicit `PUNKTFUNK_COMPOSITOR` is belt-and-braces:
|
|
|
|
```ini
|
|
# ~/.config/punktfunk/host.env
|
|
WAYLAND_DISPLAY=wayland-0
|
|
XDG_CURRENT_DESKTOP=GNOME
|
|
PUNKTFUNK_COMPOSITOR=mutter
|
|
PUNKTFUNK_VIDEO_SOURCE=virtual
|
|
# GPU zero-copy (dmabuf → CUDA → NVENC) is ON by default; auto-falls back to CPU. Set =0 to force CPU.
|
|
PUNKTFUNK_INPUT_BACKEND=libei
|
|
```
|
|
|
|
You must be on a **Wayland** session (not X11), and Mutter must be **≥ 48**. See the
|
|
[Configuration reference](/docs/configuration) for every option.
|
|
|
|
## The GL/EGL userspace
|
|
|
|
On NVIDIA, gnome-shell fails to start — or the host logs **"GPU … not supported by EGL"** — when the
|
|
NVIDIA GL/EGL userspace is missing. The base driver package doesn't always pull it in. Install your
|
|
distro's NVIDIA GL/EGL userspace package — on **Ubuntu/Debian** it's `libnvidia-gl-<version>` matching
|
|
your driver; on **Fedora/Arch** it ships with the RPM Fusion / repo driver — then confirm the glvnd
|
|
vendor file exists:
|
|
|
|
```sh
|
|
ls /usr/share/glvnd/egl_vendor.d/10_nvidia.json # must exist
|
|
```
|
|
|
|
Installing the driver itself is covered on your distro's install page
|
|
([Ubuntu](/docs/ubuntu), [Fedora](/docs/fedora), [Arch](/docs/arch)).
|
|
|
|
## Do not lock the session
|
|
|
|
A **locked** GNOME session blocks screen capture — the host fails with
|
|
**"Session creation inhibited"**. On an always-on or headless host there's no one to unlock it, so
|
|
disable the lock:
|
|
|
|
```sh
|
|
gsettings set org.gnome.desktop.screensaver lock-enabled false
|
|
gsettings set org.gnome.desktop.session idle-delay 0
|
|
```
|
|
|
|
## Start the host
|
|
|
|
With `host.env` in place, start the host from **inside your GNOME session**:
|
|
|
|
```sh
|
|
systemctl --user enable --now punktfunk-host
|
|
journalctl --user -u punktfunk-host -f # watch it come up and print its identity fingerprint
|
|
```
|
|
|
|
Then bring up [The Web Console](/docs/web-console) to arm pairing and connect a
|
|
[client](/docs/clients). For an always-on box, see the [headless session](#headless-session) below.
|
|
|
|
## Headless session
|
|
|
|
To run with no monitor and no login, keep a GNOME Wayland session up at all times and start the host
|
|
without a login. Have GDM auto-login your user:
|
|
|
|
```ini
|
|
# /etc/gdm3/custom.conf (Ubuntu) · /etc/gdm/custom.conf (Fedora)
|
|
[daemon]
|
|
AutomaticLoginEnable = true
|
|
AutomaticLogin = your-user
|
|
```
|
|
|
|
Disable the lock (see [above](#do-not-lock-the-session)), then enable the host user service and let it
|
|
linger past logout:
|
|
|
|
```sh
|
|
systemctl --user enable --now punktfunk-host
|
|
sudo loginctl enable-linger "$USER"
|
|
```
|
|
|
|
Reboot and the host comes up on the auto-login session. Full walkthrough:
|
|
[Running as a Service](/docs/running-as-a-service).
|
|
|
|
## Troubleshooting
|
|
|
|
More fixes — black screen, discovery, pairing — in [Troubleshooting](/docs/troubleshooting).
|
|
|
|
Once the host is up, bring the console up and pair — see [The Web Console](/docs/web-console).
|