Displaylink ceases to work in 10.13.4

[toastido]

Originally Posted by Carlo

Thank you toastido,

Well this is all surprising it would definitely help to see your debug info in the working case. Can you please follow the instructions in https://support.displaylink.com/know...rticles/755301 and mention that the logs are for me?

Do you see any corruption on the internal screen or the screen you have connected to the built-in external port on your MBP?

Many thanks,
Carlo

Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Attached is the output from the information tool you requested as well.

[Carlo]

Originally Posted by toastido

Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Attached is the output from the information tool you requested as well.

Thank you we're looking at the logs, we'll have a new series of experiments to run.

Cheers,
Carlo

[tpurdue]

Originally Posted by toastido

Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Attached is the output from the information tool you requested as well.

This worked for me as well. Second screen up and running. There is definitely lag and some rendering issues (white boxes over menu items, etc.) but it's mostly useful.

[dizash]

[QUOTE=toastido;85374]Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Hi,
Can you please specify what exactly to enter in the commond line? Is it only the 2nd two lines each beginning with the $ sign and if so, it appears there are more brackets in your summary than I'm used to working with in Terminal.
Thanks very much.

[toastido]

[QUOTE=dizash;85386]

Originally Posted by toastido

Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Hi,
Can you please specify what exactly to enter in the commond line? Is it only the 2nd two lines each beginning with the $ sign and if so, it appears there are more brackets in your summary than I'm used to working with in Terminal.
Thanks very much.

Oh, sure. I'm using ZSH with some customizations, so that's why my command line looks like that. the actual command is:
launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist

[dizash]

[QUOTE=toastido;85387]

Originally Posted by dizash

Oh, sure. I'm using ZSH with some customizations, so that's why my command line looks like that. the actual command is:
launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist

Thanks Toastido - especially for the quick reply. Much appreciated!!!!

UPDATE: Immediately after utilizing the command, my DL Connected Monitor also SPRANG TO LIFE:

THANKS AGAIN TOASTIDO - this is huge for me!!!

[toastido]

[QUOTE=dizash;85388]

Originally Posted by toastido

Thanks Toastido - especially for the quick reply. Much appreciated!!!!

UPDATE: Immediately after utilizing the command, my DL Connected Monitor also SPRANG TO LIFE:

THANKS AGAIN TOASTIDO - this is huge for me!!!

NP. This will at least work until DisplayLink gets a real fix in place. It's more of a bandaid since it's a little laggy and whatnot, but at least it's a workaround for the time being.

[Alanant]

This workaround doesn't work for me. Maybe it's hardware specific? I'm using an older Kensington SD3500v I believe. I can confirm the model if display link need it.

[aehsmu]

Originally Posted by Alanant

This workaround doesn't work for me. Maybe it's hardware specific? I'm using an older Kensington SD3500v I believe. I can confirm the model if display link need it.

Same here. The monitor indicates it's receiving a signal, but the screen stays black.
--
Eric H.
--
NEC AccuSync LCD 72VX monitor

[dizash]

Originally Posted by Alanant

This workaround doesn't work for me. Maybe it's hardware specific? I'm using an older Kensington SD3500v I believe. I can confirm the model if display link need it.

+1

Originally Posted by slvrscoobie

Thanks for keeping us updated! obviously 13.4 seems to have a big change in how it handles the eGPU. Any idea why this change was made or what benefits it might have long term?

+1. The updates really are appreciated and says a lot about you guys. Thanks!