4/22/2023 0 Comments Keepass linux mint![]() KeePass will behave as you desire if you simply ignore the error message. the KeePass application directory, it displays the error message and writes to the local config file location specified by -cfg-local. However, when KeePass subsequently fails to save the config file to the preferred location, i.e. KeePass will read the local config file if a global config file does not exist. In your case, even though you specified the location of the local config file on the command line, KeePass prefers to use the global config file because that is the internal KeePass default setting. The PreferUserConfiguration setting in the global config file tells KeePass whether to prefer the local config file or the global config file. See the last line of the KeePass configuration documentation. It does NOT tell KeePass to use the local configuration file. The -cfg-local command-line option tells KeePass where to find the local configuration file. The basic problem is that KeePass is trying to write a global configuration file but the KeePass application directory is write-protected. Before KeePass 2.47 if this condition occurred there was no error message. The settings as described by Paul, and that you are using, creates the error state that you have encountered.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |