fabyouless

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?

@Zgajak,

There is a solitary Warning in the launcher_log.txt:

Warning: 2022-08-24 12:05:35.884717045: LauncherConfiguration.cpp(112)] Failed to get clientToken from configuration, launcher updater will fall back to using stable versions instead of controlled experiment versions.

I left a bash "until" loop running last night, repeatedly rm'ing the launcher folder from ~/.minecraft; and attempting to fire up the minecraft-launcher. I was hoping that minecraft/mojang would fix the error while i slept. Instead, a different error popped up from when i went to bed. Now i get the GLIBC 2.29 error:

[Error: 2022-08-24 12:05:39.477280628: LauncherPluginLinux.cpp(20)] Failed to load /home/[username]/.minecraft/launcher/liblauncher.so: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/[username]/.minecraft/launcher/liblauncher.so)

This is in addition to the error i was getting in the launcher_log.txt when i went to bed last night:

[Error: 2022-08-24 12:05:39.477388516: StartLibrary.cpp(90)] Couldn't load launcher core from /home/[username]/.minecraft/launcher/liblauncher.so: LoadErrorNotPresent

<edit>

Moments before attempting to fire up minecraft-launcher last night, i did an aptitude safe-upgrade, which updated a possibly relevant javascript pacakge as seen here:

upgrade gir1.2-javascriptcoregtk-4.0:amd64 2.36.4-1~deb10u1 2.36.6-1~deb10u1

... in case this has any bearing on minecraft-launcher...

</edit>

I created/posted this bug-tracker/issue after seeing  MCL-18211 had numerous other users struggling, but none of the "resolved" fixes actually fixing this bug that was pushed out by microsoft/mojang.

And, as @knarrff pointed out, this very well could be a duplicate of MCL-22241, but i still can't fire up the minecraft-launcher, so it is definitely not resolved.