Edit history

Summary

A user on our server turned off their PC while they were connected to a voice channel using the native Linux desktop app (We no longer have access to their system settings). Since then, a ghost of their user has remained permanently connected. Deleting the voice channel does not resolve the issue and the 'ghost' remains connected. Kicking the user does not solve the issue, and inviting them back causes their app to show the community as duplicated.

Steps to reproduce

This might not be reproducible at the moment, but this is how we suspect it happened: 1 - The user connects to a voice channel. 2 - The user turns off their PC while still connected. Expected result: The user disconnects. Actual result: The user's session gets stuck inside the voice channel.

Environment (optional)

stable build 84 (356bd53), 2026-03-06 03:57:38 UTC, Chrome 144.0.0.0, Windows NT 10.0 (x64)

Logs or screenshots (optional)

image image

Summary

A user on our server turned off their PC while they were connected to a voice channel using the native Linux desktop app (We no longer have access to their system settings). Since then, a ghost of their user has remained permanently connected. Deleting the voice channel does not resolve the issue and the 'ghost' remains connected. Kicking the user does not solve the issue, and inviting them back causes their app to show the community as duplicated.

Steps to reproduce

This might not be reproducible at the moment, but this is how we suspect it happened: 1 - The user connects to a voice channel. 2 - The user turns off their PC while still connected. Expected result: The user disconnects. Actual result: The user's session gets stuck inside the voice channel.

Environment (optional)

stable build 84 (356bd53), 2026-03-06 03:57:38 UTC, Chrome 144.0.0.0, Windows NT 10.0 (x64)

Logs or screenshots (optional)

image image

Checks

• ☑ I searched for existing issues and didn't find a duplicate.