I flagged the package out of date now because the source URL is still not updated to the new one, which means this package could break randomly at any time when the legacy URL is removed.
Search Criteria
Package Details: minecraft-launcher 1:1.0.1221-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: | 1098 |
| Popularity: | 4.12 |
| First Submitted: | 2017-01-18 14:17 (UTC) |
| Last Updated: | 2024-06-17 22:10 (UTC) |
Dependencies (6)
- 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-compatAUR)
- flite (flite1AUR) (optional) – narrator support
- org.freedesktop.secrets (keepassxc-gitAUR, gnome-keyring-gitAUR, pass-secrets-gitAUR, keepassxc-allow-aur-extension-originAUR, keepassxc-allow-aur-extension-origin-binAUR, pass-secret-service-binAUR, bitw-gitAUR, dssdAUR, gnome-keyring, keepassxc, kwallet, kwallet5) (optional) – persistent login support
Sources (3)
Brottweiler commented on 2018-05-24 19:18 (UTC)
<deleted-account> commented on 2018-05-24 17:51 (UTC)
I don't see any reason why you should place the new launcher here at all. As there already is a package with the new launcher maintained by Mojang, it would result in having two packages for the same thing, which is just useless.
Wascar commented on 2018-05-18 15:44 (UTC)
Missing dependency issue : Permanently resolved
hugoarpin commented on 2018-05-17 14:50 (UTC)
Missing dependency gconf I think.
./launcher: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
Wascar commented on 2018-05-15 20:17 (UTC)
@bda Done
bda commented on 2018-05-15 08:59 (UTC)
hi, libxss is needed as dependancy: ./launcher: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
mattsturgeon commented on 2018-05-04 16:36 (UTC) (edited on 2018-05-04 16:37 (UTC) by mattsturgeon)
I suspect the underlying problem is that Mojang update their "staging" tar, but do not create versioned release archives. Therefore this package is stuck on the latest (broken) release 2.0.579, while Minecraft_staging.tar.gz stays updated and keeps working.
IMO Mojang need to improve the way they handle this, preferably by creating more releases and keeping this package in sync with them. Otherwise we are forced to use packages such as minecraft-launcher-tar that try to keep in sync with the (fully functional) staging build.
koyuawsmbrtn commented on 2018-05-04 16:06 (UTC)
@SuperGeniusZeb I added gconf to the dependencies and updated Minecraft to the latest version. Thank you :)
SteelT commented on 2018-05-04 15:37 (UTC)
It's impossible to run this because it depends on a old version of icu.
Pinned Comments
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.