Package Details: minecraft-launcher 1:2.1.3-2

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: 1106
Popularity: 6.51
First Submitted: 2017-01-18 14:17 (UTC)
Last Updated: 2025-03-22 14:57 (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 .. 25 26 27 28 29 30 31 32 33 34 35 .. 54 Next › Last »

erkexzcx commented on 2018-07-15 22:29 (UTC)

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.

jpegxguy commented on 2018-07-06 17:24 (UTC)

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

petr commented on 2018-07-06 16:15 (UTC)

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

petr commented on 2018-07-03 18:47 (UTC)

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.

Tank116 commented on 2018-07-03 15:29 (UTC)

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

petr commented on 2018-06-30 19:35 (UTC)

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

mattsturgeon commented on 2018-06-30 19:28 (UTC)

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

petr commented on 2018-06-30 19:26 (UTC)

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.

mattsturgeon commented on 2018-06-30 17:12 (UTC)

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.

smorky commented on 2018-06-30 16:07 (UTC)

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

« First ‹ Previous 1 .. 25 26 27 28 29 30 31 32 33 34 35 .. 54 Next › Last »