Inky19
- Inky19
- JIRAUSER668536
- Europe/Stockholm
- Yes
- No
MCL-18924
Changed Environment:
OS: Manjaro Linux
Default java environment: java-16-openjdk
The launcher is the official version from the AUR.
Account type : Mojang
Added Affects Versions: 2.2.3963 (Linux)
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.)@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 ?
@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.
@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.
@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).