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.

gconf is a dependency, CEF directly depends on gconf symbols. This is not changing any time soon.

Some form of Java runtime 8 is a dependency and will remain so until the issues caused by ABI breaks in later versions are resolved in one way or another.

This package is fully up-to-date.

Can't we eliminate gconf and other dependencies?

@rafasc It looks like for 1.13 you can still use the old launcher. I've been using it, blissfully unaware that they were planning on dropping support. This allows more time for a decision, I guess.

@BombStrike What about contacting petr about making minecraft-launcher the "meta package"? Then users using that package would be set, with it pulling in this package as a dependency. And this package could continue as the "official" package, as I feel of the two, "minecraft" is a better choice of package name.

Interesting, I always assumed MC was only java 8 compatible, but LegacyLauncher could well be the problem. Worth noting that forge plan on transitioning to a new modlauncher system with 1.13 (and anyone who wants to be forge-compatible will likely have to follow suit) so that may limit the issue to legacy versions and pre-1.13 mods.

@erkexzcx I'm pretty sure both the game and the launcher work fine under jre (version 10), as is my setup. A problem arises in the LegacyLauncher when trying to start stuff like OptiFine though.

@BombStrike I asked around on #archlinux-aur, and also based on what was said in this in this request https://lists.archlinux.org/pipermail/aur-requests/2018-June/024898.html, seems that this package should be updated to the new launcher and the minecraft-launcher should merged as a duplicate.

AFAIK, the old launcher will not be able to launch new versions of the game starting with 1.13, and since the new one is able to launch older versions, there's no reason for the old launcher to exist as a package. (Besides the fact it simply being available on that url which will probably go down in the future).

@jpegxguy It is recommended to run Minecraft with Java 8.

So now that the other launcher has become the official one, here is how I could do things:

• Empty this thing and only have a dependency to minecraft-launcher: making it pretty much a meta-package of sort, would (probably?) be the safest option
• Copy the existing package: not a big fan of duplicating stuff
• Submit a request to have minecraft-launcher renamed to minecraft, and this one to minecraft-legacy: will break people who had minecraft-launcher installed

Let me know what you guys think in the comments, I'll also be doing some research on my side to make sure the updates goes smoothly for you guys.

@BombStrike Minecraft website updated the launcher url.

Updated https://wiki.archlinux.org/index.php/Minecraft - Minecraft client (game) works fine even with java version 10, but the actual launcher starts only with java version 8.