Skip to content
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

Version 2.1.16 crushes on startup #2084

Open
curtwagner1984 opened this issue Jan 10, 2025 · 7 comments
Open

Version 2.1.16 crushes on startup #2084

curtwagner1984 opened this issue Jan 10, 2025 · 7 comments

Comments

@curtwagner1984
Copy link

curtwagner1984 commented Jan 10, 2025

  • Ripme version: 2.1.16-4-02372e85
  • Java version: 1.8.0_361
  • Operating system: Microsoft Windows [Version 10.0.22631.4602]

application doesn't start. Exception on startup.

Expected Behavior

application to start without an issue

Actual Behavior

image

when double clicking the jar file:
image

@NumNuts101
Copy link

I fixed this by installing a updated version of Java and made sure it was added to PATH

@Likander
Copy link

Could you explain how you got it to work a little more? I updated Java but am still getting the java error/crash on startup

@NumNuts101
Copy link

NumNuts101 commented Jan 12, 2025

I'm Just going to copy and Paste what ChatGPT helped me do!
Check Your Current Java Version Run the following command to check your Java version:

bash
Copy code
java -version
If it shows a version lower than 17, you need to update your Java installation.
https://www.oracle.com/java/technologies/downloads/?er=221886
Add the JDK to Your System's PATH
For Windows:
Find the JDK Installation Directory: Locate the folder where the JDK is installed (e.g., C:\Program Files\Java\jdk-17).

Update Environment Variables:

Press Win + S and type "Environment Variables," then select "Edit the system environment variables."
In the System Properties window, click the Environment Variables button.
Under "System variables," find the Path variable and click Edit.
Add the bin directory of your JDK installation (e.g., C:\Program Files\Java\jdk-17\bin).
Click OK to save your changes.
Restart Your Command Prompt: Open a new Command Prompt and try running:

If successful, it will display usage information for the jar tool.

I hope this helps, if it doesn't let me know what the error is and we'll chatgpt it together!

@Likander
Copy link

I still can't seem to get it to work. I don't know what bash is, or how to make it work but the version of java I have is 25, and the only jdk I could find was in legal. I downloaded jdk separately and dropped it into the java folder, copied the address and put it into the system variables Path variable and clicked ok. As far as I can tell it's still not recognizing any jar (even though I have a much older version of ripme that is a jar that still works fine).

@NumNuts101
Copy link

NumNuts101 commented Jan 12, 2025

sorry Iqnore the bash I should of deleted it, when you try to launch it in terminal what error are you getting?
I'll send you the ChatGPT link read though it and give some of the options a try
https://chatgpt.com/share/67831186-3f24-8006-b8d5-5b667110d821

@Likander
Copy link

Ok, after following 7 different guides saying different things I found one saying I should have downloaded the "x64 MSI Installer" instead of the basic x64 installer, and that should fix the pathing issue by itself. I did that, and the newer version worked. I clicked update to the newest version (had to reset the language back to eng) and it seems to be working now.

@curtwagner1984
Copy link
Author

  1. Yes. Updating java resolved the issue.

  2. I already had java installed and i thought i have the most updated version because I ran the autoupdater that's included with Java. Apparently if failed.

The way I updated was to manually uninstall the old version (Start -> Add or remove programs -> uninstalled java) and then download the installer from the link above
https://www.oracle.com/java/technologies/downloads/?er=221886
I used the msi installer. It was my hope that it updates the env vars on it's own. And this seems to work quite fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants