Updating the Host

The web console tells you when a newer host is out, and on most installs updates it for you.

The Updates cardCopy Anchor Link

The top of Host in the web console shows the version you run and whether it is current; Check for update checks right away. Once a newer release exists, the Updates card unfolds below it with the channel you follow, how the host was installed, and either an Update now button or the command that updates this install. The host checks a signed feed on git.unom.io while the console is open. The host also fires update.available and update.applied on the event stream.

The channel comes from the repository you installed from (on a Steam Deck, the branch ~/punktfunk follows), and the card never switches it — see Release Channels.

Update nowCopy Anchor Link

The button asks for the console password and warns you if a stream is live, because updating drops it. The host restarts at the end and the page reconnects by itself. On Linux the button runs your package manager against its own signed repositories; it never picks a version.

On Windows every attempt writes C:\ProgramData\punktfunk\logs\update-<version>.log (open it from an elevated PowerShell). If the new host crash-loops, the service reinstalls the previous version, says so in the card and writes update-rollback-from-<version>.log.

Update by handCopy Anchor Link

On a layered install, rpm-ostree upgrade alone reports no updates while the base image stands still; the script re-resolves just the Punktfunk packages. It takes the newest version from every enabled /etc/yum.repos.d/punktfunk*.repo, so enable only your channel's repo. If the box also runs the sysext, the sysext wins: update that instead.

Restart after a Linux package updateCopy Anchor Link

Every update restarts the running console, host and plugin runner for each signed-in user: pacman, apt, dnf, a NixOS switch, Update now, the Windows installer, punktfunk-sysext update and the Steam Deck script. A service you stopped stays stopped. A live stream drops when the host restarts. A layered rpm-ostree install moves at the reboot instead.

The apt and dnf commands above update only the host; name punktfunk-web and punktfunk-scripting too to move all three. A source build restarts by hand, console first:

systemctl --user restart punktfunk-web
systemctl --user restart punktfunk-host
systemctl --user try-restart punktfunk-scripting

A host left running on a replaced binary fails every new KDE desktop session with KWin does not expose zkde_screencast_unstable_v1 to this client until it restarts.

Bazzite sysext: channels, rollback and rebasesCopy Anchor Link

• punktfunk-sysext status shows the channel, the installed and the newest version.

• Switch channel: sudo punktfunk-sysext install --channel canary (or stable).

• Keep a build to go back to:

  Copy Text

  sudo cp /var/lib/extensions/punktfunk.raw ~/punktfunk-known-good.raw   # before updating
  sudo punktfunk-sysext install --from-file ~/punktfunk-known-good.raw   # to go back

• After a Bazzite major rebase the old image refuses to load. Run sudo punktfunk-sysext update once to fetch the image for the new base.

• refusing to downgrade: the feed's newest image is older than yours. Roll back on purpose with sudo PUNKTFUNK_SYSEXT_ALLOW_DOWNGRADE=1 punktfunk-sysext update, or the file you kept.

• The script checks the feed's signature with gpg. If it reports a bad signature, a foreign feed or an older serial, don't install: download the script again and retry.

Turn the check offCopy Anchor Link

Turn off Check for updates under Host → System (PUNKTFUNK_UPDATE_CHECK=0 in host.env). To keep the check but drop the button, turn off Console updates under Show advanced (PUNKTFUNK_UPDATE_APPLY=0). The check contacts git.unom.io and nothing else.

TroubleshootingCopy Anchor Link

The update feed hasn't changed in over 45 daysCopy Anchor Link

Checks work, but nothing new arrived. Usually there was no release. If the releases page lists a newer stable version than the card, a proxy or DNS between the host and git.unom.io serves old data. The releases page is stable-only, so on a canary host the comparison means nothing.

Anything else: Troubleshooting. Clients update on their own — Install a Client → Keeping a client up to date.