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.

Hmmm, after installing, I run minecraft from the terminal.

Launcher pops up, attempts to download update files (small dialog with progress bar) but disappears shortly afterwards.

$ minecraft-launcher 
https://launchermeta.mojang.com/v1/products/launcher/6f083b80d5e6fabbc4236f81d0d8f8a350c665a9/linux.json
(doesn't show dialog, press Ctrl + C, goes to next line and dialog appears)
^Chttps://launchermeta.mojang.com/v1/products/launcher/6f083b80d5e6fabbc4236f81d0d8f8a350c665a9/linux.json
OK
https://launchermeta.mojang.com/v1/products/launcher/6f083b80d5e6fabbc4236f81d0d8f8a350c665a9/linux.json
(launcher disappears at this point)
https://launchermeta.mojang.com/v1/products/launcher/6f083b80d5e6fabbc4236f81d0d8f8a350c665a9/linux.json
OK
https://launchermeta.mojang.com/v1/products/launcher/6f083b80d5e6fabbc4236f81d0d8f8a350c665a9/linux.json

Process is still running (with no dialog visible), and continues (for atleast 12 hours)

ps -au | grep minecraft
cybex     130202  3.8  0.2 1162716 66896 pts/5   Sl+  05:01   0:06 minecraft-launcher
cybex     130367 17.7  0.1 875252 62972 pts/5    Rl+  05:02   0:14 /home/cybex/.minecraft/launcher/minecraft-launcher --nativeLauncherVersion 928 --chainLoad
cybex     131735  0.0  0.0   6672  2596 pts/6    S+   05:04   0:00 grep --color=auto minecraft

Running on Java 8 (originally had java-18, no go)

java -version
openjdk version "1.8.0_332"
OpenJDK Runtime Environment (build 1.8.0_332-b04)
OpenJDK 64-Bit Server VM (build 25.332-b04, mixed mode)

System setup

 Kernel: x86_64 Linux 5.17.3-arch1-1
 Shell: bash 5.1.16
 DE: GNOME 42.0
 WM: Mutter

@TheK0tYaRa if gnome-keyring were to be added as a package, it should be added as an optional dep as not every uses GNOME keyring. Furthermore, kwallet is soon to get the Freedesktop Secrets API support, which is what the minecraft launcher.

You can try out kwallet with this support with the aur package kwallet-secrets, which applies the patch from the Freedesktop API pull request, and following the instructions in the pinned comments.

Basically, you first install kwallet-secrets Then, you restart your system (or KDE, making sure the kwallet binary gets killed) Thirdly, you open up Kwalletmanager on KDE and make sure you already have a wallet named kdewallet Then you run the following command

gdbus call --session --dest org.freedesktop.secrets --object-path /org/freedesktop/secrets --method org.freedesktop.DBus.Properties.Get org.freedesktop.Secret.Service Collections

And you should get something like

hurricane@TheCloutPC ~ $ gdbus call --session --dest org.freedesktop.secrets --object-path /org/freedesktop/secrets --method org.freedesktop.DBus.Properties.Get org.freedesktop.Secret.Service Collections
(<[objectpath '/org/freedesktop/secrets/collection/kdewallet']>,)

From this, you will take the wallet name after `collection, and then do

gdbus call --session --dest org.freedesktop.secrets --object-path /org/freedesktop/secrets --method org.freedesktop.Secret.Service.SetAlias default /org/freedesktop/secrets/collection/kdewallet

Then restart your system (or kwallet) for good measure

Then, now finally, you should be set to go

The package is lacking a gnome-keyring dependency according to their own article: https://help.minecraft.net/hc/en-us/articles/4408668374925-Secure-Token-Storage-Failure-on-Linux

If the launcher isn't remembering your microsoft account, installing chromium fixed it for me.

As a solution for this bug https://bugs.mojang.com/browse/MCL-18924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&showAll=true that prevents Minecraft from saving your Microsoft Account credentials, forcing you to login every time you open the game, you need to install gnome-keyring and if you're not using a GTK environment like KDE you need to follow this steps: https://wiki.archlinux.org/title/GNOME/Keyring#--start_step

It should be nice if gnome-keyring could be added as a optional dependency with a warning about this issue.

If you guys need a keyring manager on KDE that works with this, install kwallet-secrets, and follow the instructions in comments.

It is kwallet patched the freedesktop secrets API support.

@jextrevor I ran into that as well. In my case it was caused by launching Sway through dbus-run-session.

I figured out that was the problem by looking at an environment variable (I think it was DBUS_SESSION_BUS_ADDRESS).

After installing gnome-keyring, the launcher takes several minutes to load at first and then hangs again when trying to log in (tried several times, waiting several minutes each time, and never got it to finish). I don't know what's going on. Removing gnome-keyring makes it load fast again.

@logothete What if you launch it this way?

$ LC_ALL=C minecraft-launcher

@timo_capa @jpegxguy Yeah, I rebuilt the package without java-runtime as dependency and purged all Java from my system. The game behaves as if nothing happened.

Honestly, even though I use my system java and not the bundled one for the game, it is true that the launcher shouldn't need it, right? I think timo_capa is right

Gonna sound weird, but why is java a dependency?

minecraft-launcher doesn't depend on it, and the game itself ships a bundled java version for compatibility reasons

@kamilst96 Thanks for the reply. Unfortunately, that binary executes with error:

terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_M_construct null not valid

which seems to be the same as what's going on with the installed version as well.

Any theories as to what may be missing?

@logothete Launch this binary from terminal: https://launcher.mojang.com/v1/objects/ce9e6169550628003e22de8086e9fe1186c2285e/minecraft-launcher

I blindly rebuilt arch installation and tried this launcher directly (1035), via AUR (928), and via my own PKGBUILD (1035). All of them worked with KDE / GNOME on X11, so you've done something specific in your install, or maybe forgot something.

Installation either through yay or through downloading and using makepkg leaves me with a launcher that won't launch at all, and gives no GUI indication of failure either. However, looking at my logs, I see the rather large:

Process 30502 (minecraft-launc) of user 1000 dumped core.

(a hundred odd lines of modules; not particularly relevant) Stack trace of thread 30502:

0 0x00007fec63f83d22 raise (libc.so.6 + 0x3cd22)

1 0x00007fec63f6d862 abort (libc.so.6 + 0x26862)

2 0x00007fec6430d802 _ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6 + 0x99802)

3 0x00007fec64319c8a _ZN10__cxxabiv111__terminateEPFvvE (libstdc++.so.6 + 0xa5c8a)

4 0x00007fec64319cf7 _ZSt9terminatev (libstdc++.so.6 + 0xa5cf7)

5 0x00007fec64319f8e __cxa_throw (libstdc++.so.6 + 0xa5f8e)

6 0x00007fec6431036c _ZSt19__throw_logic_errorPKc (libstdc++.so.6 + 0x9c36c)

7 0x00000000004cd43a n/a (minecraft-launcher + 0xcd43a)

8 0x000000000043f0de n/a (minecraft-launcher + 0x3f0de)

9 0x0000000000410b56 n/a (minecraft-launcher + 0x10b56)

10 0x000000000041db10 n/a (minecraft-launcher + 0x1db10)

11 0x000000000040958c n/a (minecraft-launcher + 0x958c)

12 0x00007fec63f6eb25 __libc_start_main (libc.so.6 + 0x27b25)

13 0x000000000040ccf9 n/a (minecraft-launcher + 0xccf9)

Stack trace of thread 30504:

0 0x00007fec64d9a8ca __futex_abstimed_wait_common64 (libpthread.so.0 + 0x158ca)

1 0x00007fec64d94574 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf574)

2 0x0000000000470689 n/a (minecraft-launcher + 0x70689)

3 0x00007fec64347782 execute_native_thread_routine_compat (libstdc++.so.6 + 0xd3782)

4 0x00007fec64d8e259 start_thread (libpthread.so.0 + 0x9259)

5 0x00007fec640455e3 __clone (libc.so.6 + 0xfe5e3)

ELF object binary architecture: AMD x86-64

Sorry for how much text that is. Anyone have any ideas for what's the matter here? Arch install is relatively fresh, maybe a week or so old, with no real problems.

Bootstrap version 1035 is available, released 20210916, but it's not available as tar.gz.

Maybe you could follow Gentoo repo which tracks Mojang launcher meta.

Here's an example commit of what I mean: GitHub

For people having issues needing to log into Microsoft every time, this solution from the wiki solved it for me: https://wiki.archlinux.org/title/GNOME/Keyring#--start_step

You have to have gnome-keyring installed.

@nebulon download the tar.go in the source and then download the launcher from the official site. You’ll see that they are identical

@HurricanePootis I would agree with the flagging as explained in the flag comment: https://aur.archlinux.org/pkgbase/minecraft-launcher/flag-comment/

@Philanche This package isn't out of date, nor is the reason you stated correct. This package is a launcher for a tool that downloads that actual client that we run on our computer, so stating that the client is out of date is incorrect. Checking the version on my own client, I can see that this "out of date" package has me running the latest version of the client available.

+1 for adding gnome-keyring as dep/optdep

Why does the launcher create a "Downloads" directory in my home directory every time I launch it?

I think the problem is somewhere else. On Windows PC im loggin to my ms account every time when i start the session (login prompt). From this point every app which using ms account is already logged in automatically, including Minecraft. The problem wasn't there before they start migration to ms from mojang

I think you guys missin the point. Even on Gnome with keyring configured correctly, I need to login to ms account every time i reboot PC. When i login to ms account first time, then i can get back to it as many time as i want and i won't be asking for password as long im still on the same sassion. As soon i logout from account and login again, it ask for ms password ;-)

@funnyprun that is wrong. As many have said in the thread (and I have now confirmed myself), the problem with Microsoft login is that it is missing gnome-keyring. gnome-keyring may probably be one of the dependencies of chromium (I don't use chromium so I don't know) so when you have chromium installed that is why it works for you. The maintainer should probably add gnome-keyring as a dependency yeah.

I have found out what is wrong with the Microsoft login. It seems to have a dependency on chromium. I can only successfully load the login page when I have chromium installed. Therefore, we should explicitly list chromium as a dependency.

kode54, Who says im not using gnome? It is on gnome indead and the keyring is storing the keys except the one for the launcher

@pemergency As mentioned numerous times by people who want it added to the dependencies, it requires gnome-keyring to store your login credentials. This doesn't change if you're not using Gnome.

Is there any way to prevent launcher asking for microsoft password every tiime i reboot the system ?

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?

@Alchemistic: Why is that necessary? Anyone who has followed the Arch install guide should have their locale properly configured anyway.

If the launcher isn't opening, check the locale (type locale in terminal). If the output has these two lines: locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ...

Open the terminal and run this: export LC_ALL="en_US.UTF-8"

Second that, now gnome-keyring is required to auto-login. See https://help.minecraft.net/hc/en-us/articles/4408668374925

gnome-keyring should be added as a dependency as it is required for Microsoft accounts to save a security token.

@alfrednewman https://help.minecraft.net/hc/en-us/articles/4408668374925

I have to keep logging into the Microsoft account with the Minecraft launcher. Any way to fix this so it keeps me logged in?

@clebermatheus this package is no longer outdated

@bryiewes Thank you! Got it working again. The outdated version number & lack of votes led me onto the wrong path it seems.

@DarkThoughts use multimc-bin then. It's officially maintained and fully allows msa

@bryiewes I don't have an update button on the launcher. I use 0.16.13, which is the latest build of that AUR package. The "Add Microsoft" button is greyed out and I can only add Mojang accounts.

@DarkThoughts MultiMC has an update button on the launcher itself. Please update your launcher or go to multimc.org. fun fact peterix, the creator of mmc, is Petr. He works at Mojang.

@bryiewes I use https://aur.archlinux.org/packages/multimc5, which does not have an update button. And I usually do not use the official launcher, since it was not working at all unless I'd use that command, as stated in the bug report that I've linked.

@DarkThoughts MultiMC supports msa now. Update using the update button in mmc. Also you seriously launch minecraft-launcher with that command EVERY TIME?

Is there a way to launch this without having to "LC_ALL=C minecraft-launcher" through the konsole all the time? I unfortunately migrated my account, realizing that MultiMC isn't actually working with them yet, and the official launcher is not working properly for months now. https://bugs.mojang.com/browse/MCL-17531

Edit: And of course the official launcher doesn't take the Microsoft credentials either… Fucking great.

Maybe they were confused by the "928-1" version number of the PKGBUILD. Which also happens to be the version or build number used for the actual package download.

@bryiewes, yes, as far as I can tell, it is up to date.

2.2.3963 is the same version installed, listed on the Minecraft Wiki, and referenced as the current version in the out of date comment.

https://i.imgur.com/LiTTUoi.png

@xgjmibzr so is minecraft-launcher up to date?

@clebermatheus why'd you mark this out of date?

Installed version per this package:

2.2.3963

Tuesday, July 27, 2021, 12:32:41 PM

which is the same version you referenced in your outdated comment.

I wonder, should gnome-keyring be an optional dependency then?

I guess this is a good idea :-)

How about using kwallet?

kwallet was already installed but was apparently not used by the launcher, however i did not further investigate this

One more thing: The launcher saved the password in the 'default' keyring, the login manager (SDDM in my case) did only unlock a keyring named 'login' (if user login and keyring password are the same). I used seahorse to set the 'login' keyring as the default one and now the keyring is automatically unlocked and minecraft-launcher does not ask for a password anymore.

I wonder, should gnome-keyring be an optional dependency then?

How about using kwallet?

@ckuiper: thanks, that was the solution (installed gnome-keyring (even under KDE) and it saved the password)

I think secrets are now stored in a keyring now? So might need to set a keyring up for remember me to work.

"..my minecraft password isn't saved, I have to re-enter it everytime.."

I have the same issue, have to re-enter the password every time i start the launcher. Reinstalling and deleting the ~/.minecraft folder didn't help

Hello, my minecraft password isn't saved, I have to re-enter it everytime... Thanks in advance for any help, my discord is Bananasmoothii#1111

Minecraft refuses to boot up and nothing comes on screen ever since the launcher was updated.

Crashes on me on launch recently. https://bugs.mojang.com/browse/MCL-17531

Launcher requires libstdc++5 to show installer, as per bug ticket https://bugs.mojang.com/browse/MCL-18214

After doing pacman -S libstdc++5 the launcher shows the Minecraft installer.

jdk 16 you mean, and unfortunately official arch openjdk is still stuck on 15

Using jre from aur right now

Could also use the built in one which I think the launcher downloads automatically

EDIT: official openjdk is on 16 now, yay

Do note that 1.17 and above requires openjdk 16, not 8

Since arch is a shared lib distro, I don't particularly appreciate programs bundling libraries, especially the whole JRE. It feels unclean to me.

I know there are advantage, like easier dependency management and also that disk space is cheap(er) now but it still feels wrong to me.

I think the recent version of this launcher are on par with the Windows version when it comes to downloading a bundled JRE, which is probably what Leafeon is talking about. Personally I don't like it, but I see the convenience for users.

I like to use my system JRE and will manually use system JRE 8 if needed (not neeeded right now), would be interesting if there was a way to block the JRE download in the launcher

While it's nice that the package doesn't force you to use a specific JRE, it can be a double edged sword. Seeing as various versions of Minecraft use different Java versions - and many modded/legacy versions require specific Java versions (anything using launchwrapper needs JRE 8 specifically) - this leads to having multiple java versions installed and having to manually select the correct java executable for each instance in the launcher.

On windows, the launcher will download the appropriate JRE for the Minecraft version selected and default to using it.

How will this behave on Linux going forward? For example if a user wishes to play a legacy version, 1.12 forge, and 1.17 will they be prompted to install the required JREs? Warned if they aren't using the recommended JRE version? Will the launcher default to the recommend JRE version if one is found installed or will this require manual configuration on a per profile basis?

Since the aur package doesn't force a specific jre version, then you can use an autoupdating (though pacman) jre package

As of Minecraft 1.17 (unreleased as of this time), Minecraft: Java Edition for windows will be switching to Java 16.

Are there any plans to mirror these changes on the linux version?

IMPORTANT: IF YOUR LAUNCHER DOES NOT START AFTER THE NEW UPDATE RUN rm ~/.minecraft/launcher -rf in a terminal

@andreymal, yannl35133, same here. I also solved that by removing symlink and creating a normal folder. Turns out that new versions of the launcher do not recognize symlinks for some stupid reason, which results in this weird behaviour.

I have the same problem with ~/.minecraft symlink. Replacing it with a bind mount helps.

My ~/.minecraft is a symlink. It worked well, but now it doesn't and goes in an infinite loop.

Thank you @huantian Removing "$HOME/.minecraft/launcher/" was the solution.

Alright, now it works for some stupid reason

Was able to solve the same issue as @jpegxguy by deleting the .minecraft/launcher/ directory

Same error as @jpegxguy, solved by clearing .minecraft, cd-ing into newly created .minecraft/bin directory and running launcher from there. No errors or infinite loops with this approach

Same here. @jpegxguy that's not a proper solution. I have cleared .minecraft folder and started minecraft-launcher 915-1. After downloading launcher files it closed and, according to the console output, it went into an infinite loop.

UPDATE: Solved! I downgraded to 887-2 and ran it, it updated some core files, then updated to the 917 package again. Now it runs. It seems like you need to have launched the previous version one last time before you go for the package update.

Hi, I just updated to v915 and the launcher immediately closes:

$ minecraft-launcher
[Info: 2021-03-10 16:26:11.677069597: NetQueue.cpp(157)] NetQueue: Setting up.
[Info: 2021-03-10 16:26:11.677328710: NetQueue.cpp(575)] NetQueue: worker thread started.
[Info: 2021-03-10 16:26:11.677577626: mainLinux.cpp(250)] Running launcher bootstrap (version 915)
[Debug: 2021-03-10 16:26:11.679329816: PlatformLinux.cpp(44)] HOME dir (getpwuid): /home/leo
[Debug: 2021-03-10 16:26:11.679376960: PlatformLinux.cpp(49)] HOME dir (env): /home/leo
[Info: 2021-03-10 16:26:11.687189528: Common.cpp(32)] Native Launcher Version: 915
[Info: 2021-03-10 16:26:11.687295199: Common.cpp(33)] Operating System: Linux
[Info: 2021-03-10 16:26:11.687352539: Common.cpp(34)] Application Data directory: //.../.minecraft
[Info: 2021-03-10 16:26:11.687412114: Common.cpp(35)] Executable Path: /.../minecraft-launcher
[Info: 2021-03-10 16:26:11.687462609: Common.cpp(36)] App Directory dir: //.../bin
[Info: 2021-03-10 16:26:11.687509403: Common.cpp(37)] Game data directory: //.../.minecraft
[Info: 2021-03-10 16:26:11.687556896: Common.cpp(38)] Launcher dir: //.../launcher
[Info: 2021-03-10 16:26:11.687607741: Common.cpp(39)] Java dir: //.../jre-x64
[Info: 2021-03-10 16:26:11.687663125: Common.cpp(40)] TmpDir dir: //.../MinecraftLauncher.1000
[Info: 2021-03-10 16:26:11.687716833: Common.cpp(41)] x64: true
[Info: 2021-03-10 16:26:11.688382216: mainLinux.cpp(308)] relaunchedExe: /home/leo/.minecraft/launcher/minecraft-launcher selfExe: /usr/bin/minecraft-launcher
[Info: 2021-03-10 16:26:11.688445213: mainLinux.cpp(312)] Top level executable, forwarding signals.
[Debug: 2021-03-10 16:26:11.688650338: SentryAPI.cpp(314)] The string '/usr' was added to the logging blacklist
[Debug: 2021-03-10 16:26:11.688708936: SentryAPI.cpp(314)] The string '///usr' was added to the logging blacklist
[Debug: 2021-03-10 16:26:11.688754891: SentryAPI.cpp(314)] The string '/home/leo' was added to the logging blacklist
[Debug: 2021-03-10 16:26:11.688796238: SentryAPI.cpp(314)] The string '///home/leo' was added to the logging blacklist
[Debug: 2021-03-10 16:26:11.688842124: SentryAPI.cpp(314)] The string '/home/leo/.minecraft' was added to the logging blacklist
[Debug: 2021-03-10 16:26:11.688886683: SentryAPI.cpp(314)] The string '///home/leo/.minecraft' was added to the logging blacklist
[Debug: 2021-03-10 16:26:11.688930823: SentryAPI.cpp(314)] The string '/home/leo/.minecraft/runtime' was added to the logging blacklist
[Debug: 2021-03-10 16:26:11.688975312: SentryAPI.cpp(314)] The string '///home/leo/.minecraft/runtime' was added to the logging blacklist
[Debug: 2021-03-10 16:26:11.689054862: SentryAPI.cpp(314)] The string '/tmp' was added to the logging blacklist
[Debug: 2021-03-10 16:26:11.689100259: SentryAPI.cpp(314)] The string '///tmp' was added to the logging blacklist
[Info: 2021-03-10 16:26:11.689137205: Common.cpp(32)] Native Launcher Version: 915
[Info: 2021-03-10 16:26:11.689209072: Common.cpp(33)] Operating System: Linux
[Info: 2021-03-10 16:26:11.689281428: Common.cpp(34)] Application Data directory: .../.minecraft
[Info: 2021-03-10 16:26:11.689366426: Common.cpp(35)] Executable Path: /.../minecraft-launcher
[Info: 2021-03-10 16:26:11.689443461: Common.cpp(36)] App Directory dir: .../bin
[Info: 2021-03-10 16:26:11.689530763: Common.cpp(37)] Game data directory: .../.minecraft
[Info: 2021-03-10 16:26:11.689608986: Common.cpp(38)] Launcher dir: .../.minecraft/launcher
[Info: 2021-03-10 16:26:11.689684625: Common.cpp(39)] Java dir: .../.minecraft/runtime/jre-x64
[Info: 2021-03-10 16:26:11.689762568: Common.cpp(40)] TmpDir dir: .../MinecraftLauncher.1000
[Info: 2021-03-10 16:26:11.689838067: Common.cpp(41)] x64: true
[Info: 2021-03-10 16:26:11.699963515: mainLinux.cpp(416)] Current executable is not in game directory, update and run game directory version
[Info: 2021-03-10 16:26:11.700108088: mainLinux.cpp(430)] Attempting to start the launcher
[Info: 2021-03-10 16:26:11.700159910: mainLinux.cpp(118)] Window closing, exiting process
[Info: 2021-03-10 16:26:11.737875995: mainLinux.cpp(456)] Launcher finished...

Fair enough. It's time to keep only latest java installed as system. It kind of works out for me. I'd like it if you kept the option to change the path to the java binary. It's the best of both worlds, plus, it's under advanced settings for the profile.

The aim is to ship a game and for it to work ideally out of the box with no issues, not make people mess with and have to care about what version their JRE package is, and why it crashes when they add mods.

What's the use of a bundled java runtime on Linux? I already know about the java version situation and it's indeed important that a version of JRE 8 is provided, since it has the best compatibility. Why not use the system one though?

@petr Thank you for the bug link! Forcing it on the intel workarounds it. :)

@jpegxguy fair. That can be fixed easily :)

Well, we now have a bootstrap on Linux, similar to what the other platforms had for years.

That means the launcher updates itself, and you can switch between release/beta from inside of it.

We also updated the CEF (chromium embedded framework) to a version that isn't from 2016... And that may affect a few things. So please file bugs on https://bugs.mojang.com/ when you see them. The sooner, the better.

The other major change is the launcher installing a JRE for you. While that's nice, we also need the dependencies for a JRE, and that's why I'm keeping the java-runtime dependency. Not for actually using a java runtime from the system, but to get all of the dependencies for one from the system so our bundled one can work.

@MartinX3 are you using a switchable/dual graphics setup? This may be related: https://bugs.mojang.com/browse/MCL-17125

Now the screen of the launcher is just black.

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

Oh and the PKGBUILD.template file can be removed from the git since it isn't used.

The .gitignore can be updated to ignore packaged files so that users that don't use an AUR manager don't get conflicts when updating.

The change is just one line: https://git.sr.ht/~iruoy/minecraft-launcher/commit/9d378b6232299f083304518719256f266f12ad33

2.2.909 is out https://minecraft.gamepedia.com/Launcher_version_history

only thing currently working for me is using AppImage from here: https://github.com/ChristopherHX/linux-packaging-scripts/releases

@WBryie

that did it, thank you very much!

Please update minecraft-launcher to the current launcher version, I have a github repo with everything, however pkgbuild is in my name and the .git folder isnt there.

https://github.com/RealThisNoobCoder/minecraft-launcher

@xdotax please use minecraft-launcher and not minecraft, the sha256 sums for minecraft are broken and should not be used.

I get the same error for this package as minecraft-launcher:

==> Validating source files with sha256sums... minecraft-2.2.741.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build minecraft

Any help please? Referencing the pinned comment, I get this output from updpkgsums:

==> ERROR: PKGBUILD not found or is not a file

ok, I set pkgver=2.2.909 and the sha256sums provided by Vinnie_PT

I am still getting the error:

==> Retrieving sources... -> Found minecraft-2.2.909.deb ==> ERROR: Integrity checks (sha256) differ in size from the source array.

To say more: only a name clash between official repo and AUR package is formally forbidden. So if there will be some minecraft in Arch repo, we may still provide some minecraft-deb or other implementation. The package has the right to exist even if it has at least one user.

You mistake me for someone else. I maintain a lot of packages in Arch User Repositor, this package is just one of them and it doesn't break any rules. This is the free software community, we are not a branch of M$ or whatever other company. If some package is promoted as an 'official' way to install a game, we appreciate it. But until there will be an official package in one of official Arch repo's this implementation or any different one has the right to exist.

What's your problem? You're maintaining a copy of an already existing package, why continuing?

@bkb

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

Minecraft-launcher was recognized as an official package for Arch by Microsoft

The launcher was chosen over the game itself

So unless your package is meant as a plug-in, a child of Minecraft-launcher to install Minecraft in the launcher, so unless Minecraft-launcher becomes a dependency of your package, you should delete this package

And if you want the Deb to be used in the launcher package, discuss with the maintainer

To get the latest version change the following lines in your PKGBUILD

pkgver=2.2.909

sha256sums=( '02e6067790bb65b2f0229ae297806bbdc77d1d1934f8a49d5ca21286728da297' '677e2442a1ae83cc58d8d403666e508129e97dbed37fdfafdceac6101dc0dee7' '35c2bcaeb09fa4b8864e9422fd66bf60847706f8b4400ec4a66ba6436b101f71' )

@randyzhu

Breaking news :)

I saw mention of this package on official site half a year ago.

This AUR package is now officially recognized as the Minecraft download for Arch!

@shoghicp @petr I think it should be renamed Mojang Launcher and that Minecraft should be deleted to only let this launcher on the repository

It's the same problem on Lutris with Epic/Rockstar/Steam... Games Launcher

Theres some entries for the launcher and some entries for the games directly

Can you update the SHA256Sum in the PKGBUILD?

Is minecraft the same as minecraft-launcher now?

Yeah, it feels like the beta should be providing this, the other way around.

The package should provide minecraft-launcher, not minecraft-launcher-beta, right? Anyway, it would be a probably irrelevant mistake

The package was flagged out-of-date by mistake, I guess. It is currently up to date.

Choose which one to delete

                                   minecraft
https://aur.archlinux.org/packages/                  /
                                   minecraft-launcher

https://launcher.mojang.com/download/linux/x86_64/minecraft-launcher_*.tar.gz

VS

https://launcher.mojang.com/download/Minecraft.deb

Choose which one to delete

                                   minecraft
https://aur.archlinux.org/packages/                  /
                                   minecraft-launcher

https://launcher.mojang.com/download/linux/x86_64/minecraft-launcher_*.tar.gz

VS

https://launcher.mojang.com/download/Minecraft.deb

Yeah. I'm changing up the automation so we can work on the PKGBUILDs manually and something went a little weird with the pkgrel handling. Fix incoming.

minecraft-launcher is newer than aur? huh?

minecraft-launcher: local (2.1.16102-2) is newer than AUR (2.1.16102-1)

from yay. ????

This package doesn't need the obsolete gconf

EDIT: Thanks for this.

I was able to force java8 by setting the JAVA_HOME variable. I suggest having this script for /usr/bin/minecraft-launcher and having minecraft-launcher.desktop have Exec=minecraft-launcher

#!/bin/sh
export JAVA_HOME="/usr/lib/jvm/java-8-openjdk/jre/"
exec /opt/minecraft-launcher/minecraft-launcher "$@"

This would require java-runtime=8 or specifically jre8-openjdk

does this actually need gconf? if it does, that's okay, but a comment on that package says that chromium and electron havent depended on it for years, and its a bit annoying having to need it because it is also an aur pakage

@kashall

Package is out of date, Mojang has released a new version on their website but this package uses the static version of the old launcher. We actually use an unversioned link to the latest available deb package. I did a clean build and I didn't saw any checksum errors and version of the launcher is the same.

I don't really get the dependency list:

• gconf? (From a comment in the gconf package: "Chromium (and subsequently Electron) haven’t been dependent on this for years" - that, plus it's apparently obsolete)
• libxss? (X11 Screen Saver extension library)

Frankly I don't really know, just find it weird

Both the minecraft and minecraft-launcher packages are broken for me. When running them there are no errors in the console, then the window just doesn't open and the process is at 100% on one of my cpu cores.

The launcher_log.txt doesn't give any information either.

@milk package is just updated

Getting a sha256sum error with 2.1.14930-1 as well

I'm slowly working on getting the updating of both minecraft-launcher and minecraft-launcher-beta automated, and hooked up to our CI/CD setup.

So, Soon:TM:, that part of maintenance shouldn't need manual action.

I just want to point out again that this package was flagged out of date well before a new launcher version was actually released. The launcher will probably still report a new version when a new beta is available.

Updated, Minecraft Launcher just released a new version with few bug fixes:

Put these in your PKGBUILD to get new version until @petr decide to update it.

pkgver=2.1.14403

Sha256Sum:

2f888fb423133c48c987408581ff0bddfb8eb79115c9796ccc1c28167146cc20

Those who are bothered by the new version notification, here is actual "recent" version (from tar.gz file download from Minecraft website: https://www.minecraft.net/en-us/download/ & running launcher using ./minecraft-launcher file after extracting.)

pkgver=2.1.13829

in sha256 sum, replace the first hash with this: e525c31bd6bacb7483929a674a5c8515a8ebb1b3f67ffd018f6f12a84f4e7051

Edit: Release Notes https://imgur.com/t99QJAy

@petr you might want to update this. This package has been flagged out of date for long time now.

Hm, it is out of date for a while and it is one of the most popular packages in the AUR. Is there anything we can do petr? Could you update it soon?

@alx365 @prismavoid08 I fixed this problem by setting "Raw Input" in Options -> Controls -> Mouse Settings to OFF (in the Minecraft settings). Maybe this will help you!

@sim590 i have the same issue of the player just turning around randomly on manjaro

Can we really be blamed though for this?

Also can't pass the sha256sums validity check.

Also getting sha256sum validation failure.

...here we go again. For whatever reason, the release of certain launchers, listed as beta on the official wiki, continue to trigger "new version available" prompts. This seems to make minecraft-launcher-beta redundant.

Either way, this is what's causing users to perpetually flag this package out of date.

hi, files are not passing sha256sum validation

==> Validating source files with sha256sums...
    Minecraft.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: minecraft

PRs are welcome here: https://github.com/yurikoles-aur/minecraft

Unfortunately the deb file is being updated in place and I can't find a link to versioned deb file, so bad checksum means that package was updated. In case you want to solve checksum error yourself just run updpkgsums from community/pacman-contrib.

For anyone having issues with skins tab. just link required libraries to directory where launcher is looking for

sudo mkdir -p /opt/minecraft-launcher/swiftshader
sudo ln -s /lib64/libEGL.so /opt/minecraft-launcher/swiftshader/libEGL.so
sudo ln -s /lib64/libGLESv2.so /opt/minecraft-launcher/swiftshader/libGLESv2.so

SKins are not working. The app says that the system doesn't support WebGL.

I downloaded this launcher for Arch, but I am having the problem that every few seconds the player will turn instantly and be facing in a random direction, basically making the game unplayable. I had the same problem recently in Manjaro and I'm not sure how to fix it.

It seems the launcher requires gconf, which is obsolete and not available in the main Arch repo, to run at all. I tried to remove the dependency from the PKGBUILD but it wouldn't run before installing gconf from AUR.

For anyone who want to use this launcher, it work great up to the 1.14.3. But if you try to play in 1.14.4 or higher than that it wont work.

When i try to execute the launcher in terminal this is what i get :

minecraft-launcher 
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_M_construct null not valid
[1]    11433 abort (core dumped)  minecraft-launcher

@milaskiller Try installing it using the official method. Open a terminal and type:

git clone https://aur.archlinux.org/minecraft-launcher.git
cd minecraft-launcher
makepkg -si

If any errors occur during this process, we are more likely to help you.

hi could anyone help me. i keep having this problem where it cant find the tatget. then it refrenses where the tar.gz file is. https://imgur.com/02TsSBs.png

@petr Maybe you need to change the code looking up the libraries?

chenjunyu19@chenjunyu19-Linux ~> pacman -Q libglvnd 
libglvnd 1.3.1-1
chenjunyu19@chenjunyu19-Linux ~> minecraft-launcher
[0320/141519.497430:ERROR:gl_implementation.cc(241)] Failed to load /opt/minecraft-launcher/swiftshader/libGLESv2.so: /opt/minecraft-launcher/swiftshader/libGLESv2.so: 无法打开共享对象文件: 没有那个文件或目录
[0320/141519.500106:ERROR:gpu_child_thread.cc(254)] Exiting GPU process due to errors during initialization
[0320/141519.893732:ERROR:gl_implementation.cc(241)] Failed to load /opt/minecraft-launcher/swiftshader/libGLESv2.so: /opt/minecraft-launcher/swiftshader/libGLESv2.so: 无法打开共享对象文件: 没有那个文件或目录
[0320/141519.895469:ERROR:gpu_child_thread.cc(254)] Exiting GPU process due to errors during initialization
[0320/141520.309888:ERROR:gl_implementation.cc(241)] Failed to load /opt/minecraft-launcher/swiftshader/libGLESv2.so: /opt/minecraft-launcher/swiftshader/libGLESv2.so: 无法打开共享对象文件: 没有那个文件或目录
[0320/141520.311888:ERROR:gpu_child_thread.cc(254)] Exiting GPU process due to errors during initialization
[0320/141520.711561:ERROR:gl_implementation.cc(241)] Failed to load /opt/minecraft-launcher/swiftshader/libGLESv2.so: /opt/minecraft-launcher/swiftshader/libGLESv2.so: 无法打开共享对象文件: 没有那个文件或目录
[0320/141520.713662:ERROR:gpu_child_thread.cc(254)] Exiting GPU process due to errors during initialization

Updated to current release.

RE skins not working: It works for me without any of the symlinking/copying. Are you sure that's necessary? Or is just adding libglvnd as a dependency enough?

Hm, it is a popular packet and out of date for quite some time. :(

It would be very cool if you implemented the changes suggested by @chenjunyu19 into the PKGBUILD.

The latest version is now 2.1.2464. Change your PKGBUILD variables as follows: pkgver=2.1.12464 Change the first sha256sum to: 63bc6f0b8f8a387f7f49da8f75466502ef226777221e877e9c842b1a76702fcd

Accidentally deleted my previous comment. Basically said that that's all we need to do here as well, just the author isn't around to bump the version at the moment. I've emailed him and we'll see if he's able to update it.

Is there a reason we are not just modifying the version, like the GitKraken package https://aur.archlinux.org/packages/gitkraken/ , in the PKGBUILD?

A new version was just pushed. Until the AUR is updated, you can set the pkgver to 2.1.12308.

@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

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.

I just tried running this on Manjaro ARM using openjdk-13, but the following error was generated:

[12:50:42 INFO]: Getting syncinfo for selected version
[12:50:42 INFO]: Queueing library & version downloads
[12:50:42 FATAL]: Unhandled exception in thread Thread[pool-2-thread-2,5,main]
com.google.gson.JsonSyntaxException: duplicate key: null
    at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:191) ~[Minecraft.jar:?]
    at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:146) ~[Minecraft.jar:?]
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:93) ~[Minecraft.jar:?]
    at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:172) ~[Minecraft.jar:?]
    at com.google.gson.Gson.fromJson(Gson.java:795) ~[Minecraft.jar:?]
    at com.google.gson.Gson.fromJson(Gson.java:761) ~[Minecraft.jar:?]
    at com.google.gson.Gson.fromJson(Gson.java:710) ~[Minecraft.jar:?]
    at com.google.gson.Gson.fromJson(Gson.java:682) ~[Minecraft.jar:?]
    at net.minecraft.launcher.updater.RemoteVersionList.getCompleteVersion(RemoteVersionList.java:32) ~[launcher.jar:1.6.89-j]
    at net.minecraft.launcher.updater.MinecraftVersionManager.getLatestCompleteVersion(MinecraftVersionManager.java:213) ~[launcher.jar:1.6.89-j]
    at net.minecraft.launcher.updater.MinecraftVersionManager.getLatestCompleteVersion(MinecraftVersionManager.java:37) ~[launcher.jar:1.6.89-j]
    at com.mojang.launcher.game.runner.AbstractGameRunner.playGame(AbstractGameRunner.java:67) ~[launcher.jar:1.6.89-j]
    at net.minecraft.launcher.game.GameLaunchDispatcher$1.run(GameLaunchDispatcher.java:111) ~[launcher.jar:1.6.89-j]
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
    at java.base/java.lang.Thread.run(Thread.java:830) [?:?]

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.

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

Does not launch any more. Does anyone else have the same problem. I get no errors, the "gnome launcher" shows the icon, but the window does not appear.

Did this finally stop working? It can't download new versions of Minecraft, gets stuck on "Preparing..."

Indeed it shouldn't be out of date. Also the linux launcher should have auto update check disabled because the (undisclosed beta) version pops up every time you open the launcher.

I'm still not seeing why this is even flagged out of date. Latest stable version is 2.1.5965, while beta is 2.1.5969. A user got a message in their launcher and blindly flagged this without verifying (Settings -> About) that this is indeed the latest launcher, released July 23rd: https://minecraft.gamepedia.com/Launcher_2.1.596x . Use beta if you need an update.

this needs to be updated.

@ywecur @Hoid For me the problem was that (in KDE Plasma) I'd selected a language/region combination that's not an installed locale on my system (specifically: en_NL.UTF-8 - english language system with region set to the Netherlands). I think the breakage was introduced with other recent updates. A work-around is to apply another locale when launching Minecraft:

LC_ALL=C minecraft-launcher

You can use any enabled locale instead of C. For those who, like me, picked en_NL in the desktop settings, I've added an AUR package locale-en-nl-git which can help too.

You need to change the permissions for /opt/minecraft-launcher/ in the pkgbuild. The new launcher version requires write permissions for the binaries directory in order to launch.

Is there a reason this is flagged as out of date? I'm not seeing one.

I'm getting the same error @ywecur, it might be an issue with the new update to the launcher as it started happening right after I updated it

I'm getting this error when trying to launch:

terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_M_construct null not valid Aborted (core dumped)

@mattsturgeon if the problem is that users will choose the wrong version when asked (even on arch, sure), make the change in minecraft-launcher-beta only

@mattsturgeon Okay so the reason is that we're worried users who want mods won't know to choose jre8 when pacman will ASKS them about the version they want to install when they downlaod this package? And Arch users, at that? I doubt it.

My point is that with the change to >= from = the package manager would ask you what version upwards of 8 you want. You choose 8. Done. Why do we force this version? LegacyLauncher is not needed for vanilla and is indeed "hacky code to launch old mc versions". Now, mods do use it. So choose jre8 upon install. Where's the negative?

@rezystor, nope not working for me :( bummer

If your game crashes, try installing java8-openjfx, for me it fixed problem with lwjgl.so

I don't understand why it can't be "greater than OR equal"

Legacy launcher requires java "less than or equal to 8" (and also greater than or equal to the minimum compatible version, iirc 5?).

Since version 1.12 Minecraft require 8 as a minimum.

So since 8 is a minimum for Minecraft and a maximum for legacy launcher, it is the only fully compatible version of java right now. Newer versions break legacy launcher, older versions don't support Minecraft.

Even when modlauncher (legacy launcher's replacement in forge 1.13) becomes more commonplace, they'll still be a big proportion of mods using legacy launcher, and mods for older mc versions will likely always use legacy launcher (and always require java=8)

Version 2.1.5410-1 is working alright, thanks a lot.

The version 2.1.5236-1 for me just crashes with a memory access error. I got no Idea why, but it just won't run at all for me. Fresh install on a VM, no luck, same error.

So the only reason for not making it java-runtime>=8 is because users might not actually have jre 8 installed and wonder why mods dont work? I don't like to have an extra version of java just because LegacyLauncher is old and unsupported. I don't understand why it can't be "greater than OR equal". Currently, it is only "equal".

Besides, arch will prompt for a choice of the java version to install, when installing minecraft-launcher for the first time, while having no Java installed.

This package should depend on gtk2 - as without gtk2 installed, the launcher won't start. See https://bugs.archlinux.org/task/59904 for basically the same issue for another package.

If it helps:

diff --git a/PKGBUILD b/PKGBUILD
index 97aa16a..5a80df1 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,6 +1,6 @@
 # Maintainer: Petr Mrázek <petr@mojang.com>
 pkgname=minecraft-launcher
-pkgver=2.1.2472
+pkgver=2.1.2482
 pkgrel=1
 pkgdesc="Official Minecraft Launcher"
 arch=('x86_64')
@@ -16,7 +16,7 @@ minecraft-launcher.desktop
 minecraft-launcher.svg
 )
 sha256sums=(
-'ceab99e810b6e0bdf784d8600e5e01b6730af6103df7a23a406501c2b3bb5741'
+'1a50aa83ab45ad69795e2ea5209cfd8092b5be4592731c4442c5e642279d0f00'
 '677e2442a1ae83cc58d8d403666e508129e97dbed37fdfafdceac6101dc0dee7'
 '35c2bcaeb09fa4b8864e9422fd66bf60847706f8b4400ec4a66ba6436b101f71'
 )

The future plan for this is to turn the main package into a downloader/updater and bring it in line with the other platforms. Please switch to using minecraft-launcher.

I tried manually building the package by changing the pkgver in the PKGBUILD file and it installed but it would only open when run as root.

ERROR: One or more files did not pass validity checks

@jpegxguy that's answered in the pinned message. JRE 1.8 (java-runtime=8) is required for anything using legacy launcher (aka launch wrapper), which is almost all mods and also legacy versions of the game.

Newer JRE versions break stuff that legacy launcher depends on (ABIs).

He did note that there is nothing to stop you having JRE 1.8 in addition to other java versions since they do not conflict.

@petr Why not java-runtime>=8 ?

Any reason installing it into opt? Also the launcher doesn't scales on highdpi.

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.

@TheAifam5 "Some form of Java runtime 8 is a dependency and will remain so until the issues caused by ABI breaks in later versions are resolved in one way or another."

@petr Please, don't force to use specific version of Java. I'm actually thinking to create a fork of this package, to support newer Java version.

Done :)

Please add flite as an optional dependency (for the narrator)

Really wish Mojang would update their darn launcher to support the new JRE.

As for this package, the default behavior for most AUR helpers is to install the newest JRE greater-or-equal than jre8. While these higher JRE packages allow the launcher to work, they do not let you get in game.

So in other words, the game itself still requires a JRE no higher than 8 to work properly past the launcher. Just something to keep in mind.

gconf is a dependency, CEF directly depends on gconf symbols. This is not changing any time soon.

Some form of Java runtime 8 is a dependency and will remain so until the issues caused by ABI breaks in later versions are resolved in one way or another.

This package is fully up-to-date.

Can't we eliminate gconf and other dependencies?

@rafasc It looks like for 1.13 you can still use the old launcher. I've been using it, blissfully unaware that they were planning on dropping support. This allows more time for a decision, I guess.

@BombStrike What about contacting petr about making minecraft-launcher the "meta package"? Then users using that package would be set, with it pulling in this package as a dependency. And this package could continue as the "official" package, as I feel of the two, "minecraft" is a better choice of package name.

Interesting, I always assumed MC was only java 8 compatible, but LegacyLauncher could well be the problem. Worth noting that forge plan on transitioning to a new modlauncher system with 1.13 (and anyone who wants to be forge-compatible will likely have to follow suit) so that may limit the issue to legacy versions and pre-1.13 mods.

@erkexzcx I'm pretty sure both the game and the launcher work fine under jre (version 10), as is my setup. A problem arises in the LegacyLauncher when trying to start stuff like OptiFine though.

@BombStrike I asked around on #archlinux-aur, and also based on what was said in this in this request https://lists.archlinux.org/pipermail/aur-requests/2018-June/024898.html, seems that this package should be updated to the new launcher and the minecraft-launcher should merged as a duplicate.

AFAIK, the old launcher will not be able to launch new versions of the game starting with 1.13, and since the new one is able to launch older versions, there's no reason for the old launcher to exist as a package. (Besides the fact it simply being available on that url which will probably go down in the future).

@jpegxguy It is recommended to run Minecraft with Java 8.

So now that the other launcher has become the official one, here is how I could do things:

• Empty this thing and only have a dependency to minecraft-launcher: making it pretty much a meta-package of sort, would (probably?) be the safest option
• Copy the existing package: not a big fan of duplicating stuff
• Submit a request to have minecraft-launcher renamed to minecraft, and this one to minecraft-legacy: will break people who had minecraft-launcher installed

Let me know what you guys think in the comments, I'll also be doing some research on my side to make sure the updates goes smoothly for you guys.

@BombStrike Minecraft website updated the launcher url.

Updated https://wiki.archlinux.org/index.php/Minecraft - Minecraft client (game) works fine even with java version 10, but the actual launcher starts only with java version 8.

Updated https://wiki.archlinux.org/index.php/Minecraft - Minecraft client (game) works fine even with java version 10, but the actual launcher starts only with java version 8.

Why is java-runtime=8 required? why not >=8 ?

The fix should be in. As long as you don't have something extra in the network doing caching, it should work.

If you are rebuilding in the same directory, delete the file, it should redownload and have the correct checksum.

I'll put in some sort of fix as soon as I get back to a real machine with my SSH keys.

Also reporting in: Minecraft.tar.gz fails sha256 checksum in 2.1.1218-1 update

As for the reusing of filenames, I put that on the TODO pile :)

I haven't attempted to reproduce yet, however it could be a caching issue (either on your end or smorky's).

Hmm... it works for me? On multiple machines?

You'll have to provide more details about what's going wrong, because I just don't see it.

smorky: That's because when mojang update the snapshot, the link doesn't change. That means that the checksum is different so will fail integrity checks.

Ideally, mojang would provide versioned or datestamped links for the snapshots, but AFAIK they don't. Them updating the release build would also work, but iirc the latest release build doesn't even work anymore.

Minecraft.tar.gz fails sha256 checksum in 2.1.1218-1 update.

@BombStrike My apologies. Your response to my request (and recent comment) helped me to understand why things are the way that they are between the two packages.

@BombStrike: I see, my bad!

@Brottweiler The tweet mentioned do not talk about the download link, but about the version file and my package already points to the link requested by Dinnerbone: https://aur.archlinux.org/cgit/aur.git/tree/minecraft?h=minecraft#n11

I flagged the package out of date now because the source URL is still not updated to the new one, which means this package could break randomly at any time when the legacy URL is removed.

I don't see any reason why you should place the new launcher here at all. As there already is a package with the new launcher maintained by Mojang, it would result in having two packages for the same thing, which is just useless.

Missing dependency issue : Permanently resolved

Missing dependency gconf I think.

./launcher: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory

@bda Done

hi, libxss is needed as dependancy: ./launcher: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory

I suspect the underlying problem is that Mojang update their "staging" tar, but do not create versioned release archives. Therefore this package is stuck on the latest (broken) release 2.0.579, while Minecraft_staging.tar.gz stays updated and keeps working.

IMO Mojang need to improve the way they handle this, preferably by creating more releases and keeping this package in sync with them. Otherwise we are forced to use packages such as minecraft-launcher-tar that try to keep in sync with the (fully functional) staging build.

@SuperGeniusZeb I added gconf to the dependencies and updated Minecraft to the latest version. Thank you :)

It's impossible to run this because it depends on a old version of icu.

It's been over a year since the initial linux beta release, and almost half a year since the last update. Any news on an official release?

The source URL needs to be changed, more info here: https://twitter.com/Dinnerbone/status/981978843178323968

You can pin your comment and hopefully then it will stand out so no more out of date flags.

Ok this is still getting flagged as out of date so I'll explain it again:

This package is the official stable package you get when you go through the Minecraft website, which still points to "http://s3.amazonaws.com/Minecraft.Download/launcher/Minecraft.jar"

If you want the new launcher check the https://aur.archlinux.org/packages/minecraft-launcher package that is maintained by Mojang themselves.

And if you want this package to be the new launcher, just ask Mojang why 2.x is not deemed stable yet and if it is if they could update their links on the official website.

I trust that in time I will be able to update this package to the latest launcher but right now it will stay on this version.

Thank you for your understanding.

I tried to run this on a fresh Antergos installation and I got this error:

"./launcher: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory"

This file, which should be located at "/usr/lib/libgconf-2.so.4", is provided by the gconf package, which is not listed as a dependency of this package.

https://www.archlinux.org/packages/extra/x86_64/gconf/

Simply add the gconf package as a dependency and that should fix the problem.

@Leafeon thank you, I added it :)

Please dont force installation of java 8, Minecraft runs very well with java 9 by removing "-XX:+CMSIncrementalMode" from profile startup arguments.

Set it to java-runtime>=8 and leave a comment telling java 9 users about the startup argument.

https://aur.archlinux.org/packages/minecraft/?comments=all

If you're like me and got confused about the linked issue page: it seems the permalink has stopped working. Go to the "All" comments section and read by LightWayUp; basically saying to remove "-XX:+CMSIncrementalMode" from your profile's JVM arguments, also mentioned below.