Arch Linux User Repository

Set up either by way of yay or by downloading and utilizing makepkg leaves me with a launcher that won't launch in any respect, and offers no GUI indication of failure either. Nevertheless, taking a look at my logs, I see the somewhat large:

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

(100 odd lines of modules; not notably relevant) Stack trace of thread 30502:

0 0x00007fec63f83d22 elevate (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)

four 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)

eight 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_begin_principal (libc.so.6 + 0x27b25)

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

Stack hint of thread 30504:

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

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

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

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

4 0x00007fec64d8e259 begin_thread (libpthread.so.Zero + 0x9259)

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

ELF object binary architecture: AMD x86-sixty four

Sorry for a way a lot text that's. steve's blog Anybody have any concepts for what's the matter here? Arch install is relatively contemporary, maybe a week or so old, with no real issues.