PDF4QT 1.7.1.0 - Download of OCR Languages Fixed
PDF4QT 1.7.1.0 is a bug fix release of 1.7.0.0. In the AppImage and in the Windows packages, the language models of the OCR could not be downloaded (Tools > Manage OCR Languages, or PdfTool ocr-models install), and no other https connection of the application worked either (#436, reported in #85 and #432). The Flatpak package was not affected. The built-in languages (English, Czech, Slovak, German, Spanish, Russian, Chinese) worked offline in all packages.
What was fixed
Linux AppImage: crash at the start of the download
The AppImage links its own OpenSSL into the PDF4QT core library, and the library exported all its symbols. The TLS backend of Qt uses the OpenSSL of the system - its calls were bound to the copy of PDF4QT, so two different versions of OpenSSL worked with the same data. Depending on the version of OpenSSL of the distribution, the application crashed right at the start of the download (for example Ubuntu 24.04) or reported TLS initialization failed (for example Fedora 42).
The libraries of PDF4QT no longer export the symbols of the libraries linked into them, so the TLS connections use only the OpenSSL of the system, and PDF4QT uses its own OpenSSL for the encryption and the digital signatures. The build checks that no such symbol is exported.
Windows: "Network error: TLS initialization failed"
The Windows packages (MSI installer, MSIX and portable zip) did not contain the TLS plugin of Qt, so the application could not open any https connection. The packages now contain the native Schannel backend (it uses the certificate store of Windows), and the build checks it.
Verification
- AppImage: download of the languages on Ubuntu 24.04 and Fedora 42, encryption of documents (RC4, AES-128, AES-256)
- Windows: download of the languages from the portable package without any Qt installation; the MSI and MSIX contain the TLS plugin
- Flatpak: installation with the KDE runtime 6.11 and download of the languages
Notes
- The Windows MSI installer is not code signed in this release (the code signing certificate has expired). The Windows packages and the AppImage have GitHub artifact attestations, they can be verified by
gh attestation verify <file> --repo JakubMelka/PDF4QT. - Building PDF4QT with OpenSSL 4 is tracked in #437.
The complete list of resolved issues is in RELEASES.txt.