Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linked database file become a regular file #3435

Closed
SzzSHUN opened this issue Aug 9, 2019 · 4 comments · Fixed by #3463
Closed

Linked database file become a regular file #3435

SzzSHUN opened this issue Aug 9, 2019 · 4 comments · Fixed by #3463

Comments

@SzzSHUN
Copy link

SzzSHUN commented Aug 9, 2019

I make a link to an database file. If I open the database through the linked file, then modify and save the database, the link is gone and a regular file saved over the link.

Expected Behavior

The link to the original file is remaining as a link.

Current Behavior

The link to the original file saved as a regular file (copy of the original one).

Steps to Reproduce

  1. Create a link to the original file.
    createlink4file

  2. Open the database through this link. Edit something and save the database.

  3. The link file is gone, and the copy of the original file is created at the link path.
    aftereditlink4file

Context

The original KeePass 2.42.1 program don't do that.

Debug Info

KeePassXC - 2.4.3

Operating system: Manjaro Linux
CPU architecture: 64bit
Kernel: 4.19.62-1-MANJARO
neofetch

Enabled extensions:

  • None

I do not speak English well. Sorry about that.

@SzzSHUN SzzSHUN added the bug label Aug 9, 2019
@droidmonkey
Copy link
Member

Do you have safe file saves disabled?

@SzzSHUN
Copy link
Author

SzzSHUN commented Aug 9, 2019

Yes, i have.
safefilesave

@droidmonkey
Copy link
Member

Yup we should be resolving the canonical file path. Good catch!

@SzzSHUN
Copy link
Author

SzzSHUN commented Aug 9, 2019

Nice to help you improve!

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

Successfully merging a pull request may close this issue.

2 participants