Skip to content

fix(linux): use FQDN service name in desktop launcher#4874

Open
htrex wants to merge 1 commit intoLizardByte:masterfrom
htrex:fix/desktop-service-name
Open

fix(linux): use FQDN service name in desktop launcher#4874
htrex wants to merge 1 commit intoLizardByte:masterfrom
htrex:fix/desktop-service-name

Conversation

@htrex
Copy link

@htrex htrex commented Mar 19, 2026

Problem

The .desktop launcher runs:

systemctl start --u sunshine

This relies on the sunshine.service alias, which is only created when the user runs systemctl --user enable app-dev.lizardbyte.app.Sunshine. Without a prior enable, the alias doesn't exist and clicking the launcher silently fails — Sunshine doesn't start and there's no error feedback.

This became an issue after daa99db renamed the service to FQDN (app-dev.lizardbyte.app.Sunshine), but the .desktop file was not updated to match.

Fix

Use the full FQDN service name via cmake variable:

systemctl start --u app-@PROJECT_FQDN@

This resolves to app-dev.lizardbyte.app.Sunshine, which is the actual unit name and works regardless of whether the service has been enabled.

The .desktop file runs `systemctl start --u sunshine`, which relies on
the `sunshine.service` alias. This alias only exists after the user runs
`systemctl --user enable`, but the desktop launcher is intended to work
without prior enable.

Since commit daa99db renamed the service to `app-@PROJECT_FQDN@`, the
desktop launcher should use the full service name directly so it works
regardless of whether the service has been enabled.
@sonarqubecloud
Copy link

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.

1 participant