FS#76433 - [telegram-desktop] can't connect to video calls

Attached to Project: Community Packages
Opened by John Smith (ramble5417) - Saturday, 05 November 2022, 12:52 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 10 November 2022, 16:59 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Felix Yan (felixonmars)
Jiachen Yang (farseerfc)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description: after the openssl rebuild, i cannot connect to video calls, it just says connecting forever
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Thursday, 10 November 2022, 16:59 GMT
Reason for closing:  Fixed
Comment by Toolybird (Toolybird) - Saturday, 05 November 2022, 21:28 GMT
You failed to mention the version. The pkg was just updated. Does it still happen with 4.3.0-1?
Comment by John Smith (ramble5417) - Saturday, 05 November 2022, 21:35 GMT
yes it does
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 05 November 2022, 21:58 GMT
Can't reproduce, works fine for me with 4.3.0.
Comment by John Smith (ramble5417) - Sunday, 06 November 2022, 07:38 GMT
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
Comment by Nomi (cato343) - Sunday, 06 November 2022, 22:20 GMT
same issue on my end as well
Comment by Caesar Woo (caesarw) - Monday, 07 November 2022, 08:28 GMT
same issue here.
Comment by Caesar Woo (caesarw) - Monday, 07 November 2022, 08:32 GMT
> 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) ].
Comment by Christian Hesse (eworm) - Monday, 07 November 2022, 09:06 GMT
It happens for group calls only for me, calls in private chats are ok.
Comment by Marco (jellybean) - Tuesday, 08 November 2022, 12:43 GMT
Here active contributor to tdesktop mentions there's an incompatibility with openssl 3:
https://github.com/telegramdesktop/tdesktop/issues/24855#issuecomment-1201638336
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 08 November 2022, 13:24 GMT
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.
Comment by Christian Hesse (eworm) - Tuesday, 08 November 2022, 13:40 GMT
We could link against openssl-1.1 for now...
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 08 November 2022, 14:23 GMT
Oh right, we still have that. I guess I'm going to slap a build into testing and see how that goes.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 10 November 2022, 08:45 GMT
I can't manage to make telegram link to openssl 1.1 only, would appreciate some help if someone has some time.
Comment by Antonio Rojas (arojas) - Thursday, 10 November 2022, 09:14 GMT
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.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 10 November 2022, 10:51 GMT
Oh, thanks for the hint. Please test 4.3.1-2.
Comment by Caesar Woo (caesarw) - Thursday, 10 November 2022, 15:51 GMT
it seems that the bug has been resolved by switching openssl version.

Loading...