Well, we now have a bootstrap on Linux, similar to what the other platforms had for years.
That means the launcher updates itself, and you can switch between release/beta from inside of it.
We also updated the CEF (chromium embedded framework) to a version that isn't from 2016... And that may affect a few things. So please file bugs on https://bugs.mojang.com/ when you see them. The sooner, the better.
The other major change is the launcher installing a JRE for you. While that's nice, we also need the dependencies for a JRE, and that's why I'm keeping the java-runtime
dependency. Not for actually using a java runtime from the system, but to get all of the dependencies for one from the system so our bundled one can work.
@MartinX3 are you using a switchable/dual graphics setup? This may be related: https://bugs.mojang.com/browse/MCL-17125
Pinned Comments
wheat32 commented on 2025-03-08 18:32 (UTC) (edited on 2025-03-08 19:30 (UTC) by wheat32)
I seem to be having a different issue than what others are describing. Suddenly today, I an unable to start the launcher without getting a generic "An unexpected issue occurred" message. Here's what I get in the terminal:
Edit: I found that deleting the webcache2 directory in the .minecraft directory fixes the issue for me.
petr commented on 2021-10-08 09:04 (UTC)
The package version is the version of the launcher bootstrap - the part that actually downloads and updates the launcher.
That means the version number of the actual launcher (2.x.xxx) is different from the version here (9xx+) on a fundamental level, and should not be compared.
The package is outdated only when the bootstrap version you get here is different from the bootstrap version you would get from minecraft.net when using the raw tarball.