I'm not entirely sure if this issue is one that is solely related to my machine, or if this has been widespread. But recently (and seeminly completely out of the blue) I've been recieveing instability on my system relating to the minecraft launcher. There seems to be three different resulting behaviors from this instability.

1. the launcher will print 

   https://launchermeta.mojang.com/v1/products/launcher/bb3355e087ada56549e6342233b57bf65d9d7147/linux.json

    to the stdout and then hang indefinately

1.  the launcher will print 

   https://launchermeta.mojang.com/v1/products/launcher/bb3355e087ada56549e6342233b57bf65d9d7147/linux.json

    to the stdout and then hang indefinately, but try to update after being closed

1. the launcher will start normally but print the following to the stdout 

   https://launchermeta.mojang.com/v1/products/launcher/bb3355e087ada56549e6342233b57bf65d9d7147/linux.json
   [0810/234547.307049:INFO:main_context.cpp(130)] CEF initialized successfully.
   [0810/234547.307188:INFO:main_context.cpp(132)] CEF version: 99.2.14+g3f796b8+chromium-99.0.4844.84
   [0810/234547.327538:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
   sh: line 1: orca: command not found
   Created browser window for reuse: 0x7600003
   [0810/234547.431769:ERROR:browser_main_loop.cc(268)] Gdk: _gdk_frame_clock_freeze: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed

    and then hang after pressing play

1. the launcher will start as normal after printing 

   https://launchermeta.mojang.com/v1/products/launcher/bb3355e087ada56549e6342233b57bf65d9d7147/linux.json
   [0810/234547.307049:INFO:main_context.cpp(130)] CEF initialized successfully.
   [0810/234547.307188:INFO:main_context.cpp(132)] CEF version: 99.2.14+g3f796b8+chromium-99.0.4844.84
   [0810/234547.327538:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
   sh: line 1: orca: command not found
   Created browser window for reuse: 0x7600003
   [0810/234547.431769:ERROR:browser_main_loop.cc(268)] Gdk: _gdk_frame_clock_freeze: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed

    to the stdout but will be incapible of downloading older versions

1. the launcher will start normaly printing 

   https://launchermeta.mojang.com/v1/products/launcher/bb3355e087ada56549e6342233b57bf65d9d7147/linux.json
   [0810/234547.307049:INFO:main_context.cpp(130)] CEF initialized successfully.
   [0810/234547.307188:INFO:main_context.cpp(132)] CEF version: 99.2.14+g3f796b8+chromium-99.0.4844.84
   [0810/234547.327538:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
   sh: line 1: orca: command not found
   Created browser window for reuse: 0x7600003
   [0810/234547.431769:ERROR:browser_main_loop.cc(268)] Gdk: _gdk_frame_clock_freeze: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed

    to the stdout and no error will occour

Just for referance I am using a fully updated Artix 5.18.16 kernal with openrc rather than systemd. And I installed the launcher from the AUR as instructed on the website. Additionally the genaric linux version also does not work correctly. I have seen similar errors on other machines as well such as my brother's Pop!Os machine and My own thinkpad. If any other information is required I will be happy to supply it. Thank you for your time and I hope this is able to be resolved swiftly.

Update: after doing some more testing I found that I was partially being impatient, the launcher and the game and the downloads will all work in every case listed above. However they will all take about 10-15 minutes to start, obviously a great deal longer than they should take. Another peice of information that I would like to add is that this behavior was not noticed until yesterday evening, before that the launcher and the game started nealy imediately.