org.keepassxc.KeePassXC VS Flatseal

KeePassXC

Tray icon support is more complicated. flatpak override --user --talk-name=org.kde.StatusNotifierWatcher com.ylsoftware.qmmp.Qmmp might work, or it might not: https://github.com/flathub/org.keepassxc.KeePassXC/commit/362a037832c2e653eb2bf98d75eaf352c17ca3c3

For QT based apps I use Flatpak & Flathub, which should take care of dependencies. Flathub appears to have wallet and pass.

Well KeypassXC would probably be a better choice for an offline password manager. It's just a larger project with more active development and maintenance. It's not clear to me from the Passy page even who the developer is there.

I usually choose to install via flatpak.

At times this tool is utilized to grant a flatpak more permissions; to enable a specific use case. For example to enable 'communication' between KeepassXC and Brave/Librewolf for proper browser integration.

And Flatpak. You'll an easy possibility for integration with other tools, such as Browser integration of KeePassXC (details here).

And not only that, the idea of portals is, IMO, misguided. See this view/bugreport when a flatseal user understands that even though they restricted permissions to access a certain area, the flatpak, itself, can ask to open files there and if OK'd that will be allowed. Their expectation is that with the overrides say "no access" it means "no access even if the flatpak asks very nicely". https://github.com/tchx84/Flatseal/issues/196

Since you installed the programme via Flatpak, you should simply lack the necessary rights (https://docs.flatpak.org/en/latest/sandbox-permissions.html). You can extend the rights quite easily with https://github.com/tchx84/flatseal.

Yes, filed https://github.com/tchx84/Flatseal/issues/196 a while ago, got no joy.

One design feature than can turn into an issue in some scenarios (usually dev tools) is the permissions of a flatpak. In case I need to tweak things, I use Flatseal. I know you can manually do this from the command line but I don’t change permissions that often so I don’t bother learning how to do that.

Does the Flatpak Permissions Settings replace a tool like Flatseal?

What about flatseal then ? https://github.com/tchx84/Flatseal

https://github.com/tchx84/Flatseal (Also on Discover. For security reasons, the Discover store installs apps as sandboxed "flatpak" apps. This one is used to view what each up can do and change the permissions of apps. May be required if the sandboxing breaks something, though usually not required.)

I believe it does. As an example if I try running Godot from the Steam flatpak, it won't be able to see any of the contents of my ~/Projects folder unless I explicitly allow the steam flatpak access to that directory that via flatpak's CLI options or using Flatseal