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

Saving the library after any change triggers "Library has been modified by another application." #6525

Closed
systemoperator opened this issue May 25, 2020 · 7 comments

Comments

@systemoperator
Copy link
Contributor

systemoperator commented May 25, 2020

Tested with the latest JabRef development version (master branch) on Ubuntu 16.04

Saving the library after any change within JabRef, triggers the message "Library has been modified by another application.", asking either to choose "Dismiss changes" or "Review changes".

I have only tested it with Ubuntu. Maybe this results due to an unfavorable race condition with the Linux file system?

Details:

  • Saving library with CTRL+S or hitting the save button makes no difference.
  • JabRef's Autosave is not enabled.
  • All files are stored locally, without any external file synchronization.

Probably relevant (but old): #4877

@tobiasdiez
Copy link
Member

Yeaaaahhh. Finally a developer gets these warning messages! Every core developer tried to replicate these issues but couldn't, which made it really hard to fix this issue.

Since you can reliable reproduce this, can you please debug it and report which changes JabRef claims to be there between the current library and the saved file. If you have the time, feel free to open a PR with a fix as well ;-) The general problem is that certain actions are applied to the library before the save, but not to the in-memory library. This leads then to a desync between the written file and whats in memory.

@systemoperator
Copy link
Contributor Author

I have observed this issue for quite a while now, but until today, I just lived with it, but it's quite annoying. 😄 Ok, I will investigate it.

@systemoperator
Copy link
Contributor Author

To start with it, the following changes get reported:

image

image

@systemoperator
Copy link
Contributor Author

systemoperator commented May 26, 2020

Ok, what I could find out so far:

@wujastyk
Copy link

I have experienced this issue for a long time, but I've never used the "Groups" feature in JabRef.

@systemoperator
Copy link
Contributor Author

The reason is, that this reproducible case is caused by something different.

@systemoperator
Copy link
Contributor Author

systemoperator commented Jun 3, 2020

I'm closing this issue, because this concrete issue is caused by #6420 and discussed there onwards.

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

No branches or pull requests

3 participants