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.

From Google Translate:

For me, as of version 2.1.11314-1, skin management is still not working. By looking at the terminal output, you can see that the launcher is missing some library files.

To solve this problem, first make sure that you have the libglvnd package installed, and then you can use the following command to link the libraries in your system into theminecraft-launcher folder.

Alternatively, if you have other CEF / Electron applications (such as visual-studio-code-bin), you can simply copy the swiftshader folder from these applications into the minecraft-launcher folder.

中文原文：

对于我来说，截至版本 2.1.11314-1，皮肤管理仍不能正常工作。通过观察终端输出，你可以发现启动器缺少了一些库文件。

要解决这个问题，首先确保你已经安装了 libglvnd 软件包，然后可以使用下面的命令将系统中的库链接到 minecraft-launcher 文件夹中。

或者，如果你有其他 CEF / Electron 应用程序（例如 visual-studio-code-bin），你可以简单地将这些应用程序中的 swiftshader 文件夹复制到 minecraft-launcher 文件夹中。

# mkdir /opt/minecraft-launcher/swiftshader
# ln -s /usr/lib/libEGL.so /opt/minecraft-launcher/swiftshader/
# ln -s /usr/lib/libGLESv2.so /opt/minecraft-launcher/swiftshader/

Actually, in the dependency solving state, openjdk8 must be installed to properly execute minecraft. So, I timidly suggest forcing java version to 8.

Yes, gconf is required. Something inside CEF needs it. And it's not trivial to get rid of it.

Is gconf dependency really required? Currently this is single package which pulls gconf (with python2) in my system.

I recently wasn't able to launch minecraft after a Java upgrade (java would fill up the memory and not start the game when I clicked on "play" from the launcher).

I'm using jre8-openjdk (java 8) which was running fine until version 8.u212-1, 8.u232-1 wouldn't start the game. Did anyone else have the same issue?

I just upgraded from a really old version of the launcher, but I'm getting this now when I start the launcher:

** GLib:ERROR:../glib/glib/goption.c:1837:platform_get_argv0: assertion failed: (memchr (cmdline, 0, len)) Bail out! GLib:ERROR:../glib/glib/goption.c:1837:platform_get_argv0: assertion failed: (memchr (cmdline, 0, len)) Aborted (core dumped)

Any ideas what's wrong with my system?

You can work around the issue for now with env GDK_BACKEND=x11 minecraft-launcher instead. The issue is tracked here: https://bugs.mojang.com/browse/MCL-12215.

It would probably be handy if the minecraft-launcher.desktop was updated to include this workaround for now.

Alternatively:

mkdir -p ~/.local/share/applications/
cp /usr/share/applications/minecraft-launcher.desktop ~/.local/share/applications/
sed -i 's/Exec=/Exec=env GDK_BACKEND=x11 /g' ~/.local/share/applications/minecraft-launcher.desktop

Now you can start Minecraft Launcher as usual and keep updating this package as your definition of minecraft-launcher.desktop will override the one shipped with the package.

@ruabmbua @dlins @nunomartins here's the error on Wayland (sway for me) with 2.1.7658:

$ minecraft-launcher

(minecraft-launcher:63405): Gdk-WARNING **: 19:39:30.017: ../gtk/gdk/x11/gdkwindow-x11.c:5633 drawable is not a native X11 window

@ruabmbua I can confirm as well. Seems broken on GNOME Wayland; running it on X works fine, though. I further tested the beta version with the same results.