Fingers crossed!!!I spoke with an Apple support specialist. He acknowledged that this is a known bug and thinks it should get fixed in an upcoming release, though he couldn't say for sure when.
Fingers crossed!!!I spoke with an Apple support specialist. He acknowledged that this is a known bug and thinks it should get fixed in an upcoming release, though he couldn't say for sure when.
This bug [problem] has been around at least since my 2010 Mac Pro was new. Don't expect it to be fixed by Apple now.I spoke with an Apple support specialist. He acknowledged that this is a known bug and thinks it should get fixed in an upcoming release, though he couldn't say for sure when.
I saw your other thread about this issue on the Mac Studio. Was hoping it wouldn't be present on that system, but oh well. I hear you about this issue being around since 2010, but it isn't and wasn't an issue on any prior Intel-base MBP I've owned, including my other 2019 MBP running the same version of Monterey as the MBP M1 Max I own. So...Apple's reintroduced the problem with the M1 line.This bug [problem] has been around at least since my 2010 Mac Pro was new. Don't expect it to be fixed by Apple now.
I'd love to have a fix since it's happening on my new Mac Studio (2 identical monitors that randomly swap as the main screen, and a 3rd different monitor).
Nope. Spoke too soon. Back to normal again now.I don't want to jinx this...
Has anyone else installed 12.4 Beta (21F5048e)?
I have had two solid days of no problems... including a couple of restarts, and many wakes from sleep...
Apple may have addressed this finally?
Any chance you can try with an iPad with sidecar?I don't want to jinx this...
Has anyone else installed 12.4 Beta (21F5048e)?
I have had two solid days of no problems... including a couple of restarts, and many wakes from sleep...
Apple may have addressed this finally?
Hi there! Well, I spoke too soon... the issue has returned for me again now, back to manually swapping my monitor arrangement every other time the Mac wakes from sleep etc.Any chance you can try with an iPad with sidecar?
Oh man I was hoping we'd have some luck! Sounds like it's time to leave Amphetamine working to avoid this...Hi there! Well, I spoke too soon... the issue has returned for me again now, back to manually swapping my monitor arrangement every other time the Mac wakes from sleep etc.
Sigh.
If you use different input types on identical monitors the problem will go away. For instance, if you are using DisplayPort inputs on 2 monitors change one to HDMI and the problem will go away.Hi there! Well, I spoke too soon... the issue has returned for me again now, back to manually swapping my monitor arrangement every other time the Mac wakes from sleep etc.
Sigh.
My displays will not run at full resolution or in HDR over HDMI 2.0, so not really a solution for me.If you use different input types on identical monitors the problem will go away. For instance, if you are using DisplayPort inputs on 2 monitors change one to HDMI and the problem will go away.
I already use Stay app and can confirm it does not remedy the issue of monitors switching. Try this:@lfshammu how does Stay solve this problem? Window position is unrelated to the problem of inconsistent display enumeration.
Unless you can confirm that Stay looks at the display serial numbers and actually patches macOS's braindead display enumeration, I'd consider this a red herring...
Thank you for the reply. I will try this combination as well and report back.I'll repeat what's working for me: Go to System Preferences > Mission Control > uncheck "Automatically rearrange Spaces based on most recent use." Five great days and counting of no display swaps, not once.
I tried that - no luck. Displays still swap often.I'll repeat what's working for me: Go to System Preferences > Mission Control > uncheck "Automatically rearrange Spaces based on most recent use." Five great days and counting of no display swaps, not once.
#!/bin/bash
IDS=$(displayplacer list | grep "id: " | cut -d ' ' -f 4 | while read -r PERSISTENT_ID CONTEXT_ID
do
echo $CONTEXT_ID
echo $PERSISTENT_ID
done)
FIRST_PERSISTENT_ID=$(echo $IDS | cut -d ' ' -f1)
SECOND_PERSISTENT_ID=$(echo $IDS | cut -d ' ' -f3)
FIRST_CONTEXT_ID=$(echo $IDS | cut -d ' ' -f2)
SECOND_CONTEXT_ID=$(echo $IDS | cut -d ' ' -f4)
displayplacer "id:$FIRST_PERSISTENT_ID res:1920x1080 scaling:off origin:(1920,0)" "id:$SECOND_PERSISTENT_ID res:1920x2160 scaling:off origin:(0,0)"
This is the option I used to fix this issue on both my Monterey MacBook Pros and it has worked great. Seems macOS treats monitors as "Spaces".I'll repeat what's working for me: Go to System Preferences > Mission Control > uncheck "Automatically rearrange Spaces based on most recent use." Five great days and counting of no display swaps, not once.
I spoke with an Apple support specialist. He acknowledged that this is a known bug and thinks it should get fixed in an upcoming release, though he couldn't say for sure when.
This is the option I used to fix this issue on both my Monterey MacBook Pros and it has worked great. Seems macOS treats monitors as "Spaces".
Partial "fix" so far:
Go to System Preferences > Mission Control > uncheck "Automatically rearrange Spaces based on most recent use"
For me this is working to some degree for about 5 days. Sometimes it works perfectly. And sometimes it doesn't. BUT, when it fails, all I have to do is unplug and replug the external monitor cable from the Mac. This is still annoying.. but much much less annoying then having to open display preferences and rearranging them again.
My set up:
Macbook Air M1
Multi port dongle plugged in
HDMI plugged into dongle goes to one external monitor.
Again, when the screens rearrange, I unplug the entire dongle from the Air, and plug it right back in. And that seems to be working.
Rant:
But I will add my gripe to the others'. It's infuriating that this is an issue that is not fixed. And it's not the first one with the M1. The indexing doesn't work right, the system sounds lag sometimes, and a host of other annoying things that should be BASIC, and ones that worked flawlessly on my 10yr old MBP.
I don't need 99% of the pointless bells and whistles. But I do want my brand new Apple computer to do the basics right.