Launcher Update breaks Launcher (GLIBC_2.29 not found)

Same issue on Debian 4.19.249-2

Why is this marked "Resolved" when i still can not fire up minecraft-launcher? I'm on a currently supported version of Debian, so shouldn't microsoft/mojang have a version of the launcher that doesn't include this GLIBC_2.29 dependency?

Same issue on Ubuntu 18.04.6 LTS. Definitely not resolved...

I'm on Zorin 15.3, which is based on 18.04. I'm having the exact same issue

Hi there!

Have you tried to delete .minecraft folder (copy its content elsewhere before deletion) and then reinstall the Launcher?
Edit: please also browse through MCL-18211 for potential fixes.

This ticket will automatically reopen when you reply.

Hello Zgajak,

I have deleted .minecraft folder to no avail, after reinstalling it works on first launch, but on second launch seems to do the same update and breaks as knarrff stated.

I did take a look at 18211, libsecret is already the latest version and it seems some commenters on 18211 are experiencing this issue as well.

Mr Preuss, knarrff and others: thank you for your input!

Same thing in rocky8 (rhel 8)

"after reinstalling it works on first launch, but on second launch seems to do the same update and breaks as knarrff stated."

exactly.

For old distros, I guess the most sane thing to do right now is to switch to the flatpak version of the minecraft-launcher

I'm running Debian/Buster and the ONLY way I've gotten the game to load is using .snap

// author must of mis-spelled ...
sudo snap install launcher-ot-minecraft

The game play is not very smooth though.

If someone has a working workaround, please share. The current flatpak version is updated and gives the same error (requires GLIBC_2.29)

Same issue Linux Mint 19.3 Tricia

Started after an update of the launcher last night.

Tried most of what is listed above, and none of it works.

So I figured it out. Sort of.

It is right in the error itself. "requires GLIBC_2.29"

On my Mint 19.3 gaming PC it fails because the latest version installed is 2.27
Upgrading GLIBC really isn't an option. (Unless you are a lot more DEV side than I am.)
Runs just fine on my Mint 20.3 laptop.
So unless the requirement was added by mistake, I would not expect a fix to be coming.

I guess I will be reinstalling the latest version of Mint tonight.

Sorry to be the bearer of bad news.

Seems really weird for Mojang to force every Linux user to update to 20+ when 19.3 is still supported and usable - especially in such a snap update too.  
 
I hope they figure something out to allow older Linux users to still play instead of forcing everyone up possibly multiple versions; it seems really dumb to just be like "19 and below isn't supported anymore but we won't tell you that explicitly."

The way I see it, I can either wait for the issue to be fixed by Mojang, or I can reinstall, and go play Minecraft.

Since this ticket is still unassigned as I write this, I know what choice I am making.

Given that the duplicates are not even marked as such, the devs likely simply didn't have the time to look at it properly and apparently this also isn't a priority for them. So, for now, for us, it is "wait and vote".

For anyone who might be still looking at this. I installed newest Linux Mint and I am back to playing.

Sorry I do not see another option, but since the issue is still unassigned, this at least gives people an option.

Hey all, the launcher team doesn't actively track work we are doing out of this database. We are actively working on this issue at the moment. 

ya my child is complaining his Minecraft isn't working, using Ubuntu 18.04 (actually Linux Mint version of Ubuntu 18.04)

I haven't upgraded to the newer mint yet , we have 6 children and a lot of computers so I'm lagging a bit behind the curve and we're going to be moving soon.

So ya, the problem is minecraft is looking for a new version of the glibc , I compiled the new version but I don't want to break my os, I'll wait until someone puts the instructions here to run two versions of glibc.  Or perhaps Mojang will fix the glitch so that we don't have to upgrade to 20.04 /22.04 right away.  Maybe allow us to run for a while as is.

I can relate to your situation, though I only have 2 kids.

I'm debating upgrading the Ubuntu 18.04 system that they use for Minecraft. 

I totally understand sun-setting support for old unsupported software, but Ubuntu 18.04 is still receiving regular support.  Was there a notice that we (this group) missed that development was removing support for glibc 2.27?  As of right now, the Minecraft: Java Edition system requirements [https://www.minecraft.net/en-us/get-minecraft] states, "Linux: Any modern 64-bit distributions from 2014 onwards".  If that is changing, please make sure to post it like the dropped support for older MacOS versions [https://help.minecraft.net/hc/en-us/articles/4420326353933-Minecraft-Java-Edition-Versions-and-MacOS-] in Minecraft: Java Edition 1.18

Workaround for now: use a third-party launcher. Another user and I were able to get the vanilla launcher to start, but it isn't communicating correctly with Mojang's authentication servers. (Issue MCL-22271 if you're curious.)

I've been using PolyMC, which you can get right off the Mint 19 Software Manager. It works great. There are others, and they tend to have good wikis and/or YouTube videos to explain how to set them up. It takes a few minutes, but it's probably way easier than upgrading your entire OS version. 🙂

It seems the devs are assuming that, because these versions of Linux are long-term support, glibc and/or its parent library is backwards-compatible. For whatever reason, distro maintainers do not want the update installed on older systems. No idea why. But I remembered that I actually had this issue with glibc/libc6 earlier this year. A modding tool for Baldur's Gate: Enhanced Edition used the updated library version and I got it to work by downloading the tool's source code and compiling it on my own machine. (I'm a Linux n00b, so it was an adventure.) If that incident would be helpful to whoever's working on this problem, I can track down the related forum posts.

This is pretty ridiculous. A forced launcher update that breaks all functionality on supported OS's? I tried using a third-party launcher to work around this, but audio doesn't work. I wanted to relax this weekend and play some Minecraft, and I can't because the launcher team pushed out a broken update and didn't immediately revert back to a functional version. 

All of this can be avoided by just providing users with the outdated Linux launcher in the meantime while a fix is investigated, is there any reason not to do this?

Same using Linux Mint version of Ubuntu 18.04
It cannot even be run with a separate glibc 2.29 (compiled from the source). Specifying LD_LIBRARY_PATH=/path/to/glibc/lib results in a segmentation fault and nothing more.

Hi!

Does this issue occur to anybody on the newest version of the Launcher?

This ticket will automatically reopen when you reply.

At least for me, there does not seem to be any new version. The launcher is not updating and I still get the same file contents:

$ md5sum .minecraft/launcher/liblauncher.so
b6278a946bb98d2039e43a6de36cd24c  .minecraft/launcher

Same for me - there is a change to the launcher (so bdiff tells me) but it's still looking for glibc 2.29.

Downloaded the launcher from Minecraft.net, same 'LoadErrorNotPresent' issue (which I believe is just a less detailed version of this one) and also deleted the .version to try to force an update, same issue. 
 
Seems like either the newest version of the launcher isn't officially out yet or the issue is still present.

I see error   "GLIBC_2.29' not found"    on version:

[Info: 2022-08-29 20:48:06.288216338: Common.cpp(32)] Native Launcher Version: 1.1.28

(an entry taken from .minecraft/launcher_log.txt)

I just deleted my `~/.minecraft` folder and redownloaded a fresh Minecraft.deb file, and re-ran it, and I'm still getting the exact same errors:

here is the tail from my `~/.minecraft/launcher_log.txt` file showing the error still:

[Info: 2022-08-29 22:33:55.169442618: NetQueue.cpp(229)] NetQueue: Done.
[Info: 2022-08-29 22:33:55.169599897: StartLibrary.cpp(61)] Starting /.../liblauncher.so
[Error: 2022-08-29 22:33:55.192908699: LauncherPluginLinux.cpp(20)] Failed to load /home/myname/.minecraft/launcher/liblauncher.so: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/myname/.minecraft/launcher/liblauncher.so)
[Error: 2022-08-29 22:33:55.193003284: StartLibrary.cpp(90)] Couldn't load launcher core from /home/myname/.minecraft/launcher/liblauncher.so: LoadErrorNotPresent
-----------------------------------------------------------------------
If this is your first time running Minecraft, please ensure you are connected to the internet so we can download updates.
[Info: 2022-08-29 22:33:55.193089492: NetQueue.cpp(212)] NetQueue: Initiating shutdown.
[Info: 2022-08-29 22:33:55.193105191: NetQueue.cpp(217)] NetQueue: No thread currently running

as such Minecraft is currently unplayable on any distro based on Ubuntu 18.04 😞

Attempted to update via apt. It said there was an update, but it seems to be installing the same version again.

michelle@Minty:~$ sudo apt reinstall minecraft-launcher
The following packages will be REINSTALLED:
  minecraft-launcher 
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/52.3 MB of archives. After unpacking 0 B will be used.
(Reading database ... 390789 files and directories currently installed.)
Preparing to unpack .../minecraft-launcher_2.1.9618_amd64.deb ...
Unpacking minecraft-launcher (2.1.9618) over (2.1.9618) ...
Setting up minecraft-launcher (2.1.9618) ...
Processing triggers for desktop-file-utils (0.23+linuxmint8) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for mime-support (3.60ubuntu1) ...

Uninstalled the launcher and tried the .deb. It gives its version as 1.1.26. Still having the same issue. I'm attaching my bootstrap-log (which I think is the installation log?) and launcher-log, which is still complaining about glibc 2.29.

I'm not sure whatever version is on the package repo is completely up-to-date, because it seems like this is an earlier version than the one available in this tracker. 2.1.9618 vs. 2.3.377. When I get the launcher to start, it always says there's an update available and links to the minecraft.net download page for Linux, even though that's an older version.

Edit: Okay, the update manager had an update for minecraft-launcher. This time, the launcher opened without me having to reinstall dependencies as I did before, but it's still not able to authorize a login and it's still version 2.1.9618.

Hey everybody, download polymc from your app manager in your linux, to access minecraft from there, this launcher works fine, you can log via Microsoft account .

We have a fix for this issue in our beta

thank you! I tested it, and it works great now <3

This is terrible and completely unacceptable. It took me one hour and 530MB of my limited Internet to download this vanilla launcher. Just the launcher mind you, the only purpose of which is to launch the game which is unchanged. This level of incompetence is embarrassing for the team responsible for the best selling game of all time. Most frustrating is the overly simple download screen which does not indicate how much has been downloaded, how much is left, no button to report an issue. Just stripping away all power from the user as much as possible.

I will be using third party launchers from now on since the actual Mojang developers are apes who cannot program and have no empathy. As the other comment mentioned I'm going to use PolyMC launcher as it looks good.