Your message dated Thu, 23 Feb 2023 09:10:20 +0100
with message-id <f1ec04f55eed136ea67891be45664e5a20249212.ca...@ens-rennes.fr>
and subject line Re: More info needed on the RC bug you opened
has caused the Debian Bug report #1030658,
regarding fail to retrieve docset info: TLS initialization failed (caused by
unresolved OpenSSL symbols)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1030658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zeal
Version: 1:0.6.1+git20220714+6fee23-2
Severity: grave
This problem makes it impossible to download docsets and start using Zeal, thus
the severity.
I observe this error since months, so it is not related to a recent change in
some other package. Sorry for not reporting it earlier.
Trying to retrieve docsets fails with:
Download failed!
Error: TLS initialization failed
URL: https://api.zealdocs.org/v1/docsets
[Cancel][Retry]
The console contains the following:
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_init_ssl
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_init_crypto
qt.network.ssl: QSslSocket: cannot resolve ASN1_STRING_get0_data
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_reset
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_up_ref
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_CTX_new
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_param_check
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_CTX_free
qt.network.ssl: QSslSocket: cannot resolve RSA_bits
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_sk_new_null
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_sk_push
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_sk_free
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_sk_num
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_sk_value
qt.network.ssl: QSslSocket: cannot resolve DH_get0_pqg
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_set_options
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_get_security_level
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_set_security_level
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_set_ciphersuites
qt.network.ssl: QSslSocket: cannot resolve SSL_set_psk_use_session_callback
qt.network.ssl: QSslSocket: cannot resolve SSL_SESSION_is_resumable
qt.network.ssl: QSslSocket: cannot resolve SSL_get_client_random
qt.network.ssl: QSslSocket: cannot resolve SSL_SESSION_get_master_key
qt.network.ssl: QSslSocket: cannot resolve SSL_session_reused
qt.network.ssl: QSslSocket: cannot resolve SSL_set_options
qt.network.ssl: QSslSocket: cannot resolve TLS_method
qt.network.ssl: QSslSocket: cannot resolve TLS_client_method
qt.network.ssl: QSslSocket: cannot resolve TLS_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_up_ref
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get0_chain
qt.network.ssl: QSslSocket: cannot resolve X509_getm_notBefore
qt.network.ssl: QSslSocket: cannot resolve X509_getm_notAfter
qt.network.ssl: QSslSocket: cannot resolve X509_get_version
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_set_verify_cb
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_set_ex_data
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_get_ex_data
qt.network.ssl: QSslSocket: cannot resolve OpenSSL_version_num
qt.network.ssl: QSslSocket: cannot resolve OpenSSL_version
qt.network.ssl: Incompatible version of OpenSSL
qt.network.ssl: QSslSocket: cannot call unresolved function d2i_X509
(repeats numerous times)
qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed
Rebuilding the package using current unstable didn't help.
-- Damyan
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages zeal depends on:
ii libarchive13 3.6.2-1
ii libc6 2.36-8
ii libgcc-s1 12.2.0-14
ii libqt5concurrent5 5.15.8+dfsg-2
ii libqt5core5a 5.15.8+dfsg-2
ii libqt5gui5 5.15.8+dfsg-2
ii libqt5network5 5.15.8+dfsg-2
ii libqt5sql5-sqlite 5.15.8+dfsg-2
ii libqt5webchannel5 5.15.8-2
ii libqt5webenginecore5 5.15.12+dfsg-3
ii libqt5webenginewidgets5 5.15.12+dfsg-3
ii libqt5widgets5 5.15.8+dfsg-2
ii libqt5x11extras5 5.15.8-2
ii libsqlite3-0 3.40.1-1
ii libstdc++6 12.2.0-14
ii libx11-6 2:1.8.3-3
ii libxcb-keysyms1 0.4.0-1+b2
ii libxcb1 1.15-1
zeal recommends no packages.
zeal suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Le mercredi 22 février 2023 à 23:03 +0200, Damyan Ivanov a écrit :
>
> Today, however, everything works again. I tried on two systems
> tracking sid, including the one I used to report the issue. Strange.
[...]
> Anyway, the libssl3 package is installed and is a dependency of
> several other packages so it must have been present when I experienced
> the problem. dpkg.log confirms it was present here since at least June
> 2022.
>
> Perhaps the issue was transient and the reason was that more than one
> libssl version was linked in via libraries.
>
>
> Sorry for the noise. I guess this report may be closed.
Hello Damyan,
thanks for your quick feedback. I'm thus closing the bug. We are entering the
freeze period, and I don't want the package to be kicked out of testing for a
bad reason, because it may be difficult to enter back to the release afterward.
Please feel free to comment/reopen if you find a way to reproduce the bug.
A direct CC may not hurt ;)
Cheers,
Mt
signature.asc
Description: This is a digitally signed message part
--- End Message ---
