[Sunshine] crashes upon startup on current releases #1710
Comments
|
I have been doing some experimentation and running I suspect that the me@bazzite:~$ systemctl status sunshine-workaround.service
× sunshine-workaround.service - Workaround sunshine not having the correct caps
Loaded: loaded (/usr/lib/systemd/system/sunshine-workaround.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
/etc/systemd/system/sunshine-workaround.service.d
└─override.conf
Active: failed (Result: exit-code) since Fri 2024-09-27 23:35:28 IST; 10h ago
Main PID: 4701 (code=exited, status=1/FAILURE)
CPU: 27ms
Sep 27 23:35:28 bazzite systemd[1]: Starting sunshine-workaround.service - Workaround sunshine not having the co>
Sep 27 23:35:28 bazzite setcap[4701]: Invalid file '/usr/bin/sunshine' for capability operation
Sep 27 23:35:28 bazzite systemd[1]: sunshine-workaround.service: Main process exited, code=exited, status=1/FAIL>
Sep 27 23:35:28 bazzite systemd[1]: sunshine-workaround.service: Failed with result 'exit-code'.
Sep 27 23:35:28 bazzite systemd[1]: Failed to start sunshine-workaround.service - Workaround sunshine not having>
|
|
Further experimentation with # get a temporary overlay
sudo rpm-ostree usroverlay
# try to get the workaround unit to work
cd /usr/bin/
sudo mv sunshine-2024.911.215654.copr sunshine
systemctl start sunshine-workaround.service
systemctl status sunshine-workaround.service
● sunshine-workaround.service - Workaround sunshine not having the correct caps
Loaded: loaded (/usr/lib/systemd/system/sunshine-workaround.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
/etc/systemd/system/sunshine-workaround.service.d
└─override.conf
Active: active (exited) since Sat 2024-09-28 10:18:17 IST; 2min 50s ago
Process: 35569 ExecStartPre=/usr/bin/bash -c [ -x /usr/local/bin/.sunshine ] || /usr/bin/cp /usr/bin/sunshin>
Process: 35571 ExecStartPre=/usr/bin/bash -c /usr/bin/mount --bind /usr/local/bin/.sunshine /usr/bin/sunshin>
Process: 35572 ExecStartPre=/usr/bin/bash -c [ -x /usr/local/bin/.sunshine ] || /usr/bin/cp /usr/bin/sunshin>
Process: 35575 ExecStartPre=/usr/bin/bash -c /usr/bin/mount --bind /usr/local/bin/.sunshine /usr/bin/sunshin>
Process: 35576 ExecStart=/usr/bin/bash -c /usr/sbin/setcap 'cap_sys_admin+p' $(/usr/bin/readlink -f $(/usr/b>
Process: 35581 ExecStart=/usr/sbin/setcap cap_sys_admin+p /usr/bin/sunshine (code=exited, status=0/SUCCESS)
Main PID: 35581 (code=exited, status=0/SUCCESS)
CPU: 26ms
# Now try to restart the user service
systemctl --user restart sunshine.service
systemctl --user status sunshine.service
× sunshine.service - Self-hosted game stream host for Moonlight
Loaded: loaded (/usr/lib/systemd/user/sunshine.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/user/service.d
└─10-timeout-abort.conf
Active: failed (Result: core-dump) since Sat 2024-09-28 10:19:55 IST; 2min 24s ago
Duration: 1.179s
Process: 36459 ExecStartPre=/bin/sleep 5 (code=exited, status=0/SUCCESS)
Process: 36464 ExecStart=/usr/bin/sunshine (code=dumped, signal=ABRT)
Main PID: 36464 (code=dumped, signal=ABRT)
CPU: 405ms
Sep 28 10:19:50 bazzite systemd[5590]: sunshine.service: Failed with result 'core-dump'.So the COPR binary still fails even with the capabilities correct. Still, we have two issues here:
So maybe |
|
Tagging @matte-schwartz for visibility. |
On this particular point, sunshine releases provide rpm files for both current and last Fedora versions. I haven't tried, but perhaps that can be used to fully automate Copr releases. I've done this with act and kotlin with to great success, both “built” automatically via GitHub Actions, here and here respectively. |
|
I am working with the Sunshine maintainers for them to have their own official COPR builds and will recommend switching to those when available. quite frankly, i do not have the time or the willingness to maintain this package to that degree. |
|
There's a COPR beta that works on Fedora Workstation: https://copr.fedorainfracloud.org/coprs/lizardbyte/beta/. It'll switch over to stable with the next major release. There is a homebrew tap for it as well: https://github.com/LizardByte/homebrew-homebrew though that is meant for macOS and doesn't build on fedora workstation. Has there been any update on getting sunshine to work on bazzite? |
|
Great to see a copr by LizardByte! We should definitely switch to this. 🙌
FWIW sunshine works great on bazzite for me, except for minor struggles with version mismatches which may very well be my own error/misunderstanding, though they're pretty bizarre. |
Describe the bug
sunshineis still completely unreliable for me. Installing it viaujust setup-sunshineworks, but the daemon crashes upon startup on current releases. See #1359, #1260 (where I bisected the issue to an upgrade inboost) and other similar issues.What did you expect to happen?
I expected it to work. Also, for the
sunshineCOPR to be updated more frequently (and tested). Failing that, to have a flatpak alternative with the right duct taping for it to work (starting with launching correctly with Big Picture mode)Output of
rpm-ostree statusState: idle Deployments: ● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:stable Digest: sha256:bfd698a496a41a55255d03270e7c3cdbe996c62c62fb7dde81dde9ef4b214eb9 Version: 40.20240922.0 (2024-09-23T05:03:03Z) LayeredPackages: sunshine xorgxrdp-glamor xrdp ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:stable Digest: sha256:bfd698a496a41a55255d03270e7c3cdbe996c62c62fb7dde81dde9ef4b214eb9 Version: 40.20240922.0 (2024-09-23T05:03:03Z) LayeredPackages: xorgxrdp-glamor xrdpHardware
me@bazzite %%%%%%====%%%%%%%%%% %%%%%%%% %%%%%%%%%%%%%% bazzite-deck-gnome:stable %%%%%%%%% %%%%%%%%%%%%%%%% Bazzite 40 (FROM Fedora Silverblue) %%%%%%%%% %%%%%%%%%%%%%%%### Linux 6.9.12-205.fsync.fc40.x86_64 %%%%%%%%% %%%%%%%%%%%%%###### 10 hours, 2 mins == =======###### Spawned on Feb 27 2024 == =========##### %%%%%%%%% %%%%%%%####======##### HCAR6000-MI2 %%%%%%%%% %%%%%#######=====##### AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16) @ 5.14 GHz %%%%%%%%% %%%#########=====##### AMD Radeon 780M [Integrated] %%%%%%%%% %%##########=====##### 5.81 GiB / 30.60 GiB (19%) %%%%%%%%%====###########=====###### 454.03 GiB / 475.35 GiB (96%) - btrfs [Read-only] %%%%%%%%====#########======###### 1920x1080 @ 60 Hz in 22″ [External] %%%%%%%=====#####========###### %%%%###===============####### bash 5.2.26 %#######==========######### /dev/pts/0 ####################### 2462 (rpm), 28 (flatpak-system), 18 (flatpak-user) ################### ########### ● ● ● ● ● ● ● ●Extra information or context
Note that the crash dump points to there being indeed a
boostissue as bisected in #1260.The text was updated successfully, but these errors were encountered: