New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 834282 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

CFM displays white screen unit second display connected.

Reported by craig.pe...@amada.co.uk, Apr 18 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
Platform: 10176.76.0 (Official Build) stable-channel guado

Steps to reproduce the problem:
Boot CFM without a second display connected. 

What is the expected behavior?
Ideally, some message saying connect or turn on the display.

What went wrong?
White screen after the Meet App loads. 

Did this work before? No 

Chrome version: 64.0.3282.190  Channel: stable
OS Version: 
Flash Version: 

Enhancement request.
 
This issue occurs when the primary(HDMI) display is connected but turned off while the secondary is turned on. 

We currently have this issue with the new Google meet hardware with the touch screen controls.

If the TV is off when the Meet hardware reboots, the touchscreen goes all white until you turn on the TV.

Comment 2 by zork@chromium.org, Apr 20 2018

Components: -UI UI>Shell>MultipleMonitor
Cc: afakhry@chromium.org osh...@chromium.org
Owner: weidongg@chromium.org
Status: Assigned (was: Unconfirmed)
Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!
This is still an issue. It's not a very good user experience. We had two separate offices have this issue, I assume other customers will too. We had to call support, support even got us to reinstall the OS before we realised.  
Cc: weidongg@chromium.org
Owner: dbehr@chromium.org
dbehr@ can you please triage this?
Labels: -Pri-2 Pri-1
Raising priority due to level of customer impact.
Status: Archived (was: Assigned)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.

You can close this if you can't be bothered. It doesn't affect us anymore only your new customers.
Cc: dbehr@chromium.org marc...@chromium.org
Owner: mnilsson@google.com
Status: Unconfirmed (was: Archived)
mnilsson@ can you please triage this issue and confirm what the issue exactly is from the CFM side of things?
Status: Assigned (was: Unconfirmed)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment