View Single Post
Old 01-11-2017, 02:33 PM   #23
Delco24
Junior Member
 
Join Date: Jan 2017
Posts: 2
Default

Quote:
Originally Posted by Carlo View Post
Thank you for the information. It is really useful indeed.

We found what the trigger is (thanks to Christian from the team here, good he's around this week!).
To see all these issues you have to disable "Displays have separate Spaces" in the Mission Control system preference.

In all cases it looks like the contents we receive are corrupted but I can confirm Phrogg's finding that taking a screen shot forces the rendering of some contents so those corruptions won't be captured.
A quick test in 10.11 shows this is another regression in Sierra, unsure if something introduced in a minor update. We'll open a bug with Apple immediately.

As for the other defects already fixed in 10.12.1 and 10.12.2, the priority of this issue can be raised by opening more bugs with Apple at bugreporter.apple.com
We'd be grateful if you could open bugs there as well.

In the meantime you may want to enable separate spaces, currently the default setting in macOS. You won't be able to show windows across displays but there are quite a few advantages.

Thank you again for the feedback, keep it coming!

Best regards,
Carlo
This started for me after I upgraded from 10.12.1 to 10.12.2. Checking "Displays have separate spaces" resolves the issue.

I also noticed it happened regardless of whether I was using the current stable DisplayLink driver or the beta driver.

Looks like this is a regression in 10.12.2.
Delco24 is offline   Reply With Quote