KeepassXC browser integration issue [unsolved]
PERSONAL TESTING, THIS FIX WORKS (for instructions follow below the steps)
https://github.com/keepassxreboot/keepassxc-browser/issues/1631#issuecomment-1153736766
There may be a simpler solution coming in the future. For now, attempt this if you have not tried any other solutions! (It might not work if you have tried another method)
GitHub
Cannot save new credentials using browser · Issue #1631 · keepass...
When I login to a new site where I have not added my credentials, the credentials are not saved to keepassxc. Expected Behavior When a new credentials is entered, upon successful login, the credent...
9 Replies
this is a sort of continuation from #🎮bazzite
https://discordapp.com/channels/1072614816579063828/1087140957096517672/1389518455157424148
Installation: Firefox and KeepassXC are installed as a FLATPAK on the SYSTEM
Possible solution steps using the github:
1. Granted the browser access to KeePassXC flatpak app and KDE runtime installations, and to the KeePassXC proxy socket (RUN IN TERMINAL):
2. Make sure to go to ~/.var/app/org.mozilla.firefox/data and create a bin folder (it may not exist)
Created a wrapper script that will launch the official keepassxc-proxy from KeePassXC flatpak, at a path accessible by the Firefox flatpak, e.g.
3. Into the sh file paste the following:
4. Go to the folder ~/.var/app/org.mozilla.firefox/.mozilla/ and create a folder named "native-messaging-hosts". Afterwards, in that folder create "org.keepassxc.keepassxc_browser.json". Open it in an editor and paste in:
make sure to replace USERNAME with your own
5. Making the script executable (REQUIRED)
4.1 if that doesn't work then attempt to use this (also replace USERNAME):
ah, so it was a mistake. Because that is what I put into my json file lol.I also tested it with the fixed version and didn't work btw
lol i was about to say at least we solved the mystery but ig not
I would try and reinstall bazzite but if it's going to be fixed later on I won't bother.
yeah dont reinstall yet
i used an ai to write a script for the whole workaround though it looks very over engineered. havent tested it either (i have a working system and dont want it to break somehow lol)
@cube yoo guess what! It worked on a reinstalled version of bazzite :beagle_happy:
oh and sorry for ping. I had to reinstall the os because I just messed the os too much 💀
hey no worries about the ping, im glad it worked at the end
oops sorry i really forgot to turn off the ping myself lol
Okay
@bonk what is the exact method without requiring to build a proxy?
I'm testing now
Well the fix or method is just following the steps above. The github is just put there as a source on where it's from. This was the method that worked for me without issues unlike the other method which required more tinkering with stuff, from which this method FAILED to work afterwards.
I am not a linux expert so, I am just posting what I can so others can find the solution easier