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.
Search Criteria
Package Details: minecraft-launcher 1:2.1.3-3
Package Actions
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) |
Dependencies (7)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR)
- libgpg-error (libgpg-error-gitAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat)
- flite (flite1AUR) (optional) – narrator support
- orca (orca-gitAUR) (optional) – screen reader support
- org.freedesktop.secrets (gnome-keyring-gitAUR, pass-secrets-gitAUR, keepassxc-allow-aur-extension-originAUR, keepassxc-allow-aur-extension-origin-binAUR, bitw-gitAUR, keepassxc-qt6AUR, pass-secret-service-binAUR, keepassxc-gitAUR, pass-secret-service-gitAUR, dssdAUR, gnome-keyring, keepassxc, kwallet, kwallet5) (optional) – persistent login support
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 54 Next › Last »
ajigsawnhalo commented on 2019-02-19 08:15 (UTC)
iriyto commented on 2019-02-19 06:13 (UTC)
ERROR: One or more files did not pass validity checks
mattsturgeon commented on 2019-02-06 20:19 (UTC) (edited on 2019-02-06 20:21 (UTC) by mattsturgeon)
@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.
jpegxguy commented on 2019-02-06 19:19 (UTC)
@petr Why not java-runtime>=8
?
Thaodan commented on 2019-01-19 17:11 (UTC)
Any reason installing it into opt? Also the launcher doesn't scales on highdpi.
petr commented on 2018-12-20 09:56 (UTC) (edited on 2018-12-20 09:57 (UTC) by petr)
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.
lexikiq commented on 2018-12-17 22:09 (UTC)
@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."
theaifam5 commented on 2018-12-17 22:02 (UTC)
@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.
petr commented on 2018-12-07 12:16 (UTC)
Done :)
thisischrys commented on 2018-12-06 14:25 (UTC)
Please add flite as an optional dependency (for the narrator)
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:
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.