Keepassxc: AppImage indefinitely checks for an update due to an SSL error

Created on 8 Jul 2020  路  4Comments  路  Source: keepassxreboot/keepassxc

Overview

When checking for an update on 2.5.4 an SSL error is output to the system log but there is no indication of the error in the UI.

I noticed that this issue seems to be a repeat of #3280 and is also probably related to #4219
I don't know if this has been corrected in 2.6.0 but if not then it could be looked at.
It's fine if bundling OpenSSL isn't an option but I think that some kind of error should be shown and it could refer the user to Github to check for new releases.

Steps to Reproduce

  1. Open KeePassXC
  2. Help -> Check for Updates

Expected Behavior

Expected a notification that an update was avilable
Or for the check to time out at some point

Actual Behavior

This error appears in journalctl:
qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed

The dialog appears as if it is still checking (left it running for over an hour)
keepassxc.png

Context

KeePassXC - Version 2.5.4
Revision: dcca5aa
Distribution: AppImage

Qt 5.12.7
Debugging mode is disabled.

Operating system: Fedora 32 (Workstation Edition)
CPU architecture: x86_64
Kernel: linux 5.7.6-201.fc32.x86_64

Enabled extensions:

  • Auto-Type
  • Browser Integration
  • SSH Agent
  • KeeShare (signed and unsigned sharing)
  • YubiKey
  • Secret Service Integration

Cryptographic libraries:
libgcrypt 1.8.1

Operating System: Linux (Fedora 32)
Desktop Env: Gnome
Windowing System: Wayland

bug AppImage

Most helpful comment

2.6.0 is released, test it and report back

Same behaviour after the initial download yesterday but after restarting the system today it gives a proper error message when checking for updates.

Screenshot-from-2020-07-08-09-36-37.png

The update looks great by the way :+1: Thank you for your work

All 4 comments

2.6.0 is released, test it and report back

I don't think this is fixed. It's a known issue with AppImages and the way they handle OpenSSL. It's near-impossible to do it right, unfortunately.

2.6.0 is released, test it and report back

Same behaviour after the initial download yesterday but after restarting the system today it gives a proper error message when checking for updates.

Screenshot-from-2020-07-08-09-36-37.png

The update looks great by the way :+1: Thank you for your work

Having the same issue with AppImage 2.6.0. Same error with the HIBP report
image

Was this page helpful?
0 / 5 - 0 ratings