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
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 co
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 sho
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
On Sun, 2 Feb 2025 at 14:44, Frederik Schwan 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.
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 ho