Arch Linux User Repository

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.

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.

If you guys need a keyring manager on KDE that works with this, install kwallet-secrets, and follow the instructions in comments.

It is kwallet patched the freedesktop secrets API support.

@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).

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.

@logothete What if you launch it this way?

$ LC_ALL=C minecraft-launcher

@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.

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

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

@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?

@logothete Launch this binary from terminal: https://launcher.mojang.com/v1/objects/ce9e6169550628003e22de8086e9fe1186c2285e/minecraft-launcher

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.

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.

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