Segmentation fault

[himark1977]

Is there an existing issue for this?

• I have searched the existing issues

Is your issue described in the documentation?

• I have read the documentation

Is your issue present in the latest beta/pre-release?

This issue is present in the latest pre-release

Describe the Bug

Can't open sunshine after installing:
Binaries .deb/.AppImage on Ubuntu 26.04 wayland`

Expected Behavior

To be able to run it.

Additional Context

No response

Host Operating System

Linux

Operating System Version

Ubuntu 26.04

Architecture

amd64/x86_64

Package

Linux - deb

GPU Type

AMD

GPU Model

RX 580

GPU Driver/Mesa Version

Mesa 26.0.3-1ubuntu1

Capture Method

None

Apps

Log output

adrian@evokzh:~$ sunshine
[2026-05-22 14:09:55.023]: Info: Sunshine version: 2026.522.22447 commit: ccd09c1021545be14b4e072374bd5fb9d8c42e74
[2026-05-22 14:09:55.023]: Info: Package Publisher: LizardByte
[2026-05-22 14:09:55.023]: Info: Publisher Website: https://app.lizardbyte.dev
[2026-05-22 14:09:55.023]: Info: Get support: https://app.lizardbyte.dev/support
Cannot load libcuda.so.1
[2026-05-22 14:09:55.024]: Error: Couldn't load cuda: -1
[2026-05-22 14:09:55.024]: Info: [wayland] Found display [wayland-0]
[2026-05-22 14:09:55.024]: Info: [wayland] Found interface: wl_output(3) version 4
[2026-05-22 14:09:55.024]: Info: [wayland] Found interface: zxdg_output_manager_v1(4) version 3
[2026-05-22 14:09:55.024]: Info: [wayland] Found interface: zwp_linux_dmabuf_v1(23) version 5
[2026-05-22 14:09:55.024]: Warning: [wlgrab] Missing Wayland wire for wlr-export-dmabuf
[2026-05-22 14:09:55.025]: Info: /dev/dri/card1 -> amdgpu
[2026-05-22 14:09:55.027]: Info: [wayland] Found display [wayland-0]
[2026-05-22 14:09:55.027]: Info: [wayland] Found display [wayland-0]
[2026-05-22 14:09:55.027]: Info: [wayland] Found interface: wl_output(3) version 4
[2026-05-22 14:09:55.027]: Info: [wayland] Found interface: zxdg_output_manager_v1(4) version 3
[2026-05-22 14:09:55.027]: Info: [wayland] Found interface: zwp_linux_dmabuf_v1(23) version 5
[2026-05-22 14:09:55.027]: Info: [wayland] Resolution: 1920x1080
[2026-05-22 14:09:55.027]: Info: [wayland] Offset: 0x0
[2026-05-22 14:09:55.027]: Info: [wayland] Logical size: 1920x1080
[2026-05-22 14:09:55.027]: Info: [wayland] Name: DP-1
[2026-05-22 14:09:55.027]: Info: [wayland] Found monitor: Samsung Electric Company 27"
[2026-05-22 14:09:55.027]: Info: -------- Start of KMS monitor list --------
[2026-05-22 14:09:55.027]: Info: Monitor 0 is DP-1: Samsung Electric Company 27"
[2026-05-22 14:09:55.027]: Info: --------- End of KMS monitor list ---------
[2026-05-22 14:09:55.027]: Info: [portalgrab] Loaded portal restore token from disk
[2026-05-22 14:09:55.120]: Info: // Testing for available encoders, this may generate errors. You can safely ignore those errors. //
[2026-05-22 14:09:55.120]: Info: Trying encoder [nvenc]
[2026-05-22 14:09:55.120]: Info: Screencasting with KMS
[2026-05-22 14:09:55.121]: Info: /dev/dri/card1 -> amdgpu
[2026-05-22 14:09:55.123]: Error: Couldn't find monitor [0]
[2026-05-22 14:09:55.123]: Info: /dev/dri/card1 -> amdgpu
[2026-05-22 14:09:55.126]: Error: Couldn't find monitor [0]
[2026-05-22 14:09:55.326]: Info: Screencasting with KMS
[2026-05-22 14:09:55.326]: Info: /dev/dri/card1 -> amdgpu
[2026-05-22 14:09:55.328]: Error: Couldn't find monitor [0]
[2026-05-22 14:09:55.329]: Info: /dev/dri/card1 -> amdgpu
[2026-05-22 14:09:55.331]: Error: Couldn't find monitor [0]
[2026-05-22 14:09:55.531]: Info: Encoder [nvenc] failed
[2026-05-22 14:09:55.531]: Info: Trying encoder [vulkan]
[2026-05-22 14:09:55.531]: Info: Screencasting with KMS
[2026-05-22 14:09:55.531]: Info: /dev/dri/card1 -> amdgpu
[2026-05-22 14:09:55.531]: Info: Found monitor for DRM screencasting
[2026-05-22 14:09:55.532]: Info: Found connector ID [80]
[2026-05-22 14:09:55.532]: Info: Found cursor plane [61]
[2026-05-22 14:09:55.532]: Info: Creating encoder [h264_vulkan]
[2026-05-22 14:09:55.532]: Info: Color coding: SDR (Rec. 601)
[2026-05-22 14:09:55.532]: Info: Color depth: 8-bit
[2026-05-22 14:09:55.532]: Info: Color range: JPEG
lsfg-vk: An error occured while trying to parse the configuration, IGNORING:
- Unable to parse configuration file
- Configuration file version is not supported, expected 1
[2026-05-22 14:09:55.571]: Info: Streaming bitrate is 1000000
[2026-05-22 14:09:55.571]: Error: [h264_vulkan @ 0x5a3498cc6b00] Encoding of h264 is not supported by this device
Segmentation fault         (core dumped) sunshine

https://vulkan.gpuinfo.org/displayreport.php?id=48912

Online logs

No response

[RadicalityIncident]

Experiencing the same issue on an AMD BC250 running Bazzite with both the sunshine beta and stable. Setup was previously working prior to updating. Log output is basically identical.

[ReenigneArcher]

As a workaround, force it to use a different encoder

[himark1977]

As a workaround, force it to use a different encoder

Can you help me with a encoder that work?

[codeafridi]

I ran into installation issues on Ubuntu as well with the 24.04 amd64 deb package. apt --fix-broken install ended up removing Sunshine because of unresolved dependencies (boost/libmfx/miniupnpc related). Haven't tested the AppImage yet.

[codeafridi]

I tested it on the latest Ubuntu 26.04 here and Sunshine starts fine for me after installing the 26.04 amd64 package. Looking at your logs, it seems to detect the AMD GPU and enter the Vulkan encoder path, but then h264_vulkan reports that H264 encoding isn’t supported on the device. I also noticed the repeated Couldn't find monitor [0] messages before DRM monitor detection succeeds, so it might be something in the fallback/init path on Wayland after partial Vulkan encoder setup.

[Kishi85]

Try encoder = vaapi as that is what was used by default for AMD before Vulkan encoding was implemented.

[Kishi85]

@himark1977 could you try with https://github.com/LizardByte/Sunshine/actions/runs/26340071941/artifacts/7178920475 (that's for Ubuntu 26.04) to see if #5174 fixes the issue?

[himark1977]

nano ~/.config/sunshine/sunshine.conf
encoder = vaapi

worked!

@Kishi85 I tried https://github.com/LizardByte/Sunshine/actions/runs/26340071941/artifacts/7178920475 but didn't worked out of the box, still tried to run with vulkan encoder, but after using the workaround above it worked !

[Kishi85]

@codeafridi Looks like your PR does not fully fix this for @himark1977 as it is only working when specifying the vaapi encoder specifically here.

From the logs it looks like the segfault causing sunshine to crash is occurring during vulkan encoder init after the h264 failure but before returning from vulkan encoder init? @neatnoise maybe you have an idea whats going wrong here?

[codeafridi]

Yeah i tested more and figured out the first fix was only handling the failure after vulkan init had already started. i will update the pr to check Vulkan H.264 encode support earlier. if the device does not support it, sunshine now skips the vulkan encoder and continues to fallback encoders like vaapi instead of needing encoder = vaapi manually. @Kishi85 @himark1977

[neatnoise]

It's coming from ffmpeg. It's ffmpeg bug which I reported. It seems it hasn't been resolved since then

[codeafridi]

could you link the issue here?

[neatnoise]

could you link the issue here?

https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/22831

[ReenigneArcher]

@neatnoise can we add your suggested patch in build-deps?