At random points multiple minutes into VCs, the VC audio specifically will entirely disconnect. All other Discord related audio will remain. Only after leaving and rejoining the VC will audio return. Icons also do not update, as if Discord silently stopped receiving audio.
This tends to happen randomly when not interacting with the client, but most recently happened when a video booted up
What is the expected behaviour?
I expect Discord to stay connected to the VC.
How do you recreate this bug or crash?
Stay in VC and wait.
Debug Logs
[3:1003/180424.479372:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Only potentially related line; copypaste from foot isn't working for me at present so I don't have more. Seems to be triggering at random, but was sent five times at once when the incident most recently happened. May instead be related to the embed I opened instead of the issue at hand, though likely not the case.
Request Agreement
[X] I have searched the existing issues and found no similar issue
[X] I am using the latest Vesktop and Vencord versions
[X] This issue occurs on an official release (not just the AUR or Nix packages)
Discord Account
wisheth
Operating System
EndeavourOS Linux
Linux Only ~ Desktop Environment
Hyprland (Wayland)
Package Type
Flatpak
What happens when the bug or crash occurs?
At random points multiple minutes into VCs, the VC audio specifically will entirely disconnect. All other Discord related audio will remain. Only after leaving and rejoining the VC will audio return. Icons also do not update, as if Discord silently stopped receiving audio.
This tends to happen randomly when not interacting with the client, but most recently happened when a video booted up
What is the expected behaviour?
I expect Discord to stay connected to the VC.
How do you recreate this bug or crash?
Stay in VC and wait.
Debug Logs
Only potentially related line; copypaste from foot isn't working for me at present so I don't have more. Seems to be triggering at random, but was sent five times at once when the incident most recently happened. May instead be related to the embed I opened instead of the issue at hand, though likely not the case.
Request Agreement