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.

Great to see the changes to the update mechanism.

I noticed, after looking at the package list, that /usr/bin/minecraft-launcher exists only as a symlink to /opt/minecraft-launcher/minecraft-launcher, and nothing else in in the /opt subdirectory.

In that case I think it'd be better if the minecraft-launcher executable existed immediately in the /usr/bin/ location, without any folders/files under /opt

minecraft-launcher /opt/
minecraft-launcher /opt/minecraft-launcher/
minecraft-launcher /opt/minecraft-launcher/minecraft-launcher
minecraft-launcher /usr/
minecraft-launcher /usr/bin/
minecraft-launcher /usr/bin/minecraft-launcher

Can't update your package? Yeah, i couldn't either, so here's the fix: Edit your PKGBUILD file and change these lines: pkgver=2.2.2159 ; source=( https://launcher.mojang.com/download/Minecraft.tar.gz minecraft-launcher.desktop https://launcher.mojang.com/download/minecraft-launcher.svg ) ; sha256sums=( 'a7d75ef47c8e940a56c8fad0c9a68f41df8d5df85df18377c53e3da5749c645c' '677e2442a1ae83cc58d8d403666e508129e97dbed37fdfafdceac6101dc0dee7' '35c2bcaeb09fa4b8864e9422fd66bf60847706f8b4400ec4a66ba6436b101f71' )

Jumor, l'autre y faisait trop le BG genre "oui merci d'avoir appelé la hotline des paquets dupliqués, votre message à été envoyé à la poubelle avec succès", maintenant son vieux package en double qui servait à rien s'est fait supprimer, fallais écouter, cheh

Thank you for holding. Your call is important to us. Please continue to hold and the next available agent will answer your call.

Ptdr

To address the claims in the comments: the AUR guidelines specifically mention there should be no duplicate AUR packages either - not just repo duplicates. One package is a .deb, another a .tar of the same software - that's a clear duplicate. Besides that's having a debian-specific binary available when there's a generic one is hardly useful (another criterion for AUR submission). Merging this to minecraft-launcher.

thanks @Vinnie_PT

To get the latest version, change the following lines in your PKGBUILD file: pkgver=2.2.1867 ; sha256sums=( '5e19e3459015fb28bc54df588b6613320281d953bc2f394a28a95465637eeabe' '677e2442a1ae83cc58d8d403666e508129e97dbed37fdfafdceac6101dc0dee7' '35c2bcaeb09fa4b8864e9422fd66bf60847706f8b4400ec4a66ba6436b101f71' )

Why this is marked as out of date?

@AirportJake No problems here with jdk11 (Although Launcher is an Electron App and doesn't need Java to run)

I would like to report a bug that I have not seen reported yet.

When trying to open the launcher from the command line, it hangs with no output on the command line and only shows as an open process with no open GUI window. I tried both official Java 8 and OpenJDK Java 8 to no avail. The only solution was to download MultiMC. I believe this Reddit user is encountering the same bug. reddit.com/r/archlinux/comments/jvi67j/minecraft_launcher_doesnt_launch/

I am running a NVIDIA 1070 with java-8-openjdk as default java.

Is GTK2 still required as a dependency? I tried building the package w/o it and it builds and runs flawlessly (or so it seems).