Displaylink 3 - stability
Reported by
eric.kuf...@kohls.com,
Apr 1 2016
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 8104.2.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2688.0 Safari/537.36 Platform: Platform 8104.2.0 (Official Build) dev-channel lulu Example URL: Steps to reproduce the problem: 1. Setup displaylink 3.0 dock 2. Plug in dock to to chromebook (ethernet & usb keyboard/mouse already attached to dock - both work at this point) 3. Attach monitor cable to dock 4. Reboot loop What is the expected behavior? What went wrong? Reboot loop Did this work before? N/A Is it a problem with Flash or HTML5? N/A Does this work in other browsers? N/A Chrome version: 51.0.2688.0 Channel: dev OS Version: 8104.2.0 Flash Version: Shockwave Flash 21.0 r0 Was actually working for me yesterday. Today I cannot get DL3.0 to work at all.
,
Apr 6 2016
This problem was experienced with a Kensington sd3500v. W/ 1 HDMI-to-HDMI + DVI-to-HDMI. I am NOT experiencing this problem using a Dell D3100, same monitors. Both hooked up via HDMI.
,
Apr 7 2016
+displaylink folks
,
Apr 8 2016
,
Apr 11 2016
This issue is not observed with HP 3005PR and HP 3001PR. Might be isolated to Kensington sd3500v only. eric.kufrin@kohls.com, can you file a feedback by Shift+Alt+i?
,
Apr 21 2016
Dell CB13+D3100 Steps to reproduce the problem: 1. Shutdown chromebook 2. Return to chromebook hours later... 3. Power up chromebook 4. Monitors attached to dock do not activate, they are asleep (during this time the USB ports & ethernet work on dock) 5. Unplug dock usb cable from chromebook 6. Plug dock usb cable into chromebook 7. Monitors activate This is a poor user experience. Should I open a separate bug for each issue?
,
Apr 21 2016
Having separate bugs for distinct reproduction steps and end results would be more manageable. So, as initial issue is different to what's in comment #6, it would be best if it's in separate bugs (with more precise bug summary/title). Thanks.
,
Apr 21 2016
This bug can be closed then. The original problem is happening with a hardware/USB-dock we do not intend to deploy.
,
Apr 21 2016
,
Jun 30 2016
,
Jun 30 2016
,
Feb 17 2017
,
Mar 18 2017
Activating. Please assign to the right owner and the appropriate priority.
,
Nov 10 2017
This seems to work now, at least the original report. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by yini...@chromium.org
, Apr 4 2016