Flatpak KeePassXC problems

[rmwiseman]

I excitedly moved from KeePassX to KeePassXC a couple of days ago when I discovered that it has some features I've been waiting for. It seemed to work really well, and I noticed it was installed seamlessly as a Flatpak. However, today is the first day I've needed to save the database and every time I try it fails. I've filed a bug report (https://github.com/keepassxreboot/keepa ... /issues/10) in what I believe (hope) is the right place, but I wondered if anyone else has seen similar error messages...

Writing the database failed.
Cannot create /run/user/1000/doc/2d696d13/passwords.kdbx for output

It doesn't seem to matter where the database is, it gets moved to /run/user/1000/doc/something when I open it, and then can never be saved (or even "saved as").

Is it just me? Am I doing something wrong in the flatpak run command? Here's how I start KeePassXC:

Code: Select all

flatpak run --branch=stable --arch=x86_64 --command=keepassxc --file-forwarding org.keepassxc.KeePassXC

[BenTrabetere]

Is it just me? Am I doing something wrong in the flatpak run command? Here's how I start KeePassXC:

As I understand it, it is not a KeePassXC bug, but a problem with the flatpak itself. From the looks of it the flatpak was created and maintained by flathub, and they pretty much made a mess of it. (IMO, flathub made a mess of the GIMP flatpak, too.)
See: https://github.com/keepassxreboot/keepassxc/issues/1524

I suggest you install one of the official releases for KeePassXC - add the PPA and install, use the AppImage, or install the Snap. I used the AppImage the first time I used KeePassXC, but later I installed it using the PPA. The AppImage worked fine, but I switched to the PPA because that was the best way to ensure I applied security patches as soon as they became available.
https://keepassxc.org/download/#linux

[rmwiseman]

Thanks. The KeePassXC people have also redirected me to that issue! I've uninstalled and reinstalled as a snap, just because I've used snap before. Seems to save fine, I'm glad to say.

[kc1di]

I use keepassxc in an appimage and it's working fine here.

[Royi]

I think you should have opened an issue in the FlatPak project:

https://github.com/flathub/org.keepassxc.KeePassXC

Try run it with the flag --filesystem=home.
The way it is configured currently it seems it can only interact well with /tmp.

What you're experiencing is the security measure of the FlatPak which isolates the application from the file system.
This is a good feature yet it seems the FlatPak's builders doesn't configure it well enough to let the user have a smooth experience.

We should just keep opening the issues in the FlatPak project to let the developers make things better.