-
-
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[JavaFX Application Thread,5,main] #5446
Comments
Could confirm this under windows, too:
|
JabRef 5.0.0-dev--2019-10-14----d2ddff574 I can confirm this issue as well. |
JabRef 5.0.0-dev--2019-10-14----d2ddff574 |
This should be fixed in the latest development version. Could you please check the build from http://builds.jabref.org/master/. Thanks! Please remember to make a backup of your library before trying-out this version. |
Now Java just crashed when starting Jabref, core dump attached. Note that "The crash happened outside the Java Virtual Machine in native code." |
The exception is thrown from some network/proxy detection class in the VM. Do you maybe have an old instance of java or jabref lurking around? |
I have Java 12.0.2 and the JabRef version from today. |
@tobiasdiez Thanks, it works again under: JabRef 5.0.0-dev--2019-10-16----e36daae20 |
@Siedlerchr, you were right, the problem's gone now. |
JabRef 5.0.0-dev--2019-10-17----e81d58c51 Can confirm that the issue is fixed in the current development version. |
how to fix it? |
I am getting this exception still in 2021.. |
You need to report which JabRef version you are using. |
JabRef 5.2--2020-12-24--6a2a512 I am also running into this issue. It is only occurring with one of my libraries and not any others. |
Have you tried the latest dev build? Remember to make a backup of your JabRef database before installing the current development version. |
@AEgit I tried the dev build and it appears to be working fine now! Thanks. |
Cheers! |
This version is OK. |
Hi All, I have just installed version JabRef 5.10 as 'phyzhenli' suggested that works. Unfortunately it does not work. The error message sent is: "Uncaught Exception occurred in Thread[#31,JavaFX Application Thread,5,main] I use Ubuntu 2204 JabRef version 5.3 worked fine. Could anyone suggest a solution? Thanks. |
@petersaly |
Can you past the whole stack trace/the whole content of the error message? |
Thank you for answering. Meanwhile, I upgraded my opendk java to version 17. It was effectless, and it is understandable because ThiloteE writes that JabRef comes with its own bundled java version. It is OK. I did not know this information. Further, I downgraded to JabRef version 5.3, which version worked for me in last summer. However, this time version 5.3 also produced the same error. After that, I re-installed version 5.10. I install JabRef versions from .deb package via GDebi package installer. Here, I attach a text file with the details of the error message sent by version 5.10 and a screenshot |
I have forgotten to write how to reproduce:
|
Try:
in addition, you also could try to
if the portable version works, we know it has something to do with your system or the gdebi package manager. |
Hi, there seems to be something wrong with the OO style. Can you try to reset your preferences? |
Hi, The package 'libreoffice-java-common' is installed on my computer. Before I try the portable version, could give me some instruction how to reset my preferences, please? |
Dear All, I have found out how to reset preferences: JabRef menu, Options -> the rightmost icon button in the left bottom corner "Reset preferences". I have reset, and restarted JabRef 5.10. No error message. It works perfectly! Thank you very much for your time and effort to help me and others. Best regards, |
JabRef version
JabRef 5.0.0-dev--2019-10-14----824b10363
Linux 5.0.0-31-generic amd64
Java 12.0.2
on Linux 18.04 installed from .deb file downloaded from https://builds.jabref.org/master/jabref_5.0.0-1_amd64.deb
Steps to reproduce the behavior:
Log File
The text was updated successfully, but these errors were encountered: