From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] not working voice chats in tdesktop
Date: Sat, 06 Mar 2021 14:08:06 +0100 [thread overview]
Message-ID: <20210306130806.JbcWwR-1yq051rVVIQIs_5DwNNp_7anXBEfKjGUDYN0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28001@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
Closed issue by L3Nya on void-packages repository
https://github.com/void-linux/void-packages/issues/28001
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
`Void 5.5.18_1 x86_64-musl AuthenticAMD notuptodate rFFFF`
* package:
*affected package(s) including the version*: `tg_owt-0.0.0.1_1` (and subsequently `telegram-desktop-2.5.1_1`)
### Expected behavior
when you join voice chat in telegram desktop it connects and just works
### Actual behavior
when you join voice chat in telegram desktop it connects endlessly
### cause
![image](https://user-images.githubusercontent.com/47749563/104879367-a1686e00-5955-11eb-8ba3-b69ec5c77545.png)
it's last line of log, then it repeats, so it's problem with openssl likely due to libressl patch
in patch there are just removed dtls1.2 support, if it's libressl. and there are some incompatibility between DTLS and TLS.
next prev parent reply other threads:[~2021-03-06 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 6:17 [ISSUE] " L3Nya
2021-01-19 21:21 ` ericonr
2021-01-19 22:40 ` Johnnynator
2021-01-20 13:50 ` L3Nya
2021-01-20 13:51 ` L3Nya
2021-01-20 16:14 ` Johnnynator
2021-01-21 17:20 ` L3Nya
2021-01-22 1:52 ` L3Nya
2021-03-06 13:08 ` Johnnynator
2021-03-06 13:08 ` Johnnynator [this message]
2021-03-06 13:08 ` Johnnynator
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210306130806.JbcWwR-1yq051rVVIQIs_5DwNNp_7anXBEfKjGUDYN0@z \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).