Summary: | media-video/vlc-3.0.18:0/5-9: TLS handshake error, Chromecast Controller failed to create client session | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | armouredheart |
Component: | Current packages | Assignee: | Gentoo Media-video project <media-video> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | jstein, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Output of 'emerge --info' |
Description
armouredheart
2022-12-15 01:23:25 UTC
Created attachment 842721 [details]
Output of 'emerge --info'
OpenSSL 3 would be a possible reason but you're on stable, so I guess it's not that.
>[00007f86e0e9f600] main tls client error: TLS session handshake error
>[00007f86e0e9f600] main tls client error: connection error: No route to host
This makes it sound like it's networking though.
What does qlop say changed in the last day on your system?
(In reply to Sam James from comment #2) The output of qlop is as follows: 2022-12-15T00:00:37 >>> media-video/vlc: 15′42″ 2022-12-15T00:38:03 *** gentoo: 12′46″ What does emerge -pvO dev-libs/openssl say? (In reply to Sam James from comment #4) > What does emerge -pvO dev-libs/openssl say? Output: These are the packages that would be merged, in order: [ebuild R ] dev-libs/openssl-1.1.1s:0/1.1::gentoo USE="asm -rfc3779 -sctp -sslv3 -static-libs -test -tls-compression -tls-heartbeat -vanilla -verify-sig -weak-ssl-ciphers" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="(sse2)" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB I seem to have discovered a workaround. I restarted wpa_supplicant and connected to my wifi network using ipv4 instead of ipv6, and now the problem seems to be gone. The only error thrown is; 'gnutls tls client error: Certificate verification failure: The certificate is NOT trusted. The certificate issuer is unknown. The name in the certificate does not match the expected.' When I disconnect and go back to ipv6, the problem returns. I hope this helps. |