KPXC doesn't honor ConfirmAccessItem in [FdoSecrets] when it cannot find the executable path

[StayPirate]

The problem of fingerprinting short-live processes was lengthy discussed keepassxreboot/keepassxc#7571 and keepassxreboot/keepassxc#6458. The quickest workaround is to set ConfirmAccessItem=false under [FdoSecrets] to revert to 2.6.x behavior.

Flatpaked KPXC does not honor the ConfirmAccessItem option and keep showing the following dialog every time Nextcloud-client starts, even though I have ConfirmAccessItem=false

Please note that nextcloud-client is installed via Flatpak as well. I have no memories of this weird behavior in my previous setup where both KPXC and Nextcluoud-client where installed via the distro's packet manager.

[StayPirate]

My best guess is that KPXC has no visibility over the nextcloud binary because it's from another flatpak container. Hence, it behaves like shown above.

IMO if ConfirmAccessItem is set to false KPXC should not show that dialog, instead allows the process (with the inaccessible binary) to access the requested data right away.

[droidmonkey]

This is a bug in KeePassXC itself