You failed to mention the version. The pkg was just updated. Does it still happen with 4.3.0-1?

yes it does

Can't reproduce, works fine for me with 4.3.0.

sorry, what could be the problem on my end?

what's interesting is that telegram-desktop-bin 4.3 from AUR works, while the official package doesn't

same issue on my end as well

same issue here.

> what's interesting is that telegram-desktop-bin 4.3 from AUR works, while the official package doesn't
it works because it is built by Telegram, which had static OpenSSL baked directly into the binary.
checking the library linking of arch repo binary, i found that it is linked to OpenSSL 3.0.7 [ libssl.so.3 => /usr/lib/libssl.so.3 (0x00007fd81fd04000) ].

It happens for group calls only for me, calls in private chats are ok.

Here active contributor to tdesktop mentions there's an incompatibility with openssl 3:
https://github.com/telegramdesktop/tdesktop/issues/24855#issuecomment-1201638336

Ah, I tested it in a direct video call only and that worked. Kind of sucks that upstream is only at best reactive with these sorts of issues. They should try to be more up-to-date proactively. Anyway, I'm not sure what we can do here from a packaging side. Unless someone makes patch I don't think things are going to change here. We're not going to compromise user security over this feature.

We could link against openssl-1.1 for now...

Oh right, we still have that. I guess I'm going to slap a build into testing and see how that goes.

I can't manage to make telegram link to openssl 1.1 only, would appreciate some help if someone has some time.

The openssl 3 linkage comes from the statically linked libtg_owt. In theory, both openssl versions could coexist since the symbols are versioned, you'd only need to switch whichever contains the code relevant for this bug.

Oh, thanks for the hint. Please test 4.3.1-2.

it seems that the bug has been resolved by switching openssl version.