On Sun, Feb 02, 2025 at 11:22:20PM +0100, gromit wrote:
On 25/02/02 02:43PM, Frederik Schwan wrote:
# 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.
I think this may lead to partial upgrades since people may come to the conclusion to just not upgrade to the "bad" glibc version. But that will break every updated package that is linked against glibc. But Flatpak, as heftig pointed out, may be a good alternative here. I'm not sure if the fix will come with a package release. The broken code is loaded dynamically into ~/.config by Discord itself. Frederik