Closed petricf closed 3 weeks ago
Do you use Qt distributed officially or the one from Debian?
Hello,
Am Dienstag, 22. August 2023, 16:28:44 CEST schrieb Tadej Novak:
Do you use Qt distributed officially or the one from Debian?
Stock Debian 12 + Plasma WM Qt5 from Debian Qt 6 from Qt-Online Installer (qt.io) + QtCreator versions 6.4.3 and 6.5.2
The Online Installer installs to ~/Qt
Program debugged in QtCreator IDE.
kind regards Petric
I guess I'll have to debug. I was not even aware we link directly with SSL.
Does any of the Qt network examples work?
I guess I'll have to debug. I was not even aware we link directly with SSL.
Does any of the Qt network examples work?
The http-example does also not work. The output:
qt.tlsbackend.ossl: Incompatible version of OpenSSL (built with OpenSSL 1.x, runtime version is >= 3.x)
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslSocket
qt.network.ssl: The backend named "cert-only" does not support TLS
qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed
So it seems to be a problem at my side (or qt.io compiled the ssl-plugin for v1 ssl)
Any idea how to install openssl v1 additionally on debian (if that helps) ?
It seems that the new debian does not ship with 1.1 anymore: https://packages.debian.org/search?keywords=libssl1.1
I'm working on Qt 6.5 and 6.6 support (but it will take some more time) that AFAIK uses OpenSSL 3.
Feedback: libssl 1.1 and openssl 1 debs of Bookworm downloaded and installed.
Result: Its working.
The QML-File mapping part:
Plugin {
id: mapPlugin
name: "maplibregl"
PluginParameter { name: "maplibregl.mapping.additional_style_urls"; value: "https://tiles.versatiles.org/styles/colorful.json" }
PluginParameter { name: "maplibregl.api_base_url"; value: "https://tiles.versatiles.org:8080/api" }
}
Map {
id: map
anchors.fill: parent
plugin: mapPlugin
center: QtPositioning.coordinate(48.79, 9.1) // irgendwo in Deutschland
zoomLevel: 14
minimumZoomLevel: 2
maximumZoomLevel: 18
Versatiles (https://versatiles.org/) is a new free open tile server initiative based on OpenStreetMap data. It requires much less space and cpu power on an own tile server installation. On the web page there is a presentation held at the last CCC congress (in german).
Can't wait for the Qt 6.5.x adaption ;-) Is it possible to get a notification when it is released, maybe also for testing.
I can confirm that Versatiles works with maplibre-native-qt. I tested on Android as well, were using https://github.com/KDAB/android_openssl is indeed required so we don't see the same SSL errors as this issue originally mentioned.
I will close this ticket for now. 3.0 will be released by the end of the month.
Describe the bug Use Versatiles with maplibregl
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots Terminal Output (started under QtCreator):
Platform information (please complete the following information):
Additional context qml-code (hopefully relevant part):
It seems there is a ssl version mismatch.
How to overcome this ?