-
-
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
Icon doesn't show in Start menu | JabRef.exe does not start (JRE15 issue) #6890
Comments
DId you encounter this problem again? |
Deinstalled an installed from http://builds.jabref.org/master/ |
Well, removing the shortcut from the Start menu, after reinstallation nothing appears in the start menu. No JabRef folder containing JabRef link to the program, nothing in the "Recently added" section of the start menu. |
Temporary made JabRef start by running runtime/bin/JabRef.bat JabRef 5.2--2020-10-04--31f894c |
Thanks for the feedback. That's odd. We will investigate that |
@crystalfp Can you please test to start the Jabref.exe from the cmd? Do you get any errors? |
I have to run JabRef.bat from runtime\bin, the JabRef.exe in the installation directory does nothing.
The same problem happened before, unfortunately I don't remember how I had solved it. |
Forgot to add the Java Error log: |
@crystalfp Thanks. Could you please try this version? if the exe starts? |
No, it does not start. But creates the following error log: |
Is it true that latest build (JabRef 5.2--2020-10-12--46cc82c, Windows 10 10.0 amd64, Java 15) does not put an entry in Start menu and does not associate .bib to JabRef? Before downgrading to the latest official version, I want to be sure it is not a problem from my side. |
Normally it should work. I will check that. |
Deinstalled and rebooted before installing 7008/merge. |
In reference to https://discourse.jabref.org/t/5-2-dev-do-not-start/2344/6?u=buhtz The msi-version still do not start, no error output or any log. The portable-version do not start but create a log. See attachment. |
The Java 32bits was a red herring. Installed JRE 64bits and nothing changed. |
Than you should fix JabRef to write its log in the appropriated directory and also create a usefull output on stderr. I did not double click. I started via command line. |
Thanks all for the testing, I am in contact with the official Java Development Team regarding the error, because it's an error coming from the JDK itself. I will keep you updated. |
A member of the Java development Team could reproduce the issue. In the meantime you can use the bat to start JabRef or we need to downgrade on Windows back to jdk14 |
Useless because the bug ticket can not be monitored because the system is restricted to high level users. No way to create an account for normal persons like me. Thanks Oracle. ;) |
We downgraded the windows version back to java 14, so the exe issue should not be longer a problem. |
Can confirm that this version is running with Windows 10 JabRef 5.2--2020-10-14--a768f6e Thanks a lot. |
This development build is running under Windows. However, the "Check Integrity" option does not work anymore under the development build for the last few days |
@AlexPars Works fine for me. Can you please open a new issue with some details e.g. what exactly is not working. |
Sure, will open a new issue. The problem is the following: I can run "Check integrity" (Quality -> Check Integrity) , and at the end of run I am getting a pop-up message "Error occurred: Integrity check failed" , with no other details |
@crystalfp The Windows protection dialog will always come because we don't have a code signing certificate yet (that costs money). We tried to buy one but it was not successful. We will probably try this again once our non profit org is officially registered. I just merged a change which should now create a start menu folder as well. Should be ready in half an our so. |
I confirm that JabRef 5.2--2020-10-15--13a80ba solved all problems. |
JabRef 5.2--2020-09-07--aa14db9
Windows 10 10.0 amd64
Java 14.0.2
On the Start menu the JabRef icon is substituted with the icon of a generic file.
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: