You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like there is a problem with sunshine failing to autostart on the desktop images of Bazzite. tested on bazzite-gnome-nvidia:testing-41.20250101 and bazzite-gnome:testing-41.20250101
I get the following errors in the log
sunshine[6282]: Error: Client failure: Daemon connection failed
sunshine[6282]: Error reading events from display: Broken pipe
systemd[1624]: sunshine.service: Main process exited, code=exited, status=1/FAILURE
systemd[1624]: sunshine.service: Failed with result 'exit-code'.
If I manually start the service with systemctl --user start sunshine is starts without issue
Also tested on "bazzite-deck-gnome:testing-41.20250101" and the service starts without issue so it seems to be specific to the Gnome desktop images.
As a work around, I've added Sunshine to Tweaks >> Startup Applications
What did you expect to happen?
I would expect the sunshine service to start up on bazzite-gnome-nvidia and bazzite-gnome like it does on bazzite-gnome-deck
Describe the bug
It looks like there is a problem with sunshine failing to autostart on the desktop images of Bazzite. tested on bazzite-gnome-nvidia:testing-41.20250101 and bazzite-gnome:testing-41.20250101
I get the following errors in the log
If I manually start the service with
systemctl --user start sunshine
is starts without issueAlso tested on "bazzite-deck-gnome:testing-41.20250101" and the service starts without issue so it seems to be specific to the Gnome desktop images.
As a work around, I've added Sunshine to Tweaks >> Startup Applications
What did you expect to happen?
I would expect the sunshine service to start up on bazzite-gnome-nvidia and bazzite-gnome like it does on bazzite-gnome-deck
Output of
rpm-ostree status
Hardware
Desktop with Nvidia RTX 1050 TI but I also tested on the ROG Ally RC71L_RC71L and the issue is reproduce-able there.
Extra information or context
No response
The text was updated successfully, but these errors were encountered: