Russell Howard: Latest News, Net Worth, Wife, ADHD & Personal Life

There’s a peculiar moment when setting up a headless streaming box at home: you follow a guide, copy a command, and then spend the next hour wrestling with a service file that refuses to play along. If you’re running Fedora headless and trying to get Sunshine, the open-source game-streaming server, to start at boot, that frustration is likely familiar.

The situation is often worsened by a mismatch between the default service file’s assumptions and the actual binaries on your system, particularly when you’ve installed a Flatpak. This guide is built around a precise fix forwarded by the LizardByte community: changing the ExecStart= line in the user service unit to call Flatpak’s run command, and then verifying the service starts correctly on a headless box.

We’ll walk through the diagnosis of a common “Bad message” or “Exec format” error, show you the exact file to inspect, and get Sunshine running with a couple of commands that are straight from the official LizardByte documentation. By the end, you’ll have a streaming server that starts quietly in the background, waiting for you to game from the couch.

Understanding the Flatpak vs. Native Path

LizardByte’s official documentation explains the two common installation routes: the Flatpak from Flathub and the native package for your distribution. The service file that gets installed often points to the native binary location, but if you’ve installed the Flatpak, the system will be looking in the wrong place. The documentation is explicit about the correct exec line, which is a crucial detail for anyone setting up a headless server.

The nuance here is that Sunshine’s service file is designed to be distribution-agnostic, but that means it often comes with a placeholder that expects you to edit it based on your install method. As the docs at LizardByte’s usage page note, the primary way to run Sunshine is through the command line, but for a headless box, you’ll want the service to start automatically. This is where the autostart pattern from LizardByte’s documentation becomes essential.

The documentation for Sunshine version 0.21.0 and 0.22.2 both mention the same setup commands, and the service file location is consistent across these versions. This means the fix we’re about to apply should work for the latest stable releases as well as the slightly older ones.

The implication: this single edit resolves the path mismatch and ensures Sunshine runs correctly under Flatpak on any supported version.

Step-by-Step: Editing the Autostart Service

The official setup docs at LizardByte’s setup page provide the basis for this section. We’ll adapt the generic instructions to specifically solve the Flatpak issue on a headless Fedora system.

• Step 1: Open the service file. Use your preferred text editor to open ~/.config/systemd/user/sunshine.service. If it doesn’t exist, you may need to run Sunshine once or copy the sample from the install directory.
• Step 2: Locate the ExecStart line. Look for a line starting with ExecStart=. In a standard install, this will point to something like /usr/bin/sunshine or a similar path for your distro’s native package.
• Step 3: Replace with the Flatpak command. Following the guidance from LizardByte’s usage documentation, change the line to ExecStart=flatpak run dev.lizardbyte.sunshine. For non-Flatpak installs where you’ve built from source or used the .rpm, the docs say to point to /usr/bin/sunshine.
• Step 4: Reload systemd and start the service. After saving the file, run systemctl --user daemon-reload to apply the changes. Then, start the service with systemctl --user start sunshine.
• Step 5: Enable autostart. To have Sunshine start when you log in, use the command systemctl --user enable sunshine as documented by LizardByte.
• Step 6: Verify the service is running. Check the status with systemctl --user status sunshine. You should see it listed as “active (running)” in the output.

For headless systems, the LizardByte docs recommend an additional step. Since there may be no physical display or login manager, the service might not start until you log in. To bypass this, the docs suggest enabling the “linger” feature for your user, which allows user services to start at boot without an interactive login. This is documented under the LizardByte guide for headless systems.

The pattern: a single line edit is the difference between a failed service and a reliable autostart.

Comparing Installation Methods

Understanding the distinction between the Flatpak and native installations helps clarify why this service file edit is necessary. The official setup guide from LizardByte walks through both paths, and the key difference lies in how each package is structured.

The Flatpak runs in a sandbox with its own set of libraries and binary paths, which is why the exec command references the Flatpak app ID. The native package, on the other hand, places the binary in the system’s standard executable path, allowing the service to run directly. The documentation specifically notes that the Flatpak install command can be run using flatpak install --system ./sunshine_{arch}.flatpak, and the additional post-install step is flatpak run --command=additional-install.sh dev.lizardbyte.sunshine, which configures the necessary permissions and helpers. This is a step that is easy to miss, and skipping it might cause the service to start but fail to initialize properly.

The catch: if you choose convenience, you must be prepared to adjust the service file accordingly.

Headless Specifics

When you’re running a headless system, the standard autostart pattern that works on a desktop with an active session changes. The LizardByte documentation has a dedicated page for this scenario, which we can reference to ensure the service starts without a monitor or desktop environment.

The primary issue is that systemd user services are typically tied to a login session. On a headless server, you might log in via SSH, and the service may not start until you do. The docs at LizardByte’s headless SSH guide explain how to set up a virtual display, but for just getting the service to launch, you’ll often need to enable something called “lingering.” This can be done with the command loginctl enable-linger $USER, which allows your user’s services to start at boot.

What this means: without lingering, the service will only start after you’ve logged in, defeating the purpose of a headless autostart.

Frequently Asked Questions

These questions cover widely searched aspects of Russell Howard’s personal and professional life, though some figures remain unverified.