You are not logged in.
Hello.
I noticed since I update my system with glibc 2.41, Discord is partly broken. I cannot use anymore the microphone. When I launch it, I have a red ribbon in the top of the window saying (rough translation) : "It looks like your Discord installation is corrupted. Let's fix it together" (See attached image).
I created a VM with Archlinux + Gnome + Discord. With stable repositories, it work flawlessly. But when I upgrade to testing, Discord is broken. I tried to downgrade glibc and Discord is working. I don't know where to inform Discord of this bug.
I'm not sure it is worth opening a bug for this issue on Arch bug tracker.
Any help you can bring here is welcomed.
Thanks!
Offline
We can't do much on our side since discord is closed source, but dropping them a message and/or report the issue via their social media channels may help.
Offline
We can't do much on our side since discord is closed source, but dropping them a message and/or report the issue via their social media channels may help.
I'll try this. Thanks a lot!
Offline
It would still be worth identifying the glibc commit that caused this. Backwards compatibility an important in glibc development principle.
Offline
As a quick note, I noticed this issue goes away if you use Discord Canary so presumably it's something that just needs to get pushed down to stable.
Offline
Using discord-canary doesn't fix the problem for me, I've had to resort to the flatpak. Anyone else getting the mic issue with the canary build (0.0.541-1) and the new glibc (2.41+r2+g0a7c7a3e283a-1)?
Offline
did you update discord? a new update was released
Offline