I downloaded the general Minecraft installer from the official site, ran tar -xvf Downloads/Minecraft.tar.gz, then ran ./minecraft-launcher after changing into the proper directory. A nearly blank window opened, with just a bar at the top saying it was downloading some stuff, had a little spinning gear. Then the window closed, reopened, saying it was updating or something. It printed “OK” twice to the terminal, then just exited as a failed command. Any ideas?
What about this?
mkdir -p '/tmp/Minecraft' && wget -O '/tmp/Minecraft/Minecraft.tar.gz' 'https://launcher.mojang.com/download/Minecraft.tar.gz' && tar -xvzf '/tmp/Minecraft/Minecraft.tar.gz' -C '/tmp/Minecraft'
First launch (it downloads a newer one to ~):
'/tmp/Minecraft/minecraft-launcher/minecraft-launcher'
Later launches:
cd ~/'.minecraft' && ~/'.minecraft/launcher/minecraft-launcher'
First launch failed. Went into the .minecraft folder and grabbed the bootstrap and launcher txt files. Maybe they help somehow? How do I upload that info in a useful manner?
Edit: tried running the new launcher and got a new output to the terminal before immediately exiting:
[1] 553733 segmentation fault (core dumped) ./minecraft-launcher
In the meanwhile, here are the last few lines:
[Fatal: 2025-12-11 21:09:06.291750475: +x5WplY7h0I=: mainLinux.cpp(750)] Launcher crashed while executing… signal: 11
[Info: 2025-12-11 21:09:06.291868759: +x5WplY7h0I=: mainLinux.cpp(753)] Freshly updated launcher crashed.
I am experiencing exactly the same issue.
[Fatal: 2025-12-25 20:43:04.170699284: 169qbLeyjwE=: mainLinux.cpp(750)] Launcher crashed while executing… signal: 11
[Info: 2025-12-25 20:43:04.170765529: 169qbLeyjwE=: mainLinux.cpp(753)] Freshly updated launcher crashed.
I have the same. F43, x86_64, AMD Radeon graphics. In ~/.minecraft/launcher_log.txt the last line reported is the following, which may or may not be related:
[Warning: [date] [random]: PlatformLinux.cpp(280)] Failed to get framebuffer config
bootstrap_log.txt also says:
mainLinux.cpp(750)] Launcher crashed while executing… signal: 11
Not sure if it’s relevant but I have java-21-openjdk-headless-21.0.9.0.10-1.fc43.x86_64
The problem for me was the launcher was failing when running on an integrated graphics card on a system without a discrete graphics card. My fix - I added a script called minecraft-launcher-mesa:
#!/bin/bash
export __GLX_VENDOR_LIBRARY_NAME=mesa
/path/to/minecraft-launcher/minecraft-launcher
which forces the use of mesa. I saved the script in the same location as minecraft-launcher itself, and made it executable, and then referenced it in the desktop file:
[Desktop Entry]
Name=Minecraft Launcher
Comment=Minecraft Launcher
# Exec=/path/to/minecraft-launcher/minecraft-launcher
Exec=/path/to/minecraft-launcher/minecraft-launcher-mesa
Path=/path/to/minecraft-launcher
Icon=/path/to/minecraft-launcher/minecraft-launcher.png
Terminal=false
Type=Application
Categories=Game;Application;
Version=1.0
StartupWMClass=Minecraft
in fact, you don’t need the script - you could specify and export the environment variable in the desktop file directly:
Exec=env __GLX_VENDOR_LIBRARY_NAME=mesa /path/to/minecraft-launcher/minecraft-launcher
I took the route of using a script because I reuse the same files across all of my laptops and desktops, and thought this approach was slightly neater. I might try to come up with an approach that tries to figure out whether to use the nvidia or mesa vendor library, so you only need to use one file whether you use nvidia, amd, or intel GPUs.
I hope this helps.
3 Likes
I was having this issue since i updated to fedora 43. i contacted minecraft support in mid december and as of yesterday they have no idea how to fix this. I tried your solution and it works!
What’s odd is that my case is the opposite of what you describe, I’m on a system that only has discrete graphics. It’s an AMD gpu. I would have thought the launcher would default to mesa. In the logs there’s nothing beyond “failed to get framebuffer”.
How did you figure this out?
Thank you!
1 Like
I also have a system with a discrete amd GPU that required this fix - my first clue was when my laptop with a discrete nvidia GPU worked without issue.
I searched for answers to this issue for some time and found no exact solution - in fact this post was the only place I could find that directly referred to the same issue I encountered.
In my travels I found this reddit post that contained some interesting information:
which made reference to setting the following environment variable:
__GLX_VENDOR_LIBRARY_NAME=mesa
I recalled having to set the below environment variable for my discreet nvidia GPU when running steam games
__GLX_VENDOR_LIBRARY_NAME=nvidia
which was when it clicked - it occurred to me that there was a possibility the minecraft launcher for some reason expected an nvidia GPU, and needed to be told explicitly which GPU, or more specifically the version of GLX / the graphics API to use, through this environment variable. So I gave it a try and it seemed to work for me.
Delighted to hear it also worked for you. I’m sure the minecraft launcher team would be interested to hear how this issue has been resolved - this is a recent issue so they may have inadvertently introduced it without knowing - it strikes me that this is not expected behaviour.
[EDIT] - I didn’t consider that this issue could have been a Fedora 43 issue - that may be worth considering - I wonder was the above environment variable set to mesa by default on Fedora 42 and older, and is no longer set?
1 Like
I’m going to let minecraft support about this. I was playing minecraft on fedora 42 without doing anything special, then i stopped playing for a while, then i upgraded to fedora 43, and a few days later i went to launch minecraft and it wouldn’t do anything at all. maybe it was the fedora 43 update, maybe it was a minecraft launcher update? who knows!
I also came across that reddit post in my searches! but i didn’t think to try that since they mentioned it was an nvidia related problem. well done!
Thanks again!
Thank you! This fixed it for me (with AMD integrated GPU)
1 Like
The more I think about it, the more I am pretty sure that this is a problem with the launcher - the fact that it works without issue on a system with an discreet nvidia GPU without having to add:
#!/bin/bash
export __NV_PRIME_RENDER_OFFLOAD=1
export __GLX_VENDOR_LIBRARY_NAME=nvidia
/path/to/minecraft-launcher/minecraft-launcher
and you have to explicitly include it for the mesa implementation in the case of integrated intel and amd GPUs, and discreet amd GPUs, would lead me to believe that the launcher expects the nvidia GLX implementation. by default.
Well, clearly it is a bug with the Minecraft launcher. The launcher shouldn’t just crash without needing some obscure undocumented environment variable. If necessary, Mojang/Microsoft should ship it with a wrapper that sets whatever parameters are needed.
The thing is the environment variable is well documented - specifically for offloading to discreet nvidia cards on optimus systems.
I might be wrong, but I always thought the default GLX implementation was mesa whether or not you had a discreet (nvidia) GPU, and that you had to explicitly set the GLX implementation to nvidia to offload all rendering to the discreet nvidia GPU. But I would never have thought that it had to be set to the default (mesa) on systems with integrated amd or intel GPUs - with or without discreet GPUs. Which is why it took so long for me to figure this out.
This is why I considered that an environment variable setting mesa as the default GLX provider was missing. But it seems much more likely that the minecraft launcher assumes the GLX provider to be nvidia unless mesa is explicitly set - and this in my humble opinion is the wrong approach.
By the way, let us all know how it goes with minecraft support. I’d be interested to hear what they say.
They replied quickly with the following:
Too bad they closed the ticket without providing an official solution, but at least it looks like they’ll pass this on to the dev team?
1 Like
Thanks for the update Sara. One thing - I sincerely doubt this is a Fedora specific issue.
I don’t currently have any other distributions running on any devices, so I can’t check this out for myself, but I might post something on Reddit (or similar) to see if anyone is experiencing the same - though the sense I get is that many in the Linux gaming community have moved away from the official launcher in favour of others - such as Prism.
Thanks again,
J.K.
1 Like