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: 1106
Popularity: 6.65
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 .. 42 43 44 45 46 47 48 49 50 51 52 .. 54 Next › Last »

<deleted-account> commented on 2011-11-01 11:36 (UTC)

I've just found how to fix the GLX13 bug with bumblebee. In /usr/bin/minecraft, just change LD_LIBRARY_PATH="/opt/java/jre/lib/i386/:/opt/java/jre/lib/amd64/" to LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/java/jre/lib/i386/:/opt/java/jre/lib/amd64/" and voilà!

<deleted-account> commented on 2011-10-30 22:12 (UTC)

@killermoehre This package just installs the launcher, not the game itself. Which means it's not out of date at all. When the full release of 1.9 is out, the game will update itself.

killermoehre commented on 2011-10-30 09:33 (UTC)

Minecraft 1.9 pre 5 is out http://assets.minecraft.net/1_9-pre5/minecraft.jar

<deleted-account> commented on 2011-09-24 19:49 (UTC)

Hi! I know my machine is a bit outdated, but I think it could handle Minecraft. Although, I'm having some problems here. Perhaps someone here can have some insight of what happening here... All I get when I try to run it, is a black (window) screen after the download. In my terminal I see some reports: http://www.dpaste.de/NJVOn/ I'm using the opensource ATI drivers (Radeon X1200 Series, junk right? I know... =/ Perhaps the culprit of the problem.) with openjdk. I have tested with jdk and got about the same results... Thanks in advance!

<deleted-account> commented on 2011-09-24 16:56 (UTC)

1.8 or most likely 1.9prerelease now works on proprietary ati drivers. Running at average of 90fps of 6850. But sometimes the keys stick and you walk keep walking.

<deleted-account> commented on 2011-09-16 03:01 (UTC)

Would you consider adding "-server" to the java options in /usr/bin/minecraft? It doesn't seem to affect anything negatively, and I get a ~10fps performance boost from it here.

canuckkat commented on 2011-09-15 19:40 (UTC)

@VK7HSE I just submitted the bug here: http://getsatisfaction.com/mojang/topics/could_not_choose_glx13_config

JonnyJD commented on 2011-09-13 05:10 (UTC)

Looks like you are correct. There are two completely different files called both "minecraft.jar". Who would think of such a mess.. I don't particularly like it, but thanks for the clarification ;-)

dhaines commented on 2011-09-12 12:43 (UTC)

@JonnyJD: that's not how it works. The PKGBUILD is for the minecraft launcher, which is versioned independently from what you and I think of when we think of minecraft. The launcher keeps minecraft proper up-to-date, and thus it's always "latest." The MD5 only changes when the launcher is updated (last when they added those links on the right hand side). Make sense?

JonnyJD commented on 2011-09-12 12:31 (UTC)

You should include the correct version number in the PKGBUILD. "latest" is not helping and you have to change the md5 for new versions anyways.