-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Linux JabRef does not start at all #7367
Comments
@systemoperator sorry to bother, does the latest master run on your Linux machine? |
Can you try to start it from the script under runtime/bin/JabRef ? |
I get this result Log File
|
Hm, this is odd. Seems like somehow the data from our build info are not passed down... As far as I know, nothing to that has changed. I will try something and prepare a new branch build. |
I just tried this on the same configuration and it worked. I put an alias in /etc/bashrc alias jabref="/opt/jabref/bin/JabRef 2>/dev/null" after this open a new window and it should work. The logger errors are always there. This is using the rpm version of Jabref |
@ilippert I can confirm your stated issue with your mentioned master build on Ubuntu 16.04, using OpenJDK 15. The problem is that
because it requires that the key is non-empty and non- Forcing a non-empty value for testing purposes starts the application properly. |
The build info key should be set by the CI and gradle |
Hi @sambo57u with the proposed alias I get this result Log File
|
Hmmm.....why do you say bellsoft java? jabref has its own java...perhaps some path is set that interferes with it. I only have openjdk java's from Fedora repository. You get a bunch of logger messages but jabref starts. |
Since #6559 I have been only working with bellsoft. |
The java version doesn't matter. JabRef ships with a custom runtime. Can you try to add the |
this gets me Log File
|
same problem here. |
Can you test the version from here https://builds.jabref.org/pull/7371/merge/ ? |
On linux mint 20.1 Cinnamon 4.8. Installed from that deb and got the same-looking startup errors:
|
It could be too late here, but I hink, the solution is simple. I do not find the setting The workround is to set the environment variable |
This is very puzzling. Why is mine working. I am on Fedora 33 x86_64 too and have done nothing special. |
The link directed me to the master. it still gives me the result Log File
|
Can you please try again with the latest master? Newest build contains a workaround |
JabRef 5.3--2021-01-21--1be95fc works! |
JabRef 5.3--2021-01-21--94f4c1e Also good. Thank you! |
Thank you all for the patience 🎉 |
I am using
jabref-5.3.85-1.x86_64, downloaded morning of 19th Jan GMT with bellsoft-java15.x86_64 on Fedora 33.
JabRef does not start.
Happy to provide details if you tell me which commands to run in the shell ;)
The text was updated successfully, but these errors were encountered: