On 2/2/25 11:57 PM, Frederik Schwan wrote:
On Sun, Feb 02, 2025 at 02:43:25PM +0100, Frederik Schwan wrote:Hi everyone,as discussed in the Matrix packaging channel, the upcoming glibc move from testing to stable will break audio connectivity for Discord clients. Discord has fixed the issue in their canary build and has communicated an eta for the fix in stable for 2025-02-10. As the glibc update holds off package moves from testing to stable I would like to continue releasing the toolchain and give everyone instructions on how to fix their Discord installation. ------ # Glibc 2.41 corrupting Discord installation Glibc and it's friends will move from testing to stable on approx. 2025-02-03. After installing the update, the Discord client will show a read warning that the installation is corrupt. This issue has been fixed in the Discord canary build. Until the fix hits the stable Discord release, please use the canary build or login via browser if you rely on audio connectivity. There have been no reports that (written) chat connectivity is affected. ------ Best regards, FrederikNew version below. I'll send it out tomorrow around 1400 UTC+1. ------ # Glibc 2.41 corrupting Discord installation We plan to move `glibc` and its friends to stable later today, Feb 3. After installing the update, the Discord client will show a red warning that the installation is corrupt. This issue has been fixed in the Discord canary build. If you rely on audio connectivity, please use the canary build, login via browser or use the flatpak version until the fix hits the stable Discord release. There have been no reports that (written) chat connectivity is affected. ------
UPDATE: The issue has been fixed in Discord `0.0.84-1`. -- Regards, Robin Candau / Antiz
OpenPGP_0xFDC3040B92ACA748.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
