Launcher Update breaks Launcher (GLIBC_2.29 not found)
Hello, I played minecraft fine yesterday (and the past few years) on my Ubuntu 18 PC. Today, I start the launcher and it downloads an update. After the update, the launcher fails to open every time.
Launcher log says that there is a missing dependency, GLIBC29, but I have the latest libc6 installed for Ubuntu 18. I did apt update and upgrade without success. Is there any way I can go back to the old launcher that works? Thanks for any help, it sucks suddenly not being able to play the game I paid for ![]()
launcher_log.txt: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/collin/.minecraft/launcher/liblauncher.so)
$ uname -a
Linux x399 5.4.24+ #1 SMP Sat Jul 9 14:53:46 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux
$ nm --dynamic --demangle /lib/x86_64-linux-gnu/libm.so.6 | grep GLIBC
0000000000000000 A GLIBC_2.15
0000000000000000 A GLIBC_2.18
0000000000000000 A GLIBC_2.23
0000000000000000 A GLIBC_2.24
0000000000000000 A GLIBC_2.25
0000000000000000 A GLIBC_2.2.5
0000000000000000 A GLIBC_2.26
0000000000000000 A GLIBC_2.27
0000000000000000 A GLIBC_2.4
libc6 is already the newest version (2.27-3ubuntu1.6)
libstdc++6 is already the newest version (8.4.0-1ubuntu1~18.04)
$ apt-cache policy libc6
libc6:
Installed: 2.27-3ubuntu1.6
Candidate: 2.27-3ubuntu1.6
Version table:
*** 2.27-3ubuntu1.6 500
500 mirror://mirrors.ubuntu.com/mirrors.txt bionic-updates/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.27-3ubuntu1.5 500
500 mirror://mirrors.ubuntu.com/mirrors.txt bionic-security/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
2.27-3ubuntu1 500
500 mirror://mirrors.ubuntu.com/mirrors.txt bionic/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
Linked Issues
is duplicated by6
Created Issue:
Launcher Update breaks Launcher
Hello, I played minecraft fine yesterday (and the past few years) on my Ubuntu 18 PC. Today, I start the launcher and it downloads an update. After the update, the launcher fails to open every time.
Launcher log says that there is a missing dependency, GLIBC29, but I have the latest libc6 installed for Ubuntu 18. I did apt update and upgrade without success. Is there any way I can go back to the old launcher that works? Thanks for any help, it sucks suddenly not being able to play the game I paid for
launcher_log.txt: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/collin/.minecraft/launcher/liblauncher.so)
$ uname -a
Linux x399 5.4.24+ #1 SMP Sat Jul 9 14:53:46 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux$ nm --dynamic --demangle /lib/x86_64-linux-gnu/libm.so.6 | grep GLIBC
0000000000000000 A GLIBC_2.15
0000000000000000 A GLIBC_2.18
0000000000000000 A GLIBC_2.23
0000000000000000 A GLIBC_2.24
0000000000000000 A GLIBC_2.25
0000000000000000 A GLIBC_2.2.5
0000000000000000 A GLIBC_2.26
0000000000000000 A GLIBC_2.27
0000000000000000 A GLIBC_2.4
libc6 is already the newest version (2.27-3ubuntu1.6)
libstdc++6 is already the newest version (8.4.0-1ubuntu1~18.04)
$ apt-cache policy libc6
libc6:
Installed: 2.27-3ubuntu1.6
Candidate: 2.27-3ubuntu1.6
Version table:
*** 2.27-3ubuntu1.6 500
500 mirror://mirrors.ubuntu.com/mirrors.txt bionic-updates/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.27-3ubuntu1.5 500
500 mirror://mirrors.ubuntu.com/mirrors.txt bionic-security/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
2.27-3ubuntu1 500
500 mirror://mirrors.ubuntu.com/mirrors.txt bionic/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
Launcher Update breaks Launcher (GLIBC_2.29 not found)
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
I had opened a bug/ticket (
MCL-22250) but focused my efforts on this one.There is a new comment over there that seems promising. I'm stuck in WindowsLand right now so can't check it out:
I am getting around this in Linux by navigating to the minecraft-launcher binary in `~/.minecraft/launcher` and typing minecraft-launcher --skipUpdate`
is duplicated by
Thank you for your report!
We're tracking this issue in MCL-22241, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
@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.
Thank you for your report!
We're tracking this issue in MCL-22241, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
I understand login problems are usually kicked over to Customer Service. However, I think the Linux launcher has a technical problem. The launcher.log has networking errors, launcher-profiles.json looks weird (1970???) and I can log in with the same credentials elsewhere.
I had an issue identical to MCL-22241 and its relatives. The launcher updated itself and broke with the same error in the log. Following their suggestions, I got the launcher to start again by:
1. uninstalling the launcher, 2. deleting .minecraft, 3. reinstalling the following packages via the Synaptic Package Manager:
libc++1 (6.0-2) libsecret-1-0 (0.18.6-1) libsecret-common (0.18.6-1) libstdc++6 (8.4.0-1ubuntu1~18.04) libstdc++6:i386 (8.4.0-1ubuntu1~18.04)
and 4. reinstalling minecraft-launcher through SPM as well.
The launcher starts now (hooray!) but any attempt to log in results in a message that my email or password is incorrect. It is not. I can log in to minecraft.net and Microsoft just fine. The .deb on the website seems to be an older version than the one I get through the package manager. Installing it just causes the launcher to update itself and break again.
Because of the package shenanigans, I looked up minecraft-launcher's "latest version dependencies" and worked my way through them. Reinstall a few packages, delete .minecraft, reinstall minecraft-launcher, test. If this seems tedious: yes. It didn't work. I've attached a list of all the dependencies I tested.
I appreciate your help. Please let me know if there's any more information I can give you.
Thank you for your report!
We're tracking this issue in MCL-22241, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCL-22241, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCL-22241, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
If you look in .minecraft/launcher_log.txt in your home directory, you might see "Failed to load /home/white/.minecraft/launcher/liblauncher.so: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/white/.minecraft/launcher/liblauncher.so)"
If so, you're probably running Ubuntu 18 or similar, with an older version of the GLIBC library. This version needs a really new shiny version (for no real reason imho). That would make this yet another duplicate of MCL-22241.
@jfinnis I believe it is a duplicate of MCL-22241
Duplicate of MCL-22241.
Solution: update to Debian 11
Thank you for your report!
We're tracking this issue in MCL-22241, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
I'm experiencing the same issue on Debian 10, but it is fixed on Debian 11
I have the same problem. I'm using in the whole time the problem occurs, the snap version from the software-center from Ubuntu which works with this update. Not really a solution but maybe helpful to play minecraft for others.
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-18211for potential fixes.This ticket will automatically reopen when you reply.
Same issue here, and yes, occurs on brand new .minecraft directory, as yesterday's new .minecraft/launcher/liblauncher.so apparently has a new GLIBC dependency.
Error from launcher_log.txt after attempting to launch launcher is:
[Info: 2022-08-24 02:04:32.624954851: StartLibrary.cpp(61)] Starting /.../liblauncher.so
[Error: 2022-08-24 02:04:32.626887761: LauncherPluginLinux.cpp(20)] Failed to load /home/tom/.minecraft/launcher/liblauncher.so: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/tom/.minecraft/launcher/liblauncher.so)
[Error: 2022-08-24 02:04:32.626944408: StartLibrary.cpp(90)] Couldn't load launcher core from /home/tom/.minecraft/launcher/liblauncher.so: LoadErrorNotPresent
Potentially relevant:
$ ldd --version
ldd (Ubuntu GLIBC 2.27-3ubuntu1.6) 2.27
$ ldd ~/.minecraft/launcher/liblauncher.so
/home/tom/.minecraft/launcher/liblauncher.so: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/tom/.minecraft/launcher/liblauncher.so)
/home/tom/.minecraft/launcher/liblauncher.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/tom/.minecraft/launcher/liblauncher.so)
/home/tom/.minecraft/launcher/liblauncher.so: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by /home/tom/.minecraft/launcher/liblauncher.so
None of those potential fixes worked for me. Please also note the new comments on that issue indicating a re-occurrence for several more users.
Since I cannot vote atm, one "me too"-comment, with the small addition:
before the update:
$ md5sum .minecraft_2022-08-23/launcher/liblauncher.so
ef6c86ec1e39c1b81563d6d0163252ba .minecraft_2022-08-23/launcher/liblauncher.so
$ strings .minecraft_2022-08-23/launcher/liblauncher.so | grep GLIBC_2.2
GLIBC_2.2.5
after the update:
$ md5sum .minecraft/launcher/liblauncher.so
b6278a946bb98d2039e43a6de36cd24c .minecraft/launcher/liblauncher.so
$ strings .minecraft/launcher/liblauncher.so | grep GLIBC_2.2
GLIBC_2.2.5
GLIBC_2.29
GLIBC_2.25
GLIBC_2.28
The new dependencies come through usage of (in case that helps you find it):
$ nm -D .minecraft/launcher/liblauncher.so | grep GLIBC_2.2 | grep -v 2.2.5
U fcntl64@GLIBC_2.28
w getentropy@GLIBC_2.25
U pow@GLIBC_2.29
Also: deleting .minecraft did not help either. The first time it starts in that case, with the files presumably from the debian-package installer, the second time (after the update) you get the same problem.
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
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-minecraftThe 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-22271if 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 runningas 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.
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.
@Joe Smoe: I think we get what your message is. However, if you want to be taken seriously, you'll have to work (hard) on how you deliver it. And I really had to try hard to make this sound nice.
@devs: thanks. It still introduces a dependency on 2.25, which was not there previously, but it is a weak one. Not sure why that was intentional or not.
```
$ nm -D .minecraft/launcher/liblauncher.so | grep GLIBC_2.2 | grep -v 2.2.5
w getentropy@GLIBC_2.25
```
I've been playing this game since 2011, first on Windows and now on Linux, and this is the first time I've ever had an issue with the launcher. That's pretty remarkable reliability for any kind of software. I'm guessing the issue came up from the process of getting the existing launcher to play nice with Microsoft's fancy-dancy login system across three platforms, which must have been quite a process. Hiccups are understandable.
Thanks to the team who sorted this out. I hope you guys get paid many emeralds.
I tested and Issue is still there, It is not resolved, currently I am using polymc launcher to be able to play minecraft at all.
Uninstall the launcher, download the .deb from the website, and let it auto-update. Worked for me.
Deleting liblauncher.so and .version under the launcher/ directoy before starting the launcher should fix the problem now.