Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: The KeePassXC-Browser extension installed in Firefox Flatpak fails to communicate with KeePassXC with enabled browser integration. Version-Release number of selected component (if applicable): $ flatpak run org.mozilla.Firefox --version Mozilla Firefox 72.0.2 $ keepassxc --version KeePassXC 2.5.2 KeePassXC-Browser Version: 1.5.4 How reproducible: Try to use KeePassXC-Browser from Firefox Flatpak. Steps to Reproduce: 1. Install KeePassXC, Firefox Flatpak and the KeePassXC-Browser extension. 2. Try to use the KeePassXC-Browser extension from Firefox Flatpak. Actual results: The KeePassXC-Browser extension can't connect to KeePassXC. It show this error message: “KeePassXC-Browser has encountered an error: Key exchange was not successful.” Expected results: The KeePassXC-Browser extension successfully connects to the KeePassXC-Browser extension in Firefox Flatpak. Additional info:
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
There doesn’t seem to be a clean solution for handling native messaging yet, but when ready it will probably make use of dbus and/or portals. At the current time, though, it might be possible to solve this by creating a Flatpak extension that contains the keepassxc-proxy binary and configuring Firefox accordingly. (Or maybe, being a little more dirty, doing this directly in the main Firefox Flatpak.) Relevant discussions: - https://github.com/flatpak/xdg-desktop-portal/issues/655 - https://bugzilla.mozilla.org/show_bug.cgi?id=1621763 - https://discourse.flathub.org/t/how-to-run-firefox-and-keepassxc-in-a-flatpak-and-get-the-keepassxc-browser-add-on-to-work Current manual workaround: - Allow the Firefox Flatpak filesystem access to the socket at xdg-run/app/org.keepassxc.KeePassXC. - Put the (statically-linked, chmod +x) keepassxc-proxy executable at a location readable by the Firefox Flatpak, e.g., ~/.mozilla/native-messaging-hosts. - Create org.keepassxc.keepassxc_browser.json at ~/.mozilla/native-messaging-hosts and point it to the keepassxc-proxy executable. Example org.keepassxc.keepassxc_browser.json: { "allowed_extensions": [ "keepassxc-browser" ], "description": "KeePassXC integration with native messaging support", "name": "org.keepassxc.keepassxc_browser", "path": "/home/YOUR_USERNAME/.mozilla/native-messaging-hosts/keepassxc-proxy", "type": "stdio" }
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.