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.

I am having an issue with Microsoft login. After clicking "Microsoft login," the login page refuses to load with the error: ERR_NAME_NOT_RESOLVED.

DNS is working because I can access Minecraft and Microsoft websites without any problems. Also, I could log in with the same launcher using a Mojang account. It just stopped working once I migrated to a Microsoft account.

Anyone with the same issue?

@Maximilian I was very happy to see your message, but it didn't solve the problem for me.

/update: after removing my account from the launcher and re-adding it I was able to successfully log in again.

To those who are looking here because the Minecraft launcher doesn't work anymore, you can fix it by deleting the launcher folder in the .minecraft folder.

The Minecraft Launcher requires gnome-keyring in order to store your Microsoft account credentials. I don't know how to make a pull request for a PKGBUILD here, but you should add to the optdepends line:

optdepends=('flite: narrator support' 'gnome-keyring: save account credentials for automatic login')

How can i play offline with this?

@MuggleTwist I suspect this might be leftover from back when the launcher used to use system java. (If we go back even further, the launcher used to be a java applet... although I think that predates this package).

If the launcher does indeed source its own java runtime, like it does on Windows, then java probably shouldn't be a package dependency.

Is there a reason this depends on java? The launcher downloads its own version of java and works fine with that. it doesn't need system-wide java installed.

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.

Undoubtedly confusion between the application version, which Mojang lists, and you need to install the package to see locally, and the package file revision number, which you need Mojang's package repository manifest to see, as they only link to un-numbered packages for the initial download.

It will stay marked as out of date until a maintainer shows up to unflag it. It might help if someone pins either this, or a more concise explanation of the above, so that future users do not get confused by the two different version numbers.

Why is this package marked as outdated when it isn't?