DisplayLink Forum - 10.7.3 incompatibility?

DisplayLink Forum (https://displaylink.org/forum/index.php)

- Mac Software (https://displaylink.org/forum/forumdisplay.php?f=30)

- - 10.7.3 incompatibility? (https://displaylink.org/forum/showthread.php?t=1461)

As far as I see we do not only have an rotation issue in OS X 10.7.3

Since Update I get always get only a blue background without any Icons on all my monitors if the USB VGA-Adapter is connected. It makes no difference if I boot with connected Adapter or I connect the adapter after the system is running. All I found were these protocol entries:

Code:

Feb  2 15:36:19 LF-iMac DisplayLinkManager[1370]: SCNetworkReachabilityCreateWithAddress[Pair] called with invalid address family 1

Feb  2 15:36:19 LF-iMac com.displaylink.usbnivolistener[92]: terminate called throwing an exception

Feb  2 15:36:19 LF-iMac ReportCrash[1374]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.

Feb  2 15:36:24 LF-iMac DisplayLinkManager[1385]: SCNetworkReachabilityCreateWithAddress[Pair] called with invalid address family 1

Feb  2 15:36:24 LF-iMac com.displaylink.usbnivolistener[92]: terminate called throwing an exception

Feb  2 15:36:26 LF-iMac ReportCrash[1374]: Saved crash report for DisplayLinkManager[1370] version ??? (0.3) to /Library/Logs/DiagnosticReports/DisplayLinkManager_2012-02-02-153625_localhost.crash

Feb  2 15:36:26 LF-iMac ReportCrash[1374]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/DisplayLinkManager_2012-02-02-014601_localhost.crash

Feb  2 15:36:26 LF-iMac ReportCrash[1374]: Saved crash report for DisplayLinkManager[1385] version ??? (0.3) to /Library/Logs/DiagnosticReports/DisplayLinkManager_2012-02-02-153626_localhost.crash

Feb  2 15:36:26 LF-iMac ReportCrash[1374]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/DisplayLinkManager_2012-02-02-014602_localhost.crash

Feb  2 15:36:27 LF-iMac DisplayLinkManager[1392]: SCNetworkReachabilityCreateWithAddress[Pair] called with invalid address family 1

Feb  2 15:36:27 LF-iMac com.displaylink.usbnivolistener[92]: terminate called throwing an exception

Feb  2 15:36:27 LF-iMac ReportCrash[1374]: Saved crash report for DisplayLinkManager[1392] version ??? (0.3) to /Library/Logs/DiagnosticReports/DisplayLinkManager_2012-02-02-153627_localhost.crash

Feb  2 15:36:27 LF-iMac ReportCrash[1374]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/DisplayLinkManager_2012-02-02-014603_localhost.crash

Feb  2 15:36:28 LF-iMac DisplayLinkManager[1395]: SCNetworkReachabilityCreateWithAddress[Pair] called with invalid address family 1

Feb  2 15:36:28 LF-iMac com.displaylink.usbnivolistener[92]: terminate called throwing an exception

Feb  2 15:36:28 LF-iMac ReportCrash[1374]: Saved crash report for DisplayLinkManager[1395] version ??? (0.3) to /Library/Logs/DiagnosticReports/DisplayLinkManager_2012-02-02-153628_localhost.crash

Feb  2 15:36:28 LF-iMac ReportCrash[1374]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/DisplayLinkManager_2012-02-02-014604_localhost.crash

Feb  2 15:36:29 LF-iMac DisplayLinkManager[1398]: SCNetworkReachabilityCreateWithAddress[Pair] called with invalid address family 1

Feb  2 15:36:29 LF-iMac com.displaylink.usbnivolistener[92]: terminate called throwing an exception

Feb  2 15:36:30 LF-iMac ReportCrash[1374]: Saved crash report for DisplayLinkManager[1398] version ??? (0.3) to /Library/Logs/DiagnosticReports/DisplayLinkManager_2012-02-02-153630_localhost.crash

Feb  2 15:36:30 LF-iMac ReportCrash[1374]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/DisplayLinkManager_2012-02-02-014605_localhost.crash

Feb  2 15:36:30 LF-iMac DisplayLinkManager[1401]: SCNetworkReachabilityCreateWithAddress[Pair] called with invalid address family 1

Feb  2 15:36:30 LF-iMac com.displaylink.usbnivolistener[92]: terminate called throwing an exception

Regards Lutz

Quote:

Originally Posted by lfalkenburg (Post 5645)

Thanks Lutz for your report. The entries are related to a crash of the DisplayLinkManager process. We are able to reproduce this issue, but the problem seems somehow related to the rotated modes. Do you remember if you were using a rotated mode before upgrading to 10.7.3? If you set a rotated mode before upgrading, the OS tries to apply the same setting any time you connect the DisplayLink adapter, causing the issue. Thanks

Quote:

Originally Posted by ChristianP (Post 5646)

Ah, I see. I have a HP Pivot Display (2 of them but one connected using your Adapter). Usually the rotation change automatically if I tilt my display, so, yes, I think I am using rotation. =) Thats probably why I still got the issue after deleting the display setting because the Display was still tilted. So I will wait till you fix the driver - is there any eta?

Regards Lutz

Quote:

Originally Posted by ChristianP (Post 5643)

Thanks for your reports.
Are you using the DisplayLink screen in a rotated mode? In case, could you please try this:
Boot without the DisplayLink adapter connected then run in a terminal:

sudo rm -f /Library/Preferences/com.apple.window*

rm -f /Users/"USERNAME"/Library/Preferences/ByHost/com.apple.window*

This should reset your display settings.
Reconnect the DisplayLink adapter and check if the connected display is working correctly.

We are working on trying to solve the rotated mode issue.

Thanks for your rapid response to this issue Christian. However, deleting the plists doesn't work for me on my monitor at work. I can't get to the preferences to reset the rotation, because I get blue screens on my working displays.

Is there another rotation setting that gets cached somewhere? It worked on my other monitor at home, but that was running a higher resolution with a different brand display link adapter. The one that's failing is the encore electronics brand model ENMUV rev 2.

Attaching the output of the "display link information" software report.

Same issue PLUS Dock CPU% high

Hi everyone. I'm having the same issue. Two display link adapters in portrait mode. Neither work when rotated. They do come on when in "standard" orientation, however, I'm also seeing my Dock use 100% CPU when I have the displaylink adapters plugged in. I have repeatedly force quit the Dock from Activity Monitor and it immediately respawns at the high usage rate until I unplug the display link adapter and force quit it again.

It is very noticeable for me as I have a 13" MBP and the fan gets really loud when the CPU is under load.

I'm curious as to why I can't seem to find any info regarding the 10.7.3 update on the Mac page on the DisplayLink website. Shame on me for not holding off on the update I suppose but I would think the DisplayLink folks would be using the developer releases to test the software and could post notices like: "Current users using DisplayLink software on 10.7.2 on rotated monitors may want to hold off on the 10.7.3 update until we release a new driver".

My current setup doesn't have space for landscaped monitors so right now my extra two 20" along with their display link adapters are of no use.

I would appreciate an update on the timeline of the anticipated fix please.

Quote:

Originally Posted by ChristianP (Post 5643)

Yes my display was rotated no this did not fix my issue, I added in the user name . Am I not supposed to use the asterisk?

Would love to have my third monitor back.

Quote:

Originally Posted by philip (Post 5650)

Yes my display was rotated no this did not fix my issue, I added in the user name . Am I not supposed to use the asterisk?

Would love to have my third monitor back.

Just finished installing 10.7.3 and immediately after rebooting i started having the exact same issue, rotated 3rd display, even after trying the suggested commands on Terminal it was still exactly the same.

Edit: forgot to give some info, 3rd screen rotated on a MacBook Pro (Early 2011).

just here to be counted...

same problem with 180° rotated 3rd display on 27" iMac (Mid 2010).

Count me too - 27" iMac mid 2011

same here, rotated display - I can see the displaylink process dying, respawning and triggering crash reporting.