New issue
Advanced search Search tips

Issue 818825 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

external display no longer detected after updating from 63 to 64.0.3282

Reported by sun...@gmail.com, Mar 5 2018

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10323.46.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.107 Safari/537.36
Platform: Platform	10323.46.0 (Official Build) beta-channel caroline

Steps to reproduce the problem:
1. Connect external display through USB-C to DP/HDMI adapter
2. Upgrade ChromeOS from 63 to 64.0.3282 on stable channel
3. Observe that external display is no longer detected
4. Upgrade ChromeOS from 64 stable channel to 65 beta channel
5. Observe that external display is still not detected

What is the expected behavior?
External display should be detected so that I can use extended desktop mode.  Without it, I'm limited to using just my chromebook's native display.

What went wrong?
My Samsung Chromebook Pro (Caroline) has stopped detecting my external display display (connected via USB-C to DP/HDMI adapter) after upgrading from version 63 stable channel to version 64 stable channel today.

I have also tried upgrading it further to version 65 by switching from stable channel to beta channel, but no luck! :(

Did this work before? Yes 63

Chrome version: 65.0.3325.107  Channel: beta
OS Version: 10323.46.0
Flash Version: 

See also related Issue 818778.
 

Comment 1 by sun...@gmail.com, Mar 6 2018

I have also tried upgrading to the dev channel at version 66.0.3356.0, but still no luck.

Comment 2 by sun...@gmail.com, Mar 7 2018

Thankfully I was able to fix this issue by performing a hard reset (Refresh+Power) as suggested at https://bugs.chromium.org/p/chromium/issues/detail?id=819048#c6
Components: -UI UI>Shell>MultipleMonitor
Cc: afakhry@chromium.org
Owner: marc...@chromium.org
marcheu, anything to look at here? The user seems to have recovered from this problem.
Owner: tbroch@chromium.org
If only power-refresh fixes it, then it sounds like type-c negotiation problem, which lives in the ec pd, which Todd will know about.
Components: OS>Firmware>EC
Labels: Needs-Feedback
Will be difficult to debug w/o additional logs. Did you happen to file feedback?

If not, do you recall what adapter (USBC->?) and external display you were using?

Looks like last 63 update was 
  2018-01-08 platform:10032.86.0 

and the first 64 update
  2018-02-13 platform:10176.72.0

https://crosland.corp.google.com/log/10032.86.0..10176.72.0

That diff did contain a FW update (two actually)

https://chrome-internal-review.googlesource.com/c/chromeos/overlays/overlay-caroline-private/+/524158
https://chrome-internal-review.googlesource.com/c/chromeos/overlays/overlay-caroline-private/+/537998

Probably the first place to start looking if we suspect something on the EC side.


Status: WontFix (was: Unconfirmed)
Closing given
- there's no logs from original failure
- can't I repro in quick test here FW:7820.384.0 PLAT:R72-11219.0.0
  - hoho + Dell U2410, both ports, both polarities work.

Please re-open if its still failing, file feedback and reference this bug ( crbug.com/818825 )

Sign in to add a comment