Package Details: minecraft-launcher 1:2.1.3-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: 1105
Popularity: 5.64
First Submitted: 2017-01-18 14:17 (UTC)
Last Updated: 2025-04-19 12:06 (UTC)

Pinned Comments

wheat32 commented on 2025-03-08 18:32 (UTC) (edited on 2025-03-08 19:30 (UTC) by wheat32)

I seem to be having a different issue than what others are describing. Suddenly today, I an unable to start the launcher without getting a generic "An unexpected issue occurred" message. Here's what I get in the terminal:

$ minecraft-launcher
sh: line 1: orca: command not found
Created browser window for reuse: 0x1600004
[34399:34552:0308/133050.212343:ERROR:mime_util_xdg.cc(137)] Invalid mime.cache file does not contain null prior to ALIAS_LIST_OFFSET=44
[34399:34552:0308/133055.416488:ERROR:cast_crl.cc(443)] CRL - Verification failed.

Edit: I found that deleting the webcache2 directory in the .minecraft directory fixes the issue for me.

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 .. 21 22 23 24 25 26 27 28 29 30 31 .. 54 Next › Last »

toluschr commented on 2019-08-23 11:44 (UTC) (edited on 2019-08-23 12:35 (UTC) by toluschr)

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.

settyness commented on 2019-08-23 11:08 (UTC)

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

Hoid commented on 2019-08-20 09:42 (UTC)

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

ywecur commented on 2019-08-12 00:06 (UTC)

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)

jpegxguy commented on 2019-08-11 18:48 (UTC)

@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

jpegxguy commented on 2019-08-11 18:46 (UTC)

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

cjmick commented on 2019-08-04 05:24 (UTC)

@rezystor, nope not working for me :( bummer

rezystor commented on 2019-08-03 19:08 (UTC)

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