Move from Brave Flatpak to brave.deb // KeepassXC addon doesn't recognize KeepassXC

tinfoil-hat

tinfoil-hat

Active Member
Joined
Oct 24, 2021
Messages
347
Reaction score
173
Credits
2,407
Hi there,

I have installed Bravebrowser via Flatpak and I wasn't able to get KeepassXC Browseraddon to recognize my KeepassXC Application. Because of that I want to move my userdata in the folder that the .deb would recognize, without loosing any data.

- Any help appreciated
 


Why move from the native package to the Flatpak version if it was working before? You can try installing Flatseal(graphical permission manager for Flatpaks) and give both KeepassXC and Brave access to your home directory.
 
Last edited:
f33dm3bits said:
Why move from the native package to the Flatpak version if it was working before? You can try install Flatseal(graphical permission manager for Flatpaks) and give both KeepassXC and Brave access to your home directory.
Click to expand...
I have given Brave access to my /home via flatseal. But somehow my brave keepassxc addon doesnt connect to my database
 
tinfoil-hat said:
But somehow my brave keepassxc addon doesnt connect to my database
Click to expand...
It's a browser addon not the actual application, I missed that? So you are using this i.c.w. with Brave as a flatpak?
 
Last edited:
f33dm3bits said:
I came across this, try applying it to Brave instead of Firefox and also a Github topic.
github.com

Firefox Snap / KeepassXC flatpak: KeePassXC-Browser - Failed to connect: Unknown error · Issue #1875 · keepassxreboot/keepassxc-browser

Expected Behavior Connect my Firefox KeePassXC-Brower WebExtension to my KeepassXC flatpak Current Behavior It does not. Possible Solution I don't know if firefox snap on ubuntu 22.04 is currently ...
github.com github.com
Click to expand...
I don't understand this Solution :(
 
tinfoil-hat said:
I don't understand this Solution :(
Click to expand...
From my understanding if you have Brave installed as a flatpak you also need to install KeepassXC as a flatpak, then run something like the following.
sudo flatpak override --filesystem=xdg-run/app/org.keepassxc.KeePassXC org.keepassxc.KeePassXC.BrowserServer com.brave.Browser
Click to expand...
And it has a few steps where it shows you how to verify it, if you can run Proxmox server you can surely figure this out.
 
f33dm3bits said:
From my understanding if you have Brave installed as a flatpak you also need to install KeepassXC as a flatpak, then run something like the following.

And it has a few steps where it shows you how to verify it, if you can run Proxmox server you can surely figure this out.
Click to expand...
Sorry, I tried to reproduce this solution and basicially could verify, that I did as indended. But I cannot connect to KeepassXC Browser addon, I tried "Connect / Verbinden" and Refresh the DB. My Keepass has browser support enabled and I tried a reboot
 

Attachments

  • Bildschirmfoto vom 2023-11-30 21-34-18.png
    Bildschirmfoto vom 2023-11-30 21-34-18.png
    30.6 KB · Views: 85
  • Bildschirmfoto vom 2023-11-30 21-37-37.png
    Bildschirmfoto vom 2023-11-30 21-37-37.png
    37 KB · Views: 80
What distribution are you using?
 
f33dm3bits said:
What distribution are you using?
Click to expand...
LMDE6. I tought maybe it's worth a try to move Braves files to the location, an .deb installation would search for info, deinstall the flatpak and install the .deb instead
 
Looks is an issue that everyone is having and that it's a Chromium problem and both are still open.
github.com

KeepassXC-Browser will not connect to Brave-Browser. · Issue #1783 · keepassxreboot/keepassxc-browser

Done this multiple times. Followed it, did not work. Brave is basically Chromium, but it's still not chromium, It shouldn't be treated as if it's the same browser, regardless of it using the Chrome...
github.com github.com
github.com

Does not work in Chromium and Google Chrome (flatpak). · Issue #1267 · keepassxreboot/keepassxc-browser

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.Ins...
github.com github.com
 
Isn't there a possibility to copy userdata from flatpak path to .deb path?
 
You can try that not sure if that will solve your issue, user-data for flatpaks are usually located under $HOME/.var/app and then in the application folder somewhere, you would then have to copy the correct files to correct location for the deb file which will probably be under $HOME/.config somewhere.
 
Dont take this as biblical, but can you simply copy the .config file/s from whatever you have installed right now (flatpak) and paste it to the new install ? ....It is hugely possible that I am talking out of my hat here, as I have never needed to do anything similar

Edit to add:...It just occurred to me that I keep an exported file of my passwords manager in safe storage.....and I am able to Import it into a fresh extension/add on if that is necessary
 
Last edited:
You must log in or register to reply here.

Members online

Total: 642 (members: 5, guests: 637)

Latest posts

Top