MBP 2018 - Removing External Display won't switch to internal

[Trik]

I have been using the new MBP 15" 2018 with a Thunderbolt 3 Dock (that worked great with the 2017 MBP) hooked up to two external monitors, when I leave to go to a meeting with my laptop, I pull the TB3 cable and when I get to my meeting, I open the lid, the TouchBar says "External Display: Extend / Mirror" buttons, but the internal display never turns on.

The computer is working, I can Alt+Tab and the Touch Bar changes to whatever app is active. I have tried Command + fn + F2 to have it detect displays, but nothing happens.

I then invoke a restart using Alfred to reboot the machine, which does solve the problem. Sometimes something hangs the reboot, which I can't see what it is, which makes me force restart via the power button.

Has anyone else seen this issue?

 

[Trik]

My current work around for anyone that has seen this issue:

Before leaving for a meeting, I open the lid and pull it out of clamshell mode. Then when the internal screen is on, I pull the TB3 plug, then close the laptop. That ensures the internal screen is working.

 

[Painter2002]

I am going to guess this is likely a graphical bug that Apple may fix with Mojave. I would report it to Apple Senior support so that you can have the issue logged and engineering can be made aware if it hasn't already been reported.

 

[matthewadams]

Open up console.app and go to /Library/Logs/DiagnosticReports and see if you find crashes relating to WindowServer or Kernel files ending with .gpuRestart at the time it happened. I've seen this with a Dock on my machine too.

 

[Trik]

Open up console.app and go to /Library/Logs/DiagnosticReports and see if you find crashes relating to WindowServer or Kernel files ending with .gpuRestart at the time it happened. I've seen this with a Dock on my machine too.

Happened again today, seems to be fairly consistent. I did update with the supplemental update when it came out, so that didn't fix this issue.

No crashes at all, I don't think it's "crashing" ... it just isn't moving to internal display.