Bots cannot join Voice Channels if Community-Deafened

(#664) Bug Needs triage api voice
Verbatim issue copy of https://feedback.fluxer.com/p/502 follows as I have tested it to still be the case. This issue is opened per @Kamalaja's instruction. ---

Summary

When a community-deafened bot attempts to join a VC, it plays the "VC join" noise as if it joined but no bot will appear in the call. The bot will appear to join the call if you look at the call status in the bottom left of the client but will not appear in the voice channel's display. The bot itself when attempting to establish the connection simply times out upon not being able to establish a WS/S connection to the fluxer.media link (e.g. using a LiveKit "room" through the @livekit/rtc-node NPM module, LiveKit's Room.prototype.connect throws a ConnectError with message wait_pc_connection timed out). Depicted: bot is member with blue icon, I am member with red icon. Black box added on left to cover icons of communities that I am in. image I would expect the bot to just join the call and be deafened. Bots are not disconnected from calls when they are deafened and if they are undeafened while still in call no issue results. The bot cannot be undeafened through the Fluxer client because you can only community-undeafen members that are in a VC and the bot cannot join VC.

Steps to reproduce

  1. Find/create a bot able to join voice calls (e.g. https://invite.vinto.music/ or https://github.com/notgapriel/vinto-the-fluxer-bot/commit/6d6cd5ec1d9c39a6e8d07d98c403207ad74b54fa. Newer versions of Vinto may detect that they are deafened and print an error instead of attempting to join).
  2. Invite it to community you have permission to community-deafen on.
  3. Prompt the bot to join the voice call (e.g. with Vinto and derivatives this is generally done by typing !join in a text channel).
  4. Community-deafen the bot.
  5. Disconnect the bot from the call, either manually or through the bot's commands (e.g. with Vinto and derivatives this is generally done by typing !leave in a text channel).
  6. Re-invite the bot to the voice call per Step 2. This will fail.
--- End verbatim copy.

Environment

  • Client build: stable build 508 (3250c73), 2026-06-06 21:26:08 UTC, Electron 39.2.7, Linux 7.0.0-22-generic (x64), desktop stable 0.0.8
  • Client OS: Kubuntu Resolute
  • Fluxer server version: v2
  • 577075604-20599a0c-e210-4aa3-aa1e-3d7abf7001f8.png

    577075604-20599a0c-e210-4aa3-aa1e-3d7abf7001f8.png

    1009×1118 | 618 kB

Merged posts

These posts were merged into this one. Their comments are now part of the conversation below, marked with where they came from.

Merged from #502 Bots cannot join Voice Channels if Community-Deafened

RexSystemoriginally by @notgapriel on GitHub

Report details

Summary

When a community-deafened bot attempts to join a VC, it plays the "VC join" noise as if it joined but no bot will appear in the call. The bot will appear to join the call if you look at the call status in the bottom left of the client but will not appear in the voice channel's display. The bot itself when attempting to establish the connection simply times out upon not being able to establish a WS/S connection to the fluxer.media link (e.g. using a LiveKit "room" through the @livekit/rtc-node NPM module, LiveKit's Room.prototype.connect throws a ConnectError with message wait_pc_connection timed out). Depicted: bot is member with blue icon, I am member with red icon. Black box added on left to cover icons of communities that I am in. image I would expect the bot to just join the call and be deafened. Bots are not disconnected from calls when they are deafened and if they are undeafened while still in call no issue results. The bot cannot be undeafened through the Fluxer client because you can only community-undeafen members that are in a VC and the bot cannot join VC.

Steps to reproduce

  1. Find/create a bot able to join voice calls (e.g. https://invite.vinto.music/ or https://github.com/notgapriel/vinto-the-fluxer-bot/commit/6d6cd5ec1d9c39a6e8d07d98c403207ad74b54fa. Newer versions of Vinto may detect that they are deafened and print an error instead of attempting to join).
  2. Invite it to community you have permission to community-deafen on.
  3. Prompt the bot to join the voice call (e.g. with Vinto and derivatives this is generally done by typing !join in a text channel).
  4. Community-deafen the bot.
  5. Disconnect the bot from the call, either manually or through the bot's commands (e.g. with Vinto and derivatives this is generally done by typing !leave in a text channel).
  6. Re-invite the bot to the voice call per Step 2. This will fail.

Environment (optional)

  • Client build: stable build 306 (aab9336), 2026-04-12 12:16:13 UTC, Electron 39.2.7, Linux 6.17.0-20-generic (x64), desktop stable 0.0.8
  • Client OS: Kubuntu Questing
  • Fluxer server version/s unknown
  • 577075604-20599a0c-e210-4aa3-aa1e-3d7abf7001f8.png

    577075604-20599a0c-e210-4aa3-aa1e-3d7abf7001f8.png

    1009×1118 | 618 kB

4 comments

Sign in with Fluxer to comment and vote.
Comment by @notgapriel
RexSystem 1 vote edited Merged from #502 originally by @notgapriel on GitHub OP
@Roki100 please link other issue. I didn't find anything on the matter when I looked.
Comment by @Roki100
RexSystem 1 vote edited Merged from #502 originally by @Roki100 on GitHub
@Roki100 please link other issue. I didn't find anything on the matter when I looked.
no idea if there is a github issue but it is known by hampus and perhaps even fixed in v2, i have reported that directly and he has addressed it immediately sadly there are 3'ish ways to report bugs, github, email, dms, whatever and its all in some private bug tracker (if its not github for that matter) so yeah, known, but you seem to be the first to make an issue here if you cannot find anything
Comment by @notgapriel
RexSystem 1 vote edited Merged from #502 originally by @notgapriel on GitHub OP
@Roki100 well, thanks for that. There being multiple avenues for bug reports is somewhat troublesome. If Hampus and co fix this and this issue is still open I'll close it.
Deleted comment
Removed by moderator Rex: Removed a general status note that was posted on many GitHub threads. It no longer applies here.