Package Details: minecraft-launcher 1:1.0.1221-3

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: custom
Conflicts: minecraft-launcher-beta
Provides: minecraft-launcher-beta
Submitter: shoghicp
Maintainer: pschichtel
Last Packager: pschichtel
Votes: 1097
Popularity: 2.73
First Submitted: 2017-01-18 14:17 (UTC)
Last Updated: 2024-06-17 22:10 (UTC)

Pinned Comments

petr commented on 2021-10-08 09:04 (UTC)

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.

Latest Comments

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 .. 52 Next › Last »

sprinter89 commented on 2019-11-30 23:19 (UTC) (edited on 2019-11-30 23:21 (UTC) by sprinter89)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC) (edited on 2019-10-15 16:19 (UTC) by daenney)

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 (UTC)

@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

TangledShoelace commented on 2019-10-11 11:43 (UTC)

@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.

dlins commented on 2019-10-09 17:51 (UTC)

@ruabmbua Yes I have the same problem. A downgrade to an previous version works for me.

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 .. 52 Next › Last »