Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-web help doesn't work #97

Open
wjt opened this issue Sep 5, 2022 · 2 comments
Open

Non-web help doesn't work #97

wjt opened this issue Sep 5, 2022 · 2 comments

Comments

@wjt
Copy link
Member

wjt commented Sep 5, 2022

In the Help Menu, clicking any of the following three items has no effect:

  • Getting Started
  • User Guide
  • Keyboard Shortcuts

Nothing of interest is shown in the terminal.

Debug information

KeePassXC - Version 2.7.1
Revision: 5916a8f
Distribution: Flatpak

Qt 5.15.5
Debugging mode is disabled.

Operating system: KDE Flatpak runtime
CPU architecture: x86_64
Kernel: linux 5.15.0-39-generic

Enabled extensions:

  • Auto-Type
  • Browser Integration
  • SSH Agent
  • KeeShare
  • YubiKey

Cryptographic libraries:

  • Botan 2.19.1
@bbhtt
Copy link
Contributor

bbhtt commented Mar 8, 2024

KeepassXc just uses QDesktopServices::openUrl here

This seems like an issue in Qt 5.15, seems to be resolved in 6.6.

An easy way to repro this issue is:

flatpak run --command=python --socket=x11 --filesystem=$(pwd) com.riverbankcomputing.PyQt.BaseApp//6.6 test.py which shows the this dialogue

image

but flatpak run --command=python --socket=x11 --filesystem=$(pwd) com.riverbankcomputing.PyQt.BaseApp//5.15-23.08 test.py shows nothing even though it returns True

from PyQt6.QtWidgets import QApplication
from PyQt6.QtCore import QUrl
from PyQt6.QtGui import QDesktopServices

app = QApplication([])
QDesktopServices.openUrl(QUrl("file:///app/share/metainfo/com.riverbankcomputing.PyQt.BaseApp.metainfo.xml"))

(Change the imports to Qt5 when needed)

My guess is some flatpak support is missing or broken in Qt 5.15.

@droidmonkey
Copy link
Collaborator

We are moving to Qt 6 for our 2.8.0 release and this should be resolved at that time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants