Issue:
On Mac computer with multiple users, one user unable to launch Minecraft successfully since 1.19 update. Game crashes immediately when that user launches, with error code 1
Reproduction steps:
1) Log in as User 1
2) Open Minecraft launcher
3) Push "Play"
4) See game launches successfully
5) Log out User 1. Log in User 2.
6) Open Minecraft launcher
7) Push "Play"
8) See game crashes immediately with Error Code 1
Troubleshooting steps already tried without success/with continuation of issue as described above:
Uninstall Minecraft image, reboot, download dmg from website, reinstall Minecraft
Update OS version to macOS 11.6.7 2.3.228, uninstall, reboot, download dmg, uninstall, reinstall
Update Java version to latest release, uninstall, reboot, download dmg, uninstall, reinstall
Uninstall, reboot, download dmg, reinstall specifically as User 2
Notes:
Game worked correctly for both User 1 and User 2 before 1.19
With every uninstall/reboot/download/reinstall, I did manually update the permissions for the application and the package contents (including cascading to all inside package) so admin and all users can Read and Write.
Neither the launcher logs nor the Java logs have produced any content whatsoever; crash seems to occur before Java even starts
I have once managed to get an Apple crash report; I have attached that report here
Linked issues
Attachments
Comments 3
Thank you for your report!
We're resolving and linking this ticket forward as a duplicate of MCL-21799, as that ticket contains more detailed information and/or has already been triaged by Mojang.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
I was able to duplicate this issue on a different Mac computer, running MacOS 12.2.
Behavior is still exactly as described in original bug report.