Bug 2175674 - Flatpak of KeepassXC does not start on Fedora Silverblue.
Summary: Flatpak of KeepassXC does not start on Fedora Silverblue.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: keepassxc
Version: 37
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Yaakov Selkowitz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-06 10:02 UTC by malte.roc
Modified: 2023-05-03 08:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-03 08:15:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description malte.roc 2023-03-06 10:02:30 UTC
Description of problem:


Note: This bug report concerns the flatpak of KeepassXC.

Trying to start keepassXC on Fedora Silverblue results in this error:

$ flatpak run org.keepassxc.KeePassXC 
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

The application does not start.


Workaround:
$ flatpak run --env=QT_QPA_PLATFORM=wayland org.keepassxc.KeePassXC 
QSocketNotifier: Can only be used with threads started with QThread
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

Application starts and seems to work flawlessly.



Version-Release number of selected component (if applicable): 2.7.4


How reproducible:
I tried this on a relatively fresh install of Fedora Silverblue. There are not a lot of changes I have done to the system, so I expect this bug to be reproducible on a completely fresh installation of Silverblue.


Steps to Reproduce:
1. On Silverblue: $flatpak install keepassxc (select fedora repository)
2. flatpak run org.keepassxc.KeePassXC 

Actual results:
Application does not start.

Expected results:
Application should start and it should not be necessary to specify additional environment variables.


kind regards
Malte

Comment 1 Mikel Olasagasti Uranga 2023-03-06 18:12:10 UTC
Assigning to Yaakov as he is the creator of the Fedora flatpak package as per https://src.fedoraproject.org/flatpaks/keepassxc

Comment 2 Yaakov Selkowitz 2023-03-07 02:49:19 UTC
This sounds related to the tray icon.  Please try the following independently of each other:

1) Disable the socket=fallback-x11 permission.

2) Add a talk-name=org.kde.StatusNotifierWatcher permission.

3) Install gnome-shell-extension-appindicator and enable the appindicatorsupport.com extension.

Comment 3 malte.roc 2023-03-07 14:35:00 UTC
Thanks for the reply

Those are the results:

1) Disable the socket=fallback-x11 permission.
App works

2) Add a talk-name=org.kde.StatusNotifierWatcher permission.
App does not work; same error as before

3) Install gnome-shell-extension-appindicator and enable the appindicatorsupport.com extension.
App does not work; same error as before

Comment 4 malte.roc 2023-03-16 13:55:11 UTC
Are there any plans to fix this bug?

Comment 5 Ankur Sinha (FranciscoD) 2023-04-27 09:54:48 UTC
Is there a reason this bug is marked "confidential" folks. I see others who seem to be running into it too, and it'll be good for them to be able to access this report:

https://discussion.fedoraproject.org/t/keepassxc-fedora-flatpak-does-not-work-on-f38/81645

Also bumping severity etc.

Comment 6 Yaakov Selkowitz 2023-04-27 17:34:23 UTC
@malte.roc any objections to dropping the confidentiality here?

https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2023-1357635b24 should include a fix.

Comment 7 malte.roc 2023-04-27 20:05:32 UTC
Not at all.

Comment 8 malte.roc 2023-05-03 08:15:19 UTC
Thanks for the fix. I guess we can close this now.


Note You need to log in before you can comment on or make changes to this bug.