MCL-14046Launcher does not consistently censor folder paths in launcher_log.txt
The bug
Normally the launcher censors folder paths in the launcher_log.txt file by replacing them with "...".
However, for some logged messages this is not the case.
Affected log lines
The following are some (but probably not all) log lines where the folder paths are not censored, with #redacted# having been manually inserted:
[Info: 2022-04-24 22:14:47.7736703: LauncherAppBrowser.cpp(83)] Will launch a Chromium subprocess with command line string
[Info: 2022-04-24 22:17:16.3630746: GameCallbacks.cpp(177)] Launcher/launcher (main) Info Local file C:\Users\#redacted#\AppData\Roaming\.minecraft\assets\indexes\1.19.json is incomplete
[Info: 2022-04-24 22:17:16.5240165: GameCallbacks.cpp(177)] Launcher/launcher (main) Info Downloaded https://launchermeta.mojang.com/v1/packages/13dd8d9c2b9e49437718d9151754cf764febac62/1.19.json to C:\Users\#redacted#\AppData\Roaming\.minecraft\assets\indexes\1.19.json
[Info: 2022-04-24 22:20:17.0139615: ClientStarter.cpp(926)] Java argument:-Djava.library.path=C:\Users\#redacted#\AppData\Roaming\.minecraft\bin\7f1f-8476-54ea-0a04
[Info: 2022-04-24 22:20:17.0140487: ClientStarter.cpp(926)] Java argument:-cp [Info: 2022-04-24 22:20:17.0140820: ClientStarter.cpp(926)] Java argument:C:\Users\#redacted#\AppData\Roaming\.minecraft\libraries\com\mojang\logging\1.0.0\logging-1.0.0.jar;...
Created Issue:
Launcher does not consistently censor folder paths in launcher_log.txt
The bug
Normally the launcher censors folder paths in the launcher_log.txt file by replacing them with "...".
However, for some logged messages this is not the case.Affected log lines
The following are some (but probably not all) log lines where the folder paths are not censored:
The path here is not necessarily confidential, but it is censored by [Info: 2020-05-19 22:54:42.9669434: Process_Windows.cpp(33)] Creating process.
The bug
Normally the launcher censors folder paths in the launcher_log.txt file by replacing them with "...".
However, for some logged messages this is not the case.Affected log lines
The following are some (but probably not all) log lines where the folder paths are not censored:
The path here is not necessarily confidential, but it is censored by [Info: 2020-05-19 22:54:42.9669434: Process_Windows.cpp(33)] Creating process.
[Info: 2020-05-19 22:53:44.9267970: Common.cpp(36)]Game data directory:[Info: 2020-05-19 22:53:44.9268367: Common.cpp(37)] Launcherdir:[Info: 2020-05-19 22:53:45.0493580: ProfilesFileData.cpp(159)] Reading preferences on path:[Info: 2020-05-19 22:54:42.9663384: ClientStarter.cpp(811)] Java argument:The bug
Normally the launcher censors folder paths in the launcher_log.txt file by replacing them with "...".
However, for some logged messages this is not the case.Affected log lines
The following are some (but probably not all) log lines where the folder paths are not censored, with #redacted# having been manually inserted:
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
The bug
Normally the launcher censors folder paths in the launcher_log.txt file by replacing them with "...".
However, for some logged messages this is not the case.Affected log lines
The following are some (but probably not all) log lines where the folder paths are not censored, with #redacted# having been manually inserted:
![[MCQA] Zgajak](../../../data/avatars/users/10122.svg){kind=small}
I can't reproduce in version 2.2.11699 (for the most part). The paths mentioned in the description, except for the last bullet point, are censored in my launcher log. Are the rest still issues for you?
Hi there!
This ticket will automatically reopen when you reply.
Yes, I can still reproduce this in version 2.2.12145 of the Windows version of the launcher and have updated the report accordingly.
Hi there!
Does this issue still occur to you?
I cannot reproduce it.
In my launcher_log files, the paths are changed to '%USERPROFILE%\AppData'.
Maybe you could uninstall the Launcher, delete .minecraft folder (copy its content elswhere beforehand) and then install the Launcher again, maybe the files will update to what we see.
It looks like this is fixed; for me it also has replaced some paths with "<WORKDIR>" in the log file.
Will resolve as Cannot Reproduce because I don't know the exact fix version.