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.

Nevermind, I reinstalled, restarted (from the terminal) and now it works. Apologies.

I am getting this message after installing this package:

Unable to locate the Java runtime.
Error details: Success
Filename on disk: 
Path: .
Exists: Directory

Before that it was complaining about ogg files already being on disk, so I emptied my .minecraft folder.

I'm on KDE btw.

gnome-keyring should be added as an optdepend. Without this package you are forced to enter Minecraft credentials every single time the launcher is fired up.

diff --git a/PKGBUILD b/PKGBUILD
index 2e62273..8e73b26 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -12,7 +12,7 @@ license=('All rights reserved')
 depends=('alsa-lib' 'at-spi2-atk' 'at-spi2-core' 'atk' 'dbus' 'expat' 'gcc-libs' 'gdk-pixbuf2' 'glib2' 'glibc' 'gtk3'
          'libcups' 'libdrm' 'libx11' 'libxcb' 'libxcomposite' 'libxdamage' 'libxext' 'libxfixes' 'libxrandr' 'mesa'
          'nspr' 'nss' 'pango' 'util-linux-libs' 'zlib' 'java-runtime' 'xorg-xrandr')
-optdepends=('flite: narrator support')
+optdepends=('flite: narrator support', 'gnome-keyring: Storage of your Minecraft credentials')
 conflicts=('minecraft-launcher-beta')
 provides=('minecraft-launcher-beta')
 source=("https://launcher.mojang.com/download/linux/x86_64/minecraft-launcher_${pkgver}.tar.gz"

Almost all of the info about Java versions and Minecraft below is wrong.

Minecraft isn't that picky about the Java version, the only real delineation is that versions below 1.17 work with Java 8 up to IIRC 11, while newer versions work with latest Java. Mojang/Microsoft just added a java version check to the launcher which checks if you have an exact version of java installed, not if the java version you have is actually compatible with the game or not. You can disable it by deleting the JavaCheck.jar file.

https://bugs.mojang.com/browse/MCL-18306

@rabcor @bryiewes @mattsturgeon

this package doesn't not work for me. I tried all the different version of jre.

Hi!

I encountered this when launching Minecraft 1.19 (or 1.18) with minecraft-launcher with jre-openjdk17 and nvidia-xrun (to force it to use my NVidia 920M):

The game would not launch, crashing immediately and not providing any useful logs, except for 1.18, when it said

.minecraft/runtime/java-runtime-beta/linux/java-runtime-beta/lib/libnio.so: undefined symbol: ipv6_available

On another forum I found that if I do the following export:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/jvm/default/lib/server

Some other java application would run fine. I tried this for my case as well, and now both 1.18 and 1.19 are running on my nvidia-xrun X instance.

Hope this helps somebody.

Yeah, unfortunately Java versions aren't always backwards-compatible (hence why oracle still maintain old java versions).

Most somewhat-recent Minecraft versions depend on Java 8 (aka 1.8) exactly - older or newer versions are incompatible.

Minecraft recently updated to the newer Java 17, but still might not be compatible (or perhaps not yet tested/supported on) the very latest java versions. Hence why the launcher checks you are running that particular Minecraft version with a known-to-be-compatible Java version.

This problem applies to all Java projects, although you usually only notice it on the bigger more complex ones.

bryiewes, it turns out i was mistaken anyways, the bundled version is openjdk 17; I actually tried downloading openjdk17 runtimes and targetting the binaries for that version in /usr/lib/jvm and it worked, apparently minecraft is just really picky about which version you're using. Now I'm just trying to figure out how to get it working with ZGC or Shenandoah garbage collection, gives me a generic misconfiguration error when I try to run with it.

rabcor, think of java 8 vs 18 like versions of Ubuntu. 18.04 is older but still partially maintained. 20.04 is lts, etc. Java 8 is older but still maintained and has the best compatibility with versions before 1.17. Java 18 works better for 1.17 and above. Java 8 is not outdated.

How do I use native java to run the game? If I try to use the launcher settings for java executable to /usr/bin/java or even /usr/lib/jvm/java-18-openjdk/bin/java I just get an error stating: "Your Java Runtime is incompatible. Please edit your installation to use the bundled Java Runtime. Name: Java version mismatch URL: https://aka.ms/jnierror"