Arch Linux User Repository

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:

$ minecraft-launcher
sh: line 1: orca: command not found
Created browser window for reuse: 0x1600004
[34399:34552:0308/133050.212343:ERROR:mime_util_xdg.cc(137)] Invalid mime.cache file does not contain null prior to ALIAS_LIST_OFFSET=44
[34399:34552:0308/133055.416488:ERROR:cast_crl.cc(443)] CRL - Verification failed.

Edit: I found that deleting the webcache2 directory in the .minecraft directory fixes the issue for me.

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.

@kashall

Package is out of date, Mojang has released a new version on their website but this package uses the static version of the old launcher. We actually use an unversioned link to the latest available deb package. I did a clean build and I didn't saw any checksum errors and version of the launcher is the same.

I don't really get the dependency list:

• gconf? (From a comment in the gconf package: "Chromium (and subsequently Electron) haven’t been dependent on this for years" - that, plus it's apparently obsolete)
• libxss? (X11 Screen Saver extension library)

Frankly I don't really know, just find it weird

Both the minecraft and minecraft-launcher packages are broken for me. When running them there are no errors in the console, then the window just doesn't open and the process is at 100% on one of my cpu cores.

The launcher_log.txt doesn't give any information either.

@milk package is just updated

Getting a sha256sum error with 2.1.14930-1 as well

I'm slowly working on getting the updating of both minecraft-launcher and minecraft-launcher-beta automated, and hooked up to our CI/CD setup.

So, Soon:TM:, that part of maintenance shouldn't need manual action.

I just want to point out again that this package was flagged out of date well before a new launcher version was actually released. The launcher will probably still report a new version when a new beta is available.

Updated, Minecraft Launcher just released a new version with few bug fixes:

Put these in your PKGBUILD to get new version until @petr decide to update it.

pkgver=2.1.14403

Sha256Sum:

2f888fb423133c48c987408581ff0bddfb8eb79115c9796ccc1c28167146cc20