From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] `qt5` applications seem to still depend on `libssl1.1`
Date: Mon, 02 Oct 2023 05:54:03 +0200 [thread overview]
Message-ID: <20231002035403.4i_hjbaNf42xvx_Lssg0Jp7Pom6VJI5eTfu03vt_-gw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46123@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Closed issue by garylaski on void-packages repository
https://github.com/void-linux/void-packages/issues/46123
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.13_1 x86_64 AuthenticAMD notuptodate rFF
### Package(s) Affected
qt5
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://bugreports.qt.io/browse/QTBUG-115146
### Expected behaviour
qt5 applications should work properly without the `libssl1.1` package.
### Actual behaviour
When using qt5 applications, they will not work if the `libssl1.1` package is not installed. A variation of the error will be thrown:
```
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id
qt.network.ssl: QSslSocket: cannot resolve SSL_get_peer_certificate
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_get_peer_certificate
```
### Steps to reproduce
1. Install a qt5 application that uses OpenSSL (e.g. `picard`)
2. `openssl-3.x` will be installed (ensure `libssl1.1` is not installed)
3. Try and run application
4. See error
5. Install `libssl1.1`
6. Error goes away
prev parent reply other threads:[~2023-10-02 3:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 23:05 [ISSUE] " garylaski
2023-09-19 2:00 ` chrysos349
2023-09-19 2:01 ` chrysos349
2023-09-19 2:07 ` chrysos349
2023-09-19 7:11 ` sgn
2023-09-19 7:12 ` sgn
2023-09-19 7:12 ` sgn
2023-10-02 3:54 ` sgn [this message]
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=20231002035403.4i_hjbaNf42xvx_Lssg0Jp7Pom6VJI5eTfu03vt_-gw@z \
--to=sgn@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).