News draft: glibc 2.41 breaks Discord
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, Frederik
On Sun, 2 Feb 2025 at 14:44, Frederik Schwan <freswa@archlinux.org> wrote:
Glibc and it's friends will move from testing to stable on approx. 2025-02-03.
"We plan to move `glibc` 2.41 from testing to stable tomorrow, Feb 3."
After installing the update, the Discord client will show a read
"red", I assume.
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.
I would also suggest using Flatpak. I think it's the best option.
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
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
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, Frederik
New 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. ------
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, Frederik
New 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
participants (4)
-
Frederik Schwan
-
gromit
-
Jan Alexander Steffens (heftig)
-
Robin Candau