You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JabRef 5.6--2022-01-25--2c92eb0
Windows 10 10.0 amd64
Java 16.0.2
JavaFX 17.0.1+1
JabRef and the library are both on a local system WITHOUT dropbox or other sync or backup software interfering.
I was able to reliably trigger the behaviour like this:
Create new group
Immediately remove the new group that was just created. Choose also remove subgroups.
Click on save.
Result: There is a popup "The library has been modified by another program."
Most importantly, after the bug triggers once, it does not go away until Jabref was having a restart. So afterwards, every click on save will trigger the popup again, regardless of having deleted a group prior to that or not...
Expected result: No popup.
Edit: Not sure if it actually is the same issue as the original post. This is how the modified dialogue looks like:
JabRef 5.7--2022-08-05--73c111c
Windows 11 10.0 amd64
Java 18.0.2
JavaFX 18.0.1+2
I encountered the issus today after adding a single citation via Ctrl-N->Medline/Pubmed to a large library.
JabRef 5.6--2022-01-25--2c92eb0
Windows 10 10.0 amd64
Java 16.0.2
JavaFX 17.0.1+1
JabRef and the library are both on a local system WITHOUT dropbox or other sync or backup software interfering.
I was able to reliably trigger the behaviour like this:
also remove subgroups
.Result: There is a popup "The library has been modified by another program."
Most importantly, after the bug triggers once, it does not go away until Jabref was having a restart. So afterwards, every click on save will trigger the popup again, regardless of having deleted a group prior to that or not...
Expected result: No popup.
Edit: Not sure if it actually is the same issue as the original post. This is how the modified dialogue looks like:
Originally posted by @ThiloteE in #4877 (comment)
The text was updated successfully, but these errors were encountered: