Phantom 3rd Screen
 

DisplayLink,

I'm carrying over this issue since it was closed in the other thread.

Has there been any resolution to this issue yet?

Please advise,

Thanks

Unfortunately this issue has not been solved yet. Anyway we will try to solve it, but at the moment I can't estimate when it will be ready.

Come on, seriously? This has been a problem for months, and you reported months ago that you were able to reproduce it.

What do we have to do to get some engineering time dedicated to this? It’s a showstopping bug for those of us experiencing it. I’ve purchased three DisplayLink adapters over the years; it would be great to get support on this issue.

I'd also like to note that some support on this issue would be great. We have users who won't even use their dock anymore because of the phantom screen. It seems to only happen after the computer goes to sleep. A restart will generally correct the issue but that's not really something that anyone would want to do throughout the day.

Still present in 10.7.3
 

This bug is still present in the just-released Mac OS X 10.7.3. Unfortunately.

Any update?

Henge Dock Phantom 3rd Screen
 

Second that question....

I saw a new update just released. Does the new update resolve the phantom 3rd screen ChristianP? :confused:

I am having this issue as well
 

Right now, I have one monitor connected via DisplayPort, another connected with DisplayLink, and my MacBook Air is closed. I can see that the MBA's screen is active because the Apple logo is glowing, and I have taken a screen capture of the System Preferences as well which shows three active screens.

Pressing "Detect Displays" doesn't help.

This is clearly an issue with the DisplayLink software, because this behavior does not occur if the drivers are uninstalled.

I'd be happy to help experiment on ways to fix the issue. I am fairly comfortable with the terminal. I've been wondering if there is a way to force the system to reevaluate which displays are active more thoroughly than the "Detect Displays" method does, but haven't found any success.

I'm afraid I don't have any good news for this clamshell mode issue. We're not really sure this is our issue since we can't directly modify the behaviour of the internal screens, but it may be a side effect of something we can avoid doing.

We have one possible lead and most importantly looking into this area as a whole so the hope is to come up at least with a convenient workaround for you.

As usual I prefer not to give time scales: you never know when the OS vendor decides to throw a spanner in our schedules.

Cheers
Carlo

I would hope the OS vendor we're talking about would be interested in helping you solve this problem. :confused:

I wish we could dynamically load and unload the drivers in the meantime. Then at least I could script it.

Thanks for your efforts guys. It's much appreciated. Please keep us updated more frequently?