Arch Linux User Repository

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.

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.

If you guys need a keyring manager on KDE that works with this, install kwallet-secrets, and follow the instructions in comments.

It is kwallet patched the freedesktop secrets API support.

@jextrevor I ran into that as well. In my case it was caused by launching Sway through dbus-run-session.

I figured out that was the problem by looking at an environment variable (I think it was DBUS_SESSION_BUS_ADDRESS).

After installing gnome-keyring, the launcher takes several minutes to load at first and then hangs again when trying to log in (tried several times, waiting several minutes each time, and never got it to finish). I don't know what's going on. Removing gnome-keyring makes it load fast again.

@logothete What if you launch it this way?

$ LC_ALL=C minecraft-launcher

@timo_capa @jpegxguy Yeah, I rebuilt the package without java-runtime as dependency and purged all Java from my system. The game behaves as if nothing happened.