Two Identical Monitors Plugged in with USB-C

displaysleep-wakeusb

I have two identical Lenovo P24h-10 monitors plugged into my Macbook. Each one has it's own USB-C cord. I thought about using a single Display Port cord and then daisy-chaining them together, but each monitor has USB outlets that I'm using to connect my peripherals so I don't need a separate hub. I've noticed there is a 50% chance that the display arrangement will be flipped every time my computer wakes from sleep. I think this is because there is no way for my computer to differentiate between the two. Is there a way to set a name on my monitors?

In the Display Preferences, each monitor is listed as P24h-10 (1) and P24h-10 (2), and they can change.

This seems like a really silly problem to have. I'm hoping there is an easy fix, but I've been scouring the internet for weeks now looking for some help. Any thoughts?

Best Answer

I've experienced this as well, and there are a few fixes that I've found.

Solution One This fix involves involve running macros on startup. Here's a link to the "Keyboard Maestro" method which includes using a utility called displayplacer on github.

Solution Two It's possible this is related to spaces/mission control behavior. One easy thing I would suggest is going into System Preferences -> Mission Control and uncheck "Automatically rearrange Spaces based on most recent use," assuming that is checked. This may solve your problem, maybe not.

Screenshot of Mission Control Preferences

Solution 3 I'm a bit dubious about this one, but it's easy and worth a shot. Basically, you need to remove the Caches folder in your User Library folder. You can try to do this with finder, but I suggest opening terminal and entering

sudo rm -rf /Library/Caches/ColorSync
rm -rf ~/Library/Caches

And then restarting your computer. Please note that you may clear your user-specific caches with that second command, which include caches from other Applications and things like iCloud. These are caches, so you shouldn't experience any real data loss, but certainly be a bit cautious with this one.

I wish there was an easy fix. Hopefully the mission control solution works for you, but this seems like it's been a problem for several years.

Related Question