-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[Bug Report] Jmusic-0.4.0 jar file - a java exception has occured #1497
Comments
same here |
I believe this is because we have upgraded to Java 11 in version 0.4.0 & you're using Java 8 at the moment. Can you check if you have Java 8 & if you do, upgrade to 11? |
seems to work with AdoptOpenJDK x64 11 which can be handily installed via ninite dot com |
that was the reason why - its fixed now thanks |
Can you expand on how to update Java? I downloaded version 11 (11.0.22) and confirmed it is the version I am using by typing java -version into the cmd, but I am still getting the error when trying to run the bot. |
With just that screenshot it's a bit hard to debug. For anyone still running into this issue, can you share the output of running both |
Can you navigate to the folder ( |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
the issue was because i didnt know i needed Java 11 Lmao - and i dont run it via CMD - but i downloaded Java 11 and it worked so :) |
This comment was marked as off-topic.
This comment was marked as off-topic.
Please keep in mind that the issue we are tracking is a java exception occurring. This happens immediately upon double-clicking the jar in a desktop environment. |
I have the same problem. I have java 21 installed and 4.0 jar fails to start. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Is there an option to use it now just by double clicking without using cmd? I can open it only via commands you provided. |
I have a feeling that the root cause is multiple java installations, and the install that Windows picks when double-clicking is different from the default one on the Path when using command line. A potential way to help debug this is to make a dummy jar that is compiled with an older version of java that can display the current java version when launched. One solution that may be worth investigating would be using something like JSmooth to wrap the jar in an exe file. This might solve some other issues too, like default file types (people accidentally opening the jar in winrar), and possibly even default-filepath issues (where sometimes the 'current directory' doesn't match the jar when double-clicking). If we went this route, we'd need to figure out how to use JSmooth in Github Actions. |
OK! I found the solution, I uninstalled java 8 and then I installed Java SE Development Kit 11.0.23 from Oracle (skipping their login with bugmenot) and it works, all the versions have no issues with" java exception has occurred" |
Excellent, I suspect that an Adoptium install of Java 11 would have worked as well; I think it was the existence of Java 8 that was causing the problems. Either way, this seems to be resolved; I'd still like to look into JSmooth but that can be tracked separately. Thanks for the investigation. |
Bug Description
Steps to Reproduce
download the latest, then attempt to run it after setting up the file
Expected Result
to load up the music bot
Debug Output
cannot get bot to load - just has a the following thing in the image below
![image](https://private-user-images.githubusercontent.com/96262903/311431917-c28c0e76-d6c0-4d77-a1ab-3e02bb1c8fa2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQyNTM3MjUsIm5iZiI6MTcyNDI1MzQyNSwicGF0aCI6Ii85NjI2MjkwMy8zMTE0MzE5MTctYzI4YzBlNzYtZDZjMC00ZDc3LWExYWItM2UwMmJiMWM4ZmEyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODIxVDE1MTcwNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTUxMmNmNjhiNmQ2MDkxYTQ3MGUxM2I5ZGE4MzIwODdmZGNkMGMwMTc3MjBlNDIyODJmYWM0MmQ5MWM2ZTc1ZGQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.gNf8heil_CyJasFD-YULMHx1UCcL903QGfD1u89KZuU)
Additional Info
No response
Checklist
The text was updated successfully, but these errors were encountered: