MCL-22271Launcher unable to authenticate after update
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.
Environment
OS: Linux Mint 19.3
Java: AdoptOpenJDK11 JRE 11.0.16+8-0ubuntu1~18.04
Linked Issues
Created Issue:
Launcher unable to authenticate after update
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-22241and 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.
Environment
OS: Linux Mint 19.3
Java: AdoptOpenJDK11 JRE 11.0.16+8-0ubuntu1~18.04
Attachments2
duplicates
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.
I noticed a similar issue like this too while trying to resolve the GLIBC issues. It seems like Linux has access to a later version of the launcher than is available on Minecraft.net, and it actually runs instead of failing, but is totally unable to authenticate that you're you.
The launcher is asking a server somewhere what version is the newest and downloading the files if there's a change. The whole process for updating that is probably automated, unlike packaging a .deb for download, so it's not surprising that the download is out of date and self-updates as soon as it runs.
I think the launcher and the auth servers are speaking different languages. I think maybe either the thing the launcher uses to interpret data from the server, or the thing the launcher uses to encode and send data to the server, is borked, and the server is just sending back the 403 as its way of going "What is this garbage? I don't even know what it means" when the launcher sends it gibberish.
same system , same launcher, same issue here, but other launchers do not work as well, dns server doesn't respond. I have reported this issue
I forgot to add, If you want to play minecraft right now, download Polymc from your software manager, it works there and you can log in fine and play the game, official one is simply broken.
Yep, PolyMC works. Thanks!
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.