You can work around the issue for now with env GDK_BACKEND=x11 minecraft-launcher
instead. The issue is tracked here: https://bugs.mojang.com/browse/MCL-12215.
It would probably be handy if the minecraft-launcher.desktop
was updated to include this workaround for now.
Alternatively:
mkdir -p ~/.local/share/applications/
cp /usr/share/applications/minecraft-launcher.desktop ~/.local/share/applications/
sed -i 's/Exec=/Exec=env GDK_BACKEND=x11 /g' ~/.local/share/applications/minecraft-launcher.desktop
Now you can start Minecraft Launcher as usual and keep updating this package as your definition of minecraft-launcher.desktop will override the one shipped with the package.
Pinned Comments
wheat32 commented on 2025-03-08 18:32 (UTC) (edited on 2025-03-08 19:30 (UTC) by wheat32)
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:
Edit: I found that deleting the webcache2 directory in the .minecraft directory fixes the issue for me.
petr commented on 2021-10-08 09:04 (UTC)
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.