2.2, again issues as usual

itadmincrbc · 06-23-2014, 08:19 PM

In 2.2, again, the monitor connected to the Displaylink dock does not light everytime. In order to make it light, you have to unplug and replug in the USB3 cable. SO annoying. I guess this will never work properly.

Carlo · 06-24-2014, 07:14 AM

Hi,

2.2 has additional device logging that can help analyse this issue. Can you please collect your logs and send them to us?

The log tool is at http://www.displaylink.com/support/ticket.php?id=269
You can attach the logs here or send them through http://www.displaylink.com/support/ask_question.php

Thank you,
Carlo

alphadog · 06-29-2014, 12:42 PM

I am seeing almost daily occurrences (it happens overnight) of a full system crash or a window server crash. I am not sure if it is the newer 2.2 beta or 10.9.3 - but something is different and logs are filling with messages about disabling opengl. I sent a report in a week ago, but here is another.

alphadog · 06-29-2014, 12:57 PM

Addtionally the logs are logging the same message 5 times per second:

6/29/14 8:56:45.358 AM WindowServer[128]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fda68d133a0) - disabling OpenGL

Carlo · 06-30-2014, 08:11 AM

Hi Alphadog,

The OpenGL messages are expected. Long story.
Should be harmless. If the logging is too much (for frequently changing OpenGL content) the logger will skip lines automatically.

We'll look at the logs for the other issues.

Cheers,
Carlo

alphadog · 06-30-2014, 11:26 AM

Thanks Carlo,

I think Google Chrome is somehow involved - wither Chrome, Window Manager, or System will crash overnight if Chrome is left open. It may depend on which monitor Chrome is ope on. Also, my system is set to sleep at night, and that may be related.

I quit chrome last night, and this AM all was fine.

06-23-2014, 08:19 PM	#1
itadmincrbc Member Join Date: Oct 2013 Posts: 55	2.2, again issues as usual In 2.2, again, the monitor connected to the Displaylink dock does not light everytime. In order to make it light, you have to unplug and replug in the USB3 cable. SO annoying. I guess this will never work properly.

06-24-2014, 07:14 AM	#2
Carlo Mac Team Join Date: Feb 2009 Posts: 606	Hi, 2.2 has additional device logging that can help analyse this issue. Can you please collect your logs and send them to us? The log tool is at http://www.displaylink.com/support/ticket.php?id=269 You can attach the logs here or send them through http://www.displaylink.com/support/ask_question.php Thank you, Carlo

06-29-2014, 12:57 PM	#4
alphadog Member Join Date: Nov 2013 Posts: 56	Addtionally the logs are logging the same message 5 times per second: 6/29/14 8:56:45.358 AM WindowServer[128]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fda68d133a0) - disabling OpenGL

06-30-2014, 08:11 AM	#5
Carlo Mac Team Join Date: Feb 2009 Posts: 606	Hi Alphadog, The OpenGL messages are expected. Long story. Should be harmless. If the logging is too much (for frequently changing OpenGL content) the logger will skip lines automatically. We'll look at the logs for the other issues. Cheers, Carlo

06-30-2014, 11:26 AM	#6
alphadog Member Join Date: Nov 2013 Posts: 56	Thanks Carlo, I think Google Chrome is somehow involved - wither Chrome, Window Manager, or System will crash overnight if Chrome is left open. It may depend on which monitor Chrome is ope on. Also, my system is set to sleep at night, and that may be related. I quit chrome last night, and this AM all was fine.