LizardByte / LizardByte/Sunshine
Indefinite hang with no notification manager
@LizardByte-bot is already working on this.
Since Jul 1, 2025.
- Dominant language
- C++
- Stars
- 41.4k
- Forks
- 2.1k
- Avg merge
- 23h 47m
- Merged PRs (30d)
- 124
Description
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
Summary:
Sunshine hangs indefinitely when starting game streaming or pairing a device. After a lot of trial and error, I tracked down the issue to not having a notification daemon (e.g. dunst or builtin ones in KDE/GNOME) running.
Setup:
- A desktop environment which does not provide a notification manager by default (e.g. sway, hyprland)
- Don't have a notification manager running; normally this would be something like dunst but my setup didn't have any
When the issue happens:
- Start game streaming
- Try pairing a device
Symptom:
Hangs indefinitely and if you try to interact with it, sunshine crashes.
Potential Fix:
if I start a notification manager, things start working straight away. So maybe there should either be an explicit error message provided or the sending of the notification made a optional feature so it not being successful does not hang sunshine totally.
Expected Behavior
No response
Additional Context
No response
Host Operating System
Linux
Operating System Version
Linux arch-g14 6.15.4-arch2-1 #1 SMP PREEMPT_DYNAMIC Fri, 27 Jun 2025 16:35:07 +0000 x86_64 GNU/Linux
Architecture
amd64/x86_64
Sunshine commit or version
v2025.628.4510
Package
Linux - AppImage
GPU Type
AMD
GPU Model
Radeon 6800S
GPU Driver/Mesa Version
25.1.4
Capture Method
None
Config
Apps
Relevant log output
No logs, it will just hang
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.