./launcher error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
Installing gconf solved this problem and resulted, for me, in a working launcher.o Maybe add gconf to the dependencies list.
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)
BjarnoBe commented on 2017-02-07 12:16 (UTC)
FraGag commented on 2017-02-05 03:17 (UTC)
You're not actually using that MC_VERSION_URL variable in /usr/bin/minecraft. :)
BombStrike commented on 2017-01-30 02:09 (UTC)
Ok pushed a new version that should fix things, expect a launcher download.
Also added a MC_FORCE_UPDATE environment variable that can be set to force a launcher update (but shouldn't be necessary).
BombStrike commented on 2017-01-30 02:01 (UTC)
For some weird reason if we use the launcher directly from the .minecraft folder it will never update.
I'm adding a small mechanism to automatically redownload the launcher when the game itself gets updated and will push it soon.
In the meantime run "exec java -jar /usr/share/minecraft/Minecraft.jar" manually to force an update
TripleSpeeder commented on 2017-01-29 15:20 (UTC)
Can't start with client version 1.11.2. Gives following error:
[16:16:21 ERROR]: An update to your launcher is available and is required to play 1.11.2. Please restart your launcher.
Flagged package as out-of-date :-)
Brottweiler commented on 2016-10-27 16:25 (UTC)
@s123 This is only the launcher... when you run it, the launcher will download the version you want to use.
s123 commented on 2016-10-27 16:24 (UTC)
Will the recent version be available? I want to play singleplayer maps, few of them require at least 1.7.7 and one 1.10.4...
altermetax commented on 2016-10-10 15:39 (UTC)
What about making it available with Java 1.8 instead of Java 1.7? It's fully working (I use Java 1.8 to play).
yukixz commented on 2016-09-18 12:16 (UTC)
@BombStrike yep. With XIM env & fcitx, typing CJK in launcher is OK.
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.