MCL-16112Launcher freezes when attempting to launch game within a directory it does not have access to
The bug
Upon attempting to launch an installation with its directory set to a directory that the user does not have access to, the launcher silently fails to launch the game. By this, I mean that no error message is presented. The launcher doesn't even seem to realize that it has failed to launch the installation, as when trying to open another installation, the game says 'Already joined the game as this user' and presents users with the option to cancel the launch of the new installation. This proves that the launcher thinks that it has succeeded in launching the other installation.
Attempting to launch another installation in a valid directory and selecting 'Start anyway' when presented with the warning message does not do anything, as the Launcher is still trying to launch the game in the private directory.
Trying to quit the program by using the Command+Q shortcut or from the menu bar freezes the program, and the Force Quit menu must be utilized to recover.
How to reproduce
- Run the following commands in Terminal:
cd ~/Desktop mkdir TestFolder chmod 000 TestFolder
- Open the Minecraft Launcher -> Installations -> New...
- Set the game directory to the folder TestPrivate (that you have just created) and create the installation
- Navigate to the Play tab, and select the installation you have just created
- Click 'Play'
Observe the failure
Additional information
This was tested on four different operating systems:
- OS X Yosemite 10.10.5
- macOS High Sierra 10.13.6
- macOS Big Sur 11.0
- macOS Big Sur 11.1
A video of this issue occurring can be found here.
Environment
macOS
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
Created Issue:
Launcher silently fails to launch game when attempting to launch an installation within a directory that you do not have access to
The bug
Upon attempting to launch an installation with its directory set to a directory that the user does not have access to, the launcher silently fails to launch the game. By this, I mean that no error message is presented. The launcher doesn't even seem to realize that it has failed to launch the installation, as when trying to open another installation, the game says 'Already joined the game as this user' and presents users with the option to cancel the launch of the new installation. This proves that the launcher thinks that it has succeeded in launching the other installation.
Trying to quit the program by using the Command+Q shortcut or from the menu bar freezes the program, and the Force Quit menu must be utilized to recover.
How to reproduce
- Run the following commands in Terminal:
cd ~/Desktop mkdir TestFolder chmod 000 TestFolder
- Open the Minecraft Launcher -> Installations -> New...
- Set the game directory to the folder TestPrivate (that you have just created) and create the installation
- Navigate to the Play tab, and select the installation you have just created
- Click 'Play'
Additional information
This was tested on three different operating systems:
- OS X Yosemite 10.10.5
- macOS High Sierra 10.13.6
- macOS Big Sur 11.0
I have set the environment to 'macOS' because I have not tested/do not know how to test on another OS.
A video of this issue occurring can be found here.
Environment
macOS
The bug
Upon attempting to launch an installation with its directory set to a directory that the user does not have access to, the launcher silently fails to launch the game. By this, I mean that no error message is presented. The launcher doesn't even seem to realize that it has failed to launch the installation, as when trying to open another installation, the game says 'Already joined the game as this user' and presents users with the option to cancel the launch of the new installation. This proves that the launcher thinks that it has succeeded in launching the other installation.
Trying to quit the program by using the Command+Q shortcut or from the menu bar freezes the program, andtheForce Quit menu must be utilized to recover.How to reproduce
- Run the following commands in Terminal:
cd ~/Desktop mkdir TestFolder chmod 000 TestFolder
- Open the Minecraft Launcher -> Installations -> New...
- Set the game directory to the folder TestPrivate (that you have just created) and create the installation
- Navigate to the Play tab, and select the installation you have just created
- Click 'Play'
Additional information
This was tested on three different operating systems:
- OS X Yosemite 10.10.5
- macOS High Sierra 10.13.6
- macOS Big Sur 11.0
I have set the environment to 'macOS' because I have not tested/do not know how to test on another OS.
A video of this issue occurring can be found here.
The bug
Upon attempting to launch an installation with its directory set to a directory that the user does not have access to, the launcher silently fails to launch the game. By this, I mean that no error message is presented. The launcher doesn't even seem to realize that it has failed to launch the installation, as when trying to open another installation, the game says 'Already joined the game as this user' and presents users with the option to cancel the launch of the new installation. This proves that the launcher thinks that it has succeeded in launching the other installation.
Attempting to launch another installation in a valid directory and selecting 'Start anyway' when presented with the warning message does not do anything, as the Launcher is still trying to launch the game in the private directory.
Trying to quit the program by using the Command+Q shortcut or from the menu bar freezes the program, and the Force Quit menu must be utilized to recover.
How to reproduce
- Run the following commands in Terminal:
cd ~/Desktop mkdir TestFolder chmod 000 TestFolder
- Open the Minecraft Launcher -> Installations -> New...
- Set the game directory to the folder TestPrivate (that you have just created) and create the installation
- Navigate to the Play tab, and select the installation you have just created
- Click 'Play'
Additional information
This was tested on three different operating systems:
- OS X Yosemite 10.10.5
- macOS High Sierra 10.13.6
- macOS Big Sur 11.0
I have set the environment to 'macOS' because I have not tested/do not know how to test on another OS.
A video of this issue occurring can be found here.
The bug
Upon attempting to launch an installation with its directory set to a directory that the user does not have access to, the launcher silently fails to launch the game. By this, I mean that no error message is presented. The launcher doesn't even seem to realize that it has failed to launch the installation, as when trying to open another installation, the game says 'Already joined the game as this user' and presents users with the option to cancel the launch of the new installation. This proves that the launcher thinks that it has succeeded in launching the other installation.
Attempting to launch another installation in a valid directory and selecting 'Start anyway' when presented with the warning message does not do anything, as the Launcher is still trying to launch the game in the private directory.
Trying to quit the program by using the Command+Q shortcut or from the menu bar freezes the program, and the Force Quit menu must be utilized to recover.
How to reproduce
- Run the following commands in Terminal:
cd ~/Desktop mkdir TestFolder chmod 000 TestFolder
- Open the Minecraft Launcher -> Installations -> New...
- Set the game directory to the folder TestPrivate (that you have just created) and create the installation
- Navigate to the Play tab, and select the installation you have just created
- Click 'Play'
Additional information
This was tested on
threedifferent operating systems:
- OS X Yosemite 10.10.5
- macOS High Sierra 10.13.6
- macOS Big Sur 11.0
I have set the environment to 'macOS' because I have not tested/do not know how to test on another OS.
A video of this issue occurring can be found here.
The bug
Upon attempting to launch an installation with its directory set to a directory that the user does not have access to, the launcher silently fails to launch the game. By this, I mean that no error message is presented. The launcher doesn't even seem to realize that it has failed to launch the installation, as when trying to open another installation, the game says 'Already joined the game as this user' and presents users with the option to cancel the launch of the new installation. This proves that the launcher thinks that it has succeeded in launching the other installation.
Attempting to launch another installation in a valid directory and selecting 'Start anyway' when presented with the warning message does not do anything, as the Launcher is still trying to launch the game in the private directory.
Trying to quit the program by using the Command+Q shortcut or from the menu bar freezes the program, and the Force Quit menu must be utilized to recover.
How to reproduce
- Run the following commands in Terminal:
cd ~/Desktop mkdir TestFolder chmod 000 TestFolder
- Open the Minecraft Launcher -> Installations -> New...
- Set the game directory to the folder TestPrivate (that you have just created) and create the installation
- Navigate to the Play tab, and select the installation you have just created
- Click 'Play'
Additional information
This was tested on four different operating systems:
- OS X Yosemite 10.10.5
- macOS High Sierra 10.13.6
- macOS Big Sur 11.0
- macOS Big Sur 11.1
A video of this issue occurring can be found here.
Launchersilently fails to launch gamewhen attempting to launchan installationwithin a directory that you do not have access toLauncher freezing when attempting to launch game within a directory that you do not have access to
Launcher freezingwhen attempting to launch game within a directorythat you donot have access toLauncher freezes when attempting to launch game within a directory it does not have access to
![[MCQA] Zgajak](../../../data/avatars/users/10122.svg){kind=small}
On 2.2.741 (Linux) it simply exits with code 0, nothing is displayed in the terminal either, however the launcher_log correctly reports it as java.nio.file.AccessDeniedException. Was able to immediatly launch a different installation. It seems to only affect macOS.
Alright, thanks for testing!
I will say that the issue you're describing has happened in the past for me on macOS, so it could just be dependent on the launcher version/random chance? I'm not sure.
Hi there!
We could not reproduce this issue on our end with the Lates version of Launcher.
Could you answer few questions regarding this issue, it will help with the investigation:
This ticket will automatically reopen when you reply.
Hi! Nope, this is no longer an issue – it must have been fixed sometime recently. Thanks for checking!
Closing as cannot reproduce per reporters comment.