JabRef version
5.7 (latest release)
Operating system
GNU / Linux
Details on version and operating system
Debian 11 with Mate Desktop
Checked with the latest development build
Steps to reproduce the behaviour
Just import any reference using the JabRef-Brower-Extension. In my case, with Firefox.
Appendix
Whenever importing a reference using the JabRef-Browser-Extension (latest version of JabRef and extension) another new instance of JabRef is opened, independent of whether another instance of JabRef is running or not. As a result, every reference import opens an additional instance of JabRef, so several instances will run in parallel. Ticking the setting in Network -> Listen for remote operation on port 6050 does not have any effect (Is this setting still in use?) The same happens, when JabRef is run from source, then another instance will start from the installed binary version.
Log File
JabRef version
5.7 (latest release)
Operating system
GNU / Linux
Details on version and operating system
Debian 11 with Mate Desktop
Checked with the latest development build
Steps to reproduce the behaviour
Just import any reference using the
JabRef-Brower-Extension. In my case, with Firefox.Appendix
Whenever importing a reference using the
JabRef-Browser-Extension(latest version ofJabRefand extension) another new instance ofJabRefis opened, independent of whether another instance ofJabRefis running or not. As a result, every reference import opens an additional instance ofJabRef, so several instances will run in parallel. Ticking the setting inNetwork->Listen for remote operation on port 6050does not have any effect (Is this setting still in use?) The same happens, whenJabRefis run from source, then another instance will start from the installed binary version.Log File