Glyph Lefkowitz
- glyph
- glyph
- America/Los_Angeles
- Yes
- No
1 issues
Key
Summary
Status
Reporter
Assignee
Created
MCL-4038
Added Attachments:
![[Helper] pine1needle](../../../data/avatars/users/41329.png){kind=small}
I'm setting this report to community consensus because Glyph Lefkowitz said that they experienced the same issue in this comment from MCL-19830.
Confirmed unfixed in 1.6.1. I had a villager who only first spawned in 1.6.1, whose only trade offer was X'd out.
On
MCL-4038, I listed a workaround: delete ~/"Library/Application Support/Minecraft Launcher/" and the probability of a successful launch goes up a lot. (I'd also be happy to assist with any diagnostic info.)Also, unlike ~/"Library/Application Support/minecraft", that folder doesn't appear to have anything useful in it, so deleting it on every launch doesn't seem to lose anything interesting.
I have the same issue. Similarly, without copying over the application support directory from a different machine, none of these workarounds allow launching
@Yoshimasa Niwa this is interesting, thanks for the sleuthing! Would it be worth distributing a small app that automates these patches, until Microsoft gets around to releasing a working version? Having to re-download the app to get updates working is bad, especially since folks who haven't migrated from old Minecraft accounts are still totally locked out and don't seem to have any way to do a fresh download.
I am sort of struggling to understand the manifestation of this issue. Are there really only 17 people in the world who (A) have m1 macs, (B) play minecraft, and (C) can figure out how to log in to this bug tracker? Or is this affecting some smaller slice of the population? Yoshimasa's very thorough diagnostic description implies that this is in fact completely broken for everyone, but the traffic here seems surprisingly low for that fact.
Thanks for confirming that it's Monterey and not M1, I thought it was working on my Intel machine before I migrated, but I guess Monterey hit around the same time.
Nothing to do for it except keep yammering away here in the hopes that Microsoft notices the activity and actually fixes the bug?
I realize the Minecraft team is probably frantically patching everything for the log4j issue right now, but that is case in point about why this issue, which prevents launcher updates, needs to get addressed ASAP.
Sorry, I didn’t mean to suggest that the log4j issue specifically involves this bug, just that it highlights the need to be able to update conveniently and quickly to avoid large numbers of users being stuck on an old version of something. The “something” in this case is the launcher itself, which has a very different attack surface than the game itself, but given that its job is to download and execute code, arguably a somewhat more concerning attack surface in general.
Although, now that I think about it, this probably does worsen the log4j scenario just a bit, although not for anyone reading this comment. Users who haven’t come across this exact bug might launch minecraft directly from the jar file as long as the launcher appears to be completely broken (it’s not obvious how to start it without updating, after all), skipping any automatic upgrades and sticking with old, vulnerable versions of the jar files in question.
In any case this really needs to be fixed soon.
When I download a fresh copy of the launcher and start it with `–skipUpdate`, it immediately tells me that there's a new version available, which suggests to me that there is actually a newer version of the mac launcher that isn't available as an omnibus download. Does anyone have a VM from an older version of macOS that they can patch and copy over the patched version from? I'm wondering if this has been fixed under some other topic but hasn't been properly released.
I was very excited to see the notification that it was fixed! So I went to the website to download a fresh installer, and…
However, after right-click->"Open"ing it to work around the GateKeeper restriction… it does in fact launch now so it seems like this issue is addressed.