-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Uncaught exception occurred in Thread[#39,JavaFX Application Thread,5,main] -> different # -> new bug report!? #11194
Comments
Using the the latest development release (JabRef 5.14--2024-04-12--0d1b5e8 Uncaught exception occurred in Thread[#39,JavaFX Application Thread,5,main] |
Deinstallation of JabRef via Windows Preferences followed by installation of JabRef version 5.11 did not resolve the bug. Upgrading from 5.11 to 5.13 did not change this fact either. Information on Windows version: |
@frohowi Please try out https://builds.jabref.org/pull/11195/merge? |
I just installed the msi package in the "folder" indicated. JabRef 5.14-PullRequest11195.53--2024-04-15--0421bc4 After installation, Jabref did not start in normal mode but only when starting as administrator. Same bug as before: When clicking or double clicking on an entry of my library, I got the error message (but not each time...): Uncaught exception occurred in Thread[#39,JavaFX Application Thread,5,main] |
... but writing in search field didn't produce an error :) |
JabRef version
5.13 (latest release)
Operating system
Windows
Details on version and operating system
JabRef 5.13--2024-04-01--6bdcf63 Windows 10 10.0 amd64 Java 21.0.2 JavaFX 22+30
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Appendix
I tried to install the latest development build (.msi) but being in the role of "normal" uster Jabref did not start with this latest development build.
Starting the latest development build (JabRef 5.14--2024-04-12--0d1b5e8
Windows 10 10.0 amd64
Java 21.0.2
JavaFX 22+30) as administrator was successfull (and the bug was not present)
With version 5.13:
Sorry, I was not sure if my bug is identical to #11188 so I started a new one.
Log File
The text was updated successfully, but these errors were encountered: