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
{{ message }}
This repository was archived by the owner on Jun 2, 2026. It is now read-only.
System: Bazzite (immutable Fedora-based), KDE Wayland StreamController version: Latest (running on end-of-life GNOME 48 runtime) Discord: Flatpak version
Issue:
StreamController repeatedly spawns new socat processes without killing existing ones, causing duplicate IPC connections that result in delayed or completely unresponsive Discord actions (deafen, mute, etc).
To reproduce:
Set up StreamController with Discord plugin on Flatpak
Use Discord actions for a while
Run: lsof $XDG_RUNTIME_DIR/discord-ipc-0
Multiple socat processes will be visible, all connected to the same socket
Expected: One socat process managing the IPC bridge Actual: Multiple socat processes accumulate over time causing instability
Workaround: Manually killing duplicate socat processes with pkill -f socat
temporarily restores functionality but duplicates reappear over time.
System: Bazzite (immutable Fedora-based), KDE Wayland
StreamController version: Latest (running on end-of-life GNOME 48 runtime)
Discord: Flatpak version
Issue:
StreamController repeatedly spawns new socat processes without killing existing ones, causing duplicate IPC connections that result in delayed or completely unresponsive Discord actions (deafen, mute, etc).
To reproduce:
Expected: One socat process managing the IPC bridge
Actual: Multiple socat processes accumulate over time causing instability
Workaround: Manually killing duplicate socat processes with pkill -f socat
temporarily restores functionality but duplicates reappear over time.