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
Does not work in Chromium and Google Chrome (flatpak). #1267
Comments
If chromium is installed as a snap it will not work. Browsers installed as snaps cannot use native messaging. |
Offtopic: For users who want to use chromium on (K)Ubuntu anyway: My current workaround is to install chromium via linux mint's apt package. Here's a blog entry that explains how one can achieve this: https://ubuntuhandbook.org/index.php/2020/11/chromium-browser-deb-available-linux-mint-20/ |
Hello Keepassxc team, I would like to draw your attention to the fact that someone in a forum managed to make keepassxc browser work with Firefox flatpak. The idea is to run Do you think this could be a possible solution ? |
Experiencing the same issue as @candrapersada described. Using Ungoogled-Chomium installed via flatpak and KeepassXC-Browser in conjunction with KeePassXC (flatpak). |
and keepassxc does not work in Google Chrome (flatpak) |
The issue still remains, you can't sync flatpak keepassxc and flatpak browsers |
See this for a possible workaround until Flatpak has an official support for Native Messaging: #1631 (comment) |
Confirming the report by @NSurtsev on Fedora 36. I have com.github.Eloston.UngoogledChromium installed from flathub, with org.keepassxc.keepassxc_browser.json being generated at ungoogled-chromium com.github.Eloston.UngoogledChromium 103.0.5060.114-2 I get "Key exchange was not successful.". Thank you for your help. |
@blockfeed make sure you have make |
[@zihaaad Thanks for the suggestion, but it appears something else may be going on with UngoogledChromium, even after following your Brave guide (with adjustments, obviously).
File locations:
And my json:
And the result:
Any suggestions are appreciated! |
@blockfeed strange it works with Google Chrome (flatpak) but not with Chromium or Ungoogled Chromium. |
Looks like |
I followed what is written in those replies: #1631 (comment) #1631 (comment) I was able to make it work with ungoogled-chromium flatpak by putting the script in this location: I use the native version of KeepassXC from my Fedora installation but I installed the Flathub KeepassXC flatpak alongside my native version for the proposed solution to work, even though I am running my native version and the proxy seems to come from the flatpak, everything works and connects fine now. It seems that there's additional sandboxing somewhere that prevents access to the script anywhere else. I have not found any other shared folder, though I didnt try to look any further once that one worked. |
@leo-lb I don't see the |
Expected Behavior
Current Behavior
KeePassXC-Browser in Chromium won't connect to KeePassXC even when database is open and Chromium is checked.
Possible Solution
Steps to Reproduce (for bugs)
1.Install KeePassXC on Linux from flathub.org and use or create a database.
2.Enable Browser Integration for Chromium.
3.Install Chromium on Linux from flathub.org.
4.Install KeePassXC-Browser extension from the Chrome Web Store.
5.Under Connected Databases in the settings of KeePassXC-Browser, click
Connect
.Debug info
KeePassXC - {2.6.4}
KeePassXC-Browser - {1.7.6}
Operating system: Linux
Flatpak - {1.10.2}
Browser: Chromium and ungoogled-chromium
The text was updated successfully, but these errors were encountered: