Package Details: minecraft-launcher 2.1.11314-1

Git Clone URL: https://aur.archlinux.org/minecraft-launcher.git (read-only, click to copy)
Package Base: minecraft-launcher
Description: Official Minecraft Launcher
Upstream URL: https://mojang.com/
Keywords: game minecraft
Licenses: All Rights Reserved
Conflicts: minecraft-launcher-beta
Provides: minecraft-launcher-beta
Submitter: shoghicp
Maintainer: petr
Last Packager: petr
Votes: 158
Popularity: 10.88
First Submitted: 2017-01-18 14:17
Last Updated: 2020-01-24 13:18

Dependencies (12)

Required by (2)

Sources (3)

Pinned Comments

petr commented on 2018-12-20 09:56

The java version is ... problematic. The current version of the base game will work with any Java version. So will some of the very old game versions that do not use launchwrapper.

Java 8 is required for all legacy versions, and all modded versions of the game (except for some experimental builds of Forge for 1.13). It makes sense to require it, because easily, 99% of the various ways to play the game DO require it. Roughly half of the players play modded regularly.

Fixing the old and modded versions is a non-trivial (almost intractable) task. Fixing Java would require forking it and maintaining the fork. Java runtimes of different versions are installable side-by-side. The launcher needing 'a java 8 runtime' should not prevent you from installing and using a different one.

If you have any suggestions about how to improve this situation, I'm all ears. However, using Java 9+ by default would introduce major issues.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

jpegxguy commented on 2020-02-18 13:00

@Feakster This minecraft launcher isn't a jar file like the old one was, it's an Electron linux x86_64 executable. True enough that the jar file was more portable between architectures

Feakster commented on 2020-02-18 11:47

The older version of this launcher at https://aur.archlinux.org/packages/minecraft/ had arch=(any) set in the PKGBUILD file. Is there a reason this build needs arch=('x86_64') set? I thought part of the point of java was that it could be cross-platform and cross-architecture.

chenjunyu19 commented on 2020-01-27 06:48

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/

sprinter89 commented on 2019-11-30 23:19

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

petr commented on 2019-11-30 11:45

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

audrius commented on 2019-11-20 22:30

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

gkun commented on 2019-10-27 16:28

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?

aurifier commented on 2019-10-25 03:37

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?

daenney commented on 2019-10-15 16:17

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.

stick commented on 2019-10-12 23:42

@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