Notification Thread for Carlo for when Mavericks and DisplayLink Play Nice

[JamesGuymer]

Hi James,

This is a follow-up regarding Bug ID# 15945748.

Engineering has determined that this is an issue for a third party to resolve.

Apple doesn't create those drivers, DisplayLink does, so not a lot we can do about it. Don't know what calls they're making that would behave differently.

If you have questions regarding the resolution of this issue, please update your bug report with them.

We are closing this report.

Please be sure to regularly check new Apple releases for any updates that might affect this issue.

Thank you for your assistance in helping us discover and isolate bugs within our products.

Best Regards,

Developer Bug Reporting Team
Apple Worldwide Developer Relations

************************************************** ********************************************
THE INFORMATION CONTAINED IN THIS MESSAGE IS UNDER NON-DISCLOSURE
************************************************** ********************************************
-------------------------------------------------------
Bug ID #: 15945748
Bug Title: Mavericks Not playing nice with Displaylink drivers
-------------------------------------------------------
<GMT30-Jan-2014 14:02:50GMT>
Summary:
Hi

I have an issue with mavericks and display link drivers, its a know issues apparently http://www.displaylink.com/support/ticket.php?id=354.

I was running 6 monitors off my mac book retina pro using 4 external graphic cards successfully until i upgraded to mavericks.

I can only get 3 running now, 2 of which are being run from the thunderbolt ports and 1 external card

Steps to Reproduce:
1) attach more than one external display link card and screen goes flickery and unusable

Expected Results:
6 monitors running in harmony

Actual Results:
d screen goes flickery and unusable

Version:
OS X 10.9.1 13B42

Notes:


Configuration:


Attachments:

[ehendrix]

Same answer I got from Apple about WindowServer crashing when doing "Show Desktop".
Yet, I have not seen the crashes anymore after updating to 10.9.1.

I think the problem here is that we do not know what DisplayLink uses from OSx. Hence our "bug reports" really are against the DisplayLink drivers. If instead the report would state more that by using this specific API within OSx this issue occurs then it would become more clear it is an issue in OSX.

[Carlo]

Hi,

Thank you for raising the issues. The answers you got are in line with the ones we got from the first level of support on most issues, which is disappointing of course but not unexpected. It's still useful to reiterate the importance of the issue, regardless of where the blame would lie: we'd love to have one or more fundamental bugs to fix to improve the user experience on Mavericks.

We take seriously our NDA with Apple and can't share details of our own communications with further levels of support.

So far it very much looks like 10.8: it took one year for exactly the same DisplayLink driver to go from unusable on 10.8.0 to a good user experience on 10.8.5.
Thank you for your help in trying to shorten that interval this time around.

Carlo