Skip to content
This repository has been archived by the owner on Nov 26, 2019. It is now read-only.

Wrong password message after each reopening of the app #32

Open
elutz opened this issue Nov 10, 2019 · 3 comments
Open

Wrong password message after each reopening of the app #32

elutz opened this issue Nov 10, 2019 · 3 comments
Labels

Comments

@elutz
Copy link

elutz commented Nov 10, 2019

If I close the app and want to open it again with the last used database, the password isn't recognized, at least this suggests the error message I got.
I have to repeat the whole process of opening a database, selecting database file, selecting keyfile, enter password. Then it works. Until I close the app ...
This is with a database of type: Keypass 2

This is with Sailfish 3.1.0.11 (Seitseminen) on a Sony Xperia XA2

@jobe-m
Copy link
Owner

jobe-m commented Nov 11, 2019

Hi Lutz,

it could be that you used previously a keepass database with the same name but without a key file.
Please look into the config file of ownKeepass under /home/nemo/.config/harbour-ownkeepass/settings.ini and check in the "recentDatabases" list that the item for your database has a proper entry for "useKeyFile" and "keyFilePath".
If not than ownKeepass is trying to open the database without a keyfile and that -of course- cannot work.

Could you tackle your problem down to this reason? If yes, than I can look into a proper fix for this situation. Thanks.

@elutz
Copy link
Author

elutz commented Nov 14, 2019

Sorry for the late answer.
But your are right. In settings.ini I found wrong content, it pointed to the wrong keyfile.
And if I remember right I used this wrong keyfile in the past, but corrected it afterwards. But opening the database with the right settings doesn't update the settings.ini
Now I deleted the file, opened the database again and it works after closing and reopening the database.
Regards
Lutz

@jobe-m jobe-m added the bug label Nov 14, 2019
@jobe-m
Copy link
Owner

jobe-m commented Nov 14, 2019

Thanks for your message. So it seems that there is a bug in updating the settings.ini file. I will look into it later.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants