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.

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"

I don't know if this is the latest version, but this exists: https://launcher.mojang.com/download/linux/x86_64/minecraft-launcher_1121.tar.gz compare with current source https://launcher.mojang.com/download/linux/x86_64/minecraft-launcher_928.tar.gz

Found via: https://github.com/flathub/com.mojang.Minecraft/blob/master/com.mojang.Minecraft.json

For me, this package works for one user, but not for another (on the same system). For the second user, simply nothing happens. Launching from the terminal, also, nothing happens, there does not seem to be any process related to minecraft in the output of ps -au.

I'm on the latest Gnome btw.

How could I troubleshoot?

Hmmm, after installing, I run minecraft from the terminal.

Launcher pops up, attempts to download update files (small dialog with progress bar) but disappears shortly afterwards.

$ minecraft-launcher 
https://launchermeta.mojang.com/v1/products/launcher/6f083b80d5e6fabbc4236f81d0d8f8a350c665a9/linux.json
(doesn't show dialog, press Ctrl + C, goes to next line and dialog appears)
^Chttps://launchermeta.mojang.com/v1/products/launcher/6f083b80d5e6fabbc4236f81d0d8f8a350c665a9/linux.json
OK
https://launchermeta.mojang.com/v1/products/launcher/6f083b80d5e6fabbc4236f81d0d8f8a350c665a9/linux.json
(launcher disappears at this point)
https://launchermeta.mojang.com/v1/products/launcher/6f083b80d5e6fabbc4236f81d0d8f8a350c665a9/linux.json
OK
https://launchermeta.mojang.com/v1/products/launcher/6f083b80d5e6fabbc4236f81d0d8f8a350c665a9/linux.json

Process is still running (with no dialog visible), and continues (for atleast 12 hours)

ps -au | grep minecraft
cybex     130202  3.8  0.2 1162716 66896 pts/5   Sl+  05:01   0:06 minecraft-launcher
cybex     130367 17.7  0.1 875252 62972 pts/5    Rl+  05:02   0:14 /home/cybex/.minecraft/launcher/minecraft-launcher --nativeLauncherVersion 928 --chainLoad
cybex     131735  0.0  0.0   6672  2596 pts/6    S+   05:04   0:00 grep --color=auto minecraft

Running on Java 8 (originally had java-18, no go)

java -version
openjdk version "1.8.0_332"
OpenJDK Runtime Environment (build 1.8.0_332-b04)
OpenJDK 64-Bit Server VM (build 25.332-b04, mixed mode)

System setup

 Kernel: x86_64 Linux 5.17.3-arch1-1
 Shell: bash 5.1.16
 DE: GNOME 42.0
 WM: Mutter

@TheK0tYaRa if gnome-keyring were to be added as a package, it should be added as an optional dep as not every uses GNOME keyring. Furthermore, kwallet is soon to get the Freedesktop Secrets API support, which is what the minecraft launcher.

You can try out kwallet with this support with the aur package kwallet-secrets, which applies the patch from the Freedesktop API pull request, and following the instructions in the pinned comments.

Basically, you first install kwallet-secrets Then, you restart your system (or KDE, making sure the kwallet binary gets killed) Thirdly, you open up Kwalletmanager on KDE and make sure you already have a wallet named kdewallet Then you run the following command

gdbus call --session --dest org.freedesktop.secrets --object-path /org/freedesktop/secrets --method org.freedesktop.DBus.Properties.Get org.freedesktop.Secret.Service Collections

And you should get something like

hurricane@TheCloutPC ~ $ gdbus call --session --dest org.freedesktop.secrets --object-path /org/freedesktop/secrets --method org.freedesktop.DBus.Properties.Get org.freedesktop.Secret.Service Collections
(<[objectpath '/org/freedesktop/secrets/collection/kdewallet']>,)

From this, you will take the wallet name after `collection, and then do

gdbus call --session --dest org.freedesktop.secrets --object-path /org/freedesktop/secrets --method org.freedesktop.Secret.Service.SetAlias default /org/freedesktop/secrets/collection/kdewallet

Then restart your system (or kwallet) for good measure

Then, now finally, you should be set to go

The package is lacking a gnome-keyring dependency according to their own article: https://help.minecraft.net/hc/en-us/articles/4408668374925-Secure-Token-Storage-Failure-on-Linux

If the launcher isn't remembering your microsoft account, installing chromium fixed it for me.

As a solution for this bug https://bugs.mojang.com/browse/MCL-18924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&showAll=true that prevents Minecraft from saving your Microsoft Account credentials, forcing you to login every time you open the game, you need to install gnome-keyring and if you're not using a GTK environment like KDE you need to follow this steps: https://wiki.archlinux.org/title/GNOME/Keyring#--start_step

It should be nice if gnome-keyring could be added as a optional dependency with a warning about this issue.