#2446 Unable to Keep Configuration Items In Local ...config.xml File

[James D. Howard]

I am unable to restrict keepass 2 config file settings regarding triggers to the user's own config file ~/.config/KeePass/KeePass.config.xml. (Fedora Linux 44, KeePass v 2.61.1, installed from .rpm, mono version 6.14.1.) The setting <preferuserconfiguration> - while initially edited to true, is reset to false whenever the Trigger... dialog is used to set up a pair of synchronization triggers. Upon [ OK ], a warning dialog box appears telling me it will write to the system global config file
/usr/lib/keepass/KeePass.config.enforced.xml
I am then presented with a superuser authorization dialog box to enable write to KeePass.config.enforced.xml. This is not expected or desired.
keepass appears to write the trigger config to the user's ~/.config/KeePass/KeePass.config.xml file AND to the KeePass.config.enforced.xml file, then changes the user-local config file to show <preferuserconfiguration> to be false.</preferuserconfiguration></preferuserconfiguration>

Expectation: Write trigger configuration to only the user's ~/.config/KeePass/KeePass.config.xml file and leave <preferuserconfiguration>true, for continued local config reading upon next invoke. Read those trigger settings from there again upon next invoke.</preferuserconfiguration>

Observed: Unable to configure keepass to keep configuration settings local, filling up the global enforced config. This negates others from using the keepass installation on this workstation box; they have my stuff forced on them!

If this is an installation or configuration issue for a global (/usr/bin/keepass)-->(/usr/lib/keepass/KeePass.exe), PLEASE instruct me!

[James D. Howard]

ATENTION: This bug report is actually about KeePass version 2 - NOT version 1. I'm unable to find a way to edit the submission to change that field. Can someone correct that for me?

[Paul]

You don't need to open a bug report about an issue you have already been discusing, especially as it is not a proven bug.

cheers, Paul

[James D. Howard]

In my opinino it is a proven bug, misbehaving on Linux. It appears to be a logic error in handling rights and access recognition for Linux. The online documentation states how keepass is supposed to work - regardless of platform - and it is not doing so, regardless of how I adjust the file and directory access modes (permissions). keepass is insistent on ignoring the fact that, when run under the user login ID, with no write access to the global files, will STILL insist on writing to the global config file - ignoring <preferuserconfiguration>true.</preferuserconfiguration>

Why would it not be a bug to ignore <preferuserconfiguration>true?</preferuserconfiguration>

Also, could you please bounce this over to the category for KeePass v2?