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.

smorky: That's because when mojang update the snapshot, the link doesn't change. That means that the checksum is different so will fail integrity checks.

Ideally, mojang would provide versioned or datestamped links for the snapshots, but AFAIK they don't. Them updating the release build would also work, but iirc the latest release build doesn't even work anymore.

Minecraft.tar.gz fails sha256 checksum in 2.1.1218-1 update.

@BombStrike My apologies. Your response to my request (and recent comment) helped me to understand why things are the way that they are between the two packages.

@BombStrike: I see, my bad!

@Brottweiler The tweet mentioned do not talk about the download link, but about the version file and my package already points to the link requested by Dinnerbone: https://aur.archlinux.org/cgit/aur.git/tree/minecraft?h=minecraft#n11

I flagged the package out of date now because the source URL is still not updated to the new one, which means this package could break randomly at any time when the legacy URL is removed.

I don't see any reason why you should place the new launcher here at all. As there already is a package with the new launcher maintained by Mojang, it would result in having two packages for the same thing, which is just useless.

Missing dependency issue : Permanently resolved

Missing dependency gconf I think.

./launcher: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory