2.5 beta 2

[Carlo]

Hi All,

We have released today version 2.5 Beta 2. This version fixes critical issues in the beta 1 and is recommended to all El Capitan users. More information in the release note.

We'd like to hear your feedback!

A reminder: if you have downloaded the Beta 1 please uninstall it and delete the installation image. If you had device issues after using the beta 1 please contact us at http://support.displaylink.com

Best regards,
Carlo

[Junto026]

Hey all,

In case it helps someone, I use two StarTech USB32DVIPRO modules through a USB Hub. After upgrading to El Capitan, both units worked but not when plugged in through a hub.

I uninstalled my 2.4 driver, installed the 2.5 Beta 2 driver, and all works perfectly, save for a small issue I'll post on a separate thread. : )

[Superstar]

Mine still doesn't work. I can pretty much confirm that your beta 1 software broke the device permanently.

Just to be sure that the issue is not with El Capitan, I have connected it to a Windows PC and yeah it doesn't work. Its not even detected.

Going to return it for RMA.

Please do a QC before releasing a software to public! Beta is not an excuse to not perform QC.

[saudor]

PDF scrolling is a bit smoother and the app i use is less glitchy. It seems to allow me to select text without it all acting up. Best part of el cap is..there is no 1-2 second lag in Expose mode since the OS no longer blurs the background

I only use the DL display for displaying several PDF documents that hardly ever moves (aside from scrolling) so my use would be very light to begin with


EDIT: Background of the monitor connected to displayport still turns black when switching spaces. The actual displaylink monitor and the internal screen of the macbook still has its background. Also some windows when switching to a particular space become invisible (workaround is to enter expose again and everything comes back)

OS X 10.11.1 Beta 2

[Rymek]

Intalled beta2, no difference than to beta 1 and to 2.4. Still bad beformance in whole system after connecting the external usb. Starting to think it's device itself not the driver.

I've sent you debug report via PM Carlo. Take a look.

[Carlo]

Intalled beta2, no difference than to beta 1 and to 2.4. Still bad beformance in whole system after connecting the external usb. Starting to think it's device itself not the driver.

I've sent you debug report via PM Carlo. Take a look.

Hi Rymek,

Thank you very useful logs. This is most likely a known issue or at least partly a known issue. Our internal defect ID is 18765, you can use this to look for the fix in the release notes or to contact us again.

The good news is that we finally have a good reproduction and are actively analysing this issue right now. It's a SW issue, it's not yet clear why only some systems show it but we should be able to resolve or work around it.
As usual I can't give you any dates though.

Best regards,
Carlo

[DaHof]

I can move my mouse onto the screen, see the proper background, see the menu but can't bring any app or file onto the screen.

Ben

[paultzirides]

A reminder: if you have downloaded the Beta 1 please uninstall it and delete the installation image. If you had device issues after using the beta 1 please contact us at http://support.displaylink.com


Carlo, does that mean that we should uninstall Beta 1 before updating? I simply rain the new installer from the new disk image.

(EDIT: Changed quoted text selection to be more specific)

[ourzoo]

Have you resolved the issue that damaged adapters? Just being honest here, but I'm scared to try this and fry my other adapter.

[MAC]

I can confirm 2.5 beta 2 pretty much works fine now with El Capitan; no crashes or wake up from sleep problems yet. I was using 2.4, which I uninstalled before installing 2.5 beta 2.

On 2.5 beta 2, DisplayLinkManager is using between 2-6% of CPU, with 2 additional monitors plugged in; no heavy CPU usage noted in the last day.

Will report back if I find problems.

[MAC]

Have you resolved the issue that damaged adapters? Just being honest here, but I'm scared to try this and fry my other adapter.

Sorry, I seem to have missed that. Where did you get that info from?

[Carlo]

Carlo, does that mean that we should uninstall Beta 1 before updating? I simply rain the new installer from the new disk image.

(EDIT: Changed quoted text selection to be more specific)

A straight update is fine.

Really, please do delete the beta 1 installer image.

Cheers,
Carlo

[Carlo]

Have you resolved the issue that damaged adapters? Just being honest here, but I'm scared to try this and fry my other adapter.

Your issue has been fixed yes. I understand your concern!

Regards,
Carlo

[pmontelo]

Hi Carlo,

I'm on OS X 10.10.5 and with 2.5 Beta 2, my DisplayLink screen only displays my desktop image and the mouse cursor. If I drag a window over to the DisplayLink screen, I only see the desktop image and mouse cursor.

Some extra info, I have 3 displays on a Mac Mini 2012, main center display = HDMI, right display = thunderbolt, left display = DisplayLink USB

I have reverted back to 2.4 and everything is working again. I am hoping to upgrade to OS X 10.11.1 but will hold off until a driver is available.

Thanks,
Patrick

Hi All,

We have released today version 2.5 Beta 2. This version fixes critical issues in the beta 1 and is recommended to all El Capitan users. More information in the release note.

We'd like to hear your feedback!

A reminder: if you have downloaded the Beta 1 please uninstall it and delete the installation image. If you had device issues after using the beta 1 please contact us at http://support.displaylink.com

Best regards,
Carlo

[pbuckner]

No better than 2.4 for me.

El Capitan, USB2 connected (via ADC) old Apple Studio Display. Screen remains blank, mouse can move into space, but nothing is displayed.

iTunes, when minimizing, will cause user to logout. With 2.4, this happened nearly every time app minimized. With 2.5b2 it's still over 50%, so I uninstall driver.

Let me know if you want a log.

[Carlo]

Hi All,

Thank you for letting us know. This issue with no updates on DisplayLink screen but mouse visible has been reported a few times now and we'll look into it. It's very likely that we can provide a solution.

About minimising iTunes we'll refresh the bug we have open with Apple. I'm more optimistic now that we got a Window Server fix in El Capitan. More may come.

Best regards,
Carlo

[Junto026]

I can move my mouse onto the screen, see the proper background, see the menu but can't bring any app or file onto the screen.

Ben

The same thing randomly happened to me after days of use. Uninstalling 2.5 Beta 2 and re-installing fixed it for me.

[falcom]

After periodic OS lockups when waking screens I've updated from 2.4 to 2.5b2 after uninstalling 2.4. Now that I'm on 2.5b2 I'm seeing that the DisplayLinkManager always consumes 40% CPU. Additionally each time I reboot, the DL screen is frozen on the login window and this persists even after login, I can then unfreeze it by temporarily reconfiguring which of my three screens is the "main display". After that I periodically get into a state where the DL screen freezes again though the mouse pointer can still move around, nothing else is being updated. While frozen the CPU returns to normal at least ;) Changing which display is the main display again temporarily resolves this frozen state. Looks like I'll be downgrading back to 2.4 as the wake from sleep lockups are far easier to manage then the issues I'm seeing with 2.5b2.

One final issue which I've been seeing on 2.4 even pre El Cap is that the DL audio will randomly unmute itself if I have it on mute, this may occur every 5-10 minutes as if the audio adapter is being reset, same thing happens if I unplug/replug USB for instance. I haven't been on 2.5b2 long enough to know if I've got the same issue there or not.

I'm running El Capitan on a 13" early 2015 rMBP i7 with 16GB. I'm using the Dell D3100 attached over USB3 to a single 1920x1080 monitor as well as ethernet and audio and a Time Machine backup drive. I also have two 4K monitors attached directly to the Mac.

I've just attached a "spin dump" of the DisplayLinkManager while it is consuming the 40% CPU

thanks,

mark

[ourzoo]

Sorry, I seem to have missed that. Where did you get that info from?

I don't think it happened to many folks (I hope not), but when I updated to 2.5 beta 1 my adapter was no longer found even after I uninstalled and reinstalled 2.4. When I connected to my setup in my office all is well using 2.4. Something about the update damaged the firmware in the adapter.

[ourzoo]

Your issue has been fixed yes. I understand your concern!

Regards,
Carlo

Thanks Carlo. I think I'm still going to sit on the sidelines for a bit.

[dave_w]

Hi,

Just reporting consistent wakeup issues using 2.5 Beta 2 with OSX Yosemite 10.10.2, MacBook Air 11 inch Mid 2012, and a Kensington SD3500V dock.

Downgrading to 2.4 seems to have resolved the issue.

Dave

[ericslaw]

recent reboot of MBP15" revealed odd rendering problems exclusive to my DisplayLink USB video cards.

I'm was running DisplayLink 2.4.64766.0 on Yosemite 10.10.5.
Upgraded DisplayLink to 2.5b2 but problem still exists.

Workaround: disable hardware acceleration in chrome advanced settings.

Does not seem to affect normal apps like outlook, iterm2, skype (no video), etc.

[Carlo]

Hi,

Just reporting consistent wakeup issues using 2.5 Beta 2 with OSX Yosemite 10.10.2, MacBook Air 11 inch Mid 2012, and a Kensington SD3500V dock.

Downgrading to 2.4 seems to have resolved the issue.

Dave

Hi Dave,

Could you describe the kind of issues are you experiencing on Yosemite?

Carlo

[dave_w]

Hi Dave,

Could you describe the kind of issues are you experiencing on Yosemite?

Carlo

Sure. Every time I put the screen to sleep using a hot corner or by inactivity, the DisplayLink-connected screen would not wake up. The other displays (both the inbuilt and DisplayPort screen) would both awake. From memory disconnecting and reconnecting or restarting rectified the issue but obviously wasn't practical.

At other times I also had some inconsistent issues where nothing would show except the cursor and a black background on the DisplayLink monitor. Minimising windows via the menu bar would show the minimising animation to the dock on the DisplayPort screen from where they should have been on the DisplayLink monitor.

While I'm at it (not sure if it's been resolved already) but I had to start using the DisplayPort/Thunderbolt port rather than the second output of the Kensington dock a while back due to inconsistent arrangement of the monitors every time I connected. This happened after moving to Yosemite, and not before.

Dave

[Carlo]

Sure. Every time I put the screen to sleep using a hot corner or by inactivity, the DisplayLink-connected screen would not wake up. The other displays (both the inbuilt and DisplayPort screen) would both awake. From memory disconnecting and reconnecting or restarting rectified the issue but obviously wasn't practical.

At other times I also had some inconsistent issues where nothing would show except the cursor and a black background on the DisplayLink monitor. Minimising windows via the menu bar would show the minimising animation to the dock on the DisplayPort screen from where they should have been on the DisplayLink monitor.

While I'm at it (not sure if it's been resolved already) but I had to start using the DisplayPort/Thunderbolt port rather than the second output of the Kensington dock a while back due to inconsistent arrangement of the monitors every time I connected. This happened after moving to Yosemite, and not before.

Dave

Thank you Dave,

We'll try to reproduce the first issue, the second is already being investigated. We introduced a workaround for the third issue in version 2.4, that should be fine now.

Best regards,
Carlo

[TigerRob]

recent reboot of MBP15" revealed odd rendering problems exclusive to my DisplayLink USB video cards.

I'm was running DisplayLink 2.4.64766.0 on Yosemite 10.10.5.
Upgraded DisplayLink to 2.5b2 but problem still exists.

Workaround: disable hardware acceleration in chrome advanced settings.

Does not seem to affect normal apps like outlook, iterm2, skype (no video), etc.

I have also been seeing corrupted rendering of Chrome this morning. This is on Chrome Version 46.0.2490.71 (64-bit). OSX Yosemite 10.10.5. I recently upgraded to the 2.5b2 drivers - but have no idea if chrome recently updated itself. I'm pretty sure that I wasn't having this issue with he same config earlier in the week.

The workaround described by the OP also works for me.

[SusanMatt]

Hi

I am experiencing El Capitan issues with 2.5 beta 2. My monitor attached via mini display port is actually blanking out and coming back continually since install. Previously, on 2.4, the DisplayLink monitor would blank out and not come back unless I unplugged and re-plugged in. Could this software be affecting the thunderbolt/minidisplay port monitor?

Everything is running through a Belkin Thunderbolt dock, which I will try running without.

Thanks,
Susan


Model Identifier: MacBookAir5,2
Processor Name: Intel Core i7
Processor Speed: 2 GHz
Memory: 8 GB
Boot ROM Version: MBA51.00EF.B03
System Version: OS X 10.11 (15A278b)
Boot Mode: Normal
External Monitors: 2 ASUS DVI (1 via minidisplay port/thunderbolt, 1 via USB DisplayLink)

[Sinan]

I'm using 2.5 Beta 2 on a Plugable USB 3.0 4K with a 2012 Mac Mini and Apple Cinema Display(minidisplayport). All seems OK, except when running "Capo" the middle of the Capo window where transport head is stops moving. Or it turns black. The rest of the Capo App window works correctly. Focus rite Mix Control works, iConnectivity app does. VG-99 Editor works fine. These are the only Apps I have on that monitor. Just giving this as a feedback. I'm extremely pleased with the product.

[Comenius]

Experiencing issues on 2.5b2 with latest version of Google Chrome on El Capitan. There's a weird visual glitch in the main content part of the tab, although the menus and bookmarks look normal. Firefox works fine. Chrome displays fine with the built in screen on the MacBook Air, but both external monitors exhibit this behavior. Screenshot attached.

[dave_w]

Experiencing issues on 2.5b2 with latest version of Google Chrome on El Capitan. There's a weird visual glitch in the main content part of the tab, although the menus and bookmarks look normal. Firefox works fine. Chrome displays fine with the built in screen on the MacBook Air, but both external monitors exhibit this behavior. Screenshot attached.

I had this behaviour on Yosemite with v2.2 and v2.4 also, which is why i tried v2.5b2 originally. I think it may be a Chrome update that's caused it. Unchecking the following Chrome setting resolved it for me: Settings > Show advanced settings > System > Use hardware acceleration when available.

Dave

[asdfsafd]

Yep, disabling "Hardware acceleration" did it for me, too. Thanks.

[luckman212]

That fixed it on mine too. What is the overall impact of leaving this disabled? Does it run much slower, or eat battery etc??

[saudor]

That fixed it on mine too. What is the overall impact of leaving this disabled? Does it run much slower, or eat battery etc??

It runs slower since you're now relying more on the CPU to process things (i.e. rendering) that previously used the GPU (and left the CPU "free" to do other things). Might be good to use a browser like safari for DL monitors.

[Comenius]

Disabling hardware acceleration in Chrome also worked for me. Hopefully this won't be needed in a future release.

[dcoulson]

Disabling hardware acceleration in Chrome also worked for me. Hopefully this won't be needed in a future release.

The rendering issue is fixed in the current Chrome beta. I'm running "Version 47.0.2526.27 beta (64-bit)" and it works fine with my DL display.

[TigerRob]

The rendering issue is fixed in the current Chrome beta. I'm running "Version 47.0.2526.27 beta (64-bit)" and it works fine with my DL display.

Do you haver any idea when this will make it out of beta and into an official release?

Thanks for the info.

[alphadog00]

I am noticing a couple issues i have not seen mentioned.

I have brand new MBA Retina (13" 2015) - I powered it on did some updates and installed firefox and displaylink drivers - the issues i have seen:

1. The Dock on my HDMI external monitor is white instead of a semi-transparent - it sounds like something since mavericks, but i can't remember

2. I did update to El Capitan last night. And this AM, I had one instance where my mouse pointer changed to vertical bars with little tails top and bottom - so not exactly a pipe symbol. Moving mouse back to main screen changed it back to an arrow and all is fine.

EDIT:

3. Colors in title bars are really mottled and off color. The laptop has gray title bars, but the external monitor is purplish with mottling/gradient. Just moving the mouse around changes this too. I have an Asus monitor running at 1080P.

EDIT2 - 1 and 3 resolved by checking reduce transparency in accessibility


Nothing really bad at this point, but annoying.

[thk1234]

Hi Carlo,

I'm on OS X 10.10.5 and with 2.5 Beta 2, my DisplayLink screen only displays my desktop image and the mouse cursor. If I drag a window over to the DisplayLink screen, I only see the desktop image and mouse cursor.

Some extra info, I have 3 displays on a Mac Mini 2012, main center display = HDMI, right display = thunderbolt, left display = DisplayLink USB

I have reverted back to 2.4 and everything is working again. I am hoping to upgrade to OS X 10.11.1 but will hold off until a driver is available.

Thanks,
Patrick

I have the same Problems - 2 DVI connections on a ThinkPad docking Station.
Driver 2.5b2 OSX 10.11 worked fine with driver 2.4 on OSX 10.10

[dcoulson]

Do you haver any idea when this will make it out of beta and into an official release?

Not sure - You can track the bug here: https://code.google.com/p/chromium/issues/detail?id=527556

[luckman212]

Latest comment says it will be pushed to v46 (current stable) in a few days...

[TigerRob]

Latest comment says it will be pushed to v46 (current stable) in a few days...

@luckman212 - thank you.

[luckman212]

The update was released! Go to Chrome > About to get it now. I tested it and it works for me with the acceleration on now! :)

Comment #57 on issue 527556 by ccameron@chromium.org: Window visually
corrupt on DisplayLink monitor w/ Hardware Acceleration enabled
https://code.google.com/p/chromium/issues/detail?id=527556

We just pushed a new version of Chrome Stable -- if you go to
chrome://chrome/ and check for updates, it should get you to 46.0.2490.80,
which has this bug fixed. You can then re-enable hardware acceleration.

We've added these display configurations to our test matrix, so we'll be
sure not to break them in the future.

[soarhevn]

Display was working for a while, but now no matter restarts, re plugging, etc., can't get it working. Below is from the log.

2015/10/30 09:42:05.787 DisplayLinkManager[102]: CGSConnectionByID: 0 is not a valid connection ID.
2015/10/30 09:42:05.788 DisplayLinkManager[102]: Invalid Connection ID 0
2015/10/30 09:42:06.490 com.apple.xpc.launchd[1]: (com.displaylink.useragent-prelogin) This service is defined to be constantly running and is inherently inefficient.
2015/10/30 09:42:06.490 com.apple.xpc.launchd[1]: (com.displaylink.useragent-prelogin) Please switch away from OnDemand to KeepAlive.
2015/10/30 09:42:22.955 com.apple.xpc.launchd[1]: (com.displaylink.useragent) This service is defined to be constantly running and is inherently inefficient.
2015/10/30 09:42:22.955 com.apple.xpc.launchd[1]: (com.displaylink.useragent) Please switch away from OnDemand to KeepAlive.
2015/10/30 09:43:21.674 DisplayLinkUserAgent[2383]: Set a breakpoint at CGSLogError to catch errors as they are logged.
2015/10/30 09:43:21.674 DisplayLinkUserAgent[2383]: CGSServiceForDisplayNumber: Invalid display 0x2b9831c4
2015/10/30 09:43:21.675 DisplayLinkUserAgent[2383]: CGSGetDisplayModeDescriptionsOfLength: Zero list count
2015/10/30 09:45:29.768 DisplayLinkUserAgent[2383]: CGSServiceForDisplayNumber: Invalid display 0x2b9831c4
2015/10/30 09:45:29.768 DisplayLinkUserAgent[2383]: CGSGetDisplayModeDescriptionsOfLength: Zero list count

[alphadog00]

I just rebooted with Display link attached. Upon login, the second display was visible, but moving mouse to top could not click on anything in the title bar, and moving mouse to the bottom would not bring up the launcher.

Unplugging my Dynadock (USB) and reconnecting solved the issue. Will grab log if it happens again.

[volom]

On 15" Macbook Retina
Driving two external displays via HDMI and DisplayPort

Locking and unlocking the computer will prevent one of the displays (DisplayPort) from not driving, it is black but shows up in the display arrangement

http://i.prntscr.com/fddd623fe6bf42118e52664786c5effa.png

Pulling the USB cable from the mac in anything but sleep mode will lock up the computer where it will no longer respond to mouse or keyboard input, and require a restart.

Trying to get logs now.

[volom]

15" Macbook Retina
Driving 2 external displays via HDMI and DisplayPort

Locking/Unlocking computer
-DisplayPort monitor goes black, but shows in display arrangement as active.


Nov 9 08:58:48 MATTHEWs-MacBook-Pro DisplayLinkUserAgent[522]: CGSServiceForDisplayNumber: Invalid display 0x2b2875d6
Nov 9 08:58:48 MATTHEWs-MacBook-Pro DisplayLinkUserAgent[522]: CGSGetDisplayModeDescriptionsOfLength: Zero list count
Nov 9 08:58:48 MATTHEWs-MacBook-Pro DisplayLinkUserAgent[522]: CGSServiceForDisplayNumber: Invalid display 0x2b286f95
Nov 9 08:58:48 MATTHEWs-MacBook-Pro DisplayLinkUserAgent[522]: CGSGetDisplayModeDescriptionsOfLength: Zero list count
Nov 9 08:58:49 MATTHEWs-MacBook-Pro DisplayLinkUserAgent[522]: CGSServiceForDisplayNumber: Invalid display 0x2b286f95

[volom]

15" Macbook Retina
Driving 2 external displays via HDMI and DisplayPort

-Pulling USB cable from the mac in anything but sleep mode will lock the computer and require a restart.


Nov 9 09:16:03 MATTHEWs-MacBook-Pro kernel[0]: in6_unlink_ifa: IPv6 address 0x2368e864316160ed has no prefix
Nov 9 09:16:03 MATTHEWs-MacBook-Pro symptomsd[203]: nw_interface_get_agents SIOCGIFAGENTIDS failed for interface "en5" (index 11, type other): [6] Device not configured
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: arp_client_open_fd: bpf_setif(en5) failed: Device not configured (6)
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: DHCP en5: INIT-REBOOT transmit failed
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: arp_client_open_fd: bpf_setif(en5) failed: Device not configured (6)
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: [ifutil.c:520] nd_flags_set_with_socket(): SIOCGIFINFO_IN6(en5) failed, Device not configured
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: DHCP en5: ARP detect ROUTER failed, arp_client_open_fd: bpf_setif(en5) failed: Device not configured (6)
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: bootp_client_bind_socket_to_if(en5, 11): setsockopt IP_BOUND_IF failed
Nov 9 09:16:03 MATTHEWs-MacBook-Pro symptomsd[203]: nw_interface_get_agents SIOCGIFAGENTIDS failed for interface "en5" (index 11, type other): [6] Device not configured
Nov 9 09:16:03 MATTHEWs-MacBook-Pro symptomsd[203]: nw_interface_get_agents SIOCGIFAGENTIDS failed for interface "en6" (index 10, type other): [6] Device not configured
Nov 9 09:16:03 MATTHEWs-MacBook-Pro mDNSResponder[90]: getExtendedFlags: SIOCGIFEFLAGS failed, errno = 6 (Device not configured)
Nov 9 09:16:03 --- last message repeated 1 time ---
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: siocsifnetsignature(en5, IPv4, 0) failed: Device not configured
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: network changed: v4(en0:192.168.168.158) DNS! Proxy! SMB
Nov 9 09:16:03 MATTHEWs-MacBook-Pro symptomsd[203]: nw_interface_create_with_name netutil_ifname_to_ifindex(en5) failed, dumping backtrace:
[x86_64] libnetcore-582.1.4
0 libsystem_network.dylib 0x00007fff957b1a05 __nw_create_backtrace_string + 123
1 libsystem_network.dylib 0x00007fff957d28c7 nw_interface_create_with_name + 179
2 Network 0x00007fff962a0130 -[NWInterface initWithInterfaceName:] + 120
3 SymptomEvaluator 0x00007fff914d3024 config_callback + 874
4 SystemConfiguration 0x00007fff985ece0f rlsPerform + 184
5 SystemConfiguration 0x00007fff9860014f __SCDynamicStoreSetDispatchQueue_block_invoke_2 + 52
6 libdispatch.dylib 0x00007fff917038f5 _dispatch_call_block_and_release + 12
7 libdispatch.dylib 0x00007fff916f83c3 _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fff916fcff3 _dispatch_queue_drain + 754
9 libdispatch.dylib 0x00007fff917036bf _dispatch_queue_invoke + 549
10 libdispatch.dylib 0x00007fff916fbd0b _dispatch_root_queue_drain + 538
11 libdispatch.dylib 0x00007fff916fbab8 _dispatch_worker_thread3 + 91
12 libsystem_pthread.dylib 0x00007fff975bf4f2 _pthread_wqthread + 1129
13 libsystem_pthread.dylib 0x00007fff975bd375 start_wqthread + 13
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Received display connect changed for display 0x2b2875d6
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Found 1 modes for display 0x2b2875d6 [1, 0]
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x2b2875d6 changed state to offline
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x04280bc2: GL mask 0x5; bounds (0, 0)[1920 x 1200], 27 modes available
Main, Active, on-line, enabled, built-in, boot, OpenGL-accel, Vendor 610, Model a02f, S/N 0, Unit 2, Rotation 0
UUID 0x1fbf2f7f57ec56e5521f556a305d1a61, ColorSpace { -820314812 }
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: GLCompositor: GL renderer id 0x01024502, GL mask 0x00000003, accelerator 0x0000687f, unit 0, caps QEX|MIPMAP, vram 1536 MB
texture max 16384, viewport max {16384, 16384}, extensions NPOT|GLSL|FLOAT
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f003d: GL mask 0x2; bounds (4864, 0)[1 x 1], 2 modes available
off-line, enabled, OpenGL-accel, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: GLCompositor: GL renderer id 0x01024502, GL mask 0x00000003, accelerator 0x0000687f, unit 0, caps QEX|MIPMAP, vram 1536 MB
texture max 16384, viewport max {16384, 16384}, extensions NPOT|GLSL|FLOAT
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0048: GL mask 0x1000; bounds (4865, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 12, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0047: GL mask 0x800; bounds (4866, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 11, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0043: GL mask 0x80; bounds (4867, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 7, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0042: GL mask 0x40; bounds (4868, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 6, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0041: GL mask 0x20; bounds (4869, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 5, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0040: GL mask 0x10; bounds (4870, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 4, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f003f: GL mask 0x8; bounds (4871, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x2b286f95: GL mask 0x200; bounds (1920, -1080)[1920 x 1080], 46 modes available
Active, on-line, enabled, Vendor 10ac, Model a0a3, S/N 354b474c, Unit 9, Rotation 0
UUID 0x698135f81a7bb8b6bdebcb05a19135fd, ColorSpace { 529145650 }
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0046: GL mask 0x400; bounds (0, -1080)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 10, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff, ColorSpace { 1880775140 }
Nov 9 09:16:04 MATTHEWs-MacBook-Pro symptomsd[203]: __73-[NetworkAnalyticsEngine observeValueForKeyPath:ofObject:change:context:]_block_invoke unexpected switch value 2
Nov 9 09:16:11 MATTHEWs-MacBook-Pro syncdefaultsd[572]: accountsd has been removed from syncing apps.
Nov 9 09:16:12 MATTHEWs-MacBook-Pro watchdogd[274]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive
Nov 9 09:16:12 MATTHEWs-MacBook-Pro CrashReporterSupportHelper[374]: <NSXPCConnection: 0x7f8e7c3011d0> connection from pid 573: Warning: Exception caught during invocation of received message, dropping incoming message and invalidating the connection.

[Carlo]

15" Macbook Retina
Driving 2 external displays via HDMI and DisplayPort

-Pulling USB cable from the mac in anything but sleep mode will lock the computer and require a restart.


Nov 9 09:16:03 MATTHEWs-MacBook-Pro kernel[0]: in6_unlink_ifa: IPv6 address 0x2368e864316160ed has no prefix
Nov 9 09:16:03 MATTHEWs-MacBook-Pro symptomsd[203]: nw_interface_get_agents SIOCGIFAGENTIDS failed for interface "en5" (index 11, type other): [6] Device not configured
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: arp_client_open_fd: bpf_setif(en5) failed: Device not configured (6)
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: DHCP en5: INIT-REBOOT transmit failed
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: arp_client_open_fd: bpf_setif(en5) failed: Device not configured (6)
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: [ifutil.c:520] nd_flags_set_with_socket(): SIOCGIFINFO_IN6(en5) failed, Device not configured
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: DHCP en5: ARP detect ROUTER failed, arp_client_open_fd: bpf_setif(en5) failed: Device not configured (6)
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: bootp_client_bind_socket_to_if(en5, 11): setsockopt IP_BOUND_IF failed
Nov 9 09:16:03 MATTHEWs-MacBook-Pro symptomsd[203]: nw_interface_get_agents SIOCGIFAGENTIDS failed for interface "en5" (index 11, type other): [6] Device not configured
Nov 9 09:16:03 MATTHEWs-MacBook-Pro symptomsd[203]: nw_interface_get_agents SIOCGIFAGENTIDS failed for interface "en6" (index 10, type other): [6] Device not configured
Nov 9 09:16:03 MATTHEWs-MacBook-Pro mDNSResponder[90]: getExtendedFlags: SIOCGIFEFLAGS failed, errno = 6 (Device not configured)
Nov 9 09:16:03 --- last message repeated 1 time ---
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: siocsifnetsignature(en5, IPv4, 0) failed: Device not configured
Nov 9 09:16:03 MATTHEWs-MacBook-Pro configd[51]: network changed: v4(en0:192.168.168.158) DNS! Proxy! SMB
Nov 9 09:16:03 MATTHEWs-MacBook-Pro symptomsd[203]: nw_interface_create_with_name netutil_ifname_to_ifindex(en5) failed, dumping backtrace:
[x86_64] libnetcore-582.1.4
0 libsystem_network.dylib 0x00007fff957b1a05 __nw_create_backtrace_string + 123
1 libsystem_network.dylib 0x00007fff957d28c7 nw_interface_create_with_name + 179
2 Network 0x00007fff962a0130 -[NWInterface initWithInterfaceName:] + 120
3 SymptomEvaluator 0x00007fff914d3024 config_callback + 874
4 SystemConfiguration 0x00007fff985ece0f rlsPerform + 184
5 SystemConfiguration 0x00007fff9860014f __SCDynamicStoreSetDispatchQueue_block_invoke_2 + 52
6 libdispatch.dylib 0x00007fff917038f5 _dispatch_call_block_and_release + 12
7 libdispatch.dylib 0x00007fff916f83c3 _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fff916fcff3 _dispatch_queue_drain + 754
9 libdispatch.dylib 0x00007fff917036bf _dispatch_queue_invoke + 549
10 libdispatch.dylib 0x00007fff916fbd0b _dispatch_root_queue_drain + 538
11 libdispatch.dylib 0x00007fff916fbab8 _dispatch_worker_thread3 + 91
12 libsystem_pthread.dylib 0x00007fff975bf4f2 _pthread_wqthread + 1129
13 libsystem_pthread.dylib 0x00007fff975bd375 start_wqthread + 13
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Received display connect changed for display 0x2b2875d6
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Found 1 modes for display 0x2b2875d6 [1, 0]
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x2b2875d6 changed state to offline
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x04280bc2: GL mask 0x5; bounds (0, 0)[1920 x 1200], 27 modes available
Main, Active, on-line, enabled, built-in, boot, OpenGL-accel, Vendor 610, Model a02f, S/N 0, Unit 2, Rotation 0
UUID 0x1fbf2f7f57ec56e5521f556a305d1a61, ColorSpace { -820314812 }
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: GLCompositor: GL renderer id 0x01024502, GL mask 0x00000003, accelerator 0x0000687f, unit 0, caps QEX|MIPMAP, vram 1536 MB
texture max 16384, viewport max {16384, 16384}, extensions NPOT|GLSL|FLOAT
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f003d: GL mask 0x2; bounds (4864, 0)[1 x 1], 2 modes available
off-line, enabled, OpenGL-accel, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: GLCompositor: GL renderer id 0x01024502, GL mask 0x00000003, accelerator 0x0000687f, unit 0, caps QEX|MIPMAP, vram 1536 MB
texture max 16384, viewport max {16384, 16384}, extensions NPOT|GLSL|FLOAT
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0048: GL mask 0x1000; bounds (4865, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 12, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0047: GL mask 0x800; bounds (4866, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 11, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0043: GL mask 0x80; bounds (4867, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 7, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0042: GL mask 0x40; bounds (4868, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 6, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0041: GL mask 0x20; bounds (4869, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 5, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0040: GL mask 0x10; bounds (4870, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 4, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f003f: GL mask 0x8; bounds (4871, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x2b286f95: GL mask 0x200; bounds (1920, -1080)[1920 x 1080], 46 modes available
Active, on-line, enabled, Vendor 10ac, Model a0a3, S/N 354b474c, Unit 9, Rotation 0
UUID 0x698135f81a7bb8b6bdebcb05a19135fd, ColorSpace { 529145650 }
Nov 9 09:16:03 MATTHEWs-MacBook-Pro WindowServer[188]: Display 0x003f0046: GL mask 0x400; bounds (0, -1080)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 10, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff, ColorSpace { 1880775140 }
Nov 9 09:16:04 MATTHEWs-MacBook-Pro symptomsd[203]: __73-[NetworkAnalyticsEngine observeValueForKeyPath:ofObject:change:context:]_block_invoke unexpected switch value 2
Nov 9 09:16:11 MATTHEWs-MacBook-Pro syncdefaultsd[572]: accountsd has been removed from syncing apps.
Nov 9 09:16:12 MATTHEWs-MacBook-Pro watchdogd[274]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive
Nov 9 09:16:12 MATTHEWs-MacBook-Pro CrashReporterSupportHelper[374]: <NSXPCConnection: 0x7f8e7c3011d0> connection from pid 573: Warning: Exception caught during invocation of received message, dropping incoming message and invalidating the connection.


Hi this is a quite severe issue. Can you please send us the debug logs collected immediately after rebooting once the issue happens?

Please follow the instructions at http://support.displaylink.com/knowledgebase/articles/755301-how-to-report-mac-os-x-issues-to-displaylink

Thank you
Carlo

[volom]

Hi this is a quite severe issue. Can you please send us the debug logs collected immediately after rebooting once the issue happens?

Please follow the instructions at http://support.displaylink.com/knowledgebase/articles/755301-how-to-report-mac-os-x-issues-to-displaylink

Thank you
Carlo

Just sent them.

[luckman212]

How is 2.5 development coming along? any news?

[Carlo]

How is 2.5 development coming along? any news?

Hi luckman and forum,

We're working hard to bring you a new beta (hopefully the last one) but it's proving more difficult than anticipated.
I can only thank you for your patience!

Best regards,
Carlo