Skip to content

Using the Jabref 5.0 release then going back to 4.3.x will break the UI because of shared settings #6234

@Sethur

Description

@Sethur

JabRef version 5.0 and 4.3.1, Windows 10, Bundled JDK 13 and Java 1.8.0_241

I tried the current JabRef 5.0 release today on our database with approx. 2000 entries. Since I was not satisfied with the overall performance (startup time, notable lag while typing, scrolling, etc.) and resource uptake (both CPU and memory) I wanted to go back to Jabref 4.3.1. Note that I did NOT save the BIB-file in Jabref 5.0.

Unfortunately, after going back to 4.3.1., the settings of the table view seemed to have been completely messed up. Most of the columns had different names and where empty. At first I thought the BIB-file was changed, but I did a diff on a recent backup and that was not the case. It turned out, that the preferences that are saved in the windows registry for Jabref 5.0 are incompatible with the settings for previous versions but are still saved at the exact same location. This then brakes the UI.

My suggestion would be to change the path in the registry where JabRef 5.x stores its settings in order to prevent this behavior.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions