I suspect the underlying problem is that Mojang update their "staging" tar, but do not create versioned release archives. Therefore this package is stuck on the latest (broken) release 2.0.579, while Minecraft_staging.tar.gz stays updated and keeps working.
IMO Mojang need to improve the way they handle this, preferably by creating more releases and keeping this package in sync with them. Otherwise we are forced to use packages such as minecraft-launcher-tar that try to keep in sync with the (fully functional) staging build.
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.