For a few days now the launcher has been asking me to enter my password every time I open it, even though the "remember me" box is checked.
I did a clean install of the launcher to test but the problem persists.
Looking at the files and logs, it seems to be a token problem: launcher_accounts.json has an empty "AccessToken".
Linked issues
is cloned by 1
is duplicated by 21
MC-240255
Remember my login on this computer
Resolved
MC-241358
Must re-log in every time i restart pc
Resolved
MCL-18997
Logged out after restarting launcher
Resolved
MCL-19038
Launcher Logs Me Out Every Time I Close It
Resolved
MCL-19084
MC Java Launcher - login not persistent
Resolved
MCL-19257
Launcher logs out account even tho the remember me box is ticked
Resolved
MCL-19527
Launcher forget password all the time
Resolved
MCL-19598
Microsoft Login isn't kept logged-in
Resolved
MCL-19675
AUR Version of the linux minecraft launcher logs the user out after closing the launcher window
Resolved
MCL-19772
Remember account on Linux
Resolved
MCL-19781
Secure Token Storage Failure on Linux
Resolved
MCL-19899
Oh no! Something went wrong and you will not be logged in automatically next session.
Resolved
MCL-20329
Secure Token Storage Failure on Linux Debian GNU/Linux (Chrome OS)
Resolved
MCL-20679
oh no! Something went wrong, and you will not be logged in automatically next session
Resolved
MCL-21022
Launcher doesn't remember Microsoft login on Ubuntu 20.04
Resolved
MCL-21045
Microsoft account session error Linux
Resolved
MCL-21146
Launcher keeps logging me out of my Microsoft account on Ubuntu
Resolved
MCL-21160
When unlocking gnome-keyring with the launcher, the login isn't restored and need to re-enter credentials
Resolved
MCL-21202
Not having GNOME keyring running when starting the launcher invalidates the tokens it stores, causing an error
Resolved
MCL-22049
(Linux) Error: Something went wrong, and you will not be logged in automatically next session
Resolved
MCL-24621
Account isn't remembered after closing Minecraft on Linux
Resolved
Attachments
Comments 41
I am not sure if it is a duplicate since it happens every time I open the launcher, not just every time the computer is restarted.
For MCL-18331, the token should be stored if they are still logged in after closing the game. In this case, the AccessToken field remains empty. (Again, I don't know if it's a token problem or if it's the result of something else.)
The mods can fix as needed. The other duplicate MCL-18932 has that issue. Its good to somehow group similar issues.
I have the same issue, launcher installed from the AUR and same failure to get clientToken in the log. Account type is Mojang and Java is openjdk 16.0.1 2021-04-20. How do I close MCL-18997?
When the launcher is opened and I log in the accessToken key+value pair in launcher_accounts.json is added for my account but it is empty.
Could this be related to the client token being at the key mojangClientToken instead of clientToken in launcher_accounts.json?
@ThatOneLukas That might be possible because of the ongoing migration to MS accounts and the fact that the Linux launcher is slightly outdated compared to Windows :
Windows : Launcher : 2.2.3555 / Bootstrap : 1000 / UI : 7412
Linux (AUR) : Launcher : 2.2.3554 / Bootstrap : 928 / UI : 7412
(I also still use a Mojang account.)
Actually, I have no problem to stay logged in under Windows. Maybe this key has been renamed in the lastest version of the launcher but not in the current Linux version ?
@Inky19 If I rename the key to `clientToken` it changes back to `mojangClientToken`. Interesting thing is that the client token is required for authentication/getting access token (I can still join servers). I have a newly bought (Microsoft) account in the launcher but I have to log in to that too. (Edit: Ugh backticks don't work for inline code)
@ThatOneLukas I aslo tried to rename the key but to no avail.
However, launcher_profiles.json does have a clientToken key which in my case is also empty.
I checked on Windows and it seems that this key is supposed to have the same value as mojangClientToken in launcher_accounts.json.
I copied the value but it didn't solve the problem.
Launcher_log.txt doesn't contain the line "LauncherConfiguration.cpp(113)] Failed to get clientToken from configuration" anymore but I'm not sure if this is really a good indicator since any other value in clientToken will also remove that warning.
Experiencing the same issue from arch linux / launcher 2.2.3554 / openjdk 1.8.0_292 / installed from aur / mojang account
Hi,
i have the same issue in linux open suse leap 15.1 in two diferent machines whith linux when i close the launcher in version 1.17.1 it does not keep the password.
Before upgrading to 1.17.1 it was working fine.
But in windows 10 it keeps the password whith 1.17.1.
Minecraft: Java Edition
Linux minecraft launcher 1.17.1 does not keep password after closing launcher
This seems to happen every time I log in to the launcher on another OS. Very annoying on a dual boot setup...
I've got the same issue on Ubuntu 20.04 with launcher version 2.2.3963
The access token seems to not be saved
If some people under linux can delete their ~/.minecraft/launcher_accounts.json and log again and check if your account profile field accessToken in ~/.minecraft/launcher_accounts.json is populated, to check if that's the same issue.
Same issue here on Arch. Very inconvenient, especially for mod development.
@Milas Robin
I already tried to delete this file and even to make a clean installation of the launcher but to no avail : the file is recreated but still with an empty accessToken in launcher_accounts.json, even now with version 2.2.3963.
Issue still persists on launcher version 2.2.3963.
HI all,
I have the same issue in two diferent PC whith linux.
Under windows is working.
Linux UBUNTO and SUSE.
Any help on this issue??
Many thanks.
Also seeing this on 2.2.3963, Ubuntu 20.04.
This issue becomes even more pronounced once migrated to a Microsoft account, since logging in is much slower through the MS SSO system which requires clicking through all the popups.
Not sure if this helps, but on launcher version 2.2.3963 installed on Arch via the AUR, I only started experiencing this problem after migrating my account from mojang to microsoft.
I have the same problem on launcher version 2.2.3963. Manjaro linux from the package manager. I migrated from Mojang account to a Microsoft account and now I have to log in every time I open the launcher. Very inconvenient. I don't even see an option to save my login session. 😞
I found the solution. You need to install GNOME Keyring.
I recommend to follow the Arch Wiki: https://wiki.archlinux.org/title/GNOME/Keyring
Although it seems like you can skip this step even if you don't use the desktop environments listed there: https://wiki.archlinux.org/title/GNOME/Keyring#--start_step
@Patrick Zwick
This is more of a workaround than a solution. Gnome keyring allows you to auto-login but it doesn't seem to solve the token problem.
The launcher doesn't normally require Gnome keyring since it uses a token based system on all platforms. To me this is still a bug that was probably introduced with version 2.2.3554 (the dates seem to match).
Very similar situation to Jeff Derksen. Running arch linux using the latest minecraft-launcher package on the AUR. Didn't have the issue before migrating minecraft to use my microsoft account. This issue is not present on windows for me
Without the solution/workaround I mentioned earlier, the issue also occurs with a normal Mojang account.
I am having exactly the same problem. Following a new install of Linux I now have the problem of consistent logins needed.
Additionally I also have problem that following the authentication Minecraft starts but only in demo mode!
Distributor ID: Neon
Description: KDE neon User Edition 5.22
Release: 20.04
Codename: focal
WORKAROUND: installing gnome-keyring does indeed solve this problem. Rather annoying for a KDE user!
@Kevin Colyer
I guess KDE Wallet will also work but I am not sure. You can try it out: https://wiki.archlinux.org/title/KDE_Wallet
Installing gnome-keyring did not solve the problem for me. I'm on manjaro xfce, all software is up to date.
Did you also follow the other steps in the Arch Wiki like adding the PAM module?
Hi Patrick,
Yes I followed all the instructions. I added the lines to /etc/pam.d/login, I added the lines to ~/.bash_profile, and followed the instructions in the "Xfce only" section which included checking the "Launch GNOME services on startup" box
On my computer (Ubuntu 20.10) it only works if I unlock the keyring beforehand. If I unlock the keyring beforehand (by using a different application that uses the keyring) it'll automatically log me in upon opening the launcher. This could explain why installing gnome-keyring worked for some people but not for others; it may be unlocked after trying if the installation worked, but be locked again after a reboot.
If I don't unlock the keyring beforehand, it won't ask me to unlock my keyring at all. It just says I'm not logged in and shows the account selection screen. When I log in, it then asks me to unlock the keyring (presumably so that it could store the log-in token).
So it seems that whatever requests the log-in token at start-up doesn't properly cause the password screen to appear that unlocks the keyring.
Workaround: Unlock the keyring with a different application first, then start the Minecraft launcher.
Went into the .minecraft folder. Changed the properties for a number of files. Made so that they weren't read only. Fixed it for me.
Not sure what file did it be these are the ones i changed.
(launcher_profiles.json.tmp ; launcher_profiles.json ; launcher_accounts.json ; launcher_settings.json.tmp ; launcher_log.txt ; options.txt ; optionsof.txt)
I changed the last two because options weren't being changed in game and then saved.
Unlocking the default keyring before opening the launcher works for me! I installed seahorse to manage the keyrings, and use it to unlock the default keyring before opening the launcher. The launcher now logs in without asking for my password.
It is still strange that Steam and all other game launchers I use will remember my login without having to unlock the keyring.
The launcher is using the Freedesktop.org secrets service integration, which is a D-bus protocol that allows applications to communicate with password managers. Applications that implement this protocol include gnome-keyring, seahorse, kwallet and keepassxc.
I personally use keepassxc, which required me to install it through the PPA (the snap package does not work due to sandboxing). Enable secret service integration in Tools > Settings. Create and configure a group where the secrets can be stored. Once that is done, open the launcher and log in as usual. You should see 6 or 7 new keys being added for every account you use to login.
Once you've set this up you can log-in or switch accounts without providing a username or password and without any popups, as long as you have your password manager/keyring unlocked.
So basically the issue isn't so much that the launcher does not remember log in information, because it does as long as the Freedesktop.org secrets service is available, but that when it is not available, there is no feedback to the user that log in information could not be remembered due to this service being unavailable.
There is this help page now which should hopefully offer some assistance: Secure Token Storage Failure on Linux – Home (minecraft.net)
@Donuts1000 Thank you! Got it working by installing `pass` and `pass-secret` (AUR) as I think `gnome-keyring` is bloat in my opinion
Could an option be added to store the token in a separate way?
How about for the windows users? I have the same problem but on windows and your solutions are all for Linux
@Ashenguard the environment specified on this ticket is Linux (and it's been resolved). Open a new ticket if you have a similar issue on windows (you can mention this ticket, MCL-18924, for context).
Ashenguard: You can also try going in the Launcher to Settings / Accounts / Advanced Settings and clicking the "clean up cached account tokens" button - that might help on windows
But I agree logging a new bug w/your issue on Windows & launcher log files attached would help us figured out why your issue is happening.
For those using flatpak, https://github.com/flathub/com.mojang.Minecraft/issues/116#issue-1090301231
why do they mark these as resolved with so many people still having the issue?
Hello, I am here from Minecraft Community Support official discord server, I was recommended to comment here since I am also having the same problem with my Minecraft launcher and my problem begun this week.