Skip to content
This repository has been archived by the owner on Oct 20, 2022. It is now read-only.

launcher seems to "forget" which java version it's using #17

Open
lumap opened this issue Jan 19, 2022 · 4 comments
Open

launcher seems to "forget" which java version it's using #17

lumap opened this issue Jan 19, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@lumap
Copy link

lumap commented Jan 19, 2022

I often get an error message when launching ManyMC regarding my java version "not working or went missing", even tho i never touch any of the java VMs i have. I just have to re-select java 17 as the default version and it works fine, until a couple hours after closing it or after a reboot. little bug, but still annoying

@ViRb3
Copy link
Member

ViRb3 commented Jan 20, 2022

Have you tried manually browsing for your Java and using its full path, instead of selecting the first result called just "java"? Maybe that's the problem.

@ViRb3 ViRb3 added the bug Something isn't working label Jan 20, 2022
@lumap
Copy link
Author

lumap commented Jan 20, 2022

image

@caitlynrw
Copy link

This looks to be an issue with upstream MultiMC too.

@ViRb3
Copy link
Member

ViRb3 commented Feb 19, 2022

This just happened to me today. Strangely enough, after I selected the same Java version as before, it doesn't prompt me anymore.

ViRb3 pushed a commit that referenced this issue Jun 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants