Another annoying issue: if my screens go dark after the set time in power saving settings, when I wake them back up, the system behaves as if I had unplugged the adapter. It goes through the flashing blue cycle to get it back, and so all my windows that I had on the DL monitor are moved and I have to move them back. Very annoying.

gee4vee,

What product are you using? Which Mac model?
Logs collected just after sleep would help analysing this issue.

Thank you,
Carlo

I am using the StarTech USB32HDDVII with a MacBook Pro 15" Retina (the first one that came out last year, MacBookPro10,1):

http://www.amazon.com/dp/B008CXFMT6/..._M3T1_ST1_dp_1

I will try to get logs tomorrow.

Hi,

I'm using the latest drivers on a MBP Retina 15" with OS X 10.8.3 and I have this problems:

· Screen saver start to work randomly and when I log in
· Youtube videos blinks on the usb monitor


I tried to uninstall the drivers, delete the screensaver.plist and reinstall the drivers and the problem still there.

What can I do?, thanks.

Logs for my issues
 

Attached are the logs after reproducing both the screen saver kicking in and the display behaving as disconnected after waking from display sleep. Hope this helps.

I continue with problems, what can I do?, any answer from display link?.

Thanks.

Any update on this issue? Were my logs helpful? I have to uninstall the DisplayLink software every weekend because the screensaver will kick in during presentations and such at church. Then I reinstall it on Monday to use at work again. Very annoying.

I have flickering too with Safari (and using 10.8.3 and DisplayLink 2.0 drivers),

Problem fixed through restarting
 

So after a few weeks of uninstalling and reinstalling every weekend, the screen saver issue has disappeared. It no longer kicks in at logon and randomly while working. I'm not sure why it went away other than reinstalling every weekend. At some point it started working. So others who have seen this might want to try that.

I still get the problem where display sleep results in the OS thinking the device got disconnected.