MCL-23087workDir terminal argument doesn't affect launcher_log location on linux
After installing the launcher on linux from the tarball under "other", I attempted to run it somewhere other than ".minecraft" using "--workDir"; this results in everything I knew to look for being placed in the expected directory, except the launcher log which was placed in ".minecraft"
Steps to Reproduce
1) Download the minecraft launcher as a tarball from the official minecraft website
2) Run the launcher from the terminal, passing it the workDir argument. For instance:
mkdir launchertest ./minecraft-launcher --workDir launchertest
Observed Results
The launcher's files are for the most part put into the correct folder which you just created. However, the "launcher_log.txt" file is always places in "~/.minecraft" no matter what you specify
Expected Results
The "launcher_log.txt" file would be placed alongside the other launcher files when using "--workDir".
Environment
Kubuntu 22.10, x86_64
Created Issue:
workDir terminal argument doesn't affect launcher_log location on linux
After installing the launcher on linux from the tarball under "other", I attempted to run it somewhere other than .minecraft using --workDir; this results in everything I knew to look for being placed in the expected directory, except the launcher log which was placed in .minecraft
Environment
Kubuntu 22.10, x86_64
After installing the launcher on linux from the tarball under "other", I attempted to run it somewhere other than ".minecraft" using "--workDir"; this results in everything I knew to look for being placed in the expected directory, except the launcher log which was placed in ".minecraft"
Steps to Reproduce
1) Download the minecraft launcher as a tarball from the official minecraft website
2) Run the launcher from the terminal, passing it the workDir argument. For instance:
mkdir launchertest ./minecraft-launcher --workDir launchertestObserved Results
The launcher's files are for the most part put into the correct folder which you just created. However, the "launcher_log.txt" file is always places in "~/.minecraft" no matter what you specify
Expected Results
The "launcher_log.txt" file would be placed alongside the other launcher files when using "--workDir".
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mojang] Donuts1000](../../../data/avatars/users/18949.svg){kind=small}
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Could you please provide more details or/and media files. As such we have no repro of this issue.
Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
Steps to Reproduce:
Observed Results:
(Briefly describe what happens)
Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
I've updated the issue including more in-depth steps to reproduce the problem.
Hi again!
Just a few questions:
Does this issue occur on every linux installation? (.deb/.arch)
Do you put .minecraft in custom location?
Is the launcher_log file is being created correctly upon booting the Launcher again?
This ticket will automatically reopen when you reply.
I have only observed this issue on Kubuntu (a deb installation) with the tarball containing the launcher. I have not tested it on any other installations. I am trying to use a custom .minecraft directory by setting the --workDir argument, which works, with the single exception of the launcher_log.txt file, which is placed in the "default" .minecraft location (~/.minecraft) no matter what I do. I can reboot the launcher as many times as I like, and it will never place the launcher_log in the proper location.
Hi. Sorry I was gone for such a long time, there is quate a lot that has happened recently.
1) Anyway, here is the thing. I am using arch linux. I installed the launcher from the repository, as I am recommended to do, which is the newest version. ~ AUR (with yay)
2) I tried with working with the directory, locking it into a specific directory, reinstalling, updating the system, but nothing works. I have a .minecraft directory in which I tried to put my installation, and I do have my Versions of minecraft installed there, so I do not have a problem with it being incorrectly installed, just the login process.
3) I have not toucher the log file at all. I checked the launcher settings file, but nothing that I changed worked, so I reset all the settings to the default ones. I will try your method later today, thank you for the suggestion.
Hi again!
Can you verify that this issue still occurs on the newest version of the Launcher?
There has been an update, and a new issue regarding launcher_log files has been found, and I wonder how it relates to this issue.
This ticket will automatically reopen when you reply.
I just tested this on the latest version, with a fresh install of the launcher; the bootstrap_log and launcher_log are both still created in the .minecraft directory instead of in the workDir directory.