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.

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