On 25/02/02 02:43PM, Frederik Schwan wrote:
Hi everyone,
Hello 👋
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.
I'm still not a big fan of us knowingly breaking such a commonly used software, but yeah being stuck for yet another week with the glibc upgrade and kernel in testing because of a proprietary app also sounds bad so let's do it as you proposed.
# 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.
I think we could also more clearly adivise people to just not upgrade their system until we have also shipped the fixed discord version, as this is the most simple solution to the problem.
Best regards, Frederik
Cheers, gromit