Minecraft launcher arch linux

Arch Linux User Repository

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

Jackleson commented on 2023-03-04 17:20 (UTC)

bryiewes, Yeah I figured out that it was a Manjaro issue, but now it simply will not install now since it leaves bad config or something behind. Manjaro just randomly over complicates the user experience and not because it is hard to understand just that nobody asked for that particular interaction. KDE Wallet is just badly introduced to the user. 90% of folks don’t expect an OS level password manager to just shove itself into how they normally interact with a computer. worse its broken anyway. besides asking «why the fuck did it show up when i am literally just installing minecraft» it errors out when you select any option.

bryiewes commented on 2023-03-04 16:48 (UTC)

What do you mean by key nonsense. Also, manjaro has it’s own issues that cause further issues. Don’t try to bring the topic of «it’s not required on windows» onto this site, windows and arch Linux are drastically different. My suggestions for your problem are to a. Use regular arch b. Use prism launcher (multimc was great, this is better, and polymc can’t be trusted.) c. Don’t play minecraft.

teek commented on 2023-02-22 22:42 (UTC) (edited on 2023-02-22 22:44 (UTC) by teek)

Nevermind, I reinstalled, restarted (from the terminal) and now it works. Apologies.

I am getting this message after installing this package:

Unable to locate the Java runtime. Error details: Success Filename on disk: Path: . Exists: Directory 

Before that it was complaining about ogg files already being on disk, so I emptied my .minecraft folder.

feixm commented on 2022-09-07 10:53 (UTC) (edited on 2022-09-07 10:59 (UTC) by feixm)

gnome-keyring should be added as an optdepend. Without this package you are forced to enter Minecraft credentials every single time the launcher is fired up.

diff --git a/PKGBUILD b/PKGBUILD index 2e62273..8e73b26 100644 --- a/PKGBUILD +++ b/PKGBUILD @@ -12,7 +12,7 @@ license=('All rights reserved') depends=('alsa-lib' 'at-spi2-atk' 'at-spi2-core' 'atk' 'dbus' 'expat' 'gcc-libs' 'gdk-pixbuf2' 'glib2' 'glibc' 'gtk3' 'libcups' 'libdrm' 'libx11' 'libxcb' 'libxcomposite' 'libxdamage' 'libxext' 'libxfixes' 'libxrandr' 'mesa' 'nspr' 'nss' 'pango' 'util-linux-libs' 'zlib' 'java-runtime' 'xorg-xrandr') -optdepends=('flite: narrator support') +optdepends=('flite: narrator support', 'gnome-keyring: Storage of your Minecraft credentials') conflicts=('minecraft-launcher-beta') provides=('minecraft-launcher-beta') source=("https://launcher.mojang.com/download/linux/x86_64/minecraft-launcher_$.tar.gz" 

m00nw4tch3r commented on 2022-07-25 09:20 (UTC) (edited on 2022-07-25 09:24 (UTC) by m00nw4tch3r)

Almost all of the info about Java versions and Minecraft below is wrong.

Minecraft isn’t that picky about the Java version, the only real delineation is that versions below 1.17 work with Java 8 up to IIRC 11, while newer versions work with latest Java. Mojang/Microsoft just added a java version check to the launcher which checks if you have an exact version of java installed, not if the java version you have is actually compatible with the game or not. You can disable it by deleting the JavaCheck.jar file.

@rabcor @bryiewes @mattsturgeon

paranoidAndroid0 commented on 2022-07-19 19:05 (UTC)

this package doesn’t not work for me. I tried all the different version of jre.

antonfourier commented on 2022-07-17 17:43 (UTC)

I encountered this when launching Minecraft 1.19 (or 1.18) with minecraft-launcher with jre-openjdk17 and nvidia-xrun (to force it to use my NVidia 920M):

The game would not launch, crashing immediately and not providing any useful logs, except for 1.18, when it said

.minecraft/runtime/java-runtime-beta/linux/java-runtime-beta/lib/libnio.so: undefined symbol: ipv6_available 

On another forum I found that if I do the following export:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/jvm/default/lib/server 

Some other java application would run fine. I tried this for my case as well, and now both 1.18 and 1.19 are running on my nvidia-xrun X instance.

mattsturgeon commented on 2022-07-13 16:17 (UTC) (edited on 2022-07-13 16:19 (UTC) by mattsturgeon)

Yeah, unfortunately Java versions aren’t always backwards-compatible (hence why oracle still maintain old java versions).

Most somewhat-recent Minecraft versions depend on Java 8 (aka 1.8) exactly — older or newer versions are incompatible.

Minecraft recently updated to the newer Java 17, but still might not be compatible (or perhaps not yet tested/supported on) the very latest java versions. Hence why the launcher checks you are running that particular Minecraft version with a known-to-be-compatible Java version.

This problem applies to all Java projects, although you usually only notice it on the bigger more complex ones.

rabcor commented on 2022-07-13 14:58 (UTC) (edited on 2022-07-13 14:59 (UTC) by rabcor)

bryiewes, it turns out i was mistaken anyways, the bundled version is openjdk 17; I actually tried downloading openjdk17 runtimes and targetting the binaries for that version in /usr/lib/jvm and it worked, apparently minecraft is just really picky about which version you’re using. Now I’m just trying to figure out how to get it working with ZGC or Shenandoah garbage collection, gives me a generic misconfiguration error when I try to run with it.

Copyright © 2004-2023 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник

Arch Linux User Repository

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

nicegamer7 commented on 2022-01-23 05:42 (UTC)

@jextrevor I ran into that as well. In my case it was caused by launching Sway through dbus-run-session.

I figured out that was the problem by looking at an environment variable (I think it was DBUS_SESSION_BUS_ADDRESS).

jextrevor commented on 2022-01-12 06:50 (UTC)

After installing gnome-keyring, the launcher takes several minutes to load at first and then hangs again when trying to log in (tried several times, waiting several minutes each time, and never got it to finish). I don’t know what’s going on. Removing gnome-keyring makes it load fast again.

kamilst96 commented on 2022-01-08 21:50 (UTC) (edited on 2022-01-08 21:50 (UTC) by kamilst96)

@logothete What if you launch it this way?

@timo_capa @jpegxguy Yeah, I rebuilt the package without java-runtime as dependency and purged all Java from my system. The game behaves as if nothing happened.

jpegxguy commented on 2022-01-06 12:04 (UTC)

Honestly, even though I use my system java and not the bundled one for the game, it is true that the launcher shouldn’t need it, right? I think timo_capa is right

timo_capa commented on 2022-01-06 10:51 (UTC)

Gonna sound weird, but why is java a dependency?

minecraft-launcher doesn’t depend on it, and the game itself ships a bundled java version for compatibility reasons

logothete commented on 2022-01-03 07:39 (UTC)

@kamilst96 Thanks for the reply. Unfortunately, that binary executes with error:

terminate called after throwing an instance of ‘std::logic_error’ what(): basic_string::_M_construct null not valid

which seems to be the same as what’s going on with the installed version as well.

Any theories as to what may be missing?

kamilst96 commented on 2022-01-02 18:04 (UTC)

I blindly rebuilt arch installation and tried this launcher directly (1035), via AUR (928), and via my own PKGBUILD (1035). All of them worked with KDE / GNOME on X11, so you’ve done something specific in your install, or maybe forgot something.

logothete commented on 2021-12-30 17:32 (UTC)

Installation either through yay or through downloading and using makepkg leaves me with a launcher that won’t launch at all, and gives no GUI indication of failure either. However, looking at my logs, I see the rather large:

Process 30502 (minecraft-launc) of user 1000 dumped core.

(a hundred odd lines of modules; not particularly relevant) Stack trace of thread 30502:

0 0x00007fec63f83d22 raise (libc.so.6 + 0x3cd22)

1 0x00007fec63f6d862 abort (libc.so.6 + 0x26862)

2 0x00007fec6430d802 _ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6 + 0x99802)

3 0x00007fec64319c8a _ZN10__cxxabiv111__terminateEPFvvE (libstdc++.so.6 + 0xa5c8a)

4 0x00007fec64319cf7 _ZSt9terminatev (libstdc++.so.6 + 0xa5cf7)

5 0x00007fec64319f8e __cxa_throw (libstdc++.so.6 + 0xa5f8e)

6 0x00007fec6431036c _ZSt19__throw_logic_errorPKc (libstdc++.so.6 + 0x9c36c)

7 0x00000000004cd43a n/a (minecraft-launcher + 0xcd43a)

8 0x000000000043f0de n/a (minecraft-launcher + 0x3f0de)

9 0x0000000000410b56 n/a (minecraft-launcher + 0x10b56)

10 0x000000000041db10 n/a (minecraft-launcher + 0x1db10)

11 0x000000000040958c n/a (minecraft-launcher + 0x958c)

12 0x00007fec63f6eb25 __libc_start_main (libc.so.6 + 0x27b25)

13 0x000000000040ccf9 n/a (minecraft-launcher + 0xccf9)

Stack trace of thread 30504:

0 0x00007fec64d9a8ca __futex_abstimed_wait_common64 (libpthread.so.0 + 0x158ca)

1 0x00007fec64d94574 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf574)

2 0x0000000000470689 n/a (minecraft-launcher + 0x70689)

3 0x00007fec64347782 execute_native_thread_routine_compat (libstdc++.so.6 + 0xd3782)

4 0x00007fec64d8e259 start_thread (libpthread.so.0 + 0x9259)

5 0x00007fec640455e3 __clone (libc.so.6 + 0xfe5e3)

ELF object binary architecture: AMD x86-64

Sorry for how much text that is. Anyone have any ideas for what’s the matter here? Arch install is relatively fresh, maybe a week or so old, with no real problems.

kamilst96 commented on 2021-12-18 15:46 (UTC) (edited on 2021-12-18 16:11 (UTC) by kamilst96)

Bootstrap version 1035 is available, released 20210916, but it’s not available as tar.gz.

Maybe you could follow Gentoo repo which tracks Mojang launcher meta.

Here’s an example commit of what I mean: GitHub

cosmicmarley17 commented on 2021-12-16 19:37 (UTC) (edited on 2021-12-16 19:39 (UTC) by cosmicmarley17)

For people having issues needing to log into Microsoft every time, this solution from the wiki solved it for me: https://wiki.archlinux.org/title/GNOME/Keyring#—start_step

You have to have gnome-keyring installed.

Copyright © 2004-2023 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник